Bootloop after OTA Update - ZenFone 2 Q&A, Help & Troubleshooting

I have an ASUS ZenFone 2 (550 model), and I got a Push Notification about an OS Update, so I went ahead and installed it. After the phone installed the Update and rebooted, I got in a Bootloop. I can get into the Bootloader, the Stock Recovery, and the Temporary ClockworkMod Recovery mentioned here:
Code:
http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063
ADB also works, thankfully.
My phone is rooted, and I'd like to unlock my Bootloader, and install CyanogenMod, after I get out of this Bootloop.
Could someone please help?
EDIT:
Silly me, I forgot to mention the problems I actually had while trying t solve the bootloop.
So,
Problem #1: If I try to flash Firmware, the stock Recovery stops at 25% (It continues going until 50% in ADB), and then i get this error:
"E: failed to verify whole-file signature
E: signature vertification failed"
Problem #2: CWM cannot use my MicroSD. If I go to "Install zip from sd card", it doesn't show the actual SD card, jus three empty folders. I tried to mount "ext-sd" in the mounting options, but it fails to mount. (My MicroSD is 32GBs and formatted in Fat32, so it should work. :/ )

Related

[Q] Please Help! Is Phone Bricked or Salvageable?

Rooted (via Revolutionary) Incredible 2. Was running stock Rom.. Decided to try CM7. downloaded and installed via ROM Manager. MMS didn't work so i tried to restore to my backup via Rom Manager. Now phone sticks at white HTC Screen.
Can get into recovery.
But receive the following error messages:
E: Can't Mount/cache/Recovery/command
E: Can't Mount/cache/Recovery/log
E: Can't Open/cache/Recovery/log
E: Can't Mount/cache/Recovery/last-log
E: Can't Open/cache/Recovery/last-log
INFO:
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO 1.09.01.0622
EMMC-BOOT
When I attempt to restore a backup I get:
Checking MD5 sums...
Erasing boot before restore...
Restoring Boot Image...
Restoring System Image...
Error while Formatting/System!
TRIED FLASHING A COUPLE DIFFERENT ROMS:
FINDING UPDATE PACKAGE
OPENING UPDATE PACKAGE
INSTALLING UPDATE
E: ERROR IN /SDCARD/CCM7_INC2_V1.4ZIP
(STATUS 1)
INSTALLATION ABORTED
Tried Flashing the return to stock PG32img.zip
get these messages:
Loading [PG32DIAG.ZIP]
NO IMAGE!
Loading [PG32DIAG.NBH]
NO IMAGE OR WRONG IMAGE
IT LOADS THE FILE AND I START THE UPDATE.
IT BYPASSES (1) BOOTLOADER
AND THEN STICKS AT (2) BOOT----UDATING
MESSAGES AT BOTTOM OF SCREEN SAY:
DO NOT POWER OFF DEVICE!
CAN NOT ROLL BACK HBOOT VERSION
WILL JUST SAY STAY LIKE THIS FOR HOURS.
Any help to get a working phone would be greatly appreciated. THANKS!!!
Any chance the SD card is corrupted?
card
Not sure, the card seems to work ok in my computer, and I used a different card to try and flash the roms and the return to stock PM32IMG.ZIP. I will try another card when i get one.
Install another recovery... I personally like 4ext. Its in the dev section... also did u nandroid your stock rom before flashing? Try restoring it an verifying it is a correct md5 for the rom and that your recovery is up to date
Sent from my Incredible 2 using Tapatalk 2
I tried 2 different sd cards with no luck. i have 5 or 6 backups but none of them will load. how would I go about install the 4ext recovery?
http://forum.xda-developers.com/showthread.php?p=20013819
Read down where it says if you lost your recovery img... that's how u install it via fast boot
Sent from my Incredible 2 using Tapatalk 2
Hey, this is DroidDev from AndroidCentral. Just incase you didnt see it there:
Seems like corrupted HBOOT or Bootloader to me? Will do some more digging/thinking but it doesnt look good.
When you install the pg32img.zip, which is the stock RUU, you roll everything back to stock. HBOOT, OS, everything, even loosing root. First thing it tried to do is roll back the HBOOT, it if cant do that then you probably have corrupted HBOOT.
In the mean time I would grab the Froyo RUU here and try that:
http://forum.xda-developers.com/show....php?t=1466295
If you were trying with the Froyo RUU, then try the Gingerbread one. The Guide in this thread, if you read it, has instructions on pushing hboot starting at step 11. But I would just do the guide from beginning to end. It will return your phone to complete stock froyo. If successful you can upgrade back to GB.
Click to expand...
Click to collapse
If you cant get the Froyo RUU to install then I would not continue with the guide, could make it worse.
Here is a link to the GB RUU for you.
Turn on your phone and enter the bootloader, select fastboot and plug into your computer. Leave the phone here, then just run the .exe file on your computer. This'll wipe everything including bootloaders, radio, recovery etc. back to stock GB, without relying on your SD card to do the work.
It's worth a shot, while I don't think the SD card is the issue I haven't been able to not recover with an RUU before, from anything
Good luck!
Sounds like flash memory is messed up, I bet all partition sizes read zero, same thing happened to me. I tried to reformat with parted but no luck.I never could find exact sizes for the various mtblk's but my final judgment was that the physical flash memory was fried. dunno maybe if you knew the exact format sizes for everything you could try to push the needed Linux file through adb and try to reformat them one at a time, but I never could get it to work.
On a side note someone on XDA who said they work @ Verizon said they've had a rash of inc2's being turned in with similar problems, maybe a manufacturing glitch
Sent from my 2nd Incredible 2
Ok, so i tried flashing the 4EXT recovery by loading on an sd car and flashing with fastoot. Appeared to install, but still getting same problems. Tried to flash the recovery with abd fastboot from computer...just sticks a writing... never completes. Also tried flashing different backups and ROMS from flashboot with computer, with ROMS I get a message saying their is an error in zip file and can't be read. Tried to install Froyo ROM again via fastboot from SDcard. Just hangs at 2nd 1 saying updating for hrs, never completes. Not sure how to run GB RUU by the exe file? Do i extract the RUU file first? Whenever I have tried to extract those update files in the past i got an error. I'll try and figure it out this afternoon. An interesting side note, CM9 rom appears to install via flashboot from card but never loads upon reboot. Thanks to All for their continuing help!!!
PS...surfing at work and found this post - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ - sounds similar to my problem...basically says partitions on internal storage are messed up and how to use parted to fix. May also try that.
well, tried to install the gb rom exe file. Hung almost from the start, trying to reboot phone into bootloader. I'm at loss. Guess I have a new red paperweight. Not sure how to do parted, so holding off on that for now. Open to any other suggestions.
your using the wrong ruu i think you have to get the latest update, god and i forget the link, go to rootzwiki, jelly belly has what you need or condemned soul on here
My DINC2 is FIXED!
Turn on your phone and enter the bootloader, select fastboot and plug into your computer. Leave the phone here, then just run the .exe file on your computer. This'll wipe everything including bootloaders, radio, recovery etc. back to stock GB, without relying on your SD card to do the work.
It's worth a shot, while I don't think the SD card is the issue I haven't been able to not recover with an RUU before, from anything
Good luck![/QUOTE]
Hey man thank you, I had the same issue as the thread starter and tried all the same methods as he did before searching the forums. Your solution worked for me after getting the latest RUU from jellybelly. This event happened to me randomly, i think the wrong buttons were pushed while my phone was in my pocket. I have a commuter otterbox case and it makes the buttons easier to press. But some tips:
1. verify md5sum
2. i had s-off so I used the latest 2.3.3 ruu file from jellybelly
3. rename downloaded zip file "PG32IMG" only exclude the .zip part like what most folks tell you.. i explain below
i initially renamed the zip "PG32IMG.zip" and stored on the root location of the sdcard, well fastboot/hboot could not find the file, after loading the sdcard back on my computer and clicking the files properties i noticed the the file name was "PG32IMG.zip.zip", after renaming the file to "PG32IMG" the bootloader was able to find the zip file and the process was completed.
4. I do not know about an .exe file, If you can get into fastboot/hboot by holding the "volume down button" + power , that is the method i did
I hope I helped somebody and thanks everybody for yours!
I had similar problems sticking on white with green HTC on it. Mine had to do with the boot.img. I had to extract a boot.img out of a rom put it in folder on C Drive installed rom with 4extrecovery let it load but did not reboot I connect to computer pulled up bootloader with adb and flashed the boot.img and flash reboot and it past that screen and loaded. Had to be unlocked to do it.
daddythree said:
Rooted (via Revolutionary) Incredible 2. Was running stock Rom.. Decided to try CM7. downloaded and installed via ROM Manager. MMS didn't work so i tried to restore to my backup via Rom Manager. Now phone sticks at white HTC Screen.
Can get into recovery.
But receive the following error messages:
E: Can't Mount/cache/Recovery/command
E: Can't Mount/cache/Recovery/log
E: Can't Open/cache/Recovery/log
E: Can't Mount/cache/Recovery/last-log
E: Can't Open/cache/Recovery/last-log
INFO:
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO 1.09.01.0622
EMMC-BOOT
When I attempt to restore a backup I get:
Checking MD5 sums...
Erasing boot before restore...
Restoring Boot Image...
Restoring System Image...
Error while Formatting/System!
TRIED FLASHING A COUPLE DIFFERENT ROMS:
FINDING UPDATE PACKAGE
OPENING UPDATE PACKAGE
INSTALLING UPDATE
E: ERROR IN /SDCARD/CCM7_INC2_V1.4ZIP
(STATUS 1)
INSTALLATION ABORTED
Tried Flashing the return to stock PG32img.zip
get these messages:
Loading [PG32DIAG.ZIP]
NO IMAGE!
Loading [PG32DIAG.NBH]
NO IMAGE OR WRONG IMAGE
IT LOADS THE FILE AND I START THE UPDATE.
IT BYPASSES (1) BOOTLOADER
AND THEN STICKS AT (2) BOOT----UDATING
MESSAGES AT BOTTOM OF SCREEN SAY:
DO NOT POWER OFF DEVICE!
CAN NOT ROLL BACK HBOOT VERSION
WILL JUST SAY STAY LIKE THIS FOR HOURS.
Any help to get a working phone would be greatly appreciated. THANKS!!!
Click to expand...
Click to collapse
I'm having this exact same problem. Did you ever get your fixed? Any new suggestions ??

Boot loop after 4.4.2 update and Clockworkmod install

Stuck in a bootloop. Here's my story.
Updated to 4.4.2 earlier today.
Tried to root my Nexus 7 later after the update. Here's what I did:
rebooted into bootloader with adb (adb reboot-bootloader)
unlocked the bootloader with fastboot (fastboot oem unlock)
flashed clockworkmod using fastboot (this is the file i downloaded and flashed: -http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-flo.img)
rebooted into recovery
selected "install zip>choose zip from sdcard" (trying to install supersu.zip file that I had loaded onto the internal memory)
Here's where I ran into trouble. After selecting "choose zip" nothing happens, and a message shows up on botton of the screen that says "E: Can't mount /sdcard"
So I can't install anything from clockworkmod.
I rebooted into bootloader, tried to re-flash using fastboot - "device not found"
I tried to reboot the device into android - bootloop animation
I tried wiping data, cache, factory reset, dalvik chache, etc from recovery - still getting bootloop animation
Any ideas?
Ok, I wiped/deleted sdcard data from clockworkmod and I managed to get it to boot.
That's deadly but I still don't have root, which was the point of this in the first place. Anyone know where I went wrong?
Strange. I did pretty much the exact same procedure and it worked for me.
Sent from my Nexus 10 using xda app-developers app
So, I flashed TWRP.
Tried installing SuperSu from there. This worked slightly better than Clockworkmod Recovery, it at least could read the internal storage, and allowed me to select the supersu.zip file. But I get the following error when I try to install it:
E: Unable to open zip file
Error flashing zip 'sdcard/Download/UPDATE-SuperSU-v1.80.zip
Not sure what's happening here.... May have to do with the 4.4.2 update? Maybe I'll try flashing the 4.4.2 factory image and then retrying the above steps.
I also did pretty much the same. I had a new Nexus 7 2013. The very first thing I did was to update to 4.4.2 through OTA before I went to rooting procedures:
Unlock bootloader (data was wiped because of it)
Flash TWRP
Flash superuser.zip file through TWRP
Everything worked fine.

[Q] Soft-Bricked phone, would like to restore to Stock OS

I was having some problems connecting to my mobile network, I couldn't access Google Play Store, I couldn't read Chinese well enough to figure out how to download and install new apps from China's playstore, so I decided to flash a custom OS on my P6 to play around with.
These are the steps I've taken and where it's led me to now -
Installed TWRP on my phone
Installed ADB and Fastboot onto my computer
Turned on Developer Mode and enabled USB debugging
Copied new OS Zip into my memory card
Restarted phone into TWRP recovery
Followed instructions to wipe dalvik, cache, data, and system (I'll try to find the link after this post)
Attempted to install the new OS (Failed due to incompatibility, stupid me)
Tried Sideloading an official Huawei released OS from their website (Failed to recognize my device on adb)
Tried Rebooting my device into Bootloader and attempted to load a Zip to force update my phone (and displayed "e:failed to mount /cache")
Flipped through xda and thought I needed Stock Recovery to load an official OS, so I fastboot flashed it in
Rebooted my phone into Recovery, saw "wipe data/factory reset", so I attempted that (displayed "E:failed to mount /data (invalid argument)
So... I'm stuck here, not sure what to do next because I think I'm just breaking my phone more than I'm trying to make it work... Can anyone help me out here? ._."
faye2thesky said:
I was having some problems connecting to my mobile network, I couldn't access Google Play Store, I couldn't read Chinese well enough to figure out how to download and install new apps from China's playstore, so I decided to flash a custom OS on my P6 to play around with.
These are the steps I've taken and where it's led me to now -
Installed TWRP on my phone
Installed ADB and Fastboot onto my computer
Turned on Developer Mode and enabled USB debugging
Copied new OS Zip into my memory card
Restarted phone into TWRP recovery
Followed instructions to wipe dalvik, cache, data, and system (I'll try to find the link after this post)
Attempted to install the new OS (Failed due to incompatibility, stupid me)
Tried Sideloading an official Huawei released OS from their website (Failed to recognize my device on adb)
Tried Rebooting my device into Bootloader and attempted to load a Zip to force update my phone (and displayed "e:failed to mount /cache")
Flipped through xda and thought I needed Stock Recovery to load an official OS, so I fastboot flashed it in
Rebooted my phone into Recovery, saw "wipe data/factory reset", so I attempted that (displayed "E:failed to mount /data (invalid argument)
So... I'm stuck here, not sure what to do next because I think I'm just breaking my phone more than I'm trying to make it work... Can anyone help me out here? ._."
Click to expand...
Click to collapse
By the steps you've taken i can tell you are on stock recovery at this moment and with no system installed on phone, so i would suggest you downloading an official stock rom (update.app file) and put it in dload folder in a SD card and try to install. Now one thing that you should be aware before attempting this is to make sure you have the same version of OS as the one before, either JB or KK. Good luck.

Soft bricked Nexus7 can't get through "Can't mount" errors

Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!
I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.

Phone won't boot, can't flash new ROM but can get into recovery

This all started when I opened my Pokémon Go app and got "Failed to extract resources needed by Il2CPP". I tried to go into Settings and clear some App data, but I kept getting "com.xxx has stopped working" no matter what I tapped, so I just shut down the phone and try to restart but... it wouldn't go past the boot page. I went into recovery mode to try and clear Dalvik/cache, but the error said "unable to make cache/recovery". When I tried to reboot the phone from inside TWRP, it would freeze.
So I tried to go into recovery again, wiped dalvic/cache/data and that seemed to succeed. I tried to flash Fulmics via OTG but during installation, it says "set_metadata_recursive: some change failed", or sometimes it wouldn't even get to the Fulmics installation and just say "unable to map OTG file" or something like that. Tried to copy the file from the USB drive to the phone to flash directly from the phone, but that kept failing with "process has ended" and nothing copied over. I can't flash from an external SD card cause the SD slot is broken (when the phone was booted up, the SD card kept mounting and unmounting).
Is there any way to fix this? A setting in TWRP or something I need to change? Another file I can flash to fix these errors? Or do I have to try and go back to stock? Is it even possible to go back to stock at this point?

Categories

Resources