Related
just bought my evo 4g today it came with 2.2 androind i followed this tutorial
http://forum.xda-developers.com/showthread.php?t=829045
averything goes like its supposed to b euntill the last step
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
Ithis all this but sinc ethe start i kept getting to errors for radio and another one at the bottom
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is the stock unrooted rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
at this point i believe im rooted it says off on the top on my evo instead of on.
but when it restarts it gets stuck at white screen with htc evo 4g messege. i havnt flashed a rom i though i could just leave it like this. when i get to recovery from the bootmenu it only shows the red triangle with no options.
please any advice will be apreciated
q and a please !
CheesyNutz said:
q and a please !
Click to expand...
Click to collapse
i been looking everywhere cant find solution!!!
search Amon RA EVO and try to flash it via fastboot
1. go into the bootloader and make sure you have the fastboot drivers installed to your computer
2. download the latest amon ra recovery i think it is 1.8.0 then copy to the android sdk\tools folder on your computer
3. fastboot flash recovery recovery-RA-evo-v1.8.0.img
4. ???
5. profit
ty for the help I just went ahead and changed it for a new one today after 5 hours of buying it lol.
ill tryit again later to for helping.
is that supposed to be normal or did i ****d it up?
Commonly referred as a boot loop and yes it happened to me. And I fixed it with what I said earlier.
nice that mans the recovery is the one ****ing up? im scared to try it again and not be able to fix it, by the way what is the step 4. ????
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
chmod 0755 /data/local/flash_image
you need to run this via adb on your computer
1. for me I GO into windows 7 command prompt type cd which is change directory to the folder i have the android sdk folder in which would be "cd c:/androidsdk/tools" no Quotes
2. type "adb shell"no Quotes
3. you should see # or $
4. type "chmod 0755 /data/local/tmp/rageagainstthecage" no Quotes
5. type "chmod 0755 /data/local/flash_image " no Quotes
6. done
when the evo was first rooted there was a tempory recovery you could load on your phone but it had to be connected to your computer i dont know just trying to throw out ideas. http://forum.xda-developers.com/showthread.php?t=690762.
to try
Assuming you have windows like me
1. download files
2.go into bootloader press recovery if you see a red triangle continue if you dont and you see options your set
3. right click on recovery-windows.bat and click adminstrator perrmissions.
4. you should see the red triangle change into a green menu
TIPS
this is only tempory it will not work until you load it from the computer agein
I dont know if it will work
ty i found about that .bat for recovery and used it. i flashed some recoverie plus a rom but it was still the same. i changed it for a new one im not so sure about trying it again. "ALTHOUGH i wont hold myself for more than a couple days"
really ty for your help and support im saving this for when i take my pretty white evo 4g to the dark side
No problem glad to help
I have been searching and reading, but I still am unsure of which rooting method I should use. I just got my "new" EVO on Friday. Here are my specs:
HBoot 2.2
Hardware 0003
Baseband 2.15.00.09.01
Kernal [email protected]#17
Software 3.30.651.3
Any and all help would be greatly appreciated.
You have two choices:
option 1. Follow the directions and root your phone using these instructions that I copied from the thread below and use the following link to download the correct files: (http://forum.xda-developers.com/showthread.php?t=829045)
option 1 is not recommended for a noob...
option 2. Wait for unrevoked to come out with their update to unrevoked 3. If you wait, almost all of the root process will be automated. Unrevoked should be releasing this update in the next couple of weeks or so. They have been tweeting about it.
Directions from option 1 copied from thread link above:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V71.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V71 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
GOOD LUCK!
Thank you very much. I had been looking at the three different methods, I just wasn't sure which one to go with. I'm downloading the files now, but won't be able to do the thing until i get home. I had a Hero for the longest, and rooting that was pretty simple, but when I got the EVO and looked at the forum; I knew it wouldn't be quite as easy. I just wanted to be certain before I bricked my phone trying to fly blind. I'll let you know how it turns out. Thanks again, I really appreciate it.
You are welcome! I am sure you know this, but make sure you read through the thread first so you can see other hangups other people are having before you start the rooting process. If you have rooted a phone before, I am sure you can root the evo. Good luck!
Worked like a charm. 30 minutes, and I'm rooted. That went easier than I expected. Thanks again!
you are welcome...good luck with choosing a rom kernel combination. I dont flash a new rom or kernel very often (once a month) but right now i have myn 2.2 for a rom and baked battery #5 for a kernel with some setcpu profiles and it works great! I can get a full day of 10 hours of heavy usage (connected to exchange all the time) and lots of texts, web browsing etc and still have 20% battery left
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
what version is your hboot?
jay-are said:
I rooted my evo yesterday. I have super user and titanium backup but it still shows s-on. How do i change this. I used unrevoked.
Click to expand...
Click to collapse
if you still got s-on then you might need to run unrevoked forever. just go to this site.http://unrevoked.com/rootwiki/doku.php/public/forever and run the correct update.zip like you would another rom or kernel
weaselp1 said:
what version is your hboot?
Click to expand...
Click to collapse
i dunno about him. (y must i assume its a dude n not a female on these boards... tsk tsk) but i have hboot 0.97.000
I feel as if i missed my window of rooting my fone when i should of.. now theres a 1000 and 1 threads on the newer versions for newer fones.. and yes i've 'been' reading most of them.. and its all starting to stick. **and whats this i hear about the newer evo screens being more brilliant? anyways, can i follow those same directions u posted? 30 mins doesnt sound bad. even tho 30 seconds with unrevoked is pretty enticing. thanks for your time and effort. might even give u an actuall "thanks" above ur name. just seen those recently and been wanting to give em a try.
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Sent from my PC36100 using XDA App
Some people are having trouble using unrevoked-forever on hboot 2.10 saying that their radio is not supported. Some people have not had trouble and the root worked fine. So, make sure you root before updating to the latest build.
weaselp1 said:
the reason i asked what version your hboot is: if you have hboot 2.02 or 2.10 you cannot use unrevoked at this current time; you must use the above method. I just wanted to make sure you had the correct hboot to use unrevoked. I have had a friend who made this mistake, and it broke his 4g and he had to get a replacement.
as far as using th above method, unless you have hboot 2.02 or 2.10, I would advise agianst it.
Click to expand...
Click to collapse
So with me having such an older hoot - 0.97.000, u would recommend what...?? Unrevoked? Thanks for ur time.
Yes, use the unrevoked method because of the version of hboot you have
Sent from my PC36100 using XDA App
warnning: any damage you do to your phone following these directions is your responsibility. Assume you warranty is void if your are rooted.
I used the information koush provided here and info birdman provided here and adopted it in Ubutnu Linux 11.10. I hit some bumps along the way using my Linux box so I decided to write this for those of us not using OS's made by the darkside This should also work with Ubuntu 12.04 LTS just fine.
All this should work with Linux Mint 12 also.
1- Set up Android SDK, adb, and fastboot in Ubuntu Linux using the links in my signature. I can't stress how useful and easy it is to set adb and fastboot in your "path" so you can easily use it from any prompt. The links explain it. Take your time with that and it will payoff for all your devices. Here is the guide I wrote http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
2- on your phone, go to settings/Developer Options and check the box for USB Debugging
3-connect your phone, fire up a terminal, and type:
Code:
adb devices
You should get the serial number of your device appear. If not, unplug, reboot phone, re-attach the phone to your computer and try again. If you still do not get your device's serial number, go back to step 1 and make sure everything is setup correctly.
4- Now download Clockwork Recovery from here
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
(make sure it's the CDMA one (toro). The GSM one is called maguro and steps should be the same)
and su.zip from here
http://download.clockworkmod.com/test/su.zip
5-Turn the phone off, hold both Volume up and Volume Down and press the power button. You should come to a screen that has a big arrow and some writings at the bottom (fastboot). Last line should say Locked state.
6- Connect your phone to your computer, fire up a terminal and type:
Code:
fastboot devices
your phone and its serial number should appear just as it did using adb above. adb will not work here of course. If you don't see your device, go to step one. I guess you can download the fastboot for linux and cd to that directory and do it but I like to have it setup on my computer.
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
7- Now for the stuff that voids your warranty: Type
Code:
fastboot oem unlock
and enter. Look at your phone now, use the Volume up to choose YES and press the power button to accept. It should say that you are unlocked and fastboot is in good state.
9-use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
10-you are now unlocked. Turn the phone off ( I pulled battery), go to fastboot screen by holding volume up, down and power button. Connect your phone to your computer and make sure it is recognized by typing:
Code:
fastboot devices
If it is, change directory to where you downloaded clockwork recovery. If you didn't change it, it should be the Download directory (remember it's case sensitive):
Code:
cd Downloads
11- Time to re-write your recovery:
Code:
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
Please make sure you use common sense here when it comes to file names. If the file you downloaded has a different name or version, change it in the code above. I guess you can put the fastboot file in that location also to be used if you do not have it setup as in step 1. I'm not positive how and if that would work. Downloading and installing the wrong file is a mistake that may cause harm to your phone.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Code:
adb push su.zip /data/media
this will put the su.zip file in the root of your virtual sd card.
You are still in recovery, reboot into recovery to refresh the file list by typing this
Code:
adb reboot recovery
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
13- Download Rom Manager and flash the recovery again (top choice). This will erase the install-recovery.sh file and keeps your CWR at each boot. You do not have to do step 14 if you do this. I will leave step 14 here just in case someone needs it.
14-When you are back in the fastboot screen. DO NOT reboot the phone here. There maybe a file that re-writes the recovery to stock if the phone is rebooted. Your phone may or may not have this file. of the two GN I have, one did and one did not at this step(may have been erased). The file is reovery.sh and is located in /system/etc/ . You need to either rename it or delete it.
While in fastboot and after you flashed CWR, use the Volume up and Down to change the arrow's value to recovery and press the power button. You should now see the familiar Clockwork recovery. In recovery, you can use adb (you can't in fastboot of course). You need to rename that file, use these steps in terminal: (If you see no file/folder found message, you know you do not have this file)
Code:
adb shell
Code:
mount -o rw,remount /system
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
step 1 fires up adb, step 2 allows you to change permissions and read and write, and step 3 renames it. You can now unplug the phone.
Again, you can also get rid of this file by flashing the clcokwork recovery in Rom Manager or using the paid app root explorer to rename the file.
Once again referrence links:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
https://plus.google.com/103583939320326217147/posts/1Jsh9xPwnQP
thank you so much this is exactly what i was looking for. cant believe im the only one to comment on this. it is very detailed even some one new to Ubuntu could figure this out.
I've been using it too for a while but never posted so THANK YOU! Very easy to follow. Great work.
you're welcome. I find it ironic that a Linux based OS such as Android has so many HOWTOs for Windows but not enough for Linux. #powerofmonoply
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
ual4720 said:
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm not sure. How did you setup your adb and fastboot? I did not have to sudo for fastboot commands. What OS are you running?
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
AndroidSparty said:
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
Click to expand...
Click to collapse
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
loveubuntu said:
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
Click to expand...
Click to collapse
3, 6, & 9...check.
I rebooted my phone by pulling the battery and I still can't get adb to see the device. The install-recovery.sh? I don't remember reading anything about that.
In step 12 it says to let the phone reboot into the Android OS, but it's now back at factory reset, as that's what we did earlier in the instructions. As soon as it boots into the Android OS, adb lists the device.
At that point, since I'm in the AOS, I downloaded Astro File Manager and tried to put su.zip in the /cache folder, I think that's the folder that the clockwork recovery mod folder sees, and I don't have permission. I was hoping I could cheat and just drag & drop instead of pushing it. BUT...I did try the command adb push su.zip /media/play and I get permission denied. I'm guessing I don't have permission, even as sudo, to move the file to /data/media.
Okay I finally got it!
I didn't wait long enough for the Android OS to boot up. I finally was able to move the .zip file, but I couldn't find where /data/media was. So I let the OS boot up, removed the battery, went back into recovery, moved the zip file, and it was finally listed.
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Forceflow said:
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Click to expand...
Click to collapse
>Windows guides are confusing
>Windows guides
>Windows
Root of the issue
But agreed, this was a good supplement to follow for Ubuntu.
Sent from my Galaxy Nexus using xda app-developers app
Thank you for this guide. Some how I like the Linux method better than the Windows ones.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Click to expand...
Click to collapse
This step is confusing. While in recovery should be replaced by "Hit Power button to enter ClockworkMod Recovery"
Otherwise people may mis-interpret by "Stay in fastboot and position the big arrow on top to Recovery Mode"
In my case (GNex GSM stock JB 4.11):
adb push su.zip /data/media
or
adb push su.zip /sdcard
did copy su.zip successfully but could not be listed by ClockworkMod Recovery menu when selecting "choose zip from sd card". I had to do this:
Code:
adb push su.zip /sdcard/Alarms
And, within the ClockWorkMod Recevery menu, select "choose zip from sd card"
Land on another screen where I could navigate to Alarms folder and see the su.zip there.
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
Click to expand...
Click to collapse
Sorry for being picky but personally, it is NOT self explanatory for me. I was expecting a menu item in CWM Recovery menu to say "Install su.zip". Actually you must navigate in the file system and select the su.zip yourself. Ok, may be that seems obvious now that I know what to do. But on the moment, I was worried I screwed up something because I needed to do some extra manipulations while you said that should be "self explanatory".
4- Now download Clockwork Recovery from here
Click to expand...
Click to collapse
You may want to up date the link, ClockWorkMod now has a Recovery program which is touch sensitive:
GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-maguro.img
Sprint: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toroplus.img
VRZ: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toro.img
Step 12 finishes with
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
Click to expand...
Click to collapse
Therefore what is the need of doing #13 and 14?
Furthermore, Step 13 starts by
13- Download Rom Manager and flash the recovery again (top choice)
Click to expand...
Click to collapse
What is that top choice? Do you mean restart from the top at step #1? If you need to reflash again CWN, would it be simpler to restart from Step 10 instead of going back to the top?
And BTW, what is the reason to reflash the CWM Recovery again just after you have successfully flashed it at Step 12? Could that be #13 and #14 are some steps of an older guide which no longer apply now but you forgot to remove?
Sorry for the silly question but I am rather lost. After all that hardwork, when I attempt to Update SuperUser, it failed on the line "Gaining root access ..." What is the reason and how to fix that? FOUND ANSWER: the su.zip given in the post is Superuser 3.07 which is outdated, It is probably buggy. Replaced it by SuperSU 0.94 and it works perfect: http://download.chainfire.eu/204/SuperSU/
Thanks
worked like a charm.. if you have problem using fastboot, just cd to the folder with fastboot and run it like this:
Code:
sudo ./fastboot "command"
it will require your password and then work normally, seems like it need super user permissions.
Also for new user: to avoid writing a command or a folder name manually just push the TAB button, it will autocomplete the word if it's unique in that folder
I've been trying to re-root my phone since late last night, and have had nothing but problems. I've searched all over the internet, and tried anything that I thought would apply to my situation in the slightest.
I originally downgraded from 2.3.4 to 2.3.3 and rooted my phone using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1298990
I ran Revolutionary, ClockworkMod, and SuperUser. Everything worked perfect the first time around. Installed the Cyanogenmod 7.2 ROM and Tiamat v1.1.5 kernel. Then I started having issues with my battery, and Cyanogenmod seemed to be increasing the issues. At that time HTC announced they'd be releasing ICS, yada yada yada. I found a stock ROM online, and installed it, and updated as they were released OTA. Having finally gotten a new extended battery, I'd like to re-root & ROM my phone, but I've hit some road blocks.
I currently have the Android Version of 2.3.4 & Software Number of 5.10.605.9
I tried to re-do the entire process that had previously worked for me, but once I used the command hack-vivow.cmd, the phone would boot to the Revolutionary (of HBOOT ?) screen. Command line shows this, and just hangs:
c:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
Click to expand...
Click to collapse
Phone shows this:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT -6.13.1002
RADIO -1.09.01.1111
eMMC -boot
Click to expand...
Click to collapse
Phone gives me the options of "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", & "POWER DOWN". "REBOOT BOOTLOADER" changes "FASTBOOT" briefly to "FASTBOOT USB", but changes back in about 15-20 seconds. When I select "BOOTLOADER", the screen freezes for a few seconds, and it won't let me select any options, "FASTBOOT" changes to "HBOOT", and I get this in green text:
SD Checking
Loading...[PG32DIAG.zip]
No image!
Loading...[PG32DIAG.nbh]
No image or wrong image!
Loading...[PG32IMG.zip]
Click to expand...
Click to collapse
The next screen of green text says "Parsing...[SD ZIP]" followed by 9 things, and I'm only given an option to Update or No/Reboot. No/Reboot reboots my phone into an endless bootloop, until I remove the battery and power back on with Volume Down + Power Button. Update does a reset of my phone, and puts me right back to where I am now. While it is updating there is an error message at the bottom that says "Can not roll back hboot version".
I've tried multiple things to attempt to fix this... I ran the TacoRoot method from here:
http://forum.xda-developers.com/showthread.php?t=1751796
When the 8th line was completed
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
, the phone rebooted, it got stuck in a bootloop.
So that's where I am now. I'm stuck with S-Off, the PG32DIAG/PG32IMG errors, an HBOOT that seems to be far too new of a version, and I haven't found a way to get back to 2.3.3. As you can see I'm a noob. I'm really not sure where I went wrong (other than going back to a stock ROM and allowing it to update). Unfortunately a lot of things are just way over my head, without seeing a step by step process. But I'm just stuck at the moment. If anyone has any ideas on how to fix this, or any ideas of things to try I GREATLY appreciate it.
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Cleanincubus said:
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Click to expand...
Click to collapse
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
gtdtm said:
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
Click to expand...
Click to collapse
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Cleanincubus said:
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Click to expand...
Click to collapse
So with Froyo on there can you get to the stock recovery?
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I think you should be able to do 1B at this little how-to site:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I also just noticed...did you do "fastboot devices" first to make sure it actually recognized your phone? I'm really guessing, but I figured it was worth asking.
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Cleanincubus said:
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Click to expand...
Click to collapse
You shouldn't be flashing romantic zips as PG32IMG. That's what clockwork is for. If get it back to froyo, then go to the HTC recovery and follow the clockwork instructions I linked to. But maybe someone more knowledgeable than I can answer better.
Sent from my ADR6350 using xda app-developers app
After you go onto bootloader and it flashes your IMG you either rename the file on your SD card or delete it from your SD card. You will be able to proceed after that has been done
sent from my incredibly paranoid inc2
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Your s-off so the hard part is done.
sent from my incredibly paranoid inc2
You're right. The PG32IMG.zip was a problem. I removed them from the SD card's root, and it's working as it should.
Now the issue is the instructions in that link. I can't find any update.zip for the phone anywhere. I also can't find any options in the Recovery for "re-install package". I go to "BOOTLOADER" and then "RECOVERY". The Phone then boots to a small image of my phone with a red "!". I press Volume Up + Power button, and it loads the "Android system recovery <3e>". I have a Yellow error at the bottom stating"
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
sjpritch25 said:
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
Click to expand...
Click to collapse
screenshot for you
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Cleanincubus said:
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Click to expand...
Click to collapse
I don't think it's going to work until you get fastboot devices and adb devices to recognize your phone. I wish I could point you in the right direction, but I'm not very experienced with it.
I'm assuming you have the drivers for our phone installed? Some people have to reboot the pc to get those to recognize the device...
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Cleanincubus said:
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Click to expand...
Click to collapse
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
sjpritch25 said:
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Click to expand...
Click to collapse
Yup, it's there.
Did those commands, and it ended in the same result. No errors or "waiting" messages at the flashboot devices command, but it didn't show my device either.
Jasonp0 said:
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
Click to expand...
Click to collapse
Definitely installed driver. I originally tried to install the driver I previously used with my original s-off/root/rom, but it didn't work with Windows 8 (previous PC was WinXP), so I found the correct one for my OS. The "adb devices" command never found my phone, before installing the current driver.
I never installed HTC Sync. Just double checked the "Uninstall or change program" in the Win8 control panel (previously "Add/Remove Programs") to make sure it didn't get installed with out my knowledge, and it's not in there.
If you mean on the phone: "Settings" > "Applications" > "Development" > check box for "USB debugging", then yes. If it's a command of some sort, then no & I don't know how to do it.
I'm also making sure to run these commands by right-clicking the Command Prompt and selecting "Run as administrator", before doing these commands.
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...