A lot of people have said they cant get recovery to work when they use the HTC unlock method. I too had this problem with twrp. But IEF sent me a link to a CWM that worked fine for me. It didnt reboot when I tried to go into recovery like twrp did. So give this one a shot. I flashed in fastboot: fastboot flash recovery filenname.img
I was able to also do a nandroid restore.
http://www.multiupload.com/AQ9KV7IME9
so you had to start a whole new thread about this instead of using one of the other 27 topics ?
CheesyNutz said:
so you had to start a whole new thread about this instead of using one of the other 27 topics ?
Click to expand...
Click to collapse
yes, because I didnt want it to get buried in a thread or have to post the link in the "27" topics that are discussing recovery not working. This thread isnt like those. it offers a solution to the recovery problem (at least one that worked for me)
graffixnyc said:
yes, because I didnt want it to get buried in a thread or have to post the link in the "27" topics that are discussing recovery not working. This thread isnt like those. it offers a solution to the recovery problem (at least one that worked for me)
Click to expand...
Click to collapse
+1 on this, it needed a new thread so it doesn't get burried. Hopefully this will work for the people that never had s-off before.
Thanks for the tip - this worked. I had tried the newer version of CWM without success.
I already rooted with s-off and have the eng hboot myself but I was wondering...
Once you take this update can you flash the eng hboot and then flash twrp?
Thankyou for recovery. Got my root back with it.
Sent from my PG86100 using Tapatalk
SITH16 said:
I already rooted with s-off and have the eng hboot myself but I was wondering...
Once you take this update can you flash the eng hboot and then flash twrp?
Click to expand...
Click to collapse
nope, well I'm not sure. I know I wasnt able to on my buddies phone who I used the HTC unlock method(his phone was new never rooted or anything like that) I went to flash the eng boot and it would start to parse the zip the kick out back to the bootloader with no error message. Also I couldnt flash splash screens. When I tried the zip it did the same thing as the eng bootloader zip and when I tried flashing in FB I got an error about a signed bootloader. I think they only partially unlocked the phone. You can flash roms and certain recoveries(not sure why) but I dont think you can flash bootloaders, radios or splashes (have only confirmed not being able to flash splashes and the eng hboot so far)
I can also confirm I was able to flash a rom (I used this one from Haus: http://forum.xda-developers.com/showthread.php?t=1223979) after flashing this recovery.
cruise350 said:
+1 on this, it needed a new thread so it doesn't get burried. Hopefully this will work for the people that never had s-off before.
Click to expand...
Click to collapse
What you just said contradicted itself. There are already 27 topics on the subject (hyperbole), so let's make another to pile on top of it so it doesn't get buried. However, if everything thinks this way we will get another pile of topics that will bury each other. If every stuck with the same thread from the beginning they would never be buried under duplicate threads.
Korey_Nicholson said:
What you just said contradicted itself. There are already 27 topics on the subject (hyperbole), so let's make another to pile on top of it so it doesn't get buried. However, if everything thinks this way we will get another pile of topics that will bury each other. If every stuck with the same thread from the beginning they would never be buried under duplicate threads.
Click to expand...
Click to collapse
I have only seen threads about recovery not working after the HTC unlock. I didnt see any about a solution. Only people saying"recovery not working after HTC unlock" So yeah instead of posting the solution in all of those "recovery not working threads" I created a new thread offering a solution.
All I see is a bunch of threads full of people whining about how many threads there are. Seriously - it's like a bunch of retards trying to hump a doorknob. Let's move on.
graffixnyc said:
I have only seen threads about recovery not working after the HTC unlock. I didnt see any about a solution. Only people saying"recovery not working after HTC unlock" So yeah instead of posting the solution in all of those "recovery not working threads" I created a new thread offering a solution.
Click to expand...
Click to collapse
You could have changed your thread to this thread though. Just saying.
Sent from my PG86100 using XDA Premium App
I was able to flash the recovery and i did back up and flashed it with Stock Rooted 2.08.651.2 Odexed ..and i now have root
graffixnyc said:
nope, well I'm not sure. I know I wasnt able to on my buddies phone who I used the HTC unlock method(his phone was new never rooted or anything like that) I went to flash the eng boot and it would start to parse the zip the kick out back to the bootloader with no error message. Also I couldnt flash splash screens. When I tried the zip it did the same thing as the eng bootloader zip and when I tried flashing in FB I got an error about a signed bootloader. I think they only partially unlocked the phone. You can flash roms and certain recoveries(not sure why) but I dont think you can flash bootloaders, radios or splashes (have only confirmed not being able to flash splashes and the eng hboot so far)
Click to expand...
Click to collapse
If this is the case, then I'd have to argue that this is only a partial unlock... Its not worth it in my opinion to give up your warranty and still not have full unlock.
FAIL htc...
SITH16 said:
If this is the case, then I'd have to argue that this is only a partial unlock... Its not worth it in my opinion to give up your warranty and still not have full unlock.
FAIL htc...
Click to expand...
Click to collapse
I agree, Glad I did revolutionary on my phone fully unlocked and still have my warranty. Although most warranty issues I've had over the years have all been hardware related.
SITH16 said:
If this is the case, then I'd have to argue that this is only a partial unlock... Its not worth it in my opinion to give up your warranty and still not have full unlock.
FAIL htc...
Click to expand...
Click to collapse
I guess we can call it "Partia-Root". Yeah, that's the root where you kind of have root access to the device and S-On at the same time. I wonder if the S-On is really the second half of the "Real-Root" that we are lucky enough to have gotten from Revolutionary.
This thread is good as it does present the solution (modified recovery) to those that were completely stuck before but it does bring to light just what you get/don't get with the HTC Unlock.
Time will tell...
Hm... I'm not sure what to do about this one... Anyone else had an issue with INFO signature checking?...
sending 'recover' (4832 KB)... OKAY
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
catejust said:
Hm... I'm not sure what to do about this one... Anyone else had an issue with INFO signature checking?...
Click to expand...
Click to collapse
What version of recovery did you try?
So has anyone gotten a newer version of recovery to flash yet?
Related
Hi I need help going back to completely stock and my hboot is 1.50 any help or direction thanks!!
Kratz17 said:
Hi I need help going back to completely stock and my hboot is 1.50 any help or direction thanks!!
Click to expand...
Click to collapse
In the general section look into the sticky there is a guide for you there to go to stock relock . Here ya go http://forum.xda-developers.com/showthread.php?t=1388501
Weeping with frustration
reaper24 said:
In the general section look into the sticky there is a guide for you there to go to stock relock . Here ya go http://forum.xda-developers.com/showthread.php?t=1388501
Click to expand...
Click to collapse
Why the **** will this image you linked NOT flash my phone?! It loads, checks then just dumps me at the hboot screen! Ive got hboot 1.5(obviously) and the latest software 2.17.651.5. Even the .2 RUU exe will NOT work, continuously gives me hboot version error. I believe its error 140. I NEED to unlock this thing...or get pissed and hit it with a hammer.
reaper24 said:
In the general section look into the sticky there is a guide for you there to go to stock relock . Here ya go http://forum.xda-developers.com/showthread.php?t=1388501
Click to expand...
Click to collapse
Thanks a lot I'll try when I get home tonight.
Sent From My RED 3Dimension
tailsthecat3 said:
Why the **** will this image you linked NOT flash my phone?! It loads, checks then just dumps me at the hboot screen! Ive got hboot 1.5(obviously) and the latest software 2.17.651.5. Even the .2 RUU exe will NOT work, continuously gives me hboot version error. I believe its error 140. I NEED to unlock this thing...or get pissed and hit it with a hammer.
Click to expand...
Click to collapse
If you hit it with a hammer it will be broken for good lol. Did you try to re root with HTC dev way? The link was for this guy to relock his phone .
reaper24 said:
If you hit it with a hammer it will be broken for good lol. Did you try to re root with HTC dev way? The link was for this guy to relock his phone .
Click to expand...
Click to collapse
HTC unlock method will not work. I flash the token and it just sits there...Im trying to revert to .2 so I can actually unlock, like I have with two other 3d's but the friggin RUU exe tells me bootloader version error which is 140, I believe. I should know, I saw it 356 times last night.
tailsthecat3 said:
HTC unlock method will not work. I flash the token and it just sits there...Im trying to revert to .2 so I can actually unlock, like I have with two other 3d's but the friggin RUU exe tells me bootloader version error which is 140, I believe. I should know, I saw it 356 times last night.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1337379. Read this might help you. Hope it works for you. Sounds like the issue a few folks were having.
Weeping with frustration
reaper24 said:
http://forum.xda-developers.com/showthread.php?t=1337379. Read this might help you. Hope it works for you. Sounds like the issue a few folks were having.
Click to expand...
Click to collapse
Tried that a million times last night. And just now, just because.
I took a video of the process because I couldnt read what the RUU was saying. After updating signature, very quickly it says Checking Header...then it says checking MID/CID and then I get the screen that is attached! [Expletive deleted!]
tailsthecat3 said:
Tried that a million times last night. And just now, just because.
I took a video of the process because I couldnt read what the RUU was saying. After updating signature, very quickly it says Checking Header...then it says checking MID/CID and then I get the screen that is attached! [Expletive deleted!]
Click to expand...
Click to collapse
Have you tried it with adb ? What program are you using ? Though u could flash it in hboot . After using adb to relock it.
reaper24 said:
Have you tried it with adb ? What program are you using ? Though u could flash it in hboot . After using adb to relock it.
Click to expand...
Click to collapse
It is locked. Its new. That screen comes from the .2 RUU exe.
I havent tried anything with adb. I havent used adb since the Evo4g. Have a link?
I have tried running the RUU with windows, I have tried PG86IMG.zip's, Ive tried RUU's while already being in fastboot. When I try using PG86IMG's through hboot, it loads the file, checks the file then dumps me back at the Hboot screen.
tailsthecat3 said:
It is locked. Its new. That screen comes from the .2 RUU exe.
I havent tried anything with adb. I havent used adb since the Evo4g. Have a link?
I have tried running the RUU with windows, I have tried PG86IMG.zip's, Ive tried RUU's while already being in fastboot. When I try using PG86IMG's through hboot, it loads the file, checks the file then dumps me back at the Hboot screen.
Click to expand...
Click to collapse
Adb is what most folks use to do all there stuff. You have to have adb installed to do the HTC devs route from what I have read. So the phone is locked and your tryin to root it. But are gettin errors ?
So your phone now is hboot 1.5 and is currently up to date and your tryin to root it HTC dev route but get errors?
Got the pistol in my hand, thumb on the hammer.
reaper24 said:
Adb is what most folks use to do all there stuff. You have to have adb installed to do the HTC devs route from what I have read. So the phone is locked and your tryin to root it. But are gettin errors ?
So your phone now is hboot 1.5 and is currently up to date and your tryin to root it HTC dev route but get errors?
Click to expand...
Click to collapse
Yeah exactly. But posted on xda, you cant htc dev it with any software other than 2.08.651.2, which for some bizarre ass reason, I cant downgrade to!
I tweeted the other day "when the **** did adb move?!". so thats how long ago I used it. Im familiar with it, I used to delete all my bloat with adb, which was a painstaking process.
tailsthecat3 said:
Yeah exactly. But posted on xda, you cant htc dev it with any software other than 2.08.651.2, which for some bizarre ass reason, I cant downgrade to!
I tweeted the other day "when the **** did adb move?!". so thats how long ago I used it. Im familiar with it, I used to delete all my bloat with adb, which was a painstaking process.
Click to expand...
Click to collapse
That sucks I am on the newer software was gonna root soon . I'm sure HTC will have a update on the dev to allow root.
tailsthecat3 said:
Yeah exactly. But posted on xda, you cant htc dev it with any software other than 2.08.651.2, which for some bizarre ass reason, I cant downgrade to!
I tweeted the other day "when the **** did adb move?!". so thats how long ago I used it. Im familiar with it, I used to delete all my bloat with adb, which was a painstaking process.
Click to expand...
Click to collapse
This looks similar:
http://forum.xda-developers.com/showthread.php?t=1447839&page=5
reaper24 said:
That sucks I am on the newer software was gonna root soon . I'm sure HTC will have a update on the dev to allow root.
Click to expand...
Click to collapse
I am gonna look more into it when I get to my computer.
Finger on the trigger, hammer pulled back. Just unlock already!!
reaper24 said:
I am gonna look more into it when I get to my computer.
Click to expand...
Click to collapse
Thanks dude. Hopefully we can unlocked and junk. Did I mention I also love the reaper? Multiple reaper tattoos inspired by children of bodom album art. But I digress.
It would be nice if HTC updated their bootloader unlock method but frankly, I dont see that happening. I called them today and they dont support anything.
tailsthecat3 said:
Thanks dude. Hopefully we can unlocked and junk. Did I mention I also love the reaper? Multiple reaper tattoos inspired by children of bodom album art. But I digress.
It would be nice if HTC updated their bootloader unlock method but frankly, I dont see that happening. I called them today and they dont support anything.
Click to expand...
Click to collapse
I'm sure there is a way to do it . Even on the new update cause hboot is still the same . I never had trouble back in the og EVO days when it came to root.
reaper24 said:
I'm sure there is a way to do it . Even on the new update cause hboot is still the same . I never had trouble back in the og EVO days when it came to root.
Click to expand...
Click to collapse
Who's stock with the latest update? Try the .2 RUU?
I'm absolutely stumped. My brain is hot because of it.
Sent from my Google Nexus S 4G via XDA Premium
Just rooted my phone Htc devs way no issues on the latest update and hboot 1.5
reaper24 said:
Just rooted my phone Htc devs way no issues on the latest update and hboot 1.5
Click to expand...
Click to collapse
How did you do it???? Please help me/us out..I have the exact same problems, tried using the 2.08 RUU's and get an error 140. And when I try the HTC unlock method at step 12 when I flash the unlock_code.bin nothing happens, no disclaimer shows up. I am on 2.17.651.5 latest OTA and HBOOT 1.5.
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
Yes, it worths at least for myself. I have hboot 1.50 too and i rooted fast with no problems.
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
More than likely, yes. Most users who follow the guides don't seem to have issues.
The HTC unlock method changes the dynamics a bit from previous common and accepted methods. Many "new" users become between old and current guides.
As far as I've seen, there are only three limitations to hboot 1.5, compared with early "compromised" versions using the AlphaRevX revolutionary method.
1) Kernel is not able to be flashed from recovery mode. Work arounds include: flashing from normal Android mode, my app is great for that, Flash Image GUI. Loading the custom recovery from fastboot. Flashing the kernel from fastboot. Using the "dumlock" method with TWRP.
2) Unable to selectively flash radio images
3) Unable to selectively flash intial splash screens
If I'm missing anything, I'm sure somebody else can post up.
None of those seem like deal breakers to me. Thanks for the fast replies.
It's kind of a ***** just because you have to do a few extra steps but if you know what your doing you won't screw it up.
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Root is the way to go Get rid of bloat Also adb isn't hard I always fastboot boot recovery.img and wipe flash no issues
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
ls3mach said:
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
Click to expand...
Click to collapse
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
That is what he needs to do to fix .
Sent from my PG86100 using xda premium
DjNawo said:
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Click to expand...
Click to collapse
You have Hboot 1.5 with S-off?
G.Newton said:
You have Hboot 1.5 with S-off?
Click to expand...
Click to collapse
No he doesn't from what he said he is stock and asking if he should root
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
Much obliged!
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
I think some people just got ahead of themselves flashing wrong files. I got a bit worried too first go round after coming from a.Transform.
In my signature I've got a guide/flashing notes that are a bit more updated than some of the stickied threads that may help clear some things up.
Sent from my PG86100 using Tapatalk
What root did you use
Sent from my EVO 3D using XDA Premium
[/COLOR]
Yoyodude1124 said:
What root did you use
Click to expand...
Click to collapse
I used the HTC Unlock (zedomax's video), CWM Recovery, Su 3.07 zip, BusyBox (market), all layed out here:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
Hey thanks again. Yeah I have the newest update, so i would need to get the 2.17 that xcp mentioned. Also, thanks for the guide above.
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?
Sorry if the answers im looking for are somewhere else but i cant find them. Im not new to the rooting game but it has been awhile, last phone rooted was the original evo and ive fallen behind on the new software and such. anyways ive rooted successfully and am running hboot 1.19 with s-on. for some reason i get the same error message when flasing a rom saying that sdcard cannot be found. do i need to be running s-off with 1.19 to flash roms? Thanks!
zolis1931 said:
Sorry if the answers im looking for are somewhere else but i cant find them. Im not new to the rooting game but it has been awhile, last phone rooted was the original evo and ive fallen behind on the new software and such. anyways ive rooted successfully and am running hboot 1.19 with s-on. for some reason i get the same error message when flasing a rom saying that sdcard cannot be found. do i need to be running s-off with 1.19 to flash roms? Thanks!
Click to expand...
Click to collapse
What rom are you flashing? What recovery are you using? What release of said recovery are you using? can you see the sdcard in the listing of the recovery screen?
rawintellect said:
What rom are you flashing? What recovery are you using? What release of said recovery are you using? can you see the sdcard in the listing of the recovery screen?
Click to expand...
Click to collapse
i was trying to flash the new 4.2.2 CM10.1 rom, when i found that wasnt working, i tried to flash jellybam and that didnt work either. Im using TWRP v 2.1.8 and i can see the sdcard listing. ive done all the routine wiping and such. do you think its an issue of hboot and s-on?
this is the error message i get.
E: Unable to stat '/sdcard2/.
Error flashing zip '/sdcard/cm-10-1.zip"
You need to update twrp
bigdaddy619 said:
You need to update twrp
Click to expand...
Click to collapse
ahh such a simple solution lol. will this take care of the s-on?
zolis1931 said:
ahh such a simple solution lol. will this take care of the s-on?
Click to expand...
Click to collapse
Hopefully that all that is needed... but S-OFF is the way to go if you can do it. It will save you so many headaches in the future. HTC is making it harder on s-on people to do anything to their phone, this started with the 3.15 JB update and will probably get worse. S-OFF my friend S-OFF
bigdaddy619 said:
Hopefully that all that is needed... but S-OFF is the way to go if you can do it. It will save you so many headaches in the future. HTC is making it harder on s-on people to do anything to their phone, this started with the 3.15 JB update and will probably get worse. S-OFF my friend S-OFF
Click to expand...
Click to collapse
I would love to go s-off as on my old evo but unfortunately, my pc is a thing of the past and im now stuck with a macbook :/
zolis1931 said:
I would love to go s-off as on my old evo but unfortunately, my pc is a thing of the past and im now stuck with a macbook :/
Click to expand...
Click to collapse
Ubuntu can be installed on macbooks:
https://help.ubuntu.com/community/MactelSupportTeam/AppleIntelInstallation
Flashing a newer recovery didnt work, im just going to borrow a friends pc tomorrow and go s off
zolis1931 said:
Flashing a newer recovery didnt work, im just going to borrow a friends pc tomorrow and go s off
Click to expand...
Click to collapse
Hold the phone. Flashing TOO new of a recovery (like TWRP 2.4.1) can also cause problems. There's something that the dev has to place in the ROM in order to be compatible with 2.4.1. May I suggest you try 2.3.1? It seems to be the "sweet spot" and works with most ROMs out there today.
Here's the install page for the evo 4g LTE:
http://teamw.in/project/twrp2/98
rawintellect said:
Hold the phone. Flashing TOO new of a recovery (like TWRP 2.4.1) can also cause problems. There's something that the dev has to place in the ROM in order to be compatible with 2.4.1. May I suggest you try 2.3.1? It seems to be the "sweet spot" and works with most ROMs out there today.
I shall give that a shot now
Click to expand...
Click to collapse
zolis1931 said:
rawintellect said:
Hold the phone. Flashing TOO new of a recovery (like TWRP 2.4.1) can also cause problems. There's something that the dev has to place in the ROM in order to be compatible with 2.4.1. May I suggest you try 2.3.1? It seems to be the "sweet spot" and works with most ROMs out there today.
I shall give that a shot now
Click to expand...
Click to collapse
cool. and if you can't find them here is the link to the fastboot images:
http://techerrata.com/browse/twrp2/jewel
these are flashed via fastboot with the command:
fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img command
Click to expand...
Click to collapse
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
chirayu said:
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
Click to expand...
Click to collapse
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Greenfieldan said:
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Click to expand...
Click to collapse
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
chirayu said:
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
Click to expand...
Click to collapse
Is your goal to flash another ROM or to go back to stock?
If you're going to be trying to flash another ROM I'd highly recommend running rumrunner and getting s-off. Otherwise there are a lot of hoops you'll need to jump through in order to flash ROMs (for starters, you'll need to flash the kernel separately).
Code:
Greenfieldan said:
Is your goal to flash another ROM or to go back to stock?
Click to expand...
Click to collapse
Whichever one is faster, I just want the phone up and running again.
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least a usable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Greenfieldan said:
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least asable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Click to expand...
Click to collapse
RUU fails with errors and it gets stuck at "HTC" screen
Do you have HTC Sync installed on your computer?
Greenfieldan said:
Do you have HTC Sync installed on your computer?
Click to expand...
Click to collapse
Ah, I think something else made me delete it.
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Greenfieldan said:
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Click to expand...
Click to collapse
Thank you! giving that a try now
greenfieldan said:
that'll do it. You need to have htc sync and all of the necessary drivers to run the ruu
Click to expand...
Click to collapse
error [155]: Uknown error
chirayu said:
error [155]: Uknown error
Click to expand...
Click to collapse
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Greenfieldan said:
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Click to expand...
Click to collapse
You're a life saver! at least you can bet I have rooting/unrooting down for this EVO. Just like the old times
Moved to Q&A forum