So I've been trying to install Plasma Active on my Nexus 7. I followed the PA wiki and everything was going well. I got MOSLO installed, and then extracted the PA tarball and then rebooted. It didn't boot into PA, but the wiki mentioned that it might not. So it has a section describing some commands to run in fastboot to get it to boot PA at this point.
The problem is that after I installed MOSLO and extracted PA, I can no longer see the Nexus 7 with fastboot. When I run "fastboot devices" or "adb devices" nothing shows up.
Any one have any thoughts on what might be going on?
Thanks for your help!
Your N7 is in bootloader mode and all PC drivers are installed correct?
Sent from my Nexus 7 using xda app-developers app
BlackFire27 said:
Your N7 is in bootloader mode and all PC drivers are installed correct?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Correct. Fastboot worked fine when I unlocked the N7, and then when I installed moslo. But after installing PA, fastboot no longer sees the N7.
arbulus said:
Correct. Fastboot worked fine when I unlocked the N7, and then when I installed moslo. But after installing PA, fastboot no longer sees the N7.
Click to expand...
Click to collapse
What exactly is moslo? It may have interfered with the bootloader.
Sent from my SPH-M830 using xda app-developers app
BlackFire27 said:
What exactly is moslo? It may have interfered with the bootloader.
Sent from my SPH-M830 using xda app-developers app
Click to expand...
Click to collapse
The wiki isn't totally clear on what part MOSLO plays.
I would link you to the wiki that I followed, but the forum is preventing me from putting urls in my post.
Does it do ANYTHING? Hopefully it isn't in nvedit mod.
ADB is only good when you have the phone booted up and USB Debugging turned on.
Fastboot commands only work when the device is in bootloader mode.
If your phone is past bootloader mode, but getting stuck in a bootloop or something, then ADB will be unavailable too.
Try Turning the phone off completely, holding VOLUME DOWN + UP + POWER until it boots into the Bootloader. Then Connect it up to the PC and run your fastboot commands.
Can you get into any form of custom recovery? If so you have a few options that could help.
Sent from my SPH-M830 using xda app-developers app
player911 said:
Does it do ANYTHING? Hopefully it isn't in nvedit mod.
ADB is only good when you have the phone booted up and USB Debugging turned on.
Fastboot commands only work when the device is in bootloader mode.
If your phone is past bootloader mode, but getting stuck in a bootloop or something, then ADB will be unavailable too.
Try Turning the phone off completely, holding VOLUME DOWN + UP + POWER until it boots into the Bootloader. Then Connect it up to the PC and run your fastboot commands.
Click to expand...
Click to collapse
If I hold power and volume down, I can boot into the bootloader. same if I hold power and both volume keys. That's what gives me fastboot access (or would normally).
I can do that. And I can boot into the MOSLO. But I cannot get into Plasma Active. One of the last errors that I can see before MOSLO reboots is "no rootfs found. ignoring."
When I first started, I could hold power and volume down to get into the bootloader, and my computer could see it from fastboot. That is how I unlocked the bootloader and flashed the MOSLO. But once I installed Plasma Active, I couldn't see the device in fastboot anymore. And instead of booting into Plasma Active, it just shows the dead android on its back with the red triangle exclamation point.
Since the xda forum won't let me post links, if you google "install plasma active on nexus 7", the second option is the wiki for the project I'm following.
rtsati the
BlackFire27 said:
Can you get into any form of custom recovery? If so you have a few options that could help.
Sent from my SPH-M830 using xda app-developers app
Click to expand...
Click to collapse
No. If I'm in the bootloader and tell it to reboot into "recovery mode", it just shows me the dead android with the red triangle exclamation point. I imagine that is because android is no longer on the device. Which is what I want. I'm trying to put a new OS on here. Though I don't suppose that helps much.
arbulus said:
No. If I'm in the bootloader and tell it to reboot into "recovery mode", it just shows me the dead android with the red triangle exclamation point. I imagine that is because android is no longer on the device. Which is what I want. I'm trying to put a new OS on here. Though I don't suppose that helps much.
Click to expand...
Click to collapse
Android with red triangle and exclamation mark means you don't have a custom recovery installed.
No fastboot and no custom recovery...does MOSLO have any form of options?
Sent from my SPH-M830 using xda app-developers app
So does this replace android completely or does it dual boot?
Sent from my HTC One using xda premium
---------- Post added at 11:46 AM ---------- Previous post was at 11:29 AM ----------
Did a little research and there is a dual boot option, you just use the dual boot tool and flash a zip and you have plasma active as a ROM.
Sent from my HTC One using xda premium
spitfire2425 said:
So does this replace android completely or does it dual boot?
Sent from my HTC One using xda premium
---------- Post added at 11:46 AM ---------- Previous post was at 11:29 AM ----------
Did a little research and there is a dual boot option, you just use the dual boot tool and flash a zip and you have plasma active as a ROM.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, there's the dual boot option. Though I chose to go with the single OS option. In that case, it does repalce Android completely.
Related
I have a rooted nexus one running cm7.2 and it won't boot to boot loader or recovery or rom o
Sent from my SGH-T959 using xda app-developers app
Or fast boot so I can't do anything am I bricked
Sent from my SGH-T959 using xda app-developers app
Try to use passimg.zip method. Google it download that zip put it in or main SD. Hold trackball + power button. Good luck
Sent from my Nexus One using Tapatalk 2
I can't get to fadtboot or boot loader so I cantbdo passimage
Sent from my SGH-T959 using xda app-developers app
n1noob13 said:
I can't get to fadtboot or boot loader so I cantbdo passimage
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Do you have ADB and fastboot software installed in your PC? Either have that or download Android SDK. You can boot your phone via ADB command lines.
Yes I have it but nothing will work the charging lightbwont lightvwont light up orbanything
Sent from my SGH-T959 using xda app-developers app
Your phone needs a JTAG repair.
Sent from my Nexus One using xda app-developers app
humzaahmed155 said:
Your phone needs a JTAG repair.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
what is mean?
Search.
hi
humzaahmed155 said:
Your phone needs a JTAG repair.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Hi. my N1 is totally dead(i think) wont boot still showing X logo and lock. I tried everything. When using Nexus 7 toolkit, toolkit say device found (showing serial number). But when i try flash using adb command everytime i get message device not found. What is problem, what is wrong?
Thanks
bagi576 said:
Hi. my N1 is totally dead(i think) wont boot still showing X logo and lock. I tried everything. When using Nexus 7 toolkit, toolkit say device found (showing serial number). But when i try flash using adb command everytime i get message device not found. What is problem, what is wrong?
Thanks
Click to expand...
Click to collapse
Can you reach the boot menu by pressing the volume down key while powering on?
Otherwise, try to check if fastboot is able to see your device and flash some new boot and system image
You have a Nexus One, not sure why you're using the Nexus 7 Toolkit..
hi
tommert38 said:
You have a Nexus One, not sure why you're using the Nexus 7 Toolkit..
Click to expand...
Click to collapse
Hi, only Nexus 7 Toolkit shows device is connected. adb mode not responding. i've just tried N7 Toolkit
---------- Post added at 10:54 PM ---------- Previous post was at 10:45 PM ----------
efxbug said:
Can you reach the boot menu by pressing the volume down key while powering on?
Otherwise, try to check if fastboot is able to see your device and flash some new boot and system image
Click to expand...
Click to collapse
Thank you for asking. able to enter boot menu and fastboot menu. but cant flash anything, i'll tried new boot new system img's. Nothing. When connecting to PC fastboot showing Fastboot USB mode is enabled. unable to do nothing via adb mode. adb mode say error device not found.
Thanks for answer
Are drivers installed? And have you installed adb and fastboot correctly?
tommert38 said:
Are drivers installed? And have you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes, installed correct. it show up in the Device Manager list.
Anyway, i go to try this driver. Thanks. Let me know u
hmm. unlucky. Still nothing. Windows take a signal when connecting phone shows on fastboot menu => fastboot usb and adb mode say error device not found:crying:
i scanned my drivers using driver genius v11, i saw android driver named Samsung_Android_4.0_usbdrivers. now i think its something wrong with my boot.img?
When you see fastboot usb, and you type fastboot devices in a terminal, what does it say? ADB only works in recovery or when your ROM is booted, so just focus on fastboot.
it say when N1 is fastboot usb mode "error device not found". thanks for advance. tomorrow i'll be ask more.
Sent from my YP-G70 using xda app-developers app
Hey guys. Finally my N1 detected in adb mode. Im used Nexus 7 toolkit, downloaded N1 official Rom (i used only boot.img from zip file)
1st ive installed toolkit, then flashed boot.img (from official rom) to /system/ folder. Finally Windows device manager say detected new device and downloading drivers.
Started cmd.exe typed adb shell => adb mode showed HT9**********. Now problem is wont boot. What i do now? :silly:
i hope u can enter fastboot usb mode. if so try flashing any recovery.img
Sent from my Nexus One using Tapatalk
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the boot loader but I've never done anything with adb or fastboot or anything like that so hopefully there is a way to fix it with this?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
http://forum.xda-developers.com/showthread.php?p=41076144
Download the mini sdk file from that post. Use the instructions there to access fastboot. Then use the command "fastboot erase cache"
Should fix your recovery issue and then reflash the Android Revolution ROM.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
http://forum.xda-developers.com/showthread.php?p=41076144
Download the mini sdk file from that post. Use the instructions there to access fastboot. Then use the command "fastboot erase cache"
Should fix your recovery issue and then reflash the Android Revolution ROM.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks man you're awesome. It worked.
I just tried to flash 2nd booltloader and tarp recovery on my 7". I went to reboot into recovery one got a Bootloop. It flashes kindlefire for 5 seconds and then goes black for 5 seconds and on and on for about a minute and then shuts down. When I try fastboot my computers hang at and adb says no device. I searched the forum and googled and found nothing so I'm sorry if I missed the answer somewhere. I do have the drivers installed on my computer. I appreciate any help or advice
Sent from my LG-E970 using xda app-developers app
popshovit said:
I just tried to flash 2nd booltloader and tarp recovery on my 7". I went to reboot into recovery one got a Bootloop. It flashes kindlefire for 5 seconds and then goes black for 5 seconds and on and on for about a minute and then shuts down. When I try fastboot my computers hang at and adb says no device. I searched the forum and googled and found nothing so I'm sorry if I missed the answer somewhere. I do have the drivers installed on my computer. I appreciate any help or advice
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Im haveing the same problem
Yeah I tried everything I know of so hopefully someone has a trick. I'm thinking about sending it for warranty but if they see it was rooted then I might be sol.
Sent from my LG-E970 using xda app-developers app
You say you got in in fast boot or that you were trying to from adb? Because if your trying to get it in fast boot your going to need a factory cable. From there once its in fast boot you plug it back in to your PC with the normal cable and run fastboot.exe -i 0x1949 getvar product
That should return Tate something. If that happens you should be able to fix it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I can't even get it in fastboot. I have the cable that it came with. maybe I'm nit doing something right. How should I do it with the factory cable. So far I've tried adb = device not found and fastboot = waiting for device
Sent from my LG-E970 using xda app-developers app
popshovit said:
I can't even get it in fastboot. I have the cable that it came with. maybe I'm nit doing something right. How should I do it with the factory cable. So far I've tried adb = device not found and fastboot = waiting for device
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
A factory cable puts kfhd7 in fast boot automatically, not the cable that comes with device,search eBay for Motorola factory cable around 4 euros
Thank you. I'll give this a try
Sent from my LG-E970 using xda app-developers app
fixed
So i ordered the factory which put it right into fastboot. downloaded kfhdsrt, restored system,boot,recovery and it booted up and is running great. thanks for the help. it as fixed within a half hour from when i got the factory cable in the mail :good:
Anyone can help me? It cant boot-up & just stuck here.
Sent from my C6603 using xda premium
Did you tried the rsdlite?
You can try going stock by using the same tool.
The root and flash your favorite ROM again and you should be set
Sent from my MB886 using XDA Premium 4 mobile app
You should unlock your boot loader first.
Sent from my MB886 using Tapatalk 4
download myth tools
myth tools link http://forum.xda-developers.com/showthread.php?t=2262726
just use unlock bootloader method
cwm touch recovery needed to flash custom roms http://forum.xda-developers.com/showthread.php?t=2421418
name file cwm.img
posh adb needed to flash recovery http://forum.xda-developers.com/showthread.php?t=2248920
pac-man rom http://forum.xda-developers.com/showthread.php?t=2266322
scroll all the way down and download the last .zip file you see
I DO NOT TAKE RESPONSIBILITY IF YOU BRICK YOUR DEVICE happy modding:]
---------- Post added at 06:33 PM ---------- Previous post was at 06:30 PM ----------
is it just me or have i been seeing this problem alot here lately
Plug it in to your PC and perform a "Fastboot reboot" command in command prompt. If it loops back into Bootloader again, then you're gonna have to tell us what you did. If you tried to flash a custom recovery or use RSD Lite with a locked bootloader (like you have in your picture) then I'm afraid there is nothing you can do. You could try using mythtools to unlock bootloader while you're in fastboot (the screen you're stuck on now), but I'm not sure if it's possible...
Edit: Just realized it says "Security version downgraded" near the bottom. You tried to RSD Lite with a locked bootloader. I think you're hard bricked if MythTools can't work its magic
Neightbor08 is correct I assume. But in theory it will NOT do anything from that screen as it is on error.
He need to go to a fresh fastboot mode by pressing Power + Both Volume buttons until the phone reboot back again into Fastboot mode.
Once there he can try to unlock the bootloader again when is done you should see Device Unlock Code 3
Good luck!!
Sent from my MB886 using XDA Premium 4 mobile app
I have a unlocked X, was trying to install a new rom via recovery and something went wrong...but I forgot to do backup so now its on a boot loop and I didnt have USB debugging enabled. Is there anyway to load new another rom to the phone so that I can install via recovery since I dont have usb enabled?
Yes power the device off by holding the power button and volume down, after the display is off let go of the power button. You can flash recovery or boot to recovery from there
Sent from my Nexus 6 using Tapatalk
Durteedee said:
Yes power the device off by holding the power button and volume down, after the display is off let go of the power button. You can flash recovery or boot to recovery from there
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I can boot into recovery but how do I transfer the new rom to the phone so I can install via recovery? I dont know how to move it from my PC to the phone.
You should look up side loading via adb and most newer recoveries allow you drag and drop once it's booted, you are using a custom recovery for your phone correct?
Sent from my Nexus 6 using Tapatalk
Durteedee said:
You should look up side loading via adb and most newer recoveries allow you drag and drop once it's booted, you are using a custom recovery for your phone correct?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
yes team win recovery v2.6.3.1
In advance you will find sideload via adb, I am sure you have fastboot/adb commands on your PC as well an understanding of how sideloading works
Sent from my Nexus 6 using Tapatalk
when I go into terminal, type abd devices, I dont see any attached...dont I need usb debugging on to be able to see device?
mario24601 said:
when I go into terminal, type abd devices, I dont see any attached...dont I need usb debugging on to be able to see device?
Click to expand...
Click to collapse
dont use adb use fastboot.
"fastboot devices"
wildblade64 said:
dont use adb use fastboot.
"fastboot devices"
Click to expand...
Click to collapse
thanks but its still not connecting....not sure what im doing wrong.
Also trying a otg cable but phone is not recognizing it. Any suggestions? Thanks
Sent from my ONE E1005 using Tapatalk
Since I didn't have USB debugging on when it went into boot loop, am I screwed or how can I move a new rom over? I do have win recovery I am able to boot to recovery but can't figure out how to load new rom. Any help would be appreciated. Thanks
Sent from my ONE E1005 using Tapatalk
Might have to start from scratch....flash the latest 5.1 firmware again....and bootloader if you haven't done so yet.
[quote name="DJ_Tomato" post=65476125]Hello
I am receiving phone calls, and when i answer they can't hear me and i can't hear them
So buggy, can't work with it, i have lost important calls, please help me[/QUOTE]
Had the same issue, fixed it by updating the bootloader.
I followed option 5 on this link.
http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2
You will need to find the correct files for your phone varient from here.
http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
NOTE:-
Sent from my ghost using Tapatalk
---------- Post added at 11:58 PM ---------- Previous post was at 11:54 PM ----------
First link, option 5. Had a similar problem where I can go to recovery but my internal was deleted...I had nothing. Nor did I have a system.....I couldn't restore a backup nor flash a new ROM. I had nothing but recovery....so I googled the 5.1 firmware update and modem....and followed option 5 with mfastboot. Phone is up and running fine.
Sent from my ghost using Tapatalk
mario24601 said:
Since I didn't have USB debugging on when it went into boot loop, am I screwed or how can I move a new rom over? I do have win recovery I am able to boot to recovery but can't figure out how to load new rom. Any help would be appreciated. Thanks
Sent from my ONE E1005 using Tapatalk
Click to expand...
Click to collapse
Anyone have any recommendations? thanks
Finally got it working, took ALOT of trial and error! If anyone has same issue I can give step by step...not that Im good at this stuff but I can share what I learned