Related
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Try the tool kit in development.
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
Are you in bootloader/fastbootusb?
BD619 said:
Are you in bootloader/fastbootusb?
Click to expand...
Click to collapse
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
redmanjoey said:
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
Click to expand...
Click to collapse
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
joshuaw84 said:
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
redmanjoey said:
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
Click to expand...
Click to collapse
It could be outdated.
Do you have android sdk on your PC?
If so make sure it's up to date.
If not get it HERE
redmanjoey said:
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Click to expand...
Click to collapse
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
joshuaw84 said:
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Sorry if I sounded mean or anything I was literally just asking which one you meant lol. I now realize "are you implying" does sound kinda snarky. Anyway, it must have been something with my computer because I did it on another computer and got it to work.
So the thread doesn't go to waste, if anyone is having issues try on another computer.
Okay, now trying to flash the stock recovery to get the phone exchanged for radio issues, I am running into the same problem. I tried both computers now. Hopefully I figure it out soon, had to activate an old blackberry for the time being.
"sending 'recovery' (16472 KB)...
FAILED (remote: not allowed)
finished. total time: 0.007s"
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
{ParanoiA} said:
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
Click to expand...
Click to collapse
To flash a recovery? Just rename the recovery as a radio file?
Yes. Go to http://forum.xda-developers.com/showthread.php?t=2696652 and all the info you need is there along with directions.
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.
Hey guys, My phone has been bootlooping for about a few weeks now. I gave up on it thinking it was bricked, and also since i had a spare phone. Well that spare phone is no longer functional, and I need a device for work/school.
What happened was that I put the phone on the charger, and went to check on it. It was at about 60% battery life, I unplugged it, tried to unlock the screen and it crashed, went into boot loop for a while and said something along the lines as there was a problem with the OS or something?
So I tried hard resetting it via hardware buttons, and no luck. Now it just boot loops, goes from android one logo to Nokia. Stay on Nokia logo as if it's booting normally and the screen turns of and it boot loops again.
Is there anyway I could reflash the device? It's relative new so I doubt it would be a hardware issue and it was fine before?
However, and this might not be relevant, but a couple months ago i started getting modem ram dump popping up randomly on the screen, and it would restart the modem and it would be fine. Could this be the cause of my errors?
If it is a hardware issue, I'm in CA, would I be able to take it to a shop and have it fixed?
Thanks in advance!
try factory reset in recovery menu: hold power to powerdown, hold power + volume up some sec, aftet show no command with android logo on black screen, press short power + volup to show menu
k3dar7 said:
try factory reset in recovery menu: hold power to powerdown, hold power + volume up some sec, aftet show no command with android logo on black screen, press short power + volup to show menu
Click to expand...
Click to collapse
I've factory reset multiple times through recovery mode, still bootloops. Is reflashing the best option? How would I go about doing that?
zackman558 said:
I've factory reset multiple times through recovery mode, still bootloops. Is reflashing the best option? How would I go about doing that?
Click to expand...
Click to collapse
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
cristi.blidariu said:
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
Click to expand...
Click to collapse
Oh, that seems like a really solid idea! I think I had the June security Patch when these issue arised, so I should try to install July?
And that's installing it by going into recovery mode and selecting install update from SD card, correct?
cristi.blidariu said:
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
Click to expand...
Click to collapse
Hi! So I tried updating from SD using the OTA july 2019 file, and it started installing got to step 1/2 and then rebooted back to the android robot no command screen! What does this mean?
zackman558 said:
Hi! So I tried updating from SD using the OTA july 2019 file, and it started installing got to step 1/2 and then rebooted back to the android robot no command screen! What does this mean?
Click to expand...
Click to collapse
UPDATE!
I tried using june, and it wouldn't work since it's june so that made sense.
When I tried July this most recent time, it gave me the following error code:
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode : : kDownloadStateInitializationError)
E:Error in /sideload/package.zip (status 1)
Installation aborted.
What do i do now? I'm thinking of redownloading the July update and trying again
zackman558 said:
UPDATE!
I tried using june, and it wouldn't work since it's june so that made sense.
When I tried July this most recent time, it gave me the following error code:
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode : : kDownloadStateInitializationError)
E:Error in /sideload/package.zip (status 1)
Installation aborted.
What do i do now? I'm thinking of redownloading the July update and trying again
Click to expand...
Click to collapse
Try to sideload using adb sideload command
cristi.blidariu said:
Try to sideload using adb sideload command
Click to expand...
Click to collapse
I'm downloading android studio rn, how would I go about sideloading via adb? I know how to get to the adb from recovery but on the computer end what do I do. Thanks for the help so far
zackman558 said:
I'm downloading android studio rn, how would I go about sideloading via adb? I know how to get to the adb from recovery but on the computer end what do I do. Thanks for the help so far
Click to expand...
Click to collapse
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
UPDATE!
Tried to do it via adb, got it to get going. Got to 61 and then
adb: failed to read command: No error
What does this mean?
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
UPDATE!
Tried to do it via adb, got it to get going. Got to 61% and then
adb: failed to read command: No error
What does this mean?
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
Put the update file in the same folder where you have adb,then run adb sideload name of the file.zip and hit enter
zackman558 said:
UPDATE!
Tried to do it via adb, got it to get going. Got to 61% and then
adb: failed to read command: No error
What does this mean?
Click to expand...
Click to collapse
It either does this, or it fails to verify signature at 41%. Error 21
cristi.blidariu said:
Put the update file in the same folder where you have adb,then run adb sideload name of the file.zip and hit enter
Click to expand...
Click to collapse
Yes, I figured this much out but it won't complete past 61%. Recent attempts it gets to around 47%, and says signature verification failed.
Error 21
Installation aborted.
Why does this happen? Is there something wrong with the July file found on xda?
Is there a way of reflashing or something? Im confused as why it won't complete the install, only thing that i could think of is corrupted partition somehow.
zackman558 said:
Yes, I figured this much out but it won't complete past 61%. Recent attempts it gets to around 47%, and says signature verification failed.
Error 21
Installation aborted.
Why does this happen? Is there something wrong with the July file found on xda?
Is there a way of reflashing or something? Im confused as why it won't complete the install, only thing that i could think of is corrupted partition somehow.
Click to expand...
Click to collapse
I all so think that your sistem partition is corrupted,try again with August patch and see if is working,if not,then you need to take it to a service,or if is possible to unlock bootloader
cristi.blidariu said:
I all so think that your sistem partition is corrupted,try again with August patch and see if is working,if not,then you need to take it to a service,or if is possible to unlock bootloader
Click to expand...
Click to collapse
August didn't install yesterday, said something about how it needed July i think.
How would I go about unlocking bootloader? How can i check if it is already unlocked?
zackman558 said:
August didn't install yesterday, said something about how it needed July i think.
How would I go about unlocking bootloader? How can i check if it is already unlocked?
Click to expand...
Click to collapse
hi,you can all so try to downgrade aboot(bootloader) by flash an older security patch,try with december patch from 2018,as soon as you see abort error keep the phone in recovery,now download full firmware of march and try again to flash
ps/this method i have try on nokia 5,but it might all so work on nokia 7 plus i wish you best of luck
I've basically two questions: First my concrete problem and second "how can I debug problems with the horrible platformTools"? Maybe you can help me solve both.
1. fastboot fails with "unknown command"
I've sucessfully build AOSP Android 10 via the instructions from Sonys Open Devices. But I'm currently stuck at the last step - flashing the images on my phone. I've successfully put the device in fastboot mode (LED is glowing blue, and "fastboot devices" lists a connected device).
But sending the vendor image fails with an "unknown command"-error
Code:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Sending 'oem' (211868 KB) FAILED (remote: 'unknown command')
I'm using the newest platformTools on Ubuntu Linux 18.04. My bootloader is unlocked and I've already installed other Android Versions in the past on the phone. Any idea whats going on here and how to fix it?
2. How to debug it myself?
And as a more general approach, as some problems with fastboot/adb appear to occure almost everytime I try to use it: Any tipps on how to find the cause of the problem myself? Any logs which I should check? Any known problems which I should be aware of?
AllesMeins said:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Click to expand...
Click to collapse
EDIT: Does THIS help?
SXUsr said:
EDIT: Does THIS help?
Click to expand...
Click to collapse
Unfortunaly not - I already had a pretty recent version, but did an update to the newest nevertheless. Problem stays the same.
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.
AllesMeins said:
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.
Click to expand...
Click to collapse
Try it, you can always rely on EMMA to go back. I'll happily test if you want?
SXUsr said:
Try it, you can always rely on EMMA to go back. I'll happily test if you want?
Click to expand...
Click to collapse
No luck... Tried it for boot, system, vendor and everytime the same error. But it seems to be a Linux-Problem. I tried it with my flatmates Windows 10 PC and there everything worked. But of cause this is no solution for the future. Any ideas why the phone doesn't understand the commands, when coming from my system?
AllesMeins said:
Any ideas why the phone doesn't understand the commands, when coming from my system?
Click to expand...
Click to collapse
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?
SXUsr said:
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?
Click to expand...
Click to collapse
In normal mode: yes.
$ ./adb devices
List of devices attached
BH906VHH9E device
Click to expand...
Click to collapse
In fastboot mode no - but there it is listed under fastboot devices
I wish I could be of more help, I really want to see 10 on this phone.
I managed to flash it on Windows, but version is 5 , but got loopboot afte reinstalling PIxel Experience Plus.
https://forum.xda-developers.com/xperia-xz1-compact/help/pixel-experience-10-0-plus-how-to-t4077747
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.