my phone (HTC Her) was rooted, and had version 1.5.
I wanted to upgrade the opertating system to 2.1, so I made a hard reset and then installed the official RUU from HTC site and all the upgrades that were suggested.
It all went great, except for one thing: the phone was locked again so I could not install the local font (Hebrew fonts) which I need for daily use.
For days I tried various method to root the phone, including making a goldcard but it did not help.
Finally I used something (I think it was the file called universalandroot.apk, but i'm not sure if that's the file) which claimed that the phone was rooted.
Then I installed the Hebrew fonts using an application called "IsraelPack" and all the fonts in the phone turned to gibberish. That was the last time that the phone was working... I turned the phone off and then on again, and it was stuck on the Hero logo.
I've tried several methods, including adb, but the phone i is not connecting with the pc. when i run "adb devices" I get "list of devices attached" and nothing follows. every command I try to use I get a "device not found" or "waiting for device". I've tried to run several RUU, but it always says that it can't connect to the device.
I apologize for the long description of the problem, and I will be very happy to get some help. thanx in advance.
Have you tried turning on without SD in?
Once rooted with androot did you install a custom recovery (amon Ra)?... can you get into that?
Can you get into fastboot?
ddotpatel said:
Have you tried turning on without SD in?
Click to expand...
Click to collapse
Yes, it acts just the same.
ddotpatel said:
Once rooted with androot did you install a custom recovery (amon Ra)?... can you get into that?
Click to expand...
Click to collapse
No.
ddotpatel said:
Can you get into fastboot?
Click to expand...
Click to collapse
Well, when I turn it on using the Power and Back keys, I see a red message FASTBOOT and below two options:
<VOL DOWN> HBoot Mode
<MENU> Reset Device
Is that what you refer to as fastboot?
Yep thats it,... so press VOL- again for hboot,... then try running the RUU again?
Do you have adb set up?.... If you do, and the above fails,... then you need to try
fastboot oem rebootRUU
It should then say RUU usb on the screen, then try running the RUU again?
Going to sleep now pal,... If you don't get sorted update this thread and drop me a PM as a reminder for me for the morning, but I'm sure others will help you before I even check.
Good Luck.
ddotpatel said:
Yep thats it,... so press VOL- again for hboot,... then try running the RUU again?
Click to expand...
Click to collapse
RUU doesn't work. error 170 - usb not connected.
ddotpatel said:
Do you have adb set up?.... If you do, and the above fails,... then you need to try
fastboot oem rebootRUU
It should then say RUU usb on the screen, then try running the RUU again?
Click to expand...
Click to collapse
no... it says "<waiting for device>"
Change the driver as per my correct driver thread (see sig).
Aha,.... there are different drivers for fastboot mode,... did not know that.
BTDAG to the rescue once again. One of the two people I was hoping would jump in to help.
thanx btdag and ddotpatel. you are great!!
well, an update: i reinstalled the drivers and the HTC Sync (changed from android 2.1 back to the android 1.5 version) and now the pc is connecting with the phone.
I'm now trying to install RUU 2.73.405.5.
I truly hope it will work this time...
update: the RUU failed, after 30 minutes or so.
maybe because it's the same version as was installed before (2.73.405.5)?
I intend to try to install a different version. hoping it will work this time.
Yeah, downgrade is not possible without goldcard.
So use one from http://forum.xda-developers.com/showthread.php?t=720394,...
Or use BTDAGs guide linked in my signature, down to the bottom of the 1st post, goldcard instructions are there.
ddotpatel said:
Yeah, downgrade is not possible without goldcard.
So use one from http://forum.xda-developers.com/showthread.php?t=720394,...
Click to expand...
Click to collapse
Thanks again for your efforts...
As far as my understanding goes, these RUU will make the phone unrootable forever, and I need the rooting in order to replace the fonts.
ddotpatel said:
Or use BTDAGs guide linked in my signature, down to the bottom of the 1st post, goldcard instructions are there.
Click to expand...
Click to collapse
I've already made a goldcard a few days ago, and it's in the phone. but the upgrading doesn't seem to work. The RUU is making progress almost 'till the end of the scale, and then stops (on the phone itself). On the PC it works endlessly in the "sending......" stage.
No no, they should still be rootable using androot (as per BTDAGS guide) or TeamVillains sticky in the Development section. Use a fresh download of everything or check MD5 thingies for all if possible.
Sent from my HTC Hero using XDA App
Didn't you already downgrade?
Bear in mind it shouldn't be necessary to downgrade at all. The Universal Androot program works on all versions of Android.
well, I've tried to use this RUU:
RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6 .35.15.11_release_signed.exe
and it's the same story: the installation goes almost to the top of the bar (top right in the phone display) and then hangs... in the PC it's in the "sending....." stage.
Update: YES! YES! YES!
It's working!!!
after many hours of ups and downs, and exactly when I was ready to give up, I decided to try a different approach and to move to another PC (maybe this one hates the phone?).
and suddenly, the RUU was working and moving ahead, and in 10 minutes the phone was alive again...
many thanks to btdag and ddotpatel, my guides in this journey, for their patience and help.
And now for the second phase: how do I root the phone? (I used this RUU:
RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6 .35.15.11_release_signed.exe).
Congratulations. Check out my Newbie Guide in my Sig on how to root.
Related
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App
Hi guys,
I turned my flyer on today and had a prompt to complete a software update, roughly 4.5 mb so I assume it's to do with HTC's security update that is rolling out.
However when the device restarts to install the update, all I see on screen is the yellow triangle and a blue android...
I've left it like this for 20 minutes and nothing actually happens with the update, nor do any of the hard buttons work ect
I unlocked the bootloader a while ago via one of the methods in the Dev forums but haven't really used the flyer since, so I assume it's down to the bootloader being unlocked?
What I want to know is, how to I restore the Flyer to TOTAL stock, ie bootloader, ROM, EVERYTHING.
I've had a look around and haven't managed to find anything, so I hope someone can help
thanks!
Same problem the last security updade dont work with rooted flyer
please help us
I've seen that if you remove htcloggers.apk from /system/app with root explorer or something, but this doesn't seem to have got me anywhere!
To restore use the ruu for you model and software version. There are a lot of guides on how to do it all and to relock your bootloader. You just boot into fastboot and run adb. And type fastboot oemlock and that will relock the bootloader if that doesn't help the problem. Just run the ruu as I stated before hope everything works put well with you. Repost here and I will check later to see your progress and se if I can help a little more.
tydgilyard said:
To restore use the ruu for you model and software version. There are a lot of guides on how to do it all and to relock your bootloader. You just boot into fastboot and run adb. And type fastboot oemlock and that will relock the bootloader if that doesn't help the problem. Just run the ruu as I stated before hope everything works put well with you. Repost here and I will check later to see your progress and se if I can help a little more.
Click to expand...
Click to collapse
Thanks for this - I've downloaded the RUU from the top of the thread in development but when I attempt to run it, it throws up a 170 error (I think, not at home at the moment)
When I check the logs it picks up HTC sync and I can see that it's trying to run adb but doesn't seem to manage it. Any ideas?
I will give the other thing a go this evening!
tydgilyard said:
To restore use the ruu for you model and software version. There are a lot of guides on how to do it all and to relock your bootloader. You just boot into fastboot and run adb. And type fastboot oemlock and that will relock the bootloader if that doesn't help the problem. Just run the ruu as I stated before hope everything works put well with you. Repost here and I will check later to see your progress and se if I can help a little more.
Click to expand...
Click to collapse
Thanks so much i'll try this evening when wont need the flyer as phone, XD. could be so kind to adress me in which RUU i should download i we a ITALIAN HTC FLYER WIIFI and 3G P510E
thank
adaimespechip said:
Thanks for this - I've downloaded the RUU from the top of the thread in development but when I attempt to run it, it throws up a 170 error (I think, not at home at the moment)
When I check the logs it picks up HTC sync and I can see that it's trying to run adb but doesn't seem to manage it. Any ideas?
I will give the other thing a go this evening!
Click to expand...
Click to collapse
Its a guide on here where you run the ruu and pull the rom image from your one of your temp folders on your pc. there is a guide on that in the development form.
http://forum.xda-developers.com/showthread.php?t=1257909
leepton said:
Thanks so much i'll try this evening when wont need the flyer as phone, XD. could be so kind to adress me in which RUU i should download i we a ITALIAN HTC FLYER WIIFI and 3G P510E
thank
Click to expand...
Click to collapse
For you Look here:http://forum.xda-developers.com/showthread.php?t=1062184
and here:http://android.modaco.com/topic/346058-flyer-stock-rom-links/
To you both none of this belongs to me. Im just pointing you both in the right direction to find your answers and hopefully it helped. And if so be sure to hit the thanks button.
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
iamstafford said:
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
Click to expand...
Click to collapse
Try the method I described in the thread I came up with this morning - if you're comfortable with doing everything. It wasn't too hard to do. I just had to convert the jargon into words I could understand.
Try using the Moonshine method first though! It's easy and straightforward - if it will recognize your device (which it wouldn't recognize mine for some reason).
Here's what I did.
Good luck!
iamstafford said:
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
Click to expand...
Click to collapse
Take a look at the link in my sig. It should answer some of your questions.
Sent from my EVO using xda premium
iamstafford said:
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
Click to expand...
Click to collapse
A second what venkman21 says, moonshine is the easiest method and works with all versions of Windows. Took me about 7 minutes and I was s-off and loving it. Good luck.
Sent from my EVO using xda app-developers app
SoFaKiNgStOkeD said:
A second what venkman21 says, moonshine is the easiest method and works with all versions of Windows. Took me about 7 minutes and I was s-off and loving it. Good luck.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I tried moonshine. it didnt work! i have usb debugging on, i installed the android sdk tools and yes they are working properly. i am hooked up to a usb 2.0 port. but, whenever i run the program, it says Error ccannot check for updates, and at times it says error, run distiller again and read. any help?
iamstafford said:
I tried moonshine. it didnt work! i have usb debugging on, i installed the android sdk tools and yes they are working properly. i am hooked up to a usb 2.0 port. but, whenever i run the program, it says Error ccannot check for updates, and at times it says error, run distiller again and read. any help?
Click to expand...
Click to collapse
I get the same error messages. For the update one, make sure your firewall and anti-virus are off. That solved mine. For the "Error run distiller again" issue, that's what brought me here. Pleases let me know if you solve this!
iamstafford said:
I tried moonshine. it didnt work! i have usb debugging on, i installed the android sdk tools and yes they are working properly. i am hooked up to a usb 2.0 port. but, whenever i run the program, it says Error ccannot check for updates, and at times it says error, run distiller again and read. any help?
Click to expand...
Click to collapse
I think the "run distiller again and read" part means you pushed some buttons and otherwise touched or maimed your phone while Moonshine is working. I solved my issue. I was unzipping Moonshine to one folder then cutting the visible files out and pasting them to a separate folder. This left behind a hidden file. Solved problem by unzipping directly to my SDK platform tools folder which contains adb.exe and fastboot.exe. Worked first try. I'd already stopped firewalls, turned off anti-virus and tried to switch to usb file sharing during install (which is why I was told to "read". None of those were required this time. Never touched phone even though it was not in correct file sharing mode, and it still worked.
Hello,
I was recently given a bootlooping Evo 4G Lte. I have been trying to figure out how to get this thing out of a bootloop and havent been able to do it. I, unfortunately, have no history on what happened to this device. Currently, it bootloops on the "Mean Bean" loading screen but will go no further. I can get into the bootloader, which says it is Unlocked, S-On, but I am unable to boot it into a recovery, it just returns back to bootloader. I have tried fastbooting twrp, but it fails (remote: image update error), and I have tried fastbooting the Mean Bean kernel thinking maybe thats all it needs, but that failed as well. Anybody have an insight? Much appreciated! Thanks.
Mike
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thanks for the quick reply. I downloaded the RUU and ran it. However it sits and says "Waiting for bootloader" then errors out with "USB connection issue". The usb is working. The reason I never ran the RUU in teh first place was because i thought i read that you cant RUU with and unlocked bootloader. Is that not true? or is that my problem?
Mike
Not 100% sure but I will check with someone who used this tool recently and see if they were still unlocked at the time. Were you connected via Fastboot USB? Sounds more like a driver issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Shouldn't matter. I know of a couple of users who were having phone issues and had unlocked bootloaders when they ran this tool. Were you connected via Fastboot USB? Sounds more like a driver issue.
Click to expand...
Click to collapse
Yeah I was connected and it said fastboot USB. It said rebooting to bootloader and rebooted, still said fastboot USB. Then it sat at a screen that said "waiting for bootloader" and after a while error ed out.
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
crazymike1234 said:
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Click to expand...
Click to collapse
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
YoFayce said:
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
Click to expand...
Click to collapse
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
crazymike1234 said:
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
Click to expand...
Click to collapse
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
YoFayce said:
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
Click to expand...
Click to collapse
The drivers seem to be ok, but I am still not able to get any further. The RUU finds my phone, then reboots again to bootloader, but it just sits there saying "Waiting for bootloader" until it errors out due to "USB Connection error". I have tried a few different cables, and different USB ports. Not sure what the problem is but it just wont go any further. I re-unlocked my bootloader with htcdev. I have tried fastbooting a recovery to the phone but it errors out. I just cant get anything to work so I can boot anything. I really just want to get something working...anything! Any other ideas? Thanks.
Mike
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Sinistertensai said:
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Click to expand...
Click to collapse
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
crazymike1234 said:
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
Click to expand...
Click to collapse
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Sinistertensai said:
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Click to expand...
Click to collapse
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
crazymike1234 said:
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
Click to expand...
Click to collapse
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Sinistertensai said:
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Click to expand...
Click to collapse
Hmmm, Ill try download again. I got it from the main TWRP site.
crazymike1234 said:
Hmmm, Ill try download again. I got it from the main TWRP site.
Click to expand...
Click to collapse
careful on the vol down press you might be holding it too long and its canceling the update.
Sinistertensai said:
careful on the vol down press you might be holding it too long and its canceling the update.
Click to expand...
Click to collapse
Well, which recovery file should I be using? When I use the main TWRP ones (ie openrecovery-twrp-2.6.0.0-jewel.img) it gives me the errors like I said above. I now see they have a few labeled like this PJ75IMG-twrp-2.3.1.0-jewel.zip. When I use these, it tries to continue but says "Main Version Is Older. FAILED"
Sorry for being a noob in advance I really would like to root this phone, and have been trying for like the past 3-4 months trying everything from z4 root the app to hasoon2000's all-in-one toolkit, and I still cannot seem to root it. If anyone thinks they can help me or if you would like to try please msg me. I appreciate you reading this thank you
nzgx beast said:
Sorry for being a noob in advance I really would like to root this phone, and have been trying for like the past 3-4 months trying everything from z4 root the app to hasoon2000's all-in-one toolkit, and I still cannot seem to root it. If anyone thinks they can help me or if you would like to try please msg me. I appreciate you reading this thank you
Click to expand...
Click to collapse
Go read the S-off after 2014 OTA thread under development. All steps, information and links are there.
therreid said:
Go read the S-off after 2014 OTA thread under development. All steps, information and links are there.
Click to expand...
Click to collapse
Also verify the build version that is currently on your phone. I would assume you have the latest OTA (2.19), if so, then therreid is spot on. If you're earlier, then you have a few additional options, but it might be easiest for you to install the OTA and follow those instructions.
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Still dont understand.-.
I've read them but like my drivers apparently aren't installed, my phone isn't recognized on my computer, and this is all confusing lol. Do any of you know where to find like a video to help me
Here are the drivers:
http://forum.xda-developers.com/showthread.php?t=2089508
Okay...
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Click to expand...
Click to collapse
okay so what exactly is s-off? and what do drivers do and how do i know which to get? and how to temp root?
kimba99 said:
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Click to expand...
Click to collapse
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Sent from my TouchPad using Tapatalk
puhleez said:
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Click to expand...
Click to collapse
actually temp-root shouldn't go away after reboot at all! ... but rather leave the device in an unstable status (android booted with status-bar, but no lockring and partial screen-flickering going on/off etc) ... temp-root script should QUIT on its own IF it was sueccessful
... and only AFTER THAT ... start rumrunner (which reboots the device like 5-6 times i think). that's at least the way it works in windows.
only as a note: after s-off completed, the device will still be _unstable_ (as temp-root is still active and the device therefore unstable) ... so best would be to flash (thereby: install) a _new rom_ (as desired) directly after replacing the hboot & the recovery
kimba99 said:
actually temp-root shouldn't go away after reboot at all! ... but rather leave the device in an unstable status (android booted with status-bar, but no lockring and partial screen-flickering going on/off etc) ... temp-root script should QUIT on its own IF it was sueccessful
... and only AFTER THAT ... start rumrunner (which reboots the device like 5-6 times i think). that's at least the way it works in windows.
only as a note: after s-off completed, the device will still be _unstable_ (as temp-root is still active and the device therefore unstable) ... so best would be to flash (thereby: install) a _new rom_ (as desired) directly after replacing the hboot & the recovery
Click to expand...
Click to collapse
OK, thought that if reboot took place, temp-root was lost. So, when I ran rumrunner, it would just timeout and fail. I'll try to get the exact details later.
Anyway, thanks for your reply. May try again today using Windows to see if it works any differently.
EDIT: here's what happened under Windows.
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (12/120)
Waiting
Test 2: Booting device
Waiting for ADB (20/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (29/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
just saw above, that you guys referenced the __hasoon2000's all-in-one toolkit__ ... as for root (well, better said: [s-off]) in the "[s-off] after 2014-ota" thread, i wrote to use mdmovers script-kit! ... the hasoon2000 kit might be outdated (in terms of temp-root) ... i didn't check the details, but for clarity, please do AS IT'S WRITTEN down ... do not deviate from the (fairly easy) route given in that thread!
puhleez said:
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
I was finally able to get the method oiutlined by kimba99 to work using Linux, but you are correct, the initial adb & fastboot connection tests cause the phone to lose the temp-root and go back to my normal lock screen with ring and icons(in a usable state).
I know i sound conflicted but i tested it several times.
Here is the weirdness.
What finally got it to work was "attempting" using my win8 system. The win8 failed due to windows losing the device. I used drivers from HTC and then used drivers from the link provided. While rumrunner ran I would get a pop-up saying an unrecognized device was plugged in and then rumrunner would timeout being it could no longer talk to the phone. After 3 failed attempts on windows it got late so I rebooted my laptop into Ubuntu so i could use rumrunner to remove the temp-root and make it usable again as it had done 5 previous times.
Suddenly rumrunner was able to go past the root checks. The only difference than before is that while trying on windows my device went from LOCKED to TAMPERED to TAMPERED LOCKED.
Anyways, everything worked as after that just as advertised.
]