Related
Hi all,
My fone is Zenfone 2 4GB RAM 32GB internal. It's rooted and updated to version UL-Z00A-WW-2.20.40.59 few days ago.
This morning i seeing the update alert from Asus showing on phone, so i go head with update.
But after reboot, at the screen with Asus logo and slogan In Search of Incredible... and the loading icon keep rolling for hours
I leave it rolling for 2 hours and nothing happen. So i go to recovery mode and do factory/wipe all data. Update process going fine, but after complete and reboot. it still stuck at the loading icon under Asus logo.
Anyone pls help.
i've tried the fastboot erase cache also but still getting same result.
Update: I tried to use adb sideload command below but getting some errors.
adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
even that i place the file update.zip as same folder as adb.exe and this is proper image i used to flash my Zenfone before
Have a look at this thread, here. Look under "Steps to recover from a bootloop".
Follow the instructions carefully otherwise you may hard brick your device, especially at step 7 where you are flashing files to the device. Also do not ever apply OTA on a rooted phone, you must unroot first via SuperSU.
Or go to Shakalaka's thread for Pre-rooted Roms... As long as you can download from MEGA you just fastboot flash the rom.img file and there you have a pre-rooted rom...
I also have my bootloader unlocked so I generally just reflash the last pre-rooted rom and then OTA... Works fine...
I have had this issue caused by inserting an unformatted or corrupt 64GB microSD card. Once removed the boot loop stopped, I never figured out why but on the odd chance that you have the same issue I hope this helps.
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.
Hi,
I followed the instructions to install Line Age ROM and formated my internal storage by TWRP!
Now, I can't boot and everytime returns to recovery.
I tryed to install stock firmware, following with ADB and the same occurs.
Please I need help!!!!
Happened to me as well...i resolved it by flashing the stock image (retail one) and reboot ..it will show error on first boot but press volume up and down and phone will restart to normal
Added screenshot for the build number that worked for me ..my model is XT1710-10
TL;DR: After rebooting to slot b with TWRP following a failed LineageOS flash, my XA2's screen is broken: showing only flashing vertical lines. This problem persists after an attempted reversion to stock firmware and software using Emma.
Apologies for the long post, but I'm at a total loss even after a lot of reading, and would appreciate any suggestions to turn this £180 paperweight back into a phone. I'm not trying to blame the LineageOS or TWRP teams here; any error is my own
What I've done to install TWRP on my XA2:
Installed the newest system updates (including an update to Android 9)
Unlocked the bootloader
Enabled developer options and USB debugging
Installed TWRP as per the instructions on TWRP's XA2 page (i.e.: not flashing TWRP using fastboot)
Happily rebooted into fully-functional TWRP
I then tried to flash LineageOS using TWRP:
Formatted data
Wiped system, cache, and internal storage partitions
Attempted to flash LineageOS (lineage-16.0-20190916-nightly-pioneer-signed.zip)
Flash failed with "ERROR: 1"; "Error applying Update: 18 (ErrorCode:: kdownloadPayloadPubKeyVerificationError)"
After some reading I found a post which suggested rebooting into slot b to fix this problem
Used TWRP to reboot into slot b
Screen is now glitching: flashing vertical lines on a black background; Sony splashscreen doesn't show during boot, nor does the unlocked bootloader screen
Here's what I've tried to fix it:
Flashed stock firmware, and then software, using Emma (which showed both operations as being successful)
Attempted to reboot to slot a using fastboot
The current state of the device:
Broken screen showing only flashing lines and colours (no splashscreens)
Boots to voice-assisted setup (!?) despite the broken screen. From what voice assist is saying, there seems to be a system there (e.g.: I can take screenshots)
Can be powered on and off, and put into flash mode (green LED)
Is still recognised by (and can be controlled using) fastboot
Thanks for reading. Any help is much appreciated
Update: I've tried using Newflash to flash stock firmware downloaded via Xperifirm.
The operation complete successfully, and the device boots (thankfully not to voice-assisted setup), but the screen is still broken, as described in my OP.
Does anyone have any suggestions?
Alright, on the off-chance that anyone comes here with the same problem (i.e.: XA2, broken screen), I seem to have fixed it by:
Powering off the device
Putting it into flash mode (green LED)
Fastbooting a special TWRP .img with "fastboot boot /path/to/twrp.img"
Rebooting the device normally
I have no idea whether my previous step of using Newflash is a dependency of this working, or whether it works on its own
Now my screen works again, but every attempt to flash LineageOS zips with TWRP fails as described in my OP:
Error applying update: 18 (ErrorCode: : kDownloadPayloadPubKeyVerificationError )
Updater process ended with ERROR: 1
Error installing zip file
This happens:
With several different nightly pioneer builds
With several different versions of TWRP
Trying to flash the .zip from SD card
Trying to adb push the .zip
Trying to flash from the fastboot booted .img
Trying to flash from different versions of the TWRP .zip, flashed from the fastboot booted .img
Despite having already flashed the older firmware version (50.1.A.13)
So I am again at a loss
Google Translate
did you see this guide?
https://forum.xda-developers.com/xperia-xa2/how-to/guide-flashing-lineageos-16-0-sony-xa2-t3944964
bane.twit said:
Google Translate
did you see this guide?
https://forum.xda-developers.com/xperia-xa2/how-to/guide-flashing-lineageos-16-0-sony-xa2-t3944964
Click to expand...
Click to collapse
Hi Bane, thanks for your reply
The guide you've linked is the guide I was attempting to follow. However, I get "Error applying update: 18 ..." at step 22.
Do you know how I can fix this error (perhaps bypassing verification)?
Google Translate
works with me with twrp-3.3.1-1-pioneer.img
bane.twit said:
Google Translate
works with me with twrp-3.3.1-1-pioneer.img
Click to expand...
Click to collapse
Interesting; I encountered the error using either twrp-3.3.1-1.img alone, or using twrp-3.3.1-1 to flash twrp-install-pioneer-3.2.2-0.zip
I've also tried various combinations of twrp.img and twrp.zip, but to no avail.
This was despite: flashing the Oreo firmware to both slots, formatting data, and wiping the system partitions.
Is there something I'm missing? Following the guide you kindly linked, everything works, until step 22 when I encounter this error and can't flash lineage.
Google Translate
- follow the guide instructions...
- via ADB, only twrp-3.3.1-1-pioneer.img ...
- adb sideload lineage ... the latest build ...
bane.twit said:
Google Translate
- follow the guide instructions...
- via ADB, only twrp-3.3.1-1-pioneer.img ...
- adb sideload lineage ... the latest build ...
Click to expand...
Click to collapse
Amongst other things I've tried:
-Flashing Oreo firmware (with Emma or Newflasher)
-Rebooting to fastboot (?); blue LED
-"fastboot boot ./twrp-3.3.1-1-pioneer.img" to boot TWRP
-Formatting data and wiping system partitions
-Trying to flash lineage, either from SD card or by sideloading
...but I always run into error 18, and flashing fails
Am I missing any steps here?
i can't help you
bane.twit said:
i can't help you
Click to expand...
Click to collapse
Ah OK, thanks for your help though
I'll try again in a week or so (I'm away from home for a while) and if I get it working I'll post the solution here.
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Leonniar said:
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Click to expand...
Click to collapse
Can you flash full rom with mi flash tool
Rares6567 said:
Can you flash full rom with mi flash tool
Click to expand...
Click to collapse
Already did, it didn't work...
Leonniar said:
Already did, it didn't work...
Click to expand...
Click to collapse
Maybe is some motherboard issues?
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Leonniar said:
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Click to expand...
Click to collapse
There is no volume buttons problem?
If no maybe you should reflash whole phone, fastboot, recovery, all, using edl ig.... I don't have this phone or any Snapdragon phone, so I don't really know....
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Leonniar said:
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Click to expand...
Click to collapse
So then why your phone goes to fastboot?
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Leonniar said:
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Click to expand...
Click to collapse
It seems that this a software bug ig, can you try go to recovery and flash the rom?
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Leonniar said:
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Click to expand...
Click to collapse
So where u downloaded the fastboot rom, there is a recovery rom too :
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Be sure u download the recovery rom not fastboot.
Btw use your miui version u had
Tho I'm not 100% sure if you flashed the fastboot rom correctly, did u :
1. Open MiFlashTool : download the tool from here if you don't have it ---> https://xiaomiflashtool.com/
2. Select your rom ( make sure your path to the rom isn't long and the folder/folders don't have long names )
3. Connect your phone
4. Click Refresh ( to make your device appear)
5. And click flash
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Leonniar said:
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Click to expand...
Click to collapse
Ok so to fix the error : go to miflashtool folder and create a new folder called : log
Fixed the start up error, I get the screen that says "Please install driver", I press Install and I get this:
https://prnt.sc/I53g6bs_8i5w
Pressing ok gets me back to the "Please install driver" screen
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Rares6567 said:
It seems that this a software bug ig, can you try go to recovery and flash the rom?
Click to expand...
Click to collapse
flashing miui_APOLLOEEAGlobal_V12.5.4.0.RJDEUXM_451a2324af_11.0.zip from stock recovery is good idea, you can do this from MicroSD card to circumvent any usb issues you are obviously facing on fastboot.
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
So it worked?
This "error" isn't an "error" so don't worry about it
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
This error is normal since you are not re-locking the bootloader.
If some functions are inoperative.
Try to flash the same rom (fastboot) that you had when you bought the phone, probably an A11.
Use clean all(flash_all.bat).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/