hey guys/gals, let me start off by saying that i knew better but as always i screwed up by letting my add get the best of me! i relocked bootloader to RUU to stock . problem is that i didnt load the correct splash1 first! now when i try to flash anything i get the signature error. im hoping that a work-around is available. i tried the htcdev but get an error 160 MID not allowed. tried the toolkit(s) available, NO ADB!!! soooo here i am hoping that you guys might have experienced a moment of dumbness as i did....i get a multitude of errors when trying to flash stuff (error 12 sig failure,wrong main version error)...was unlocked and rooted per rumrunner (THANKS BEAUPS!!!!!) prior to my screw up... heres what i have
s-on
hboot-1.33.0001
radio-1.01.1112
baseband-1.01.01.1112
version main-3.06.605.4
cid-VZW_001
bootloader-041a62aa
(lmk if any further info is needed)
like i stated before , i know i needed to flash splash1 BEFORE locking bootloader but in my defense i had my 11 week old son in my arms (multitasking FAIL) , so if you guys have ANY suggestion please feel free to lmk...THANKS IN ADVANCE as this is a new problem for me!
and btw, i spent yesterday sifting through threads to try to solve this ,to no avail....i didnt want to tie you guys up prematurely
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
stephenculkin6277 said:
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
Click to expand...
Click to collapse
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
i get the error:remote not allowed....I had those files downloaded yesterday
i just tried in the rebootRUU status (blask screen with HTC logo and got error 43 main versio check fail?
i got firmware2 to run (both times) ... do i need to try to reset to stock from bootloader now?
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
stephenculkin6277 said:
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
Click to expand...
Click to collapse
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
k thanks, but I think the problem im having running the RUU is the image...whatever that is, I think the splash1 I forgot to load...I will try running the jb_50 RUU now though , thanks
finanandroid said:
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
Click to expand...
Click to collapse
finanandroid said:
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
Click to expand...
Click to collapse
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
stephenculkin6277 said:
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
Click to expand...
Click to collapse
You're welcome! glad that you can back on business. :victory:
Instructions clearly said the splash image was only for custom splash images. It is not a necessary step.
Sent from my DLX using xda app-developers app
See that's the thing, I was running pro bam which had a non stock splash img so I assumed I had to, my bad
You may need to reinstall adb?
thayl0 said:
You may need to reinstall adb?
Click to expand...
Click to collapse
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
stephenculkin6277 said:
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
Click to expand...
Click to collapse
You can no longer do that any more.
That sucks donkey balls!
If you're s-off you can set cid to 22222222 and get an unlock token at htcdev
Thank you sir! I now have the token I have been needing!
Sent from my HTC6435LVW using xda app-developers app
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.
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?
please delete
chazking said:
Did a boo boo and flashed a recovery to kernel got the phone back to working again just not working the right way cannot relock bootloader as when i try to it will just go into a reboot mode and just reboot into bootloader everytime tried flashing ruu will not take as i did the over the air and have those radios and bootloader tried doing ota and that will not go through either please help if you can am lost been trying for 5 days to get this fixed and just can't thank you for your help in advance
Click to expand...
Click to collapse
Dude, thats like the longest run on sentence I have seen in a LONG time. Can you slow down a bit add a few periods for us? Are you S-ON or S-OFF.
please delete
chazking said:
sorry hate typing i am s-on
Click to expand...
Click to collapse
to relock the bootloader just type this in when you are in the bootloader screen where it says fastboot usb
Code:
fastboot oem lock
then you can run the RUU then after the RUU is done flash you Unlock_code.bin and it will re-unlock the bootloader then you can take the OTA
please delete
chazking said:
won't work already tried that as i did over the air wont run ruu and bootloader will not relock as explained above thanks for the reply though
Click to expand...
Click to collapse
Well considering I couldn't understand half of the op because of how run on it was...
Sent from my HTC6435LVW using xda app-developers app
chazking said:
won't work already tried that as i did over the air wont run ruu and bootloader will not relock as explained above thanks for the reply though
Click to expand...
Click to collapse
the bootloader should still lock regardless of if you took the ota
please delete
please delete
It was ok man just giving ya a hard time. English is my one and only language and I suck at it so.. hope you get things working..
Not pointed at you zone23, you were trying to help
Help! My DNA isn't working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldn't mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Edit: Phone is now fixed, I went to IRC and a guy named Beaups took remote control and fixed it. Im not sure if thats his XDA username or not but if you guys see him make sure to give him a thanks Night everyone
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Its ok its very fixable, at this point. Just be very careful and very patient.
The worst thing you can do with something like this is get in a hurry or try to fix it while you're still very stressed out.
I'm passing on this advice because I almost screwed up yesterday because I made a boo boo and was in a huge hurry.
I'm going to wait for someone who knows more about this particular issue to chime in, but you have my word, I will help you resolve it after I do some more research while I wait for someone with more information or experience to post some info.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
In the original unlock downloader thread, there is a link to an irc chatroom, I would suggest you go there as well as look for help here, and be patient waiting for some one to respond ...
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Click to expand...
Click to collapse
Thats pretty much what I did but I keep getting that error:178 image file problem when its trying to finish (I am using the RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe RUU) Also my phone is recognized as 2.04 when I haven't flashed anything
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Re-Unlock your bootloader with your Unlock token (Unlock_code.bin) then do a fastboot flash recovery recovery.img and use the CWM recovery that is 6.0.2.8 (i believe is the most recent version) and you should be able to sideload your rom ... or if sideloading doesnt work just do an adb push rom.zip /sdcard/rom.zip and that will put the rom that you want to use on the root of the sdcard and then you can flash that there...
This should hopefully get you working again...
beasleyj62 said:
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Click to expand...
Click to collapse
I keep getting this when I flash the hboot
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.274s
and when I flash the Radio I get
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
beasleyj62 said:
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
Click to expand...
Click to collapse
I can unlock it at anytime....
see if you can flash after you unlock again
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
All I needed to run the RUU was the ENG Hboot. Flash it then you should be able to install the RUU provided you have the correct drivers installed.
Sent from my HTC6435LVW using xda app-developers app
He is still s-on.
Sent from my HTC Droid DNA
Andro X said:
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
How would I go about doing that?
beasleyj62 said:
see if you can flash after you unlock again
Click to expand...
Click to collapse
I didnt work. This is my 2nd DNA so I have done this before and it worked successfully(The first one had a screen problem)
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Halcyon7 said:
How would I go about doing that?
Click to expand...
Click to collapse
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
beasleyj62 said:
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I only found 1 link on my computer doctors forum but that link wasn't it
.torrented said:
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
Click to expand...
Click to collapse
No I haven't. I used the s-off facepalm method and I did everything as it said and now when I went into recovery nothing will mount and my device when trying to use the RUU says its a 2.04. So I didnt take the ota but thats what it is recognized as
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