I'm not sure what's going on with my device or how to fix it so I'm hoping someone here may be able to assist.
I just got my Moto X from AT&T. It came with Android 4.2.2 and immediately upon starting it up asked me if I wanted to software update to which I responded no. I then used this guide (http://forum.xda-developers.com/showthread.php?p=45598679) to root the device with the PwnMyMoto. I installed the APK and the device was then rooted. I restarted the phone and upon reboot I was asked again to update the software.
This time I did update the software and the device proceeded to turn off, restart, and do this over and over. It would continue to turn itself back on for somewhat of 20 seconds before saying "Powering Off..." and then restart again. I tried using the RSD Lite method to flash the stock firmware back on the device but RSD Lite wouldn't recognize it, even with USB debugging on and the phone in bootload mode.
I could really use all the help I can get. It's completely stuck and I have no idea how to recover it from this state.
Konvett said:
I'm not sure what's going on with my device or how to fix it so I'm hoping someone here may be able to assist.
I just got my Moto X from AT&T. It came with Android 4.2.2 and immediately upon starting it up asked me if I wanted to software update to which I responded no. I then used this guide (http://forum.xda-developers.com/showthread.php?p=45598679) to root the device with the PwnMyMoto. I installed the APK and the device was then rooted. I restarted the phone and upon reboot I was asked again to update the software.
This time I did update the software and the device proceeded to turn off, restart, and do this over and over. It would continue to turn itself back on for somewhat of 20 seconds before saying "Powering Off..." and then restart again. I tried using the RSD Lite method to flash the stock firmware back on the device but RSD Lite wouldn't recognize it, even with USB debugging on and the phone in bootload mode.
I could really use all the help I can get. It's completely stuck and I have no idea how to recover it from this state.
Click to expand...
Click to collapse
Try fastboot erase cache first, you can not flash the ota while having any form of a custom recovery
Sent on my Moto X
flashallthetime said:
Try fastboot erase cache first, you can not flash the ota while having any form of a custom recovery
Sent on my Moto X
Click to expand...
Click to collapse
Anything I try to do in fastboot menu results in the phone restarting. If I select any of the options, it just starts the phone up and goes through this process all over again.
flashallthetime said:
Try fastboot erase cache first, you can not flash the ota while having any form of a custom recovery
Ops might be to late, now that I see it did flash it.
Make sure your phone is recognized first through fastboot, then open redlite and you should see its connected. If still no connection make sure you have all the current Motorola drivers
Sent on my Moto X
Click to expand...
Click to collapse
Really, do you have all the current Motorola drivers
Sent on my Moto X
I'm not really sure on what you're saying to do now.
Konvett said:
I'm not really sure on what you're saying to do now.
Click to expand...
Click to collapse
Make sure all Motorola drivers are up to date , I believe its Motorola device manager, otherwise rsdlite will not recognize your phone
Also your phone needs to be in fastboot mode, hopefully it won't reboot during the process
Sent on my Moto X
I've made sure the drivers are correct. RSDLite still won't recognize the device.
Konvett said:
I've made sure the drivers are correct. RSDLite still won't recognize the device.
Click to expand...
Click to collapse
What version of windows are you running
Sent on my Moto X
flashallthetime said:
What version of windows are you running
Sent on my Moto X
Click to expand...
Click to collapse
Windows 8
Konvett said:
Windows 8
Click to expand...
Click to collapse
That's probably the issue, try to run rsdlite under windows 7 comp. Its either that or a driver issue, leave it to windows 8, did you find the thread with the instructions to use rsdlite?
Sent on my Moto X
What keys are you hitting by chance when you get into fastboot? I had the same problem with mine while trying to root it and get software updated on it, but mine is a developer edition so I had some options.
I would try this first.
1. Turn phone completely off (you will have to have the phone unplugged from the wall outlet and/or computer when you do this) by beating the bootloop and powering it off manually.
2. Hold both the volume up and volume down and power button at the same time for 4 seconds and let go of all of them.
3. This should bring you to fastboot
4. Plug the phone up to your computer and open a command prompt
5. In the command prompt type in fastboot erase cache
6. Hit enter and it should show on the phone that your deleting the cache partition.
7. After its complete use the volume down key to go to Normal Power Up or Normal Boot (I can't remember what exactly the option is)
8. Hit the volume up key to select it and it will start booting back in Android.
Let the phone sit for a few seconds and see if it restarts anymore. If it does then your only option to stop it is to either erase user data or RSDLite it back to factory. You can erase the userdata by doing this.
1. Power off the phone
2. Hit the volume down and volume up and power button for 4 seconds and then let go
3. While the phone is in fastboot open up a command prompt on your computer and hook up the phone by USB to your computer
4. In the command prompt type in fastboot erase userdata
5. Hit enter
6. After it completes type in fastboot erase cache
7. Hit enter
8. Use the volume down key to select Normal Powerup or Normal Boot and hit the volume up key
9. That should get you back to android and let you set it back up. After that I would no longer take an OTA update unless you removed root.
flashallthetime said:
that's probably the issue, try to run rsdlite under windows 7 comp. Its either that or a driver issue, leave it to windows 8, did you find the thread with the instructions to use rsdlite?
Sent on my moto x
Click to expand...
Click to collapse
thank you flashallthetime!!!!! **** you windows 8!!!!!!!
Konvett said:
thank you flashallthetime!!!!! **** you windows 8!!!!!!!
Click to expand...
Click to collapse
So did it work?
Sent on my Moto X
supr2nr said:
What keys are you hitting by chance when you get into fastboot? I had the same problem with mine while trying to root it and get software updated on it, but mine is a developer edition so I had some options.
I would try this first.
1. Turn phone completely off (you will have to have the phone unplugged from the wall outlet and/or computer when you do this) by beating the bootloop and powering it off manually.
2. Hold both the volume up and volume down and power button at the same time for 4 seconds and let go of all of them.
3. This should bring you to fastboot
4. Plug the phone up to your computer and open a command prompt
5. In the command prompt type in fastboot erase cache
6. Hit enter and it should show on the phone that your deleting the cache partition.
7. After its complete use the volume down key to go to Normal Power Up or Normal Boot (I can't remember what exactly the option is)
8. Hit the volume up key to select it and it will start booting back in Android.
Let the phone sit for a few seconds and see if it restarts anymore. If it does then your only option to stop it is to either erase user data or RSDLite it back to factory. You can erase the userdata by doing this.
1. Power off the phone
2. Hit the volume down and volume up and power button for 4 seconds and then let go
3. While the phone is in fastboot open up a command prompt on your computer and hook up the phone by USB to your computer
4. In the command prompt type in fastboot erase userdata
5. Hit enter
6. After it completes type in fastboot erase cache
7. Hit enter
8. Use the volume down key to select Normal Powerup or Normal Boot and hit the volume up key
9. That should get you back to android and let you set it back up. After that I would no longer take an OTA update unless you removed root.
Click to expand...
Click to collapse
Thank you for the help, I was able to get RSD Lite to recognize the device. I'm restarting it now in the hopes that it will successfully have flashed the stock ROM. I now don't really know what to do about rooting/unlocking the bootloader. Any ideas? Not sure if it's possible for the AT&T version due to all their stupid restrictions.
Konvett said:
Thank you for the help, I was able to get RSD Lite to recognize the device. I'm restarting it now in the hopes that it will successfully have flashed the stock ROM. I now don't really know what to do about rooting/unlocking the bootloader. Any ideas? Not sure if it's possible for the AT&T version due to all their stupid restrictions.
Click to expand...
Click to collapse
You can't unlock with AT& idiot
If its a retail version, you have to go back to 4.2 I believe and use rockmymoto do the upgrade and use slapmymoto, not sure as my boot loader is unlocked. I used the easy way to root
Sent on my Moto X
flashallthetime said:
You can't unlock with AT& idiot
If its a retail version, you have to go back to 4.2 I believe and use rockmymoto do the upgrade and use slapmymoto, not sure as my boot loader is unlocked. I used the easy way to root
Sent on my Moto X
Click to expand...
Click to collapse
This one is currently on 4.2.2. I should be able to go right from there right?
Konvett said:
This one is currently on 4.2.2. I should be able to go right from there right?
Click to expand...
Click to collapse
I believe so but read the slapmymoto thread, so I guess it booted
Sent on my Moto X
I think I'm asking the wrong questions.
With my Moto X (AT&T - NOT developer edition) on 4.2.2, I'd like to install CyanogenMod. Of course the bootloader is locked, but I'm not presently aware if it has been cracked. I don't want to install TWRP and risk bricking it if it's not going to work.
Has the bootloader been cracked yet?
Konvett said:
I think I'm asking the wrong questions.
With my Moto X (AT&T - NOT developer edition) on 4.2.2, I'd like to install CyanogenMod. Of course the bootloader is locked, but I'm not presently aware if it has been cracked. I don't want to install TWRP and risk bricking it if it's not going to work.
Has the bootloader been cracked yet?
Click to expand...
Click to collapse
No, your boot loader will likely never be unlocked, as for cm Roms , again not at this point in time. The only way for locked boot loaders to flash Roms is with safestrap and that requires a safestrap compatible kernel. To make you feel better, you can get all the customizations that cm has with xposed frameworks and a few modules on our stock ROM. So there's really no reason for cm roms
Sent on my Moto X
flashallthetime said:
No, your boot loader will likely never be unlocked, as for cm Roms , again not at this point in time. The only way for locked boot loaders to flash Roms is with safestrap and that requires a safestrap compatible kernel. To make you feel better, you can get all the customizations that cm has with xposed frameworks and a few modules on our stock ROM. So there's really no reason for cm roms
Sent on my Moto X
Click to expand...
Click to collapse
I'll check into xposed, thank you!
Related
Hey guys
i just wiped all my data and tried to reboot my nexus, but now it's been stuck on the google logo for ages...
trying to flash to stock + unroot with nexus toolkit doesn't work, any way to unbrick it?
please help...
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
badboy47 said:
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
Click to expand...
Click to collapse
works
thank you very much
fabian.m said:
works
thank you very much
Click to expand...
Click to collapse
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
luiseteyo said:
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
Click to expand...
Click to collapse
well.. technically thanking isn't in the rules.
exb0 said:
well.. technically thanking isn't in the rules.
Click to expand...
Click to collapse
It is in the good behaviour and politeness rules. Not everything is written.
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Qbsti said:
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Click to expand...
Click to collapse
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
simms22 said:
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
Click to expand...
Click to collapse
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Qbsti said:
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Click to expand...
Click to collapse
not booting after flashing something or modding something is the easiest of all to fix, just reflash the rom(gapps and kernel too if need be), no need to wipe anything. since i test all the trinity kernels before any get released, and pre-kernels, i get many that dont boot my device or bootloop(among some other funky behaviors), reflashing a good kernel always works
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Qbsti said:
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Click to expand...
Click to collapse
Try another rom. You might have downloaded corrupted zips. Also, make sure you flash the things you need first. Eg, flash rom and gapps. Don't restore anything if you're using titanium backup. Try restarting the phone, see if it gets into a bootloop. If it doesn't, then try restoring apps from TB. (if you use TB.)
Hi!
I´ve got a big problem. Today i flashed the new PA version, but it seems that the download had some issue. I could install it but after a while, I wanted to reboot the phone and it got stuck at the Google logo. I can only access fastboot mode and recovery.
So the problem is, i made a full wipe, so i have no rom on the sdcard anymore. Also I am now able to enable the debbuging mode. I tried every toolkit i couzld find, but everyone needs debugging mode enabled. windows doesnt recognize the phone ( it says unkown device). So i tried to install the adb drivers, but nothing happens.
i wanted to try to push a rom with adb on the phone but it says no device found. i am such a noob, i hope some can help me.
thx
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.
gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:
Didn't work Will try other method
Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Two options:
1. Flash a custom recovery using "fastboot flash recovery recovery.img", then boot into it and flash a ROM
2. Download the stock android images from the Google dev site and flash them using fastboot
nikonjunkie said:
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Click to expand...
Click to collapse
Download the 4.3 image HERE
Then, plug in your phone into your computer, boot into fastboot mode, extract the zip and run the flash-all.bat file (Or the .sh if your on a *nix/OSX computer). This will flash 4.3. If you don't want to loose your data, delete the userdata.img in the zip file before running the .bat/.sh file. Wipe cache in recovery, and it should boot.
Go into fastboot and download the stock image from Google.
Run the batch file it comes with and bam, you should be good to go
Sent from my Nexus 4 using xda app-developers app
nikonjunkie said:
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Click to expand...
Click to collapse
Once you see the Android laying on its back with a red triangle, press and hold power button and then press volume up once. That'll take you to the recovery options. At this point you must decide if you want to wipe data/factory reset (which will let you go past the X logo) because that'll wipe your device, all your data will be gone.
lopezk38 said:
Download the 4.3 image HERE
Then, plug in your phone into your computer, boot into fastboot mode, extract the zip and run the flash-all.bat file (Or the .sh if your on a *nix/OSX computer). This will flash 4.3. If you don't want to loose your data, delete the userdata.img in the zip file before running the .bat/.sh file. Wipe cache in recovery, and it should boot.
Click to expand...
Click to collapse
Do I need ADB installed? Have never needed it for any reason on this computer
The flash-all.bat file is giving me the error "fastboot is not recognized as an internal or external command" (am on Win 8)
Not sure if it's relevant, but I don't believe I have USB debugging enabled right now. It is 99% of the time, but of course right now I'm almost sure it's not. Am I screwed? My phone isn't showing up as a drive on my computer like it normally would. Thanks in advance!
nikonjunkie said:
Do I need ADB installed? Have never needed it for any reason on this computer
The flash-all.bat file is giving me the error "fastboot is not recognized as an internal or external command" (am on Win 8)
Not sure if it's relevant, but I don't believe I have USB debugging enabled right now. It is 99% of the time, but of course right now I'm almost sure it's not. Am I screwed? My phone isn't showing up as a drive on my computer like it normally would.
Click to expand...
Click to collapse
Yeah, you need fastboot.exe. I attached a copy from my Windows partition. Download it, extract it, and put the fastboot.exe in the same folder that you have the flash-all.bat
lopezk38 said:
Yeah, you need fastboot.exe. I attached a copy from my Windows partition. Download it, extract it, and put the fastboot.exe in the same folder that you have the flash-all.bat
Click to expand...
Click to collapse
Thanks. I downloaded the file from your link, extracted it, moved to the same folder I have the BAT file. Ran the BAT file, got this error:
The program can't start becayse AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
nikonjunkie said:
Thanks. I downloaded the file from your link, extracted it, moved to the same folder I have the BAT file. Ran the BAT file, got this error:
The program can't start becayse AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
Click to expand...
Click to collapse
Same thing that you did with the fastboot.zip with the attached ADB.zip
lopezk38 said:
Same thing that you did with the fastboot.zip with the attached ADB.zip
Click to expand...
Click to collapse
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
nikonjunkie said:
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
Click to expand...
Click to collapse
Your welcome
nikonjunkie said:
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
Click to expand...
Click to collapse
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
nikonjunkie said:
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
Click to expand...
Click to collapse
I have the similar problem here - OTA 4.3 finished ok, but I've lost my root. When I try to boot into recovery, I got "No command" (probably in english, it's in fact translated) and Android laying with open belly.
After rebooting, system itself works as normal.
Thanks for any help.
nikonjunkie said:
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
Click to expand...
Click to collapse
That's the stock recovery, press and hold power and then press volume up to get the stock menu
EddyOS said:
That's the stock recovery, press and hold power and then press volume up to get the stock menu
Click to expand...
Click to collapse
The open Android belly is *supposed* to show up? Wow, then I guess I've had a custom recovery so long I can't recall ever seeing this.
If I do that sequence, then I get the options:
- reboot system now
- apply update from ADB
- wipe data/factory reset
- wipe cash partition
If this is the stock recovery, then how do I go about getting a custom recovery on here? So far have been unsuccessful with sideloading anything via the toolkits. I'm now on 4.3, unrooted, but unlocked bootloader. I guess I was expecting the menu that permits you to flash a zip on the phone FROM the phone.
Thanks!
nikonjunkie said:
The open Android belly is *supposed* to show up? Wow, then I guess I've had a custom recovery so long I can't recall ever seeing this.
If I do that sequence, then I get the options:
- reboot system now
- apply update from ADB
- wipe data/factory reset
- wipe cash partition
If this is the stock recovery, then how do I go about getting a custom recovery on here? So far have been unsuccessful with sideloading anything via the toolkits. I'm now on 4.3, unrooted, but unlocked bootloader. I guess I was expecting the menu that permits you to flash a zip on the phone FROM the phone.
Thanks!
Click to expand...
Click to collapse
Download the latest TWRP version for Mako. Boot to bootloader. Open a CMD window and type:
fastboot flash recovery yourrecoveryname.img
Mercado_Negro said:
Download the latest TWRP version for Mako. Boot to bootloader. Open a CMD window and type:
fastboot flash recovery yourrecoveryname.img
Click to expand...
Click to collapse
J*sus C******. Now I can't even get the phone to be recognized as an ADB device. What happened since last night, I have no idea. The toolkits don't help, by any method. Have rebooted computer, phone, unchecked and rechecked USB debugging about a zillion times, uninstalled and reinstalled drivers. It's like the phone is invisible. Four more hours, and I am throwing this Nexus off the 23rd floor balcony.
Thanks, though!
nikonjunkie said:
J*sus C******. Now I can't even get the phone to be recognized as an ADB device. What happened since last night, I have no idea. The toolkits don't help, by any method. Have rebooted computer, phone, unchecked and rechecked USB debugging about a zillion times, uninstalled and reinstalled drivers. It's like the phone is invisible. Four more hours, and I am throwing this Nexus off the 23rd floor balcony.
Thanks, though!
Click to expand...
Click to collapse
When you connect your device via USB, does the computer recognize it and open up a window where you can see your files/folders?
Mercado_Negro said:
When you connect your device via USB, does the computer recognize it and open up a window where you can see your files/folders?
Click to expand...
Click to collapse
Sometimes it does, sometimes it doesn't. I can't figure out the inconsistency. Same things are checked. I've changed USB ports (tried all three), tried a new cable, quadruple-checked the settings. Rebooted the phone and the computer, and still it's inconsistent. I can hear the little chime on the computer indicating it's recognizing the device, but only half the time does it open the folder to view files. The other half of the time, the phone doesn't show up as a drive under My Computer at all--even after a refresh.
In a strange new dvelopment, in Wug's Nexus Root Toolkit, the phone is recognized in bootloader mode, but nothing on this green earth can make it show up as an ADB device when powered up and booted into Android. I've tried going at it from every angle. Didn't have this problem last night. Other than setting up email and moving icons around, I didn't do much to it, so I'm mystified and annoyed.
Thanks for any ideas.
Yeah, that's happened here as well. Sometimes I have to unplug and plug it back in to make it show folders and files. It's inconsistent as you say (though to be honest, I can't remember if it's happened again since I flashed 4.3 a week ago). Anyways, you say that adb can't see it when you type "adb devices", right? If you turn off your device (unplugged), then press and hold power and volume down buttons for a few seconds to go to Bootloader and then plug it back in, can you run any adb command? Like push, pull, etc.? That would rule out any faulty file in your platform-tools folder (where fastboot.exe is).
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.
I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app
Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.
Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.
Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.
Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?