can somebody tell me how to boot into recovery in my xperia arc
is by holding buttons
or download some app ???
thx ^_^
Hi, I've the same issue here:
Tried with fastboot and the boot the recovery Image: just starts normal
Then i tried pushing vol up / down during starting, just starts standart
I rooted mine with rooted rom, then tried other programms (with root access) to get into the recovery mode: also just standart booting, no recovery mode.
omaritta said:
can somebody tell me how to boot into recovery in my xperia arc
is by holding buttons
or download some app ???
thx ^_^
Click to expand...
Click to collapse
if u have working recovery then use this:
http://forum.xda-developers.com/showthread.php?t=1123576
I think thats the point: how to get the recovery menu working??
I've got installed quick reboot as well as xperia reboot but none of them is working.
I tried yesterday at home via fastboot tool with the commands mentioned in the root for all arc's thread and the relevant files to get into the recovery mode, but no chance.
It seems that i've to try the files mentioned in the other thread http://forum.xda-developers.com/showpost.php?p=14903452&postcount=169 by binary this afternoon at home. basically at my corporate laptop its not allowed to install uncertified drivers.
merlin667 said:
I think thats the point: how to get the recovery menu working??
I've got installed quick reboot as well as xperia reboot but none of them is working.
I tried yesterday at home via fastboot tool with the commands mentioned in the root for all arc's thread and the relevant files to get into the recovery mode, but no chance.
It seems that i've to try the files mentioned in the other thread http://forum.xda-developers.com/showpost.php?p=14903452&postcount=169 by binary this afternoon at home. basically at my corporate laptop its not allowed to install uncertified drivers.
Click to expand...
Click to collapse
you need to unlock the bootloader before you can use recovery via your pc. see how to:- http://forum.xda-developers.com/showthread.php?t=1034087
This will install the necessary drivers also, that will allow you to use fastboot, you will need to install unsigned drivers. Download the img from your link. Then you can reboot into fastboot via holding the required button or using doom's app, make sure you have the usb lead in. Then with the img in same folder issue the command fastboot boot recoveryARC.img via command prompt window. Both links explain it.
my bootloader is unlocked, otherwise it would not be possible to write it at least onto the phone.
I allready did everything at home where I'm possible to install uncertified drivers.
I already flashed via fastboot the updrade to 2.3.3 as well as yesterday the rooted 2.3.3
Also tried doom's app, nothing changes.
just for confirmation here are the steps i did on the arc since the beginning:
Unlock bootloader, beginning of May (since when it's available)
rooted 2.3.2
upgraded to 2.3.3 via fastboot (root lost)
now the steps from yesterday:
Phone off
CMD: fastboot boot recovery.img
connected phone with USB cable and pressed menu button
Blue led on
at the CMD window recovery.img was shown as transfered to device
Arc was rebooting, but not into the recovery mode.
basically i'll try today with a different recovery img maybe thats the reason.
merlin667 said:
my bootloader is unlocked, otherwise it would not be possible to write it at least onto the phone.
I allready did everything at home where I'm possible to install uncertified drivers.
I already flashed via fastboot the updrade to 2.3.3 as well as yesterday the rooted 2.3.3
Also tried doom's app, nothing changes.
just for confirmation here are the steps i did on the arc since the beginning:
Unlock bootloader, beginning of May (since when it's available)
rooted 2.3.2
upgraded to 2.3.3 via fastboot (root lost)
now the steps from yesterday:
Phone off
CMD: fastboot boot recovery.img
connected phone with USB cable and pressed menu button
Blue led on
at the CMD window recovery.img was shown as transfered to device
Arc was rebooting, but not into the recovery mode.
basically i'll try today with a different recovery img maybe thats the reason.
Click to expand...
Click to collapse
I explain again!
MY RECOVERY IMAGE (your link above post #169) is a recovery boot only, NOT FLASH! just fastboot boot.
The FreeXperia kernel incl. recovery is only for flashing, NOT BOOT!
So you have 2 easy options, but i provided the boot only version to help stock users to have a recovery!
Not other recovery image that MY POSTED can be used to fastboot boot into recovery.
Regards
So, finally i got it working:
In my case its only possible to get into the recovery mode via following setup:
Connect arc with fastboot mode (unlocked bootloader necessary).
recovery.img from this post: http://forum.xda-developers.com/showpost.php?p=14903452&postcount=169
then
cmd: fastboot boot recoveryARC.img
then i get into the
thats it.
The app from doom is not working in my case. tried it now twice (once USB cable connected, once not), not working in any case.
If you get the first sony ericsson screen it was not working. it needs a while on a black screen (longer than waiting normally for sony ericsson) but then you're directly in.
Exactly the reason my lg is with me for the last days, just flash roms with 'rom manager' and playing with it and test things... Arc is to complicated for me to get this to work...
sent from arc or optimus 2x
It's not like someone has step-by-step instructions in, say, a guide...
I know, like I said, very complicated, especially when you only have an imac as computer at home and your laptop is broken:-D, so not able to open .exe files at the moment....
for lg I only needed to root and install "ROM manager", even people like me can use that. Plenty of roms and there you go.
For now I themed with uot kitchen, but this is the first time in two days I picked up my arc again just because the lg with custom rom is lightning, blazing fast and smooth...
sent from arc or optimus 2x
That wasn't really aimed at you so much as the OP, though I guess it applies to you too
Lol
sent from arc or optimus 2x
Related
Hi.
Hoping someone can help.
Struggling a little to get my Play rooted (not new to Android but coming from a HTC Desire where everything is pretty much done for you with one click tools etc)
I have unlocked the bootloader (Jinx13) and sim unlocked (was 02 - now using t mobile sim).
After unlocking bootloader I accepted the 2.3.3 (UK) update using SE Companion Tool (was this a mistake?)
Now trying to install the FreeXperia Recovery. I have installed the Android SDK and I'm pretty sure the driver is right (sa0102adb). If I type command "ADB Devices" I get a serial number returned so I presume ADB recognises the Play. However when I type the command to load the recovery (as per ClockwordMod recovery thread) ADB states "waiting for device" and I can go no further.
Any help would be much appreciated.
will.
You need to do it with fastboot (hold search button and plug usb - blue light) not adb and you can't install/flash that image you need to boot it. If you flash it you'll brick your phone. Ohh you need to download fastboot package and set it up. Try to look in the 'how to unlock your bootloader' thread for download link and 'how to'.
The play doesn't got a recovery partiton and therefor you can't install it as the recovery is part of the boot.img afaik. It's not like HTC where you have your S-ON/OFF and engHboot and can install a custom recovery. So on the play you can only boot CWM and then flash .zip files from there or flash Doomlords kernel as CWM is embeded in the kernel (boot phone, spam volume up/down when you see the splashscreen).
Regards Dousan...
Thanks
It was the ADB v Fastboot that confused me! I had downloaded Fastboot but had not installed the drivers for fastboot (only the ones for ADB). I now have a superuser app showing so all appears to be well!
Thanks very much.
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.
Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.
were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.
you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium
not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper
I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.
Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.
did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?
I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"
My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?
Have I bricked my xperia-zl?
(originally posted in the wrong place, one of the members directed to repost it here)
1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101
2. Successfully unlocked the bootloader
3. Used Flashtool to Iinstall CWM
4. Now my phone
a. does not boot: tried all combination of switches, including the yellow button next to the SD Card
b. is not recognized by flashtool any more
c. not recognized by Sony PC companion
d. no light/indication when put to charge.
5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?
Want help, desperately.
r_s_dhar said:
Have I bricked my xperia-zl?
(originally posted in the wrong place, one of the members directed to repost it here)
1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101
2. Successfully unlocked the bootloader
3. Used Flashtool to Iinstall CWM
4. Now my phone
a. does not boot: tried all combination of switches, including the yellow button next to the SD Card
b. is not recognized by flashtool any more
c. not recognized by Sony PC companion
d. no light/indication when put to charge.
5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?
Want help, desperately.
Click to expand...
Click to collapse
I'm sorry to say that, but you're still in the wrong place, you need to go there:
http://forum.xda-developers.com/xperia-zl/help
Anyways, did you flash the correct kernel? Or did you just try to flash a recovery?
St.Jimmy90 said:
I'm sorry to say that, but you're still in the wrong place, you need to go there:
http://forum.xda-developers.com/xperia-zl/help
Anyways, did you flash the correct kernel? Or did you just try to flash a recovery?
Click to expand...
Click to collapse
St.Jimmy,
I am a first time member, joined only yesterday (that is after my tail caught fire!); sorry to be still in the wrong place. Could moderators please relocate my post to the right location? Thanks a million to this wonderful site.
Thanks for the reply. I think installing CWR required flashing a "boot.img" file. The device gave up its ghost after flashing the boot.img file. As of now, there seems to be a slight improvement -- there is a red LED indicator that has come on when put to charging; it is faint, but it is there alright! Any chances of resurrection or is my phone really gone to its Heavenly Kingdomo?
I suggest u first charge it for 1-2 hours and then try using flashtool
Sent from my MT25i
kedar a.k.a. 3K said:
I suggest u first charge it for 1-2 hours and then try using flashtool
Sent from my MT25i
Click to expand...
Click to collapse
Kedar,
Thanks. I have charged my phone overnight (10 hours). Still LED glows red. For a while I could connect in flashboot mode (LED=blue). Any help?
r_s_dhar said:
Kedar,
Thanks. I have charged my phone overnight (10 hours). Still LED glows red. For a while I could connect in flashboot mode (LED=blue). Any help?
Click to expand...
Click to collapse
I can now sometimes connect in flashboot mode; flashtool initially recognizes the phone but when I try to flash a stock ROM, asks the phone to be connected (as if it has not already recognized the phone)! HELP PLEASE!!
r_s_dhar said:
Have I bricked my xperia-zl?
(originally posted in the wrong place, one of the members directed to repost it here)
1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101
2. Successfully unlocked the bootloader
3. Used Flashtool to Iinstall CWM
4. Now my phone
a. does not boot: tried all combination of switches, including the yellow button next to the SD Card
b. is not recognized by flashtool any more
c. not recognized by Sony PC companion
d. no light/indication when put to charge.
5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?
Want help, desperately.
Click to expand...
Click to collapse
might have a solution for the recovery if the fastboot is working
download minimal adb and fast boot from here
place boot.img in minimal adb and fast boot folder after installation
Put your phone in fastboot( hold power up key and plug usb)
open minimal adb and fast boot application
it will open a cmd window
type fastboot flash boot boot.img
after that type fastboot reboot
your phone will restart now
PS: your phone is refusing to boot because the recovery is corrupted
What if you fastboot a custom kernel with inbuilt recovery and then flash a Rom with the recovery?
Since you have fastboot working
Sent from my MT25i
---------- Post added at 07:53 AM ---------- Previous post was at 07:49 AM ----------
What if you fastboot a custom kernel with inbuilt recovery and then flash a Rom with the recovery?
Since you have fastboot working
You may try the method by @androidtweaker mentioned above as it is similar :thumbup:
Sent from my MT25i
First, what exactly did you flash to your phone and where did you get it from?
Sent from my C6603 using Tapatalk
Androidtweaker1: Thanks. Cannot connect in fastboot mode. The blue LED comes on but the device is not recognized (adb drviers etc. no problem, all correctly installed, all set).
kedar: cannot connect in the fastboot mode. See reply to Androidtweaker1 above. Thanks
kingvortex: Thanks. I was trying to follow the following tutorial:
After downloading Z_DooMLoRD_AdvStkKernel_FW-4.3-101_v12.zip, place it in external SD Card of your smartphone
Now extract Z_DooMLoRD_AdvStkKernel_FW-4.3-101_v12.zip on your PC’s desktop and copy boot.img
Paste this file inside the folder where you have installed Minimal ADB and Fastboot
Now turn off your smartphones completely
Plug in mobile’s USB in cable in PC port only
Hold Volume up button and plug in USB cable in mobile’s port
LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above
Once you are successfully in fastboot mode, then you can continue
Now type Fastboot flash boot boot.img and press Enter
It will flash boot.img file on your device
Now unplug the device and boot it up
As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode
In CWM Mode, select “Install Zip”
Now select the storage you have put that zip file in and just confirm its installation
There are two ways to navigate in this CWM recovery
You can navigate with volume buttons and make a selection with power button
Another way of navigating is by swiping your finger on empty area in recovery
Swipe up to move up, swipe down tp move down, swipe right to make a selection and swipe left to go back
After installation is complete, go back to main menu and reboot your smartphone
Congrats! You have successfully installed CWM custom recovery on your smartphones
I have a similar situation and I'm stuck.
Q: is working the minimal adb if in the settings was not checked the debug mode?
In my case I can go in fastboot mode each time but not help.
When I try to go in flash mode, there is strange because the flashtool say it it connected in flash mode , even the PCC say this, but the LED it's not green, is off, first is try to go green after get red and after off, but the software say is in flash mode.
I can try to flash any ftf, it's working without erors but my phone it's still dead after restart, even SONY logo is not appear, just vibrate once.
Other strange think, each time when I made a new flahing, there is a status message of device, it say that the version of ftf is 230 even if last time I was tring to flash 101 for ex and was finished without errors. Always show the same ftf version like nothing is changing inside. The only thing can change is the BL, lock or unlock and I can see this in the status device, this is made in fastboot mode and there I have the blue LED.
Can anybody give me some ideeas to fix this?
have the log of flahtool attached.
Thanks.
SOLUTION
remav said:
I have a similar situation and I'm stuck.
Q: is working the minimal adb if in the settings was not checked the debug mode?
In my case I can go in fastboot mode each time but not help.
When I try to go in flash mode, there is strange because the flashtool say it it connected in flash mode , even the PCC say this, but the LED it's not green, is off, first is try to go green after get red and after off, but the software say is in flash mode.
I can try to flash any ftf, it's working without erors but my phone it's still dead after restart, even SONY logo is not appear, just vibrate once.
Other strange think, each time when I made a new flahing, there is a status message of device, it say that the version of ftf is 230 even if last time I was tring to flash 101 for ex and was finished without errors. Always show the same ftf version like nothing is changing inside. The only thing can change is the BL, lock or unlock and I can see this in the status device, this is made in fastboot mode and there I have the blue LED.
Can anybody give me some ideeas to fix this?
have the log of flahtool attached.
Thanks.
Click to expand...
Click to collapse
Hey, have you already solved your problem? I had the same as you and I could fix it, I will try to submit a post here explaining the steps I followed
I solved but in other way. I bought another Zl with the battery dead and I replaced the motherboard. I have it now working from gew months without any problems. The old motherboard is still broken.
Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.
Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?
I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!
anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )
Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!
np...
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)