I need help understanding why I'm stuck in reboot loop with my EVO 4G.
I originally was trying to root the device using unrevoked3 but getting the ERROR "Backup CID is Missing" message and unable to proceed. I followed the instructions at http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies.html which talk about troubleshooting this. It talks about going into recovery mode to see if I've lost the recovery mode which I did (black screen with phone and read arrows). It says to reboot but I was unable to so I unplugged the battery.
Since then I have been stuck in a mode where the device boots but the sdcard is not recognized and upon completion of boot up it shuts down and vibrates five times. I did a bunch of research last night on understanding what I thought I needed to do alleviate this. My thought was since I was stuck without a recovery image I need to flash new one. At this point I'm fine with not being rooted with all the trouble I've had.
I downloaded the latest stock recovery rom (3.70.651.1) from http://androidforums.com/evo-4g-all-things-root/259446-clockwork-amon-ra-pc36img-files.html and pushed it to my sdcard under the name PC36IMG.zip (with two files .info and recovery.img). I restarted my phone via HBOOT and it sees the zip file, reads it in, goes to checking and then does nothing (back to HBOOT screen). I don't get what I'm doing wrong. I also tried getting the stock image from http://forum.xda-developers.com/showthread.php?t=874091 but I can't seem to open the firmware.zip file to try that recovery image.
Again I just want to get back to stock ROM and recovery files now. Any help would be greatly appreciated!
Hello
My i9250 has a strange problem
If I use ODIN to flash anything on it nothing changes even though it says "PASS".
If I use fastboot to flash a new recovery onto it, it says "OKAY" but when loading recovery the same version as before (v5.x.x.x) is still there even after trying to flash a new one on (v6.0.4.7).
When in recovery and factory resetting it does not produce any errors, but when I try to load up the OS it does not seem to have anything wiped.
I have a problem with my OS where when it just starts and shows the lockscreen after a few seconds it restarts.
I've had experience with other phones like the Galaxy S2 and HTC One X and none of these have produced the same kind of problem, where no matter what I try nothing seems to change on the device itself.
Possibly related information: In cwmrecovery (v5.x.x.x), whenever I push files onto the /sdcard/ through adb they only stay on the /sdcard/ until I power off the phone (then it disappears). Installing update from zip using these files does not result in any change to the device. I tried installing a new cyanogenmod version but after saying "Installation success" or something like that it still proceeds to load up the old version of cyanogenmod, with the same customized background image and lockscreen (and then proceeds to crash in the same manner as before).
I'm extremely confused why nothing I do seems to produce any change, even using ODIN to try repartition the device and install the stock rom and everything. What's wrong with my phone and what can I do to make flashing actually do something?
So my second zenfone is dead.
Like many others, it gets stuck at the asus loading screen with the spinning wheel.
This did not happen after any obvious action, like an update - it was just turned off when i woke up, and wont load beyond the spinning wheel of death.
I have booted into fast boot mode (power and vol +), selected [recover mode] and got the broken android logo.
I then hit power and vol+, then release vol+ as suggested, but instead of a menu, i get a bunch of yellow console output, 3rd line of which is:
E: failed to mount /cache (invalid argument)
This appears for less than a second, then back to flashing broken android logo.
Repeating ( power and vol+, then release vol+) results in the same briefly visible console output
I turn off, and reboot into fast boot mode, and try using adb.
I enter the command 'fastboot erase cache' and it completes in 0.4 seconds, no errors. Has no effect on phone (reboot stuck loading, recovery mode same error as above).
Next i try 'fastboot format cache' - the command appears to work, but again completes in just over a second, and has no effect on the phone.
The only info i could find directly relating to this error is on a random .info website, so im reluctant to follow the steps:
http://mobilecon.info/fix-asus-zenf...-into-recovery-mode.html#sthash.slqGoK95.dpbs
Anyone here solved this issue? Or is it time for a warranty claim?
Thanks
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
azthemansays said:
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
Click to expand...
Click to collapse
Thanks for the link - it looks much the same as the one i posted, with the addition of flashing the system image.
Do you know if there is any danger in trying without flashing system 1st?
Also, have you used or seen this method used specifically to fix the mount failure i have described, or its just a general 'de-bricking' guide?
Finally, do you or anyone else have any insight into why this might have happened in the 1st place - as i mention, i did not do anything beyond normal use prior to the issue.
thanks
Sounds like the recovery corrupted... could be a range of things from improper shutdown to an improperly coded app that caused the error. If you want to flash just the recovery and see if that fixes it, go right ahead, but don't forget to erase your cache after you flash recovery.
Whenever I get stuck in a bootloop, the steps I follow are:
1) clear the cache and see if it fixes it, as something might be there that's preventing you from booting
2) flash the most current firmware to see if it fixes it, as something might have modified a section of one of the partitions that's preventing you from booting (make sure to clear cache after flashing)
3) contact support because it's more likely hardware failure
There's no danger in flashing any of those partitions, at most you'd lose the Xposed framework, root and busybox - which are easy to reinstall. It doesn't affect much else, and your info should be intact. I would advise getting the firmware from a reputable source though... I just get it off the Asus website, then root the phone after.
Try reinstall recovery
Download stock recovery(there is download link from zenfone2 index)>go fastboot mode>then flash recovery using command :
fastboot flash recovery (recovery image name).img
>Reboot to recovery>adb sideload full firmware
Hello guys, I had bootloop and researching on Google I got into heating Samsung chip to turn it on again. It goes into fastboot mode, and first I got an error:
FAILED (too many links) - When installing system, after various tries I flash it good, but it gets into bootloop again and again and can't go into recovery, do you have any idea how I can fix this?
I really need your help.
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Need info on phone model and current firmware and firmwares you are flashing etc