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
Related
Hi Community,
I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!
I tried factory resetting through fastboot didnt work;
I tried flashing stockrom, latest rom, downgrade rom and the error is the same:
Verifying update package...
E: footer is wrong
Update package verification took 0.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..
What Can I do now? any help appreciated
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Everything is described there.
If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
irongas said:
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
Click to expand...
Click to collapse
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
screwyou00 said:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
Click to expand...
Click to collapse
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
irongas said:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
Click to expand...
Click to collapse
Did you install Motorola fastboot drivers?
The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.
sleeptab said:
Did you install Motorola fastboot drivers?
I did, I used to workaround with adb and sending commands, but the command prompt would recognize my device, now, even in bootloader when I plug it in bootloader says: usb plugged in, but the pc wont see my device... im almost crying here lol
Click to expand...
Click to collapse
RESOLVED!
hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working
Thank you a looot guys!!! sorry being such a noob! =)
Have a nice one!!
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
FIXED
@RomLover1999: gave the tip to reboot without a sim card, and that seemed to have fixed the problem!
seend said:
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
Click to expand...
Click to collapse
did you tried a factory reset before updating
galardo_2 said:
did you tried a factory reset before updating
Click to expand...
Click to collapse
Nope, but just tried it and it didnt work.
Try booting without sim card
Same and via fastboot method same. Any solution? We need help its a one mi a2 more????
Unfortunately the error is not informative. I had this error when installing November update. The only way I found to see what went wrong is to check logcat during upgrade, but I think it requires root. In the end I flashed the OTA using fastboot. Still didn't get this update. Try opening shell from adb and reading logcat. I don't think anyone can help you unless we know what is 5he reason for failure
RomLover1999 said:
Try booting without sim card
Click to expand...
Click to collapse
Oh my, that worked! :highfive:
Why would something like that even work?
seend said:
Oh my, that worked! :highfive:
Why would something like that even work?
Click to expand...
Click to collapse
The november update has a bug in it that it only boots in english with a simcard inserted , other languages make the screen bug out ( at least that's what I had ) and only boot without a simcard
Worked greatly
Hey folks, just reinforcing the answer: removing the sim card before restart did the trick, the update went smooth.
Thanks @RomLover1999 and @seend
January update failed
Help! My phone is Mi A2 lite. I can't install January update. My phone is rooted and unlocked.
Thank you!
The same problem....
The same problem....anyone help?
nedjog said:
The same problem....anyone help?
Click to expand...
Click to collapse
did you unlock ? ever run TWRP/Magisk or similiar?
luminoso said:
did you unlock ? ever run TWRP/Magisk or similiar?
Click to expand...
Click to collapse
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
nedjog said:
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
Click to expand...
Click to collapse
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
luminoso said:
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
Click to expand...
Click to collapse
Ok, my phone is not rooted.
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
luminoso said:
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
Click to expand...
Click to collapse
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Mr.Krulez said:
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Click to expand...
Click to collapse
I´m assuming you have xiaomi a2? it must match codename "jasmine"
luminoso said:
I´m assuming you have xiaomi a2? it must match codename "jasmine"
Click to expand...
Click to collapse
fastboot does say that my product is jasmine
Hello!
I just got this phone today and tried to update (8.0 November security update) and keep getting the same error!
I've tried with and without sim card, tried with and without my google acc, and tried with full battery!
Do not really want to unlock/install rom again... Any ideas?
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.
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Do you believe this could help with the ram dump issue?
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Blumi511 said:
Do you believe this could help with the ram dump issue?
Click to expand...
Click to collapse
I have no idea, but I think it can't get worse by trying it.
Flashing the firmware (so called "RAW"-firmware) that allows one to turn back to A11 on the A12 beta page, should get back every device back to a working condition if the problem isn't hardware or extremely messed up in the few partitions that the raw doesn't flash.
I tried using this method to get back to stock from OmniROM, but after several reboots, the phone is stuck in fastboot mode. I tried booting normally and recovery mode, and it immediately goes back to fastboot mode. Any ideas?
/Edit: Got it to boot by flashing Lineage recovery, rebooting into it, and doing a factory reset from there.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...KS-30.11.51.115-MR0-user_20210826-release.zip
Turn of your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
# Thanks to NisseGurra for the link to the latest RAW image.
Click to expand...
Click to collapse
Thank you very much! This safed my phone! I stupidly flashed the boot image from a different build and wasn't able to boot. Only your flash.cmd worked! I hat to comment out the hardwareid check though, because mine was 0 somehow.
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This could also be just an issue with the fastboot drivers. Try reinstalling them, also clearing up orphaned devices in device manager could help.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This is a known issue with Windows 10 computers. They have some sort of signature check where even if you install the correct drivers, they don't really get "installed" because of this check. There is a workaround for this though, I'm not sure how.
However, if you have a Win 7, Vista / 8 PC, adb and fastboot will both work flawlessly with no hassles (experienced personally).
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Where do you get latest RAW links from?
I could not find them via Asus site.
HyperCriSiS said:
Where do you get latest RAW links from?
I could not find them via Asus site.
Click to expand...
Click to collapse
A12 beta page. The firmware that allows you to go back to A11
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Yippee38 said:
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Click to expand...
Click to collapse
Works for me.
is there a newer image out?
it would be good if there is a full raw android 12 image posted...since android 12 is released now.
Hi there,
Installed LineageOS 18.1 yesterday because my phone was having awkward moments, I want to go back to RAW stock, but I can't finalize the install.
I followed OP's instructions, but I never could find the flashall_AFT.cmd from the extracted archive.
Anyway, i managed to use LineageOS Recovery, but it requires signature at 47% , and when I press Yes, it says :
E:error: 21
Installing update...
E: Package is for product ASUS_I006D but expected sake.
Installation version
Installation tried : UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip.
When I tried WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, it required signature after 0.2 seconds, with following message :
E:footer is wrong
update package verificationtook 0.2 s (result 1).E:Signature verification failed
E:error: 21
Installing update...
E:Open failed: /metadata/ota: No such file or directory
E:Couldn't mount Metadata.
E:Failed to find update binary META-INF/com/google/android/update-binary.
I resetted before launching above operations, everytime.
What can I do to go back to Asus RAW Rom ?
Forward thanks and best regards.
EDIT : OK, found it, I just had to extract the .zip file. I thought I had to flash it like any image.
My bad.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thank you so much! You saved my phone! The only thing is that I couldn't find the flashall_AFT.cmd file in the new image, I had to use the WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, and it worked perfectly. After I flashed the boot.img trying to get root on android 12 several times, my phone was in a ram dump state.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thanks! This helped me after I got into a ramdump situation. I flashed a rom and a boot image through the bootloader instead of fastboot and got things corrupted.
On my Asus Zenfone 8, I upgraded from Lineage OS 18.1 to 19.1.
When I wanted to flash gapps and did a reboot into recovery, since then the device no longer works.
I can't get into recovery and I can't get into fastboot mode.
When I turn off the device and turn it on again, the following appears on the screen.
Waiting for flashing full ramdump...
PLS help me
Good day,
My phone is currently stuck in a bootloop and I'm unable to access the Developer Options to enable to the OEM Unlock option. I am able to access Fastboot and Recovery. Any help on how I can unlock the Bootloader is appreciated. Thanks.
shivapersad said:
Good day,
My phone is currently stuck in a bootloop and I'm unable to access the Developer Options to enable to the OEM Unlock option. I am able to access Fastboot and Recovery. Any help on how I can unlock the Bootloader is appreciated. Thanks.
Click to expand...
Click to collapse
The bootloader cannot be unlocked unless OEM Unlocking is turned on.
Since you're able to access recovery, I suggest sideloading the latest OTA package. That should get your device running.
V0latyle said:
The bootloader cannot be unlocked unless OEM Unlocking is turned on.
Since you're able to access recovery, I suggest sideloading the latest OTA package. That should get your device running.
Click to expand...
Click to collapse
Hi. Thanks for your response.
I tried performing an "adb sideload" with the most recent OTA package for the P7 "panther-ota-tq1a.221205.011-7bdbdb25". I downloaded it directly from Google's Developer website. The verification process reaches 47% and then I receive the following messages on the P7's screen:
Installing update...
Error applying update: 1 (ErrorCode: : kError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install from ADB completed with status 1
Installation aborted,
shivapersad said:
Hi. Thanks for your response.
I tried performing an "adb sideload" with the most recent OTA package for the P7 "panther-ota-tq1a.221205.011-7bdbdb25". I downloaded it directly from Google's Developer website. The verification process reaches 47% and then I receive the following messages on the P7's screen:
Installing update...
Error applying update: 1 (ErrorCode: : kError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install from ADB completed with status 1
Installation aborted,
Click to expand...
Click to collapse
Usually that's because the package you're trying to sideload is older than what's already on the device, but if what you're trying to flash is indeed what you posted, it should work. The only thing I can suggest is download the OTA package again and try again.
V0latyle said:
Usually that's because the package you're trying to sideload is older than what's already on the device, but if what you're trying to flash is indeed what you posted, it should work. The only thing I can suggest is download the OTA package again and try again.
Click to expand...
Click to collapse
I actually just did that. I thought maybe the download had an issue so I downloaded the OTA package again and attempted an adb sideload but still got the same error. I tried downloading an older OTA just to see if that would work but it gave me the error that I was attempting to install an older OTA to the device so it aborted the process. adb sideload won't work with the Factory Images? I've even thought about installing another Recovery onto the device and see if I can use that to restore the device to stock. Any thoughts?
With the bootloader locked it seems almost impossible to attempt any fix on the device in its current state. I'm not sure if I just have a paperweight on my hand until I can get the phone to a Google Store for them to check and fix/replace.
shivapersad said:
adb sideload won't work with the Factory Images?
Click to expand...
Click to collapse
No, they have to be OTA images.
shivapersad said:
I've even thought about installing another Recovery onto the device and see if I can use that to restore the device to stock. Any thoughts?
Click to expand...
Click to collapse
Not possible on a locked bootloader, and there's little point to using a custom recovery on Pixels anyway because you can (if the bootloader is unlocked) flash partitions directly via adb
shivapersad said:
With the bootloader locked it seems almost impossible to attempt any fix on the device in its current state. I'm not sure if I just have a paperweight on my hand until I can get the phone to a Google Store for them to check and fix/replace.
Click to expand...
Click to collapse
Seek warranty repair. You don't necessarily have to go to a Google Store. Use this link to enter your IMEI (visible on the back of the device); the customer service reps will direct you to a nearby repair station, or have you mail it in.
V0latyle said:
Usually that's because the package you're trying to sideload is older than what's already on the device, but if what you're trying to flash is indeed what you posted, it should work. The only thing I can suggest is download the OTA package again and try again.
Click to expand...
Click to collapse
V0latyle said:
No, they have to be OTA images.
Not possible on a locked bootloader, and there's little point to using a custom recovery on Pixels anyway because you can (if the bootloader is unlocked) flash partitions directly via adb
Seek warranty repair. You don't necessarily have to go to a Google Store. Use this link to enter your IMEI (visible on the back of the device); the customer service reps will direct you to a nearby repair station, or have you mail it in.
Click to expand...
Click to collapse
Awesome. Thanks for the information. Yea I'll just seek warranty repair because honestly nothing I've tried has worked so it seems this device has a manufacturer issue. This happened when I activated an eSIM on the device as crazy as that sounds.
shivapersad said:
Good day,
My phone is currently stuck in a bootloop and I'm unable to access the Developer Options to enable to the OEM Unlock option. I am able to access Fastboot and Recovery. Any help on how I can unlock the Bootloader is appreciated. Thanks.
Click to expand...
Click to collapse
Just curious since you haven't mentioned it...have you tried a factory reset from recovery mode?
Lughnasadh said:
Just curious since you haven't mentioned it...have you tried a factory reset from recovery mode?
Click to expand...
Click to collapse
Yep I have tried that. I get the following error:
ERROR: recovery: DM_DEV_CREATE failed for [system_b-base]: Device of resource busy
ERROR: recovery: Could not create logical partition system_b as device system_b-base
ERROR: recovery: Unable to map partitions to complete merge.
Unable to check merge status and/or complete update merge.
Unable to check update status or complete merge, cannot wipe partitions.