So, i tried to do the WireTrick and it f-ed up my phone. i lost recovery + rom and can't flash anything cuz i'm on HBOOT 1.58 S-ON. (UNLOCK HTCdev).
I wanna relock it and run the Sprint RUU.exe but i'm getting the follow error;
_____________________________________________________
C:\rootevo3dnew>fastboot oem lock
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(114):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(166):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.014s
________________________________________________________
Is there any other way to get Lock/Relock?
MANY THX
Sorry I may be wrong and hopefully someone will correct me if I am because I cant remember for sure but since your unlocked, you could install recovery thru bootloader with PG86100.zip. Once you get recovery then you could at least get your phone will working again...
Sent from my Rooted S-OFF EVO 3D
Hit that thanks button if I helped.
scottypeterson said:
Sorry I may be wrong and hopefully someone will correct me if I am because I cant remember for sure but since your unlocked, you could install recovery thru bootloader with PG86100.zip. Once you get recovery then you could at least get your phone will working again...
Sent from my Rooted S-OFF EVO 3D
Hit that thanks button if I helped.
Click to expand...
Click to collapse
No, I can't cuz I still s-on...
Axhole said:
So, i tried to do the WireTrick and it f-ed up my phone. i lost recovery + rom and can't flash anything cuz i'm on HBOOT 1.58 S-ON. (UNLOCK HTCdev).
I wanna relock it and run the Sprint RUU.exe but i'm getting the follow error;
_____________________________________________________
C:\rootevo3dnew>fastboot oem lock
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(114):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(166):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.014s
________________________________________________________
Is there any other way to get Lock/Relock?
MANY THX
Click to expand...
Click to collapse
Is there some reason you can't reinstall a recovery using adb? If you boot to bootloader, I would think you could flash your recovery image using adb commands. Then you should be able to reinstall your rom. I installed my recovery with s-on this way with no issues.
Barring that, I am not sure if the wire trick works on 1.58, I did it before I allowed my hboot to upgrade, but what happens if you try it again? Do you have anything to lose?
Just boot into bootloader, enter fastboot then in fastboot connect usb cable.
In PC you can flash downloaded recovery using "fastboot flash recovery recovery_name.img" command, just make sure that recovery image is in the same dir as fastboot.exe.
Guys, come on. I can't flash/boot recovery. that's the why i wanna relock it. when i try to boot an img, i get the msg "FAILED (remote: reproduce boot image with on-flash ramdisk error)", as far as i know it's cuz the ramdisk is empty. HELP PLEASE. lol.
Helppp!!!
Damn it! Nobody? Any one? I'm phoneless...
http://forum.xda-developers.com/showthread.php?t=1677053
read this thread. there is a command that will restore the backups in the folder with the exe file.
"(bootloader) Lock successfully..."
That line is there, more likely than not you're locked successfully. Run the RUU and see what happens
Axhole said:
Damn it! Nobody? Any one? I'm phoneless...
Click to expand...
Click to collapse
U can flash a zip ruu u just need to dl a signed ruu that u were currently on and run it then extract the zip from the .exe if ur on Windows search in the start menu %temp% delete everything and if it leaves some files that's fine then run the ruu .exe then look in the newest of the 2 folders it creates then find a file in the folder with another folder in it open that folder and find rom.zip move it to desktop and rename PG86IMG.zip place on sd and boot in bootloader and press vol + and u can try the wire trick again if u want
Sent from my PG86100 using xda premium
rockerdudelive said:
http://forum.xda-developers.com/showthread.php?t=1677053
read this thread. there is a command that will restore the backups in the folder with the exe file.
Click to expand...
Click to collapse
i tried that... no good ;-/
beneath-a-burning-turtle said:
"(bootloader) Lock successfully..."
That line is there, more likely than not you're locked successfully. Run the RUU and see what happens
Click to expand...
Click to collapse
NO my friend... it's like, "ok, you got it", then next line you have "NO WAIT, you can't get it" lol. STILL a big "UNLuCKy" ;0)
kickyoace said:
U can flash a zip ruu u just need to dl a signed ruu that u were currently on and run it then extract the zip from the .exe if ur on Windows search in the start menu %temp% delete everything and if it leaves some files that's fine then run the ruu .exe then look in the newest of the 2 folders it creates then find a file in the folder with another folder in it open that folder and find rom.zip move it to desktop and rename PG86IMG.zip place on sd and boot in bootloader and press vol + and u can try the wire trick again if u want
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
i did that and it just reboot with no changes... no errors. darn it!
Axhole said:
NO my friend... it's like, "ok, you got it", then next line you have "NO WAIT, you can't get it" lol. STILL a big "UNLuCKy" ;0)
Click to expand...
Click to collapse
Trust me, I think you got it. When I had a stroke of stupidity and relocked to take ota (which you should NEVER do), it gave me that EXACT line after it said locked successfully and I was locked just fine. Ran the ruu and was back to stock
Sent from my PG86100 using xda app-developers app
I went through similar issues but never got full update to New hboot I had to reunlock my phone flash stock rooted Rom then do wire trick but as previously stated I was still on 1.5 hboot and not sure if wire trick works on 1.58
Sent from my PG86100 using xda app-developers app
I just wanna said to y'all that I really appreciate all the help. I went to a sprint store and the technician told me that my cellphone has a "hardware failure". New cellphone, end of story. Thanks y'all.
Related
So I know I'm a dumb ass but here's what happened:
HTC Rezound S-off
Amon Ra 3.15
Hboot 2.27
ViperRez 1.0.3
My phone was acting a little buggy and my friend kept telling me I should flash a firmware update so I flashed
this " PH98IMG-firmware.zip - 33.02 MB " from here: http://forum.xda-developers.com/showthread.php?t=1835811&highlight=ruu&nocache=1
I checked the MD5 when I dl'd to PC BUT not when I copied to sd card. When flashing, all steps were successful except for 2: MDM9K - FAIL-UZ & RADIO_V2 - FAIL-UZ
I rebooted and got stuck at the white HTC screen. Battery pop and I tried to flash again. This time almost everything returned -- FAIL-PU except for the two above which still said FAIL-UZ.
Adding insult to injury I tried flashing two more RUU's from android police, I have a screenshot attached of one of my failed attempts.
ADB Devices doesn't recognize my phone but FASTBOOT devices returns a serial number. Boot loader also changes from " fastboot" to "fastboot-usb" when I plug into a PC but my PC doesn't see my phone.
I think it was a corrupted RUU because I decided to check the MD5 of a RUU on my sd card after the damage was done and it was bad. I then copied the same file over to my sd card a bunch of times, checking each MD5 and more than half the time they were bad.
I appreciate any suggestions anyone might have.
Sorry, thought I was in the Q & A section. (I already said I was a dumb ass)
Try this one http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Thanks Squirrel...tried that one. That's actually the RUU that I ran for the screenshot. I think the problem has to do with updating my partition in the internal memory.
Squirrel1620 said:
Try this one http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I tried flashing in fastboot...heres what I got:
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor> fastboot -w update rezound_AndroidPolice_4.03.605.2_PH98IMG.z
ip
Whoops: didn't find expected signature
read_central_directory_entry failed
²ετ╪»╛g[ÑÖ╥yïS¬☼û÷A☼├║f:e{ûhh%►ÉÉW└|'╢σG╣S╙τφN}┐{S
c:\mini-adb_vigor>
Yikes!!
Try this in fastboot. Make sure you have the rezound_AndroidPolice_4.03.605.2_PH98IMG.zip in the same directory with fastboot.exe Make sure it is way over 33MB.
fastboot oem rebootRUU
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
Here we go....
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor>fastboot oem rebootRUU
... INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFOerase sector 130560 ~ 131071 (512)
INFOemmc_erase(1853): sd_write_sector failed!
OKAY [ 0.082s]
finished. total time: 0.083s
c:\mini-adb_vigor>
Flyhalf205 said:
Try this in fastboot. Make sure you have the rezound_AndroidPolice_4.03.605.2_PH98IMG.zip in the same directory with fastboot.exe Make sure it is way over 33MB.
fastboot oem rebootRUU
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
Click to expand...
Click to collapse
jksell07 said:
Here we go....
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor>fastboot oem rebootRUU
... INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFOerase sector 130560 ~ 131071 (512)
INFOemmc_erase(1853): sd_write_sector failed!
OKAY [ 0.082s]
finished. total time: 0.083s
c:\mini-adb_vigor>
Click to expand...
Click to collapse
Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. Download a recovery. CWM. AmonRA. or TWRP. A fastboot command would be fastboot boot recovery.img or fastboot flash recovery recovery.img. Use the first command if you can't flash the recovery. If you can get a recovery to load. Flash a rom
Just an idea here. I would go here http://shipped-roms.com/index.php?category=android&model=Vigor and down load one of the "EXE" RUU and try it. These are windows executables, so just double click on the file after downloading. Start with a ICS first and if that dont work try the GB
mclass55 said:
Just an idea here. I would go here http://shipped-roms.com/index.php?category=android&model=Vigor and down load one of the "EXE" RUU and try it. These are windows executables, so just double click on the file after downloading. Start with a ICS first and if that dont work try the GB
Click to expand...
Click to collapse
The .exe basically does the same thing as fastboot oem rebootRUU. Just does it for you in a GUI.
Wish I could help here but curious about something, if he some how flashed a bad dl of an ruu, which contains hboot, and radio's etc..I know that if you have a bad dl of an hboot, or radio and you flash it it would brick your phone. could it be possible he bricked his phone due to this same theory? Except by running an ruu, or could that even be a possibility when updating via ruu? Just my 2cent and ??
Sent from my ADR6425LVW using xda app-developers app
Maybe he can try flashing just the hboot then trying the ruu again
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Maybe he can try flashing just the hboot then trying the ruu again
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Agreed, he is s-off.. you can try doing everything seperately, make sure you check your md5s.. start with your hboot..
Sent from my ADR6425LVW using xda app-developers app
I just got home and my internet connection's out. I'm tethered to my OG droid right now and it is slooooooowww. When it rains, it pours.
" Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. " Thanks Flyhalf205, I already tried unlocking and that was a no go.
I tried messing around in a linux terminal:
" Detect the device using the script provided. Type this in the terminal: ./brickdetect.sh "
(I got this from here - http://forum.xda-developers.com/showthread.php?t=1833530&page=6)
It said something like permission denied.
I'll try flashing an hboot...I had thought about that but since its the only thing working on my phone I was a little hesitant. First I have to get my internet back up and running. I'll check back later.
Everyones help is much appreciated.
jksell07 said:
I just got home and my internet connection's out. I'm tethered to my OG droid right now and it is slooooooowww. When it rains, it pours.
" Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. " Thanks Flyhalf205, I already tried unlocking and that was a no go.
I tried messing around in a linux terminal:
" Detect the device using the script provided. Type this in the terminal: ./brickdetect.sh "
(I got this from here - http://forum.xda-developers.com/showthread.php?t=1833530&page=6)
It said something like permission denied.
I'll try flashing an hboot...I had thought about that but since its the only thing working on my phone I was a little hesitant. First I have to get my internet back up and running. I'll check back later.
Everyones help is much appreciated.
Click to expand...
Click to collapse
Can't wait to hear if it worked. But as famouscollin said, check check and triple check that MD5. A bad hboot = permanent brick
Sent from my ADR6425LVW using xda app-developers app
Here are some confirmed working hboots, in case you were unsure of where to get them or which to use. They are based on the latest release, but have fastboot enabled without HTCDev unlock, and have the "LOCKED" at the top replaced with various other words.
Internet's back up but I won't have a chance to play with my phone until Tuesday night, so I'll post again when I have something to report. :good:
Like to hear how it went for you
mclass55 said:
Like to hear how it went for you
Click to expand...
Click to collapse
Not good. Nothing will flash. The only thing I have left to try is some fastboot erase commands. That might be the nail in the coffin though if I lose hboot.
Heres something else I tried...extracted the img from a RUU:
c:\mini-adb_vigor>fastboot flash mdm9k mdm9k.img
sending 'mdm9k' (23389 KB)... OKAY [ 3.259s]
writing 'mdm9k'... FAILED (remote: not allowed)
finished. total time: 3.575s
Flyhalf205 said:
Stinks to say but it looks like if you have bad blocks
Click to expand...
Click to collapse
If your'e still around, when you say bad blocks, is that something physically wrong like fried or just that the blocks are not accessible? Even if my phone is toast, I'm still curious as to what exactly happened.
I've been rooting phones for a few years now and no matter how bad I messed up my phone, I've always been able to bring it back from the brink. I was starting to think that bricking your phone wasn't really possible. It's like your dog dying and learning about death for the first time.
That's weird, I've only seen the remote not allowed when the bootloader is locked and you are s on
Can you try and unlock even though you are s off?
Sent from my ADR6425LVW using xda app-developers app
jksell07 said:
If your'e still around, when you say bad blocks, is that something physically wrong like fried or just that the blocks are not accessible? Even if my phone is toast, I'm still curious as to what exactly happened.
Click to expand...
Click to collapse
A bad HBOOT will cause a bad block. I am not sure how I can explain it. But the original MD5 did not match the one you downloaded and so it was a bad flash but this time a bad flash that can't be undone.
I know this sounds crazy. But trying doing the wire trick again and if asked to flash HBOOT. Do it!
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
I purchased a EVO 4G LTE for my sister a little while back and recently she had her boyfriend attempt to root it for her, and since I'm here it obviously didn't go over all too well. All he said he did was follow a video (which he gave me) on how to root for the newer software version. "Something happened and it didn't work so I watched another video and tried that" The phone is currently unlocked with S-ON and he flashed a working version of TWRP and cm10 couldn't figure it out and here we are. help please. Rooted using Linux. i did some reading and found out i had to flash the boot.img through fastboot. it just hangs at <waiting for device> in the terminal. Apologies if this has been answered, if so please point me in the right direction.
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
BusstopBill44 said:
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
Click to expand...
Click to collapse
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
jesuscash said:
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm not really sure what he did or why he even tried. How can I check adb to see if that was done correctly?
tilltheend714 said:
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
Click to expand...
Click to collapse
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
Boot into bootloader and check the radio. If its 1.12.11.1210 then he took the 3.16 OTA and your only choices are what premo15 said.
premo15 said:
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm: (Had to remove link)
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
BusstopBill44 said:
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
Click to expand...
Click to collapse
Did you run babyracun before relocking and running the ruu?
tilltheend714 said:
Did you run babyracun before relocking and running the ruu?
Click to expand...
Click to collapse
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
re-flash twrp
bigdaddy619 said:
re-flash twrp
Click to expand...
Click to collapse
another error, $ sudo ./fastboot flash recovery openrecovery-twrp-2.4.2.0-jewel.img
sending 'recovery' (8032 KB)...
OKAY [ 1.277s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.107s
and tried it with 2.4.1.0, which i had before, as well.
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again.
Click to expand...
Click to collapse
^^^^ true
I don't know if this will work since you've already tried dirtyracun; but I just used this method to achieve s off. It's ridiculously easy, and took me 5 minutes..
http://forum.xda-developers.com/showthread.php?t=2163013
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
Click to expand...
Click to collapse
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
BusstopBill44 said:
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
Click to expand...
Click to collapse
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
tilltheend714 said:
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
Click to expand...
Click to collapse
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
BusstopBill44 said:
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=2163013
But that requires root. You don't have a 2gb card laying around anywhere?
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
andres8900 said:
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
Click to expand...
Click to collapse
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
shubham211995 said:
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
Click to expand...
Click to collapse
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
andres8900 said:
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
Click to expand...
Click to collapse
Are you sure that your sdcard slot is working ??
Sent from my HTC_Amaze_4G using xda app-developers app
Mobilicity ruu isn't working it's a firmware zip with a update it's not a ruu... And it's not a brick.. Also a ruu can't be flashed from recovery... Flash the t mobile R2 RUU from bootloader and it'll work.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
I'm somewhat of a noob at this - this is my first HTC, so I had no idea what S-Off or unlocked bootloader meant. With my Samsung, rooting and installing a custom recovery involved a one-click method, so I never had to learn all the ins and outs of this stuff. With this DNA, I used the revone method (since the phone was purchased with 2.06 firmware already installed), so I still didn't need to learn much.
Anyway, I recently tried to go back to stock. I figured that would involve an RUU, going back to S-On, and locking the bootloader. So I first (yes, before performing the RUU like a dodo) used revone to go back to S-On, then found something saying I needed to execute "fastboot oem writesecureflag 3", so I did that, and now I am stuck at fastboot. I don't have access to CWM recovery, and if I try to boot beyond fastboot it hangs on the initial HTC screen.
Without being able to use ADB since it doesn't boot that far, I can't go back to S-Off via revone. I can't flash anything that I have been able to find so far via fastboot because it fails at signature verification. And I can't use the RUU that I found because it is firmware 1.15 and it won't allow me to install on top of 2.06.
Does anyone have any ideas on how to fix this? Is there a way to get to S-Off through fastboot? Is there an RUU for the 2.06 firmware? I have spent a few days searching and the answer to both seems to be no...
UPDATE: I grabbed the Rom.zip out of the 1.15 RUU and tried flashing that via fastboot (in RUU mode). I got the following message:
sending 'zip' (913111 KB)...
OKAY [ 35.667s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 118.073s
Click to expand...
Click to collapse
I assume this has something to do with the firmware version difference (1.15 vs. 2.06). But I was very excited to see a signature check be successful for once.
I should note that the ROM I was running when doing this was Newt's NOS m7 v 3.0.6
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Phaded said:
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Click to expand...
Click to collapse
It doesn't do nothing per se, it shows a screen that I'm not used to with a red triangle and exclamation point on top of a picture of a phone with a blue background. I assume this is the recovery screen from the factory, not the CWM recovery I had installed previously.
Is there a way to get s-off without ADB (only using fastboot)?
Flash firmware zip located on the moonshine thread, then use moonshine
Phaded said:
Flash firmware zip located on the moonshine thread, then use moonshine
Click to expand...
Click to collapse
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
jdpalmer2k13 said:
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
Click to expand...
Click to collapse
I've been thinking about this. Why did the firmware zip from Moonshine pass signature inspection? Was it signed? Could that same signature be placed on a rom or some other zip that installs a recovery or even somehow performs s-off? I know I am not very well experienced with android development, so I'm probably talking out of my ass.
I recently flashed the RUU from fastboot.
http://forum.xda-developers.com/showthread.php?t=2115987 post#4
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
bwhxeon said:
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
Click to expand...
Click to collapse
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
jdpalmer2k13 said:
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
Click to expand...
Click to collapse
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
bwhxeon said:
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
Click to expand...
Click to collapse
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Phaded said:
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Click to expand...
Click to collapse
Correct, the guide was not at fault here, I am just an idiot. Here are the results of flashing the dna2.06firmware.zip file from the moonshine thread: http://pastebin.com/GkgdGt19
Following what is shown at this link, I executed "fastboot reboot-bootloader", selected "Power Down", and then tried to turn the phone on again. I got the same result as always (stuck on the initial HTC quietly brilliant screen - not the bootanimation screen).
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
jdpalmer2k13 said:
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
Click to expand...
Click to collapse
I talked to beaups last night about the same thing... Hes a good guy. I'm in the exact same boat. I hope there is a break through on this but if not I guess JTAG is our only option. Let me know if you figure anything out jdpalmer, i'd really appreciate it.
Try this please
fastboot oem readcid
What's it say?
Phaded said:
Try this please
fastboot oem readcid
What's it say?
Click to expand...
Click to collapse
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
PiperBen85 said:
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
Click to expand...
Click to collapse
Yep same here
jdpalmer2k13 said:
Yep same here
Click to expand...
Click to collapse
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Phaded said:
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Click to expand...
Click to collapse
Yes, I am locked. Here is the result of trying to writecid:
Code:
C:\Android>fastboot oem writecid 22222222
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.005s