Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
Related
All I can see is the HTC logo with 4 ! inside of a triangle on each corner. This is a been bricked for a long time and I cant remember how it happened but just wonder is there is anyway to fix it
Thanks,
The state your phone is in sounds similar to this
http://forum.xda-developers.com/showthread.php?t=824290
but there is no way to be sure of that, based on the zero details you provided.
Read the ENTIRE POST, not just part of it (it is quite long).
WOW, exactly the same problem this phone has!
If I remember right it was a mix up with ClockworkMod recovery.
That was a very nice recovery, I will have to read and learn all that. That's a lot of info and stuff that I will have to learn to try to fix this phone.
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
stick2e said:
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
Click to expand...
Click to collapse
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
bftb0 said:
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
Click to expand...
Click to collapse
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
stick2e said:
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
Click to expand...
Click to collapse
Well, first off - you should say what version of the boot loader you have. It is shown on the fastboot screen. If you already have the 1.49.2000 S-OFF bootloader this current step can be skipped, And you can proceed directly to flashing a recovery using fastboot from the pc. If you do not have the S-OFF bootloader the whole point of this current step is to get it on the phone - in which case you should be using the ROOT PB00IMG.ZIP file, not the Leak-V3 PB00IMG.ZIP file.
All Eris RUU and PB00IMG.ZIP files can be found at:
http://forum.xda-developers.com/showthread.php?t=909921
When the RUU program is running, just prior to the moment when you would begin flashing to the phone, you use the search function on your PC in the folder
C:\Documents and Settings\<your_user_name>
(Edit - in Win7, C:\Users\<your_user_name> )
to look for the file named "rom.zip". (You will probably need to twiddle the dumbass Microsoft setting which prevents searching for hidden files and folders.)
Then, you delete the rom.zip file, rename the ROOT PB00IMG.ZIP file to rom.zip, and drop it into the same location.
Before starting this step, make sure your phone is completely charged and also be sure to verify the file size and md5 checksum of the ROOT PB00IMG.ZIP file you downloaded.
As I mentioned above if you already have the S-OFF bootloader present on your phone, this operation is not necessary and we can proceed to flashing a recovery using the fastboot program on the PC.
Lemme know how it goes.
PS - It would be helpful for you to answer a few questions about your current skill set and computer setup:
- have you used either the "fastboot" or "adb" programs in the past on your pc?
- if not, do you know how to verify communication with the phone in fastboot mode?
(Note that running the RUU utility will install drivers on your PC)
The original Amon_RA recovery for the Eris can be found here:
http://forum.xda-developers.com/showthread.php?t=648025
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
stick2e said:
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
Click to expand...
Click to collapse
"fastboot devices" when the phone is in fastboot mode.
adb only applies when the normal OS is running with USB debugging turned on, or if the Amon_RA recovery is booted.
What bootloader version do you have?
This is where the phone is right now.
1.49.0000 S-ON bootloader
When I get home today I will look for the proper img file and try the RUU option to see if I can get the S-OFF in there. We will see.
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot, then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
PS - don't let the phone sit in fastboot mode for extended periods of time - it will discharge rapidly even if it is plugged into the charger
This thread honestly scares me and I hope this never happens to me lol
willwgp said:
This thread honestly scares me and I hope this never happens to me lol
Click to expand...
Click to collapse
All you need to remember is this:
newb + Eris + ClockworkMod = disaster waiting to happen
In almost every bricking that has been reported here on the (XDA) Eris forums, ClockworkMod (or running the battery down to very low charge levels) was involved.
What is also notable is that in almost every case, the folks that got into trouble:
- got their rooting instructions from non-XDA sites (e.g. unrevoked, z4root, unlockr)
- could not clearly explain what they had been doing immediately prior to the event - even after repeatedly being asked to do so,
- were unaware what ROM signing is about (or that ClockworkMod doesn't perform it)
The second observation seems to imply a behavioral trait of innattention or sloppiness.
In the hands of people that are experienced, ClockworkMod seems to behave correctly.
For the moment though, let's stay on topic and see if we can revive stick2e's phone. At the moment, I am guessing that there is about a 30% chance of that. We'll find out more when we hear the result of his/her flashing attempt.
bftb0
I think this is going to work!!!! Thinks are looking better.
I try to flash the RUU but replace the rom.zip (what a pain to find it!!!) with the root rom (PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and now I have to load a rom in the sdcard to flash the phone. Fingers crossed we will see.
I'm downloading a ROM now.
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
stick2e said:
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
Click to expand...
Click to collapse
DId you rename the new PB00IMG.zip file to rom.zip?
bftb0 said:
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot,
Click to expand...
Click to collapse
Ok, HBOOT-1.49.2000 and S-OFF
bftb0 said:
then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Click to expand...
Click to collapse
C:\sdk\tools>fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... OKAY [ 0.826s]
writing 'recovery'... OKAY [ 1.357s]
finished. total time: 2.183s
bftb0 said:
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
Click to expand...
Click to collapse
RUU Utility report ERROR [110]: FILE OPEN ERROR
Parsing... [download ZIP]
[1] User Data - OK
[2] System - Fail-PU
[3] Recovery - OK
[4] Radio_V2 - OK
[5] Boot - Fail-PU
Partition update fail!
Update Fail!
Gimme a minute to fire up a real computer instead of this stupid phone browser.
Well, I fastboot recover revery-RA-eris-v1.6.2.img but nothing happen now :-(
Before used to take me to RA Recovery but now is not.
Okay, so I got hboot 2.09 unlocked. I then proceeded to follow QBKing77 instructions for rooting and installing openrecovery. I downloaded the root files from the link he provides. When I type in "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" and hit enter, it tells me error: cannot load fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img,: Unkown Error. Can anyone offer any suggestions here? Thanks.
cmparramore said:
Okay, so I got hboot 2.09 unlocked. I then proceeded to follow QBKing77 instructions for rooting and installing openrecovery. I downloaded the root files from the link he provides. When I type in "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" and hit enter, it tells me error: cannot load fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img,: Unkown Error. Can anyone offer any suggestions here? Thanks.
Click to expand...
Click to collapse
Do you have android SDK instaslled?
bigdaddy619 said:
Do you have android SDK instaslled?
Click to expand...
Click to collapse
Yes I actually went back through the entire process, and checked the path to make sure it was installed correctly. Rebooted the computer and the phone, but still getting unknown error message.
try this open your sdk folder and press shift and right click platform tools and select open cmd window here
that will put you in a writeable folder
Unfortunately I do not get that option. Running windows XP.
hmmmm
is the .img file in your platform tools folder?
drivers installed?
does your pc recognize your phone when you plug the USB in?
---------- Post added at 05:47 AM ---------- Previous post was at 05:36 AM ----------
try downloading this it has all the files you need
once you open cmd window point to this folder
http://d-h.st/5zT
Yes, Yes & Yes
try this
DOH!! Dang, it helps if you use the right directory. I am such a dunce. Thanks for all the help and sorry for being such a goonhead, maybe I need some more coffee!!
hahaha no worries
hey do you know if there coming up with a s-off for hboot 2.09
cmparramore said:
Yes, Yes & Yes
Click to expand...
Click to collapse
Worked for me. and I'm hboot 2.09 also. I don't have windows xp but when I open the sdk directory. hold shift and right click I get a prompt saying "open command window here" I then issue the fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.img command. it flashes just fine. I think you're missing a step or two.
Please take a look at my thread on rooting/superuser/TWRP installs. It's a pretty good guide. I tried to take the mystery out of this process.
http://forum.xda-developers.com/showthread.php?t=2038123
I am having issues rooting via qbking77's method on Youtube.
I'm stuck at the 5:42 mark where I need to mount USB storage via Teamwin / TWRP recovery.
The 'Mount Cache/Mount SD Card/Mount Internal' aren't' checked on my phone and I can't check them manually. When I click on 'Mount USB Storage'. My computer pops up a message telling me that 'You need to format the disk drive in F:before you can use it. I'm not sure what to do next.
Any suggestions? Thanks.
Thanks this forum helped me find my problem while following qbking77 video on how to root. I realized after quite a few tries that the twrp img file had changed a bit since the video was posted. When bigdaddy619 check for file I found file to be openrecovery to have some different numbers.
Also the actual root file towards the end of the video name/version had changed also. Little details make a big difference.
Im having an issue trying to install openrecovery as well. Ive followed all of qbking77's instructions in the videos. Im running HBOOT 2.09 which is already unlocked. I have SDK tools and everything as well. When i get to the step to install openrecovery, I go to the folder containing the file and shift+right click and open a cmd window. This is what I get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-tw
rp-2.5.5.0-jewel.img
< waiting for device >
sending 'recovery' (8196 KB)...
And thats it. It locks up and doesn't go any further. I've tried several times and retraced my steps through the whole install procedure with the same result. Can you fellas help me out?
PooPCovington said:
Im having an issue trying to install openrecovery as well. Ive followed all of qbking77's instructions in the videos. Im running HBOOT 2.09 which is already unlocked. I have SDK tools and everything as well. When i get to the step to install openrecovery, I go to the folder containing the file and shift+right click and open a cmd window. This is what I get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-tw
rp-2.5.5.0-jewel.img
< waiting for device >
sending 'recovery' (8196 KB)...
And thats it. It locks up and doesn't go any further. I've tried several times and retraced my steps through the whole install procedure with the same result. Can you fellas help me out?
Click to expand...
Click to collapse
When you type adb devices and hit enter, what happens?
Sent from my EVO using xda premium
FinZ28 said:
When you type adb devices and hit enter, what happens?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
When I type "adb devices" with my phone connected and in bootloader menu this is what i get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>adb devices
List of devices attached
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Not sure if that's what i'm supposed to get, but if I instead type "fastboot devices" I get this:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot devices
HT25PS403929 fastboot
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
PooPCovington said:
When I type "adb devices" with my phone connected and in bootloader menu this is what i get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>adb devices
List of devices attached
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Not sure if that's what i'm supposed to get, but if I instead type "fastboot devices" I get this:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot devices
HT25PS403929 fastboot
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Click to expand...
Click to collapse
My bad, forgot you were in fastboot. Looks like everything is working as it should, though, so I can't think of why you would be having the problems you are
Sent from my EVO using xda premium
FinZ28 said:
My bad, forgot you were in fastboot. Looks like everything is working as it should, though, so I can't think of why you would be having the problems you are
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Anyone else have any ideas? I've rooted this phone before in the past and never had a problem unlocking and rooting or unrooting and relocking so this is most peculiar. I've tried qbking77's method, i've also tried other tutorials out there as well as attempting to use other versions of openrecovery but it just won't root.......
PooPCovington said:
Anyone else have any ideas? I've rooted this phone before in the past and never had a problem unlocking and rooting or unrooting and relocking so this is most peculiar. I've tried qbking77's method, i've also tried other tutorials out there as well as attempting to use other versions of openrecovery but it just won't root.......
Click to expand...
Click to collapse
Try uninstalling everything HTC from your PC
reboot PC and device
re-install drivers including HTC Sync(you can delete it afterwards and the drivers will remain)
plug in your device via usb cable it should install the drivers again also boot into the bootloader drivers should install again
You should be good to go now
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.
I am currently S-on and I have not been able to successfully flash any new ROM at all. I have tried several times to do a super wipe, flash the new ROM and Gapps but I get stuck in a boot loop and I can't quite figure out the problem. Never had this problem flashing any ROM or even updating my RUU so I am puzzled as to where these issues are coming from. Any insight would be greatly appreciated. I am not complaining about me being there is a very stable rom but I would not mind upgrade to 4.2 or 4.3 and maybe a different ROM. Oh and I'm using TWRP 2.63 I believe is the newest.
Sent from my EVO using Tapatalk 4
hillje1 said:
I am currently S-on and I have not been able to successfully flash any new ROM at all. I have tried several times to do a super wipe, flash the new ROM and Gapps but I get stuck in a boot loop and I can't quite figure out the problem. Never had this problem flashing any ROM or even updating my RUU so I am puzzled as to where these issues are coming from. Any insight would be greatly appreciated. I am not complaining about me being there is a very stable rom but I would not mind upgrade to 4.2 or 4.3 and maybe a different ROM. Oh and I'm using TWRP 2.63 I believe is the newest.
Sent from my EVO using Tapatalk 4
Click to expand...
Click to collapse
Because you are s-on you have to fastboot flash the kernel/boot.img then flash the rom
Look here to fastboot flash kernels/boot.img while s-on
http://forum.xda-developers.com/showthread.php?t=2256478
okay I will definitely try that, was there a point in time when this method change because I have always been S-on
never had to flash and that particular order?
lol in response to the attached photo I am still S-On because my phone would not take the dirty raccoon S off flas.
but lately my phone has been completely spazzing out on me it will do random lock ups and start swyping characters, in opening and closing menus without me pressing any buttons I almost feel like it is on its last leg. Not to mention random shut offs with black screens but still powered on if that makes sense. Normally when that happens it'll get stuck in a boot loop and I'll have to restore a previous backup... #itsucks
hillje1 said:
okay I will definitely try that, was there a point in time when this method change because I have always been S-on
never had to flash and that particular order?
lol in response to the attached photo I am still S-On because my phone would not take the dirty raccoon S off flas.
but lately my phone has been completely spazzing out on me it will do random lock ups and start swyping characters, in opening and closing menus without me pressing any buttons I almost feel like it is on its last leg. Not to mention random shut offs with black screens but still powered on if that makes sense. Normally when that happens it'll get stuck in a boot loop and I'll have to restore a previous backup... #itsucks
Click to expand...
Click to collapse
Some roms have kernel installers for s-on folks MeanBean being one of those roms.
As for s-off DirtyRacun may not be your only option tell me your baseband number.
The spazzing out sounds like a similar problem my buddy was having, he was s-off I ran an RUU and he says it sems to have fixed the problem.
bigdaddy619 said:
Some roms have kernel installers for s-on folks MeanBean being one of those roms.
As for s-off DirtyRacun may not be your only option tell me your baseband number.
The spazzing out sounds like a similar problem my buddy was having, he was s-off I ran an RUU and he says it sems to have fixed the problem.
Click to expand...
Click to collapse
Baseband 1.12.11.1119
hillje1 said:
Baseband 1.12.11.1119
Click to expand...
Click to collapse
Good news you can use FacePalm if you want assistance PM me I'll help you out
bigdaddy619 said:
Good news you can use FacePalm if you want assistance PM me I'll help you out
Click to expand...
Click to collapse
What is facepalm?
It's an s-off exploit
http://forum.xda-developers.com/showthread.php?t=2163013
Facepalm
bigdaddy619 said:
It's an s-off exploit
http://forum.xda-developers.com/showthread.php?t=2163013
Click to expand...
Click to collapse
Are you still able to help me get S-Off with my device. Hopefully that'll fix the issues I mentioned before b/c this is getting ridiculous!
Do you have ADB & Fastboot set up on your computer? If not, look here. This is a small file and the setup is very easy. You may also want to install HTC Sync on your computer so your drivers are up to date. Once you've done this you need to go to the Facepalm thread that Bigdaddy provided a link to previously. In the first post, there are two files to download, the modified boot.img and signed firmware. Download both of these and place them in your ADB-Fastboot folder (if you downloaded and installed the one I linked above, it should be named android-tools). Once you've done this, connect your computer and phone via USB cable. Use your mouse curser and place it on the android-tools folder, then press Shift+right click on the mouse, then select the option to open a command window. Type the following command:
Code:
adb devices
The serial number of your phone should be output on the line below. If not, you might need to change the device type in the notification pull-down on your phone from sync manager to disk drive. Once you're able to successfully run the adb devices command, you are ready to start.
Type:
Code:
adb shell
press enter, then type:
Code:
su
and hit enter. Once you've done this, you can run the command to gain SuperCID on your device. The easiest thing to do is copy the command from the line below and paste it into the command terminal. The command is:
Code:
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Hit enter. Once you've done this, you can begin at step 1, which will reboot your phone to the bootloader. To verify that you've got SuperCID, you should see a line underneath your Hboot version that says something like "CID-22222222". If so, you're ready to move on to step 2, making sure that you're connected via Fastboot USB mode. Just follow the commands in the Facepalm thread and you should be good to go. If after you're done your phone doesn't reboot, simply press the power button to start the phone. You can reboot to the bootloader once the phone powers on to confirm that you're S-off. Also, once you're done gaining S-off, I recommend deleting the two files you downloaded from your android-tools folder to prevent any issues in the future.
..In the past 24 hours I've done a lot to this phone, some good, some bad, some mix guidance that caused my own user error.
I have CWM Recovery 6.0.3.2 on my screen. I was trying to install SkyDragon's 11.1, BUT I did not copy files to the SD card. I forgot, I was not paying attention, I don't know... but I didn't realize thi was an issue until I could not load the files from the CWM menu. so my current setup right now is...
HTC One DEVELOPERS EDITION!
I have CWM on my device. (so I have wiped EVERYTHING)
Sky Dragon attempted and went though all steps.
I can use command prompt to communicate to device SOMETIMES but can't "push the files" through. but I can communite to device (it's detected which mean adb is working)
I can't turn on phone.
Fastboot is accessable.
I have done the HTC developers website
These guides are not working for me so I thought it couldn't hurt to ask... Let e know what else I need to share...
UPDATE: when I attempted to run Dev RUU, it says it will upgrade this version. Image Version L: 1.29.1540.17
to 1.29.1540.16
was downloading brightstar for 3.22.1540.1 and still same.
mcooke said:
..In the past 24 hours I've done a lot to this phone, some good, some bad, some mix guidance that caused my own user error.
I have CWM Recovery 6.0.3.2 on my screen. I was trying to install SkyDragon's 11.1, BUT I did not copy files to the SD card. I forgot, I was not paying attention, I don't know... but I didn't realize thi was an issue until I could not load the files from the CWM menu. so my current setup right now is...
HTC One DEVELOPERS EDITION!
I have CWM on my device. (so I have wiped EVERYTHING)
Sky Dragon attempted and went though all steps.
I can use command prompt to communicate to device SOMETIMES but can't "push the files" through. but I can communite to device (it's detected which mean adb is working)
I can't turn on phone.
Fastboot is accessable.
I have done the HTC developers website
These guides are not working for me so I thought it couldn't hurt to ask... Let e know what else I need to share...
UPDATE: when I attempted to run Dev RUU, it says it will upgrade this version. Image Version L: 1.29.1540.17
to 1.29.1540.16
was downloading brightstar for 3.22.1540.1 and still same.
Click to expand...
Click to collapse
still the same what ? ..did you relock the bootloader to run the RUU ?
fastboot oem lock
then fastboot reboot-bootloader
then run the RUU
clsA said:
still the same what ? ..did you relock the bootloader to run the RUU ?
fastboot oem lock
then fastboot reboot-bootloader
then run the RUU
Click to expand...
Click to collapse
cmd 1: Locked
cmd 2: Okay!
3: trying now... nvm last reply