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.
Related
okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.
flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart
but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.
Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly
ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[
Boot.img must be flashed via fastboot. Not via recovery !
ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!
Good, thanks to @tomascus. He summed it up real nice
Cheers
HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help
I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!
https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy
YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.
ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs
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.
Recently I tried to flash my Asus Fonepad 7 to an earlier version as the last update slowed down the tablet.
I did following steps and all were successfull.
1. Installed and configured ADB and fastboot.
2. Downloaded Firmware and copied to SD card.
3. Flashed boot.img and fastboot.img using fastboot.
As the next step I choose SD Download to install the firmware.
Then it successfully copies the firmware to cache and restarts to install.
After restart it waits few seconds in bootscreen and restart. Then it stuck on bootscreen forever.
I tried several firmware versions and bootloaders, but the result is same.
*All the other steps mentioned were successfull
Please help me to solve this.
hpsoftz said:
Recently I tried to flash my Asus Fonepad 7 to an earlier version as the last update slowed down the tablet.
I did following steps and all were successfull.
1. Installed and configured ADB and fastboot.
2. Downloaded Firmware and copied to SD card.
3. Flashed boot.img and fastboot.img using fastboot.
As the next step I choose SD Download to install the firmware.
Then it successfully copies the firmware to cache and restarts to install.
After restart it waits few seconds in bootscreen and restart. Then it stuck on bootscreen forever.
I tried several firmware versions and bootloaders, but the result is same.
*All the other steps mentioned were successfull
Please help me to solve this.
Click to expand...
Click to collapse
-----------------------------------------
same occurred to me. bricked,
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/