Hi, i just recently bought a used zenfone 2. It has a really old version of lollipop android (2.13 version) and i want to upgrate to 6.0 android. Problem is i can't get into recovery mode. Everytime i download the update phone restarts, but instead of seeing recovery screen i see usb sign. The phone turns off after a while and tries again-but same usb screen. Getting into it manually i get the same usb screen. What to do? All i can guess that the phone was tried to be rooted and failed, as i found SU program.(Phone itself boots up normally as i should!)
I'm still new to these things, so please keep it as simple as possible and ask anything more you need to know.
here are two things if you think BL is already unlocked download latest TWRP and flash that. if you think BL is locked download recovery image for the same version you are currently on and flash via fastboot
sukhwant717 said:
here are two things if you think BL is already unlocked download latest TWRP and flash that. if you think BL is locked download recovery image for the same version you are currently on and flash via fastboot
Click to expand...
Click to collapse
Well that's the thing, i can't do both ways, cause holding power+volume up buttons i instantly get a usb screen. If I could enter it i wouldn't have any problems. Bootloader is locked, when i start up my phone the asus splash screen is black, not white.
IchiBan360 said:
Well that's the thing, i can't do both ways, cause holding power+volume up buttons i instantly get a usb screen. If I could enter it i wouldn't have any problems. Bootloader is locked, when i start up my phone the asus splash screen is black, not white.
Click to expand...
Click to collapse
one thing did you use xFSTK to recover your device recently? what is your model number? send me you device serial number. do not use xFSTK you may brick completely. after boot check with root checker app from app store if you are rooted. as you stated found su binary on device. and revert me back
Related
followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?
Hello everyone, need a little help if possible .
The say curiosity killed the cat, well… it killed my phone. To be more precise I wanted to know if my 550ml (with unlocked bootloader and running cm12.1) could run a 551ml firmware so… I did install thru TWRP the superzen firmware and after that the screen turned black. Can’t see anything . Not even in fastbootmode, no logo, no nothing. If I turn it on and plug it to the pc it shows, I see the internal memory and the sdcard. It’s gotta be from the different resolution that 550 and 551 have but how do I change it since I can’t see anything?
I did a userdata reset thru fastboot, wiped cache , reinstalled stock recovery ,boot recovery, tried to install stock firmware, still no change. I even managed to enter stock recovery and did an adb sideload of the latest firmware from the asus site.
As for now the phone boots, the capacitive buttons respond, the led indicates that it charges, the pc sees it but no matter what I do the screen remains black. Most likely I’m on the setup wizard but like I said I don’t see anything.
So… What can I do now? To the Asus service with it or …?
I'm not much of a forum user so go easy on me. Thank you.
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
fastmix said:
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
Click to expand...
Click to collapse
Unfortunately it does not work, when i try to sideload a rom with twrp it gives this: error closed. Probably because usb debugging is not enabled... and in cwm different error: Device unauthorized...
Are you sure bootloader is unlocked?
It has to be unlocked cause i can flash permanent TWRP and when I enter TWRP recovery i can touch the buttons, even tried to do a restore in the dark... But nothing... Still the black screen persists... Thank you anyways.
PS: Well it looks like I've managed to resolve my problem. Thanx to user helroz i have found in his google drive a Raw firmware and I was able to flash it via fastboot with Asus Flash tool and now the phone booted, no more black screen for me. Lesson learned.
Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.
I bought my phone from a chinese seller, its the 1.8ghz 4GB Ram and 16gb internal memory version.
It already had the WW version of LL, I followed a guide in the asus forums and reflashed the recovery and the rom from ww (just to be sure it was not in the chinese rom)
Afterwards I did adb sideload to MM. So far so good.
But if I go to the recovery there are several issues, first off when I boot to the recovery it appears the "Error!" screen, I searched and if I power button and volume up quick, I get to the recovery. And before choosing to enter the recovery, fastboot mode??, there are some status messages and they show the product name, variant, etc. Some of them show unknown, BL_Version, HW_Version, Signing, Secure_boot
Is there any fix for this? Is it safe to unlock the bootloader like this? I think I might have a diferent bootloader, ie MM FW with LL BL.
Thanks
dicamarques said:
I bought my phone from a chinese seller, its the 1.8ghz 4GB Ram and 16gb internal memory version.
It already had the WW version of LL, I followed a guide in the asus forums and reflashed the recovery and the rom from ww (just to be sure it was not in the chinese rom)
Afterwards I did adb sideload to MM. So far so good.
But if I go to the recovery there are several issues, first off when I boot to the recovery it appears the "Error!" screen, I searched and if I power button and volume up quick, I get to the recovery. And before choosing to enter the recovery, fastboot mode??, there are some status messages and they show the product name, variant, etc. Some of them show unknown, BL_Version, HW_Version, Signing, Secure_boot
Is there any fix for this? Is it safe to unlock the bootloader like this? I think I might have a diferent bootloader, ie MM FW with LL BL.
Thanks
Click to expand...
Click to collapse
buddy you don't have any issue with your device. and the error screen while entering recovering mode is usual. if you don't like that flash twrp. you will overcome that issue. also fasboot screen showing versions as unknown is also not an issue.
sukhwant717 said:
buddy you don't have any issue with your device. and the error screen while entering recovering mode is usual. if you don't like that flash twrp. you will overcome that issue. also fasboot screen showing versions as unknown is also not an issue.
Click to expand...
Click to collapse
Well I unlocked the bootloader, installed twrp and rooted using the new Toolkit available here and it still says BOOTLOADER STATUS: UNKNOWN in the toolkit window.
Also, now when I boot it theres an error screen saying that cant verifiy some signature, right before asus logo, is it because of the Unlock of the bootloader?
Okay, so i just followed the steps on how to unlock and root my phone and all was going well as i followed all the steps to the letter, however at the end when i tried to reboot my phone it got stuck on the LG screen and will not load up.
I found a similar post on this forum here: https://forum.xda-developers.com/lg-g7-thinq/help/g7-doesnt-boot-flashing-modified-boot-t3872445. However in their case the phone ran out of charge and they were able to get into download mode, my phone however is on full charge so will take ages to die and i cannot seem to access download mode. In the current state the phone is completly unresponsive without me being able to turn it off.
The root guide i use this this one: https://www.theandroidsoul.com/lg-g7-root/ and the .img was also sourced from the link on that site.
Idealy I'd like help to fix this issue continuing with the root, but am happy to reset the phone if that is easier and give up rooting the phone.
For me it sounds like wrong boot.img. I mean from other version of firmware than you have.
If you unlocked bootloader, then you have LMG710EM, but...
What version of firmware you have?
For most of EM variant, newest firmware is v10q, so first try to flash img for q version.
https://drive.google.com/drive/folders/1NtbfxAbYLeQNryPg0odgLa8hBgabrH3j here you have boot images by LameMonster82, and for me it works.
There are two versions of boot.img. Original, and patched. If you want to have root, then flash patched boot.img
So if you don't know which version you have, then flash boot for v10q, if it doesn't work, then v10p etc etc.
Juat plugg the usb cable in the phone.
Hold power and - down for about 8 sec. When it reboot release power. And just hold down - (vol minus). It should Boot into download mode. Timing is everything so keep.trying untill u get it.
Also flash the correct Boot img.