Hi.
Yesterday, i rooted my phone and installed xposed. it worked great. But with that + busybox + amplify + supersu, the game i play a lot didn't let me play (unauthorized program detected).
so i try to delete supersu or amplify, but it still didn't work.
So i uninstall xposed, unrooted my phone.... But it still doesn't work!
so i uninstall the game and try to install it. but during installation (downloading data), it crashed.
So i did a factory reset, tried to install my game, but it always crashes during installation!
I'm desesperate!!! it never did this to me before!
Plus, i'm still in 139 version of asus. I tried to update it yesterday (to 160 version), but it crashed!!!!!!!! and it doesn't want to try to install it again (it's like there is no upgrade)
and there is some buggy moment when the keyboard doesn't appear ect...
I have enough! i desesperaly need help!!! my phone never got problem before except battery, but now, i'm desesperate! i shouldn't have try to root it!
is there something i can do? reinstall root and xposed and remove them with another way?
please, i really need your help ... if i have know it was this troublesome, i wouldn't try anything! i want my phone back!
Please, i really need you... thank you...
Sideload the firmware in recovery mode.
KillerNo2 said:
Sideload the firmware in recovery mode.
Click to expand...
Click to collapse
first, thank you for the answer.
but i'm really a noob... how do you do that? enter recovery mode (power +volume + ?) and then try to update the mobile?
nevew said:
first, thank you for the answer.
but i'm really a noob... how do you do that? enter recovery mode (power +volume + ?) and then try to update the mobile?
Click to expand...
Click to collapse
Follow the instructions in this thread
i succeeded making my game work (at least! i'm so damn happy!) by wiping cache partition.
but when i do "check updates", there is nothing.
But no problem, i'm scared of touching the phone again, i stay with the 139 version >__>.
thanks anyway, but i won't do anything with a computer. my phone can stay the way it is. i'm scared of having problem again... the only thing i'm gonna do, is using apk or this kind of thing. but no root anymore...
nevew said:
i succeeded making my game work (at least! i'm so damn happy!) by wiping cache partition.
but when i do "check updates", there is nothing.
But no problem, i'm scared of touching the phone again, i stay with the 139 version >__>.
thanks anyway, but i won't do anything with a computer. my phone can stay the way it is. i'm scared of having problem again... the only thing i'm gonna do, is using apk or this kind of thing. but no root anymore...
Click to expand...
Click to collapse
Go to the pre-rooted roms thread and download the latest rom.
Make sure you have the fastboot tools, put the rom.img file in there, rename to system.img if it isn't already and flash with fastboot...
1. Hold down volume up and power, keep holding until you get to download mode, press up volume.
2. Connct to PC. Go to the folder you have the fastboot tools in and hold SHIFT then press right mouse button and select "Open CMD window here".
3. Type "fastboot devices", if you have done everything right then you will get the serial number displayed otherwise you need to update drivers.
4 Type "fastboot flash system system.img".
It will break the rom into about 5 parts to flash, just let it go, it will give a prompt when finished...
5. Type "fastboot reboot", your phone will reboot, be updated and have root while leaving all apps there.
Be aware that there may be problems running xposed and that may have been what killed your phone...
If you do install anything, before doing the OTA again, reflash the pre-rooted rom again and you should be able to update with the OTA with no problem...
Good luck...
ultramag69 said:
Go to the pre-rooted roms thread and download the latest rom.
Make sure you have the fastboot tools, put the rom.img file in there, rename to system.img if it isn't already and flash with fastboot...
1. Hold down volume up and power, keep holding until you get to download mode, press up volume.
2. Connct to PC. Go to the folder you have the fastboot tools in and hold SHIFT then press right mouse button and select "Open CMD window here".
3. Type "fastboot devices", if you have done everything right then you will get the serial number displayed otherwise you need to update drivers.
4 Type "fastboot flash system system.img".
It will break the rom into about 5 parts to flash, just let it go, it will give a prompt when finished...
5. Type "fastboot reboot", your phone will reboot, be updated and have root while leaving all apps there.
Be aware that there may be problems running xposed and that may have been what killed your phone...
If you do install anything, before doing the OTA again, reflash the pre-rooted rom again and you should be able to update with the OTA with no problem...
Good luck...
Click to expand...
Click to collapse
thank you for your help!
but i won't do it ^^"...
i don't want to root my phone anymore (too much trouble, and the game i play a lot doesn't like root... i won't try it again. pissed me off 2 days ago that it didn't work even when i unrooted my phone)...
i just wait for the marshmallow update (and hope that the phone will propose me the update and i won't have to make it manually).
i won't try to touch my phone again, i won't do the same mistake...
Related
I know there is a script to get into recovery mode, anyone know if there is one for download mode, or can someone make one, for the phones not able to use 3 button combination. ?
12.My phone cannot enter download mode or recovery mode using the buttons combos. What can I do?
Some batches in various countries seem to not have this feature. Whether this is an intentional change made by Samsung or simply a software error is not completely clear. While some Samsung offices see it as a softwarebug and are claiming that they will release a software fix, others do not acknowledge the issue and so not replace phones without the fuction. If you are one of the unfortunate group who cannot use the button combos (VolumeUp+Home+Power for recovery and VolumeDown+Home+Power for download mode), you can use the commands "adb reboot recovery" and "adb reboot download" to get into the respective modes (See Post#3 for a step-by-step tutorial on using ADB). However, if you cannot enter download mode by using the button combo, you will NOT be able to recover from a failed flash! Since this is a rather common occurance, I strongly advise you NOT to flash your phone using the adb reboot download command!
Click to expand...
Click to collapse
Read the big faq
Ahh ok, ty.
I will try that.
Ok i have a small script for you to use! but read the WARNING below!
IF the flash fails... you won't be able to restore or reflash your phone and it WILL be bricked. Because your not able to go into download mode anymore.
So use it at your own risk (generally flashing is pretty ok and safe with odin and it has never failed for me!) But thats just my experience. If your pc crashes or you get unlucky any other way.
Anyway script is in this post! Download it but don't spread without a warning it because it is very dangerous and similar to Russian roulette.
Instructions:
1) Put phone in USB Debugging
2) Connect Phone
3) Download script and unzip it somewhere
4) open Reboot recovery.bat
also you could just use adb. i guess this is what BackfireNL's script does, so just to give you all the information:
Code:
adb reboot recovery
or
Code:
adb reboot download
is what you want
And it must be said, since you dont have access to the 3 button combo, you have only ONE shot of getting this right.
Thx, this is just what I was looking for.
I have flashed my own sgs tons of times, never had any problems, this is to be able to flash a friends phone(lacks 3 button comb.)
I have the same problem and i tried adb reboot download, but not working.
It worked with rooted firm, but without the 3 button i cannot root the new firm, so this command not works.
Any useable advice?
krisz222 said:
I have the same problem and i tried adb reboot download, but not working.
It worked with rooted firm, but without the 3 button i cannot root the new firm, so this command not works.
Any useable advice?
Click to expand...
Click to collapse
I am quite certain that I went into recovery mode using ADB without root. Then of course I rooted.
sorry for my last message
i was able to flash the new firm because i used this command
but now adb refuse it, i thought its because its not rooted...
but now i have "no way out"....cannot flash recover or root...
a new kernel can fix this? or what should i do?
USB-Debugging enabled?
Settings -> Applications -> Development -> USB-Debugging
I've been trying to follow
http://forum.xda-developers.com/showthread.php?t=835971
But in order to go into bootloader, i need to hold volume down and power (Which is broke)...
What i tried was, "adb reboot bootloader"
which goes in bootloader but doesn't scan like the guide says... and from there i'm lost.
Any help is appreciated.
oh wow. so you cannot manipulate your power button at all? no tweaking or pushing in with something else (is the button still there or did it break off?
warning -- do not do this -- im just trying to be helpful but I am probably not.... dont do this on my account.
well im looking in TJWorld... please dont do this without a real dev taking a look at this
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess#FastBootRestart (Chain Operating System down 1/4 of the way)
in so many words connect serial-usb-to control Hboot (need linux host)
screen /dev/ttyUSBO
press enter till you see "hboot"
and then basically I guess just like in GOTO language
gotofastboot
or
gotohboot
and then theres OEM Reboot Codes
-reboot=oem-1F Regular reboot
--reboot=oem-42 HBoot menu
--reboot=oem-74 In some indeterminate state, for all intents and purposes powered off or just plain dead
--reboot=oem-76 Wipe data and cache (factory reset) Amber and Green LEDs flash whilst it is doing it, then the device reboots
--reboot=oem-78 ??
I hope this helps at all..
The buttons there, you can press it as hard as you want but nothing. Just no response
I have this exact problem!! It's been sitting in my room collecting dust. If anyone can find a fix.. a cup of coffee on me!
My power button is also in perfect condition, I've compared it to another G2 and the button's "press feel" is exactly the same.
why dont you just remap the keyboard and map the camera button as power
^^ i thought the power button combo is not remappable....
and that Its only mapped within android not for the default system combos
Do you have CWM? If so, the phone should turn on when it is plugged into a power source.
^^ Do have CWM, problem is not the phone turning on... the problem is I have no usable power key to follow the guide to unroot and put a stock rom on so i can send it in for warranty.
Using keyboard I can turn on the screen so thats do-able... but restoring to stock + removing root is what I'm trying to ultimately achieve.
i think theres an app thts called quick boot maybe tht could help...
Could you not flash the zip file from within rom manager. By selecting install rom from SD Card, you avoid needing to use powerbutton to get into bootloader. Correct me if you cant do this.
I tried flashing from CWM and error... rom manager didn't reboot it to CWM to flash, so not sure what to do.
This is what I have tried --
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
on hex editor the version is 1.19.531.1, and it already was so i didn't need to change it. But when i try putting that zip through cwm it doesn't work.
I've tried adb reboot bootloader , but it doesn't scan for PC10IMG which i downloaded from the guides....
Torob said:
I tried flashing from CWM and error... rom manager didn't reboot it to CWM to flash, so not sure what to do.
This is what I have tried --
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
on hex editor the version is 1.19.531.1, and it already was so i didn't need to change it. But when i try putting that zip through cwm it doesn't work.
I've tried adb reboot bootloader , but it doesn't scan for PC10IMG which i downloaded from the guides....
Click to expand...
Click to collapse
Which version CWM have you got on there? If its 3.0 I dont think you can flash a froyo rom with that. You would have to install an earlier version.
You can remap the power button with the button remapper app it cost 1.04$ it works fine for me even if you turn off your phone u can use camera button to turn it on, I got the app for free if u dnt want to spend but I cannot post the apk I'm using my phone right now just search it on google beansoft button remapper
http://forum.xda-developers.com/showthread.php?p=11021708#post11021708
My posted app.. hope this helps
i don't think remapping keys will work. It's a hardcoded thing the power+volume key during boot. What i don't get is the fact that hboot doesn't find the file. did you rename it to PC10IMG.zip?
thats the only filename hboot understands as an update or new rom. (Be shure to follow the original guide)
edit: tried myselve.. it doesn't go to hboot does it.. you have to select with powerkey
how can we just make the phone crash? to leave no trace of root or anything of the sort.
Possible solution
Hi !
While I am still thinking about a solution how you could boot into hboot (by using adb reboot bootloader you boot into fastboot mode and not hboot mode) the following might be a solution.
I can not test it because I don't have windows but this is what might work:
1. You need windows and you need the USB drivers from HTC Sync (You can get that here http://www.htc.com/uk/supportdownloadlist.aspx?p_id=325&act=sd&cat=all
2. You need a Desire Z RUU:
You can get one from here http://shipped-roms.com/index.php?category=android&model=Vision
Select any WWE I would probably use RUU_Vision_HTC_WWE_1.22.405.1_Radio_12.26.60.1301_26.02.00.24_M2_release_151197_signed.exe
3. You need the G2 Stock ROM zip, i.e PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
The procedure is the following:
1. Install the HTC Sync so that you have the USB Drivers installed
2. Start the RUU and let it do it's job until the Welcome Screen apears.
At this moment you should have a directory in C:\C:\Documents and Settings\<your user>\Local Settings\Temp\{some-CLSID}\{another-CLSID} that contains a file called rom.zip.
Delete this file and copy the PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip to the directory and rename it to rom.zip
3. Connect you phone to the USB and on the welcome screen check the checkbox and continue.
If I am right the RUU should update your phone using the G2 rom.
As said, I am blind driving cause I ain't got Windows but this might work.
have fun Guhl
ACMilan07 said:
how can we just make the phone crash? to leave no trace of root or anything of the sort.
Click to expand...
Click to collapse
Well there is an option if you do have the engineering hboot installed.
DO NOT TRY THIS BECAUSE THERE IS NO RECOVERY FROM THIS BRICK
1. boot the phone into fastboot mode by using
Code:
adb boot bootloader
2. use fastboot do completely erase the emmc
Code:
fastboot oem fdisk_emmc
After this the phone will be completely erased and will not even know that it is a phone anymore. You can send it in and have it replaced and no one will ever know how your phone got bricked like this
And again: There is no way to recover from this state !!!
Torob said:
I've been trying to follow
http://forum.xda-developers.com/showthread.php?t=835971
Click to expand...
Click to collapse
Last thing I wanted to add is that the probably better way to unroot and go back S-ON, CID and restore SIM-Lock is described in the wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
guhl99 said:
Well there is an option if you do have the engineering hboot installed.
DO NOT TRY THIS BECAUSE THERE IS NO RECOVERY FROM THIS BRICK
1. boot the phone into fastboot mode by using
Code:
adb boot bootloader
2. use fastboot do completely erase the emmc
Code:
fastboot oem fdisk_emmc
After this the phone will be completely erased and will not even know that it is a phone anymore. You can send it in and have it replaced and no one will ever know how your phone got bricked like this
And again: There is no way to recover from this state !!!
Click to expand...
Click to collapse
SO THIS WILL WORK?? THERES NO WAY FOR THEM TO FIND OUT IT WAS EVER ROOTED??? im in shock, seriously?
***EDIT***
DOES NOT WORK. Anything else specific?
ACMilan07 said:
SO THIS WILL WORK?? THERES NO WAY FOR THEM TO FIND OUT IT WAS EVER ROOTED??? im in shock, seriously?
***EDIT***
DOES NOT WORK. Anything else specific?
Click to expand...
Click to collapse
This does not work?
Do you have the engineering hboot installed? (hboot or fastboot has to say VISION PVT ENG S-OFF)
Does
Code:
fastboot oem ?
show INFOfdisk_emmc ?
Hello !
Here's my prob :
I installed CWM Recovery on my OUYA, and then i wanted to flash a ROM via recovery.
Unfortunately, i've done a full wipe while in recovery, and restarted the console.
Now it's turning on, with the power button on, black screen, and identifyed as an MTP USB device.
I tried the alt + Sysreq + i trick, but it doen't seems to work here ...
Any chance to get it back to life in other way ?
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
imerrn said:
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
Click to expand...
Click to collapse
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
ElMeteK said:
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
Click to expand...
Click to collapse
Try these timings. I had the same issue and these worked for me. The keyboard trick is currently your only hope.
I keep pressing alt + sysreq + i keys at the same time takes me about 30 times to get to recovery the light will flash one time then i know im in recovery some times iget the ouya smile with a ! mark some time a black screen then i press home button to get to recovery push the home button again it goes away i have done about three ouya.
Problem solved.
My ouya doesn't loved my Microsoft Keyboard...
I used a generic on, and it works directly
Ouya saved
Another advice : if it doesn't work, try another keyboard !
Ouya Bricked Need Help Reward For The Fixer
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
labossiere said:
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
Click to expand...
Click to collapse
You have to fastboot the "boot.img" supplied with CM10. I had the same issue so pm me if you need help.:good:
Never, ever ever ever ever ever wipe the boot.img, if you want to be safe, never replace it either, you can always 'fastboot boot boot.img" it.
Sent from my SAMSUNG-SGH-I317 using xda premium
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
glitchhawk said:
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
Click to expand...
Click to collapse
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
ok, cuz im basically in the same boat as everyone else. i flashed CM10 and now its hanging at the CM boot screen. so i guess its time to sit there and tap keys for hours lol.
BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
glitchhawk said:
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
Click to expand...
Click to collapse
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
BUS DR1V3R said:
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
Click to expand...
Click to collapse
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
glitchhawk said:
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
BUS DR1V3R said:
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
Click to expand...
Click to collapse
well this is lame.. it keeps telling me Error: Closed
glitchhawk said:
well this is lame.. it keeps telling me Error: Closed
Click to expand...
Click to collapse
What keeps telling you that? What are you doing? I need more information.
BUS DR1V3R said:
What keeps telling you that? What are you doing? I need more information.
Click to expand...
Click to collapse
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
glitchhawk said:
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
Click to expand...
Click to collapse
If it says <waiting for device> then its probably a driver issue with fastboot. When you reboot into the bootloader go into device manager and check the driver again. I also had this issue.
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
Hi guys, I have an issue with my Zenfone 2 (ZE551ML).
I flashed CyanogenMod 12.1 and everything was working fine. That is, until I decided I wanted to go back to stock ROM. That's when everything went wrong.
1) I went into recovery mode (using Power + Volume UP).
2) I wiped cache partition (probably my first mistake)
3) I restored to factory settings (possibly my second mistake)
4) After this I tried to flash the "recovery1.img" of the stock ROM I had.
5 ) That didn't work so I tried using ADB to flash different ".zip" files (all firmware downloaded from Asus website)
When that didn't work either, I abandoned and rebooted the phone. But it doesn't boot anymore.
It is stuck on the Asus screen and nothing happens.
Does anyone know if and how I can get out of this situation?
I must insist on the fact that I am only a novice. Until now I've only ever known iOS and have no knowledge whatsoever of how Android works.
I already posted my question here ("http://forum.xda-developers.com/general/xda-assist/possibly-softbricked-zenfone-2-t3248318") and was told I might want to try posting it here as well. I hope one of you can help me repair my mess !
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
shawnchalfant said:
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
Click to expand...
Click to collapse
Thanks for the reply. Do you have a link for the one click root with CWM Recovery ? Can't seem to find it... Also, when I connected my phone to the computer and opened oneclickroot (basic) it says my phone needs to have USB debugging activated (which it did).
I can't get into recovery mode anymore, the phone just loops back to fastboot with no error message.
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
shawnchalfant said:
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
Click to expand...
Click to collapse
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Boot into fastboot, Vol Up + Power, once it vibrates quickly press and hold volume down a few seconds. Fastboot should appear. Then run the batch file. Adb does not run in fastboot mode.
m3j said:
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Click to expand...
Click to collapse
there is still hope ... go for a lower version of recovery, boot (flash it in fastboot) and then keep the rom by keeping it in the external sd card renaming it to MOFDS_Update (i dont remember the name ). flashing should be done on its own...
search "Tutorial Upgrade / Downgrade / Unbrick Zenfone 2" in Asus ZenTalk. it helps for me
Thank you all for trying to help but I wasn't able to repair the phone.
I sent it back and by some miracle they accepted to give me my money back. Buying a new one now but I won't do anything stupid with it this time !