I have a rooted sprint moto x that was running cm 12.1 and I used a toolkit to try and restore it to stock and ended up deleting the os and twrp recovery. I managed to flash the recovery back onto the phone using adb commands, however my PC doesn't recognize my moto as a USB storage device so I am unable to move the rom zip file to the phone. I tried flashing in fastboot and also adb push to push the file to the phone however nothing works..... If anyone could help me I'd greatly appreciate it
Shadowblade19 said:
I have a rooted sprint moto x that was running cm 12.1 and I used a toolkit to try and restore it to stock and ended up deleting the os and twrp recovery. I managed to flash the recovery back onto the phone using adb commands, however my PC doesn't recognize my moto as a USB storage device so I am unable to move the rom zip file to the phone. I tried flashing in fastboot and also adb push to push the file to the phone however nothing works..... If anyone could help me I'd greatly appreciate it
Click to expand...
Click to collapse
When you get into bootloader mode, are you using fastboot or mfastboot to flash system? If your system image is a single file instead of sparse chunks, you need to use mfastboot.
JulesJam said:
When you get into bootloader mode, are you using fastboot or mfastboot to flash system? If your system image is a single file instead of sparse chunks, you need to use mfastboot.
Click to expand...
Click to collapse
At first I used fastboot to flash the entire zip but it would say download size too large. Then I tried using mfastboot to flash the boot.img separately but that just gives me an error message.
Shadowblade19 said:
At first I used fastboot to flash the entire zip but it would say download size too large. Then I tried using mfastboot to flash the boot.img separately but that just gives me an error message.
Click to expand...
Click to collapse
what is the error message?
JulesJam said:
what is the error message?
Click to expand...
Click to collapse
I can't really check right now I'm at the beach... I'm using fastboot on a windows 8 tablet not a full fledged PC would that make any difference?
Shadowblade19 said:
I can't really check right now I'm at the beach... I'm using fastboot on a windows 8 tablet not a full fledged PC would that make any difference?
Click to expand...
Click to collapse
It is impossible for anyone to know what is wrong with your device if you can't tell us what the error message is. Post back when you know.
JulesJam said:
It is impossible for anyone to know what is wrong with your device if you can't tell us what the error message is. Post back when you know.
Click to expand...
Click to collapse
okay it keeps saying remote failure on the command prompt and it says "downgraded security version, update gpt_main version failed, preflash validation failed for gpt" on the bootloader
UPDATE": so after some time I was sorta able to get the mfastboot to work my moto x booted up normally and seemed to be running stock 4.2.2 however i get the message "the process com.android.phone has stopped" constantly to the point where the phone is unusable
Shadowblade19 said:
okay it keeps saying remote failure on the command prompt and it says "downgraded security version, update gpt_main version failed, preflash validation failed for gpt" on the bootloader
UPDATE": so after some time I was sorta able to get the mfastboot to work my moto x booted up normally and seemed to be running stock 4.2.2 however i get the message "the process com.android.phone has stopped" constantly to the point where the phone is unusable
Click to expand...
Click to collapse
UPDATE2- so after reflashing the files I stopped receiving the message and I am able to make and receive calls and texts. However, the phone will constantly power off after a minute of use... this seems to be the only problem so far.
Shadowblade19 said:
UPDATE2- so after reflashing the files I stopped receiving the message and I am able to make and receive calls and texts. However, the phone will constantly power off after a minute of use... this seems to be the only problem so far.
Click to expand...
Click to collapse
Aha I think I finally got it ! so i forgot to flash the stock recovery over my twrp so when i went to upgrade to 4.4.4 it would keep powering the phone off to install the update but load up twrp intead. A quick flash of the custom recovery and everything seems to be working fine. Thanks for all your help JulesJam I was seriously worried I bricked my phone beyond repair.
Related
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Well you tried to flash a rom through stock recovery with a locked bootloader. Not the best decision. Go look at the tutorial in general.
Sent from my PACMAN MATRIX HD MAXX
iv-med said:
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Click to expand...
Click to collapse
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
i have the same problem but flashing back to stock rom with rsd will not work
I get a 1/23 partition type erro
and myth will now work due to fastboot, adb and attrib is not known as and internal or external command
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
Having this same problem when trying ota Kit Kat update from T-Mobile. The only way I can get back into 4.2.2 is to use Minimal Fastboot and give the command 'fastboot erase cache'. Even when I do this the phone never says if the cache erasure is complete but Minimal Fastboot says that it is. I have RSD lite installed on my CPU but can't seem to find a working link to the stock T-Mo images. Any help would be appreciated.
Just to add...if I attempt ota I get 'failed to hab check boot'. When trying to boot into recovery I get 'failed to hab check recovery'.
Edit: could I just unlock and root to solve this problem? If so, would someone point me to a different method than the Moto Toolkit found here? It doesn't recognize my moto even though all drivers and Motorola Device Manager are installed.
Sent from my XT1053 using Tapatalk
Ota KitKat update?
What phone do you have?
I have the T Mobile motomaker. Solved the problem with RSD Lite and factory Kit Kat images.
Sent from my Galaxy Nexus using Tapatalk
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
karlsin said:
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
Click to expand...
Click to collapse
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
gdjindal said:
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
karlsin said:
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
Click to expand...
Click to collapse
Power off the phone, pret volume up and insert USB cable . Now follow the guide.
Sent from my LG-D405 using XDA Free mobile app
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
See if you can flash a rom from your sd. hopefully you have something on there. Also see if you can see anything on fastboot since adb is not seeing anything
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
htcoveblue said:
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
Click to expand...
Click to collapse
Update your android SDK. Then try again.
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
I read the story, then at the end is your problem. well, part of it. you weren't using adb in the bootloader, it doesnt work there, ever. you were using fastboot, and you should've fastboot devices
That's encouraging. Any idea how to get past the system.img file is too large error?
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
Is your SDK updated?
My drivers are updated using the Google USB Drivers from this link: http://developer.android.com/sdk/win-usb.html
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
There is a different fast boot that you have to use called mfastboot.
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
The fastboot not being recognized can sometimes be a driver error. Is it recognized look through device manager and try uninstall then unplug USB and plug back in.
Also the android naked drivers might help. Give them a try. http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Sent from my Nexus 6 using Tapatalk
htcoveblue said:
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
Click to expand...
Click to collapse
Can you not use MTP from TWRP?
Jnewell05 said:
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
htcoveblue said:
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
Click to expand...
Click to collapse
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Evolution_Tech said:
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Click to expand...
Click to collapse
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
htcoveblue said:
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
Click to expand...
Click to collapse
No problem. I've run this and as long as you follow the installation instructions precisely, it is very stable and capable of being a daily driver.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
There's another flashable here:
http://forum.xda-developers.com/showthread.php?t=3066052
I haven't run this one but it seems to be getting good reviews.
Hi All,
I'm hoping someone will be able to help as I've spent most of the day chasing my tail it seems.
My 'stock' (non-rooted/non-flashed) Pixel 5 went into a boot loop randomly last night.
I've restarted, I've gone into the recovery mode and have tried to flash an OTA via ADB (which may not sound like much but is an achievement for someone with my limited technical skills), it's getting to 94% and then I'm receiving an error on the cmd prompt saying 'adb: failed to read command: No error' but on the phone itself it says that is was a 'success' status 0.
I've tried the current OTA and the developer version and I'm getting the above issue on both.
I tried copying the 'zip' to a USB stick and have plugged that in using the USB A to USB C dongle that comes with the pixel but I'm receiving an error stating that it cannot be initiated.
Can anyone suggest a possible next step? I have some files that I've realised don't go to my cloud backup and they are important to me so I'd like to if possible not have to wipe the device.
Many thanks.
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for taking the time to respond. Everything was downloaded yesterday so is up to date. I re-downloaded just now and checked again and am still getting the same.
(~94%) adb: failed to read command: No error on cmd
Install from ADB completed with status 0 on the phone.
Is there a simple guide on how to flash-all (for someone as not technical as me) that you can point me towards?
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
did you try a different cable or usb port? borrow your friend's pc perhaps?
l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for this, I'll try another sideload with the April update and attempt it from another laptop, if that still doesn't work then I'll try the flash as you suggest.
swangjang said:
did you try a different cable or usb port? borrow your friend's pc perhaps?
Click to expand...
Click to collapse
I tried a different cable and port but not another laptop. I'll try that next after trying the April update.
Thanks.
tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
WFHbot said:
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
Click to expand...
Click to collapse
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Chad_Petree said:
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Click to expand...
Click to collapse
That sucks. Hopefully they'll be able to do something more than just a factory reset.
I've tried sideloading the April update and that also failed at 94%. Will try another laptop in a while and see if that works, then try the flash as suggested above, if not then it's a factory reset for me.
ProjectAlly said:
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
Click to expand...
Click to collapse
Thanks, will have a look around and see what I can work out. It's looking like I'll have to go this route...
DO I need to unlock the bootloader do do this flash?
tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
WFHbot said:
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
Click to expand...
Click to collapse
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Thanks, I tried that. Edited the file and tried running the flash-all.bat file but it's giving me an error:
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active: ) is not allowed when locked')
fastboot: error: Command failed
Not sure what I'm doing wrong. Am I missing a step? Should the phone be on a certain menu when running the bat file?
l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
bobby janow said:
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
Click to expand...
Click to collapse
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
l7777 said:
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
Click to expand...
Click to collapse
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
WFHbot said:
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
Click to expand...
Click to collapse
You'll have to factory reset in recovery. I had something similar happen yesterday morning. The reboot was done by me on the way to work though. A factory reset fixed it. Of course all user data was wiped, but Google backups did a good job of restoring almost everything I wanted restored (except for apps not on the G Play Store of course). You'll need to sign into everything again, but most things won't be lost including root.