I successfuly rooted , Cyanogenmod 10.2.1-dlx. It was a stumbly road for me, fully grasping the steps (which now, i get it), S-off, waeksauce, SU, then the ROM.
my issue: after S-off, weaksauce, and SU, i was rooted, able to use the great apps etc, and had my stock - still tuned as it was before. was GREAT. none of that required a FULL wipe of my apps and data. Then i flashed Cyanogenmod, and as great as much about it is, (i had it years ago on HTC Incredible) there are a few issues that i CANNOT stay with.
Gmail account contacts / sync is all kinds of screwed. (not worried about cus all backed up and will get resolved)
My MHL adapter - usb misco to HDMI adapter - not supported
The HTC stock camera i LOVED. slow motion video camera i NEED. I hate the cyanogenmod camera. my instagram - www.instagram.com/benjamin.blue
and other(s) i forget this moment.
point is, can i uninstall the ROM and go back to the previous state of ROOTED stock, as oppposed to starting from scratch? and if i have to start from scratch, kindly point me towards quickest steps. If thats the case, i WILL now backup everything via titanium backup AND MyBackup Pro.
guessing i could use the backups i SHOULD have in CWM recovery, assuming i made one pre-cyanogenmod, and pretty sure i get md5 errors trying any restore.
thanks for patience - i have indeede googled like hell before making this post, on top of many full nights of brain implosion.
ben
EDIT - see next post - all i want is to unroot completely.
http://forum.xda-developers.com/showthread.php?p=48250930
You must wipe data and cache when changing ROMs. App backup apps can cause some issues, so restore wisely.
Sent from my One using XDA Free mobile app
i have been searching far and wide and am desperate to get my DNA back to stock, so i can activate it and use it again. i am trying every bit of sense and good advice and tutorials and my brain is just exhausted. i know i can get this, i just need a little help.
i have relocked it, and followed the instructions for running the RUU - 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 - exactly, and keep getting ERROR 155.
one thing i notice is during the RUU, it says going "from image" "to image" the from is blank. i click update ROM, it fills the "to" field with the RUU, 1.15, and, it runs for a minute ish and i get ERROR 155. Thanks guys I am really having a tough time.
i just tried again with new download of RUU. same results.
bluedimensional123 said:
i have been searching far and wide and am desperate to get my DNA back to stock, so i can activate it and use it again. i am trying every bit of sense and good advice and tutorials and my brain is just exhausted. i know i can get this, i just need a little help.
i have relocked it, and followed the instructions for running the RUU - 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 - exactly, and keep getting ERROR 155.
one thing i notice is during the RUU, it says going "from image" "to image" the from is blank. i click update ROM, it fills the "to" field with the RUU, 1.15, and, it runs for a minute ish and i get ERROR 155. Thanks guys I am really having a tough time.
i just tried again with new download of RUU. same results.
Click to expand...
Click to collapse
Why did you relock it?
Why didn't you just flash a stock rooted rom and be done with it?
probably because i didnt realize what i could or couldnt do along the way. i'm pretty noob and created a mess, a phone that boots up, into cyanogenmod, but will not activate. now i just need to get to square one.
Since you flashed cm, then your stock ROM was overwritten unless you made a backup. You'll probably have to reflash a stock from and setup everything again.
orangechoochoo said:
Since you flashed cm, then your stock ROM was overwritten unless you made a backup. You'll probably have to reflash a stock from and setup everything again.
Click to expand...
Click to collapse
i'm ok with that - exactly what i'm attempting.
this is what you were referring to, right? http://forum.xda-developers.com/showthread.php?t=2017525.
doing that i keep getting ERROR 155, searching what that could be. (now if i boot to CM recovery, files are missing, telling me the RUU install may have begun to overwrite files...but doesnr get too far.
by stock ROM you meant RUU as mentioned in thread above, right? as opposed to adb sideloading a zip ( "reflash a stock rom?")
im not sure where i went wrong, and at this point all i want is to get my dna to be able to be activated and have cell service working. (currently it boots up into CM, verizon tries to activate it, says it looks right on their end, i receive their test text, but, dialing anything, i get "mobile network unavailable.) so you can see, being not too apt in all this, there may be more than one way to get where i need. whether back to total stock, or able to activate in its current state - i'll take it.
i hope that all makes sense, i'm so appreciative for any of you guys' help.
The thread you referred to is to ruu (return to completely stock). If you can boot into CM, then do that and download Santods stock ROM in the development section. Then go into recovery and flash it.
orangechoochoo said:
The thread you referred to is to ruu (return to completely stock). If you can boot into CM, then do that and download Santods stock ROM in the development section. Then go into recovery and flash it.
Click to expand...
Click to collapse
Will try that for sure. I am still preferring to RUU and I keep getting the ERROR 155 - if can run that I can be at square one which is OK . I will try your suggestion though.
bluedimensional123 said:
Will try that for sure. I am still preferring to RUU and I keep getting the ERROR 155 - if can run that I can be at square one which is OK . I will try your suggestion though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2570548
That ruu zip should work if the exe is giving you trouble. Be warned: ruu will wipe the internal SD, so back everything up before flashing the ruu.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
http://forum.xda-developers.com/showthread.php?t=2570548
That ruu zip should work if the exe is giving you trouble. Be warned: ruu will wipe the internal SD, so back everything up before flashing the ruu.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
i tried and the results, of That ruu zip, and notice failing t the end..
fastboot oem rebootRUU
fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 35.228s]
writing 'zip' ...
(bootloader) rom parsing start
(bootloader) rom parsing finish
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
Finished. total time 41.495s
fastboot reboot
i'm grateful and still need direction. desperately. at this point happy to flash to stock. thanks guys. after that process it boots right back into cyanogenmod, nothing stock..
bluedimensional123 said:
i tried and the results, of That ruu zip, and notice failing t the end..
fastboot oem rebootRUU
fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 35.228s]
writing 'zip' ...
(bootloader) rom parsing start
(bootloader) rom parsing finish
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
Finished. total time 41.495s
fastboot reboot
i'm grateful and still need direction. desperately. at this point happy to flash to stock. thanks guys. after that process it boots right back into cyanogenmod, nothing stock..
Click to expand...
Click to collapse
That will happen and continue to happen, if the firmware on your device is newer then that of the RUU.
If you can downgrade your firmware, then you may stand a chance of flashing that old RUU.
But since you have relocked, I'm not sure you can.
I know you have to at least be s-off to downgrade, maybe unlocked bootloader isn't needed.
But I think that it may be. Good luck. :good:
If it were me, I would go back to unlocked and s-off.
Then flash latest firmware and rooted stock rom and be done with it.
thank you so much for the last few suggestions, i'm just wanting my phone back to stock i'm losing my mind.
could any point me to the way to downgrade my firmware to successfully run the old RUU?
Ive tried running the new RUU and i, as above, get ERROR 155. excuse my noobness, the help is great.
if i cant get this thing back to stock, so i can activate it - my goal - im gonna shell out the $100 and get insurance replacement. this is too complicated, but im not giving up.
thanks
ben
should running the newer RUU possibly finish installing? have tried but will again.
Related
ok so I am s-off, my hboot says 2.21.0000 and I am running the latest stock ICS leak.
I am doing my darndest to flash RA and get some root going.
When I flash anything via ADB, I am getting
C:\android\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\android\platform-tools>fastboot flash recovery ra315.img
sending 'recovery' (7078 KB)...
OKAY [ 1.445s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.765s
I have tried renaming the recovery just "recovery.img", it is in the same folder as ADB.
I have even tried flashing the modified hboot again and got the same error message.
What is with the remote not allowed? I do have usb debugging on (I tried on and off)
So fine I figure I am smarter than all that. I figured I would flash it via the PH file, not, acts like it will, but will not.
THen I figured that I would do it via flashing the rooted stock ROM that scott has out....nope again it acts like it will but just will not do anything.
Anyone have any ideas? I did everything before without issue (just got this phone as a replacement)...
Try this....download, rename PH98IMG.zip place on sd card and flash in downloader.
http://db.tt/UuiVjcrb
This is the version of amon ra 3.15 I was able to get to flash while having the same issue.
Sent from my ADR6425LVW using Tapatalk 2
Adb commands may not work due to bootloader being locked. Do not HTC unlock. If you do your bootloader will always say relocated or unlocked. Basically this is why some people flashed eng hboots or had the jouponut bear hboot.
Most people can get by with flashing stuff as ph98img and not worry about messing stuff up and stay on the stock bootloader.
You may want to check the dev section for more info on hboots if you need to use Adb commands and want a modified hboot.
If you unlock after s off, and decide to return to stock its a lengthy process. Scotty has a thread on how to do it. Basically you need to s on, redo s off and then go s on again. After the steps the bootloader will be like Verizon shipped the phone.
When s off first came out, we thought running a ruu would return the bootloader to locked if you unlocked....sadly it didn't. I myself had to redo the process, since I unlocked after s off. Such is life for early adopters.....
Sent from my ADR6425LVW using Tapatalk 2
Thanks a ton for the help. I did flash your AR file, and that seemed to do the trick. I do not know what the difference was between that one and the other 50 I downloaded.
I wasnt really satisfied there though. I ended up nuking the whole thing and going back to GB, flashing RA, then ICS, then the modified Hboot. The whole process went as flawlessly this time as the first time...
Thanks again
piizzadude said:
Thanks a ton for the help. I did flash your AR file, and that seemed to do the trick. I do not know what the difference was between that one and the other 50 I downloaded.
I wasnt really satisfied there though. I ended up nuking the whole thing and going back to GB, flashing RA, then ICS, then the modified Hboot. The whole process went as flawlessly this time as the first time...
Thanks again
Click to expand...
Click to collapse
Glad to hear you got it working.
Sent from my ADR6425LVW using Tapatalk 2
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 all,
I'm having a problem with putting a new ROM on my device. Goiung back to backup ROm has failed to as it seems the Backup wasn't complete
I thought it had something to do with S-Off, but someone from another thread said I should make a new topic as this would probably be another problem.
I wanted to go to the SuperSense DX5 ROM, but then i need to upgrade my hboot version and boot.img.
At this moment my hboot version is 1.24.0000. Also the the device is still in S-On.
When I try to load boot.img i get the following message
flash boot boot.img
sending 'boot' (4452 KB)...
OKAY [ 0.811s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 0.811s
Click to expand...
Click to collapse
Fot the hboot i get following message:
flash hboot bravo_alphaspl-sense.img
sending 'hboot' (512 KB)...
OKAY [ 0.234s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.234s
Click to expand...
Click to collapse
When i looked these errors up I Always ended up about S-Off or get stock recovery.img. Already got the stockrecovery.img on device but still nothing works.
Is there anyone that could help me solve this problem please? I'm completly not sure why now I'm not able to put ROM's on it anymore.
With Kind Regards,
Günther
1. You're trying to flash hboot meant for Desire not Desire X
2. Your hboot is 1.24, you cannot flash boot.img or ROM meant for hboot 1.25
3. You should flash only ICS boot.img, ICS recovery and ICS ROM
So find any ICS ROM in dev section and follow instructions there on how to flash the ROM.
Or go to general section and look for how to restore to ICS stock and update your device to JellyBean.
Then you can install all those JB ROM that you wanted to.
Remember this ? It's the same problem and the same way that you need to do to solve your problem.
doninckg said:
Got it fixed, after some Stock rom install and then tried another ROM Shadow, and it seems to be working once again.
Sorry for my question. I might have done something wrong about the hboot version I think.
Click to expand...
Click to collapse
Good thing you still have S-On or else you would have a paperweight right now
Ohhh OK,
I just followed the guide on the SuperSense DX5 where they refered to hboot 1.25.
But I still don't get why i'm not able to flash a boot.img. Tried the ICS ROM I Always used before "Sense Revolution+ R2
But I'm not able to get this working anymore
But I actually wanted to upgrade because I had some difficulties with this ROM about my Mobile Data. Had high hopes that it could be fixed with a JB ROM for Desire X. The only boot.img and hboot i tried to install was meant for the Desire-X. I'm also using Hassoon 3.0 for Desire-X to have the right recovery flashed for ICS of JB.
Still I must be doing something wrong I guess now, but don't know what then.
So S-On is alright for this device then? I don't need to change annything for this device to try and put it in s-off?
Sorry if I lack a bit of knowledge to root. Thought I did everything that was needed, like I used to do before.
doninckg said:
But I actually wanted to upgrade......
Click to expand...
Click to collapse
1. If you have a backup of your ROM, restore that then update to JB with OTA.
2. Or use the RUU RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe to restore your device then do OTA update.
Download : http://www.androidruu.com/?developer=Proto
3. Or for more advance user, follow this guide - http://forum.xda-developers.com/showthread.php?t=2212067 but not sure whether all links still active for the needed files.
Option 2 is the best for you.
How-to:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
thanks ckpv5, I will try to do this now.
ckpv5, this fixed everything!!! Thanks a million times for helping me out this fast.
Hey guys, havent been on the forums in awhile, my buddy has an HTC One Max that he wanted to root/rom, we've had some trouble, was up to the new ROM however it wasn't getting service from sprint, pretty much wanted to go back to stock and just not worry about any of this, i have read through some of the RUU threads and such but im having a good amount of trouble. Could i get some help? i am able to send commands to the phone but cant get into anything else, keeps going to fastboot when phone is restart. believe it is locked in fastboot. Let me know any info you need.
I think you have re-locked your phone as of now. If you have re-locked it you need to run the RUU or flash the ROM.zip via hboot. you can find the RUU in couple of threads now..
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
asnpdirtezw said:
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
Click to expand...
Click to collapse
As pradeepvizz said you need to make sure your bootloader is Locked/Re-Locked to run the RUU it would also be good measure to have a stock Recovery installed.
DeadPhoenix said:
As pradeepvizz said you need to make sure your bootloader is Locked/Re-Locked to run the RUU it would also be good measure to have a stock Recovery installed.
Click to expand...
Click to collapse
I was sure to re-lock the unit, dont think i had flashed over a stock recovery now that i think about it, ill try that and get back to you.
asnpdirtezw said:
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
Click to expand...
Click to collapse
Do you mean you tried to flash it via command prompt on the PC?
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
asnpdirtezw said:
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
Click to expand...
Click to collapse
Weird because because I ruu the other day. But I'm also unlocked and soff
Sent from my HTC6600LVW using XDA Premium 4 mobile app
asnpdirtezw said:
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
Click to expand...
Click to collapse
well since you are unlocked again, i would suggest to go ahead and install an Custom ROM. I know you had problems with Sprint when you did if the first time, but do try again with the following checks
1. Make sure you get the proper ROM for your phone - i assume your phone is from Sprint and so download the Sprint variant and not the international or anything else.
2. Use TWRP recovery for flashing the ROM. we have had users reporting similar issues when CWM was used.
HTC preloaded some image files for the "stickers" in the duo effects camera. They are preloaded to /data/preload so you can either flash the zip at the bottom of the second post or manually copy them over to that directory. They (HTC) haven't fully implemented this yet... so you probably won't even notice them missing. The also preload calc and flashlight app this way too.
NOTE- This will work for S-on users provided their current software level is at or below this version. S-off users can user this either way.
OPTION 1)
Rename download file to 0P3PIMG.zip. Make sure you use an SD card formatted to fat32!! (otherwise the phone might not see it) Place file on physical SD card (not internal phone memory)... i repeat physical SD card. Boot up phone to bootloader mode and the phone will auto-detect the file and prompt to install it. Follow any remaining prompts to allow the RUU to flash the software to your phone.
-or-
OPTION 2)
Download file into working fastboot directory. Boot phone to fastboot mode and connect to pc. Type in the following commands.
fastboot oem rebootRUU
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
first time you run this it will be short... so run it a second time
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
The command prompt output will show you details as it flashes each partition and will show you when it has completed. At this time the green bar on the phone will appear 99% of the way across the screen.. Completely normal!~ Issue the next command to kick it out of RUU mode or optionally flash the custom recovery TWRP if you intend to root/flash custom roms and THEN issue the below command to get out of RUU mode.
fastboot reboot
(note) if you just want to reboot back to bootloader you can issue the command fastboot reboot-bootloader This will allow you to boot directly to recovery and start flashing/rooting fun.
I don't own this model phone... so if someone would like to capture the output of the command prompt I would be happy to add it to the OP similar to how I have my VZW ruu threads.
Downloads Do NOT mirror these elsewhere.
RUU Download link
https://www.androidfilehost.com/?fid=23622183712460121
Data preload apps/stickers
https://www.androidfilehost.com/?fid=23622183712460132
RUU Mode TWRP 2.7.1 (must be s-off or unlocked)
https://www.androidfilehost.com/?fid=23622183712460136
Getting error, too many links
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
martinoj2009 said:
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did your md5 check out fine?
dottat said:
Did your md5 check out fine?
Click to expand...
Click to collapse
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
martinoj2009 said:
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
Click to expand...
Click to collapse
Do you have an sd card to try it via option 1?
dottat said:
Do you have an sd card to try it via option 1?
Click to expand...
Click to collapse
I'm sure I do, I'll let you know, and thanks for the prompt reply!
martinoj2009 said:
I'm sure I do, I'll let you know, and thanks for the prompt reply!
Click to expand...
Click to collapse
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
dottat said:
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
Click to expand...
Click to collapse
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
martinoj2009 said:
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
Click to expand...
Click to collapse
How long did it take to run the zip?
dottat said:
How long did it take to run the zip?
Click to expand...
Click to collapse
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
martinoj2009 said:
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
Click to expand...
Click to collapse
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
dottat said:
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
Click to expand...
Click to collapse
Lol, shhhh, forgot to S-Off
martinoj2009 said:
Lol, shhhh, forgot to S-Off
Click to expand...
Click to collapse
OK... so if you aren't S-off AND this firmware is older than what you have it will fail. Only S-off can downgrade. You guys don't have a newer RUU yet and there were two OTAs after this one. Definitely S-off that thing while you still can (assuming it's not too late).
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
mido.fayad said:
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
Click to expand...
Click to collapse
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
dottat said:
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
Click to expand...
Click to collapse
Yes I know that I should be s-off
And that's why I said I should downgrade first to sense 5.5 firmware then flash the ruu
And I won't be able to downgrade without s-off
So I was writing only about the error when I already have a-off because it took me 2 days till I found this fix after many trials
posted a current RUU for s-off users here...
http://forum.xda-developers.com/htc...rint-ruu-3-02-651-5-s-off-pre-rooted-t2865704
i have some troubles here
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
w1n73rf3ll said:
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
Click to expand...
Click to collapse
IF sunshine doesn't work on your current rom (have you tried running it yet).... you need to unlock your bootloader and flash a 100% stock older rom. Then use that to s-off. Then flash whatever rom you want and sim unlock.