Database Info

[GUIDE] **SPRINT CDMA HERO**Unroot without RUU / From SD Card

If for some reason you cannot get ADB access to your device, can't run windows, or there is physical damage to your USB ports, this is a guide showing how to un-root from only using the SD card.
Method ONE
***Overwrites ALL data on phone***
This method grabs
Code:
android-info.txt
boot.img
hboot.1.41.0000.img
nv.img
radio.img
recovery.img
splash1_HTC_320x480.nb0
system.img
userdata.img
From Flipzmode's 1.56 RUU
This works in almost all situations, unless you ran the 2.1 test RUU, which updates your HBoot to 1.47. Stock HBoot is 1.41.
Download the following file: Desktop Link Mobile Link
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
place in /root of SD card
Reboot phone into HBoot mode, by holding Volume Down
Press action (the trackball) when prompted
Reboot phone
and you're done!​
Many many thanks to johnsongrantr for his method.
Method TWO
only if Method ONE fails. much longer/more complicated process
Files needed:
Flashrec 1.13.apk (133 KB)
Desktop Download Link
Mobile Download Link
No Root Nandroid Backup (93.14 MB)< (SW Version 1.56, IE 1st OTA update)
Desktop Download Link
Mobile Download Link
^Stock Recovery Image^ (5 MB)
Desktop Download Link
Mobile Download Link
Original radio update 1.04 (THANKS FLIPZ!!!) Link
***NOTE*** Radio updating is one of the only risky behaviors that you can engage in with your phone Possible Bricking alert. ONLY flash this if you have previously updated your radio with an update.zip. Just flashing ROMs doesn't change your radio.
Extract NoRootNandroid.zip, revealing a folder called NoRootNand
Move NoRootNand to
Code:
/sdcard/nandroid/HTxxxxxxxxxx/NoRootNand
Move recovery-backup.img, Radio update.zip, and flashrec-1.1.3-20091107.apk to the root folder of your SD card
Boot into Recovery mode (hold Home + End when booting). Restore Nandroid backup called NoRootNand
Update the radio by flashing the Radio update .zip file
Install FlashRec
Run FlashRec (its name has changed to 'Recovery Flasher' when you installed it)
Click on 'Restore Backup Image'
If there are errors in FlashRec, reboot your phone, try again
and you're done!​
**I take no responsibility for bricking of any sort, but it worked for me**
Method TWO was adapted from dfbonney's post, found here

rt1oo said:
If for some reason you cannot get ADB access to your device, can't run windows, or there is physical damage to your USB ports, this is a guide showing how to un-root from only using the SD card.
Files needed:
Flashrec 1.13.apk (133 KB)
Desktop Browser Link
Mobile Browser Link
No Root Nandroid Backup (93.14 MB)
Desktop Browser Link
Mobile Browser Link
^Stock Recovery Image^ (5 MB)
Desktop Browser Link
Mobile Browser Link
Okay. now that you have all the files you need, follow the steps below
Extract NoRootNandroid.zip, revealing a folder called NoRootNand
Move NoRootNand to
Code:
/sdcard/nandroid/HTxxxxxxxxxx/NoRootNand
Move recovery-backup.img and flashrec-1.1.3-20091107.apk to the root folder of your SD card
Boot into Recovery mode (hold Home + End when booting). Restore Nandroid backup called NoRootNand
Install FlashRec
Run FlashRec (its name has changed to 'Recovery Flasher' when you installed it)
Click on 'Restore Backup Image'
If there are errors in FlashRec, reboot your phone, try again
You're unrooted!
**I take no responsibility for bricking of any sort, but it worked for me**
Click to expand...
Click to collapse
im sorry is this for the sprint hero? isee its posted in the cdma hero forum, but that picture doesnt look like cdma hero
but i guess some heros are also not google branded and look different?
idk, some clarificatio would be awesome

sinistermeshes said:
im sorry is this for the sprint hero? isee its posted in the cdma hero forum, but that picture doesnt look like cdma hero
but i guess some heros are also not google branded and look different?
idk, some clarificatio would be awesome
Click to expand...
Click to collapse
That is the droid eris by Verizon.
It's the verizon version of the sprint hero. It's pretty much the exact same except for the phone body.

sorry to bump, but its getting buried, and id really like to know
thanks

sinistermeshes said:
sorry to bump, but its getting buried, and id really like to know
thanks
Click to expand...
Click to collapse
I answered your question already

chococrazy said:
That is the droid eris by Verizon.
It's the verizon version of the sprint hero. It's pretty much the exact same except for the phone body.
Click to expand...
Click to collapse
That doesn't look like any Eris I have ever seen:

oh! you mustve been posting as i was! i apologize!
so, in theory, this wouldnt work?
just looking for a riskfree way to unroot

danknee said:
That doesn't look like any Eris I have ever seen:
Click to expand...
Click to collapse
just wanted to report an [email protected] response (ive played with a friends eris, and agreed, the phone depicted in the OP is most certainly not the eris)
and ask if you knew of any ways to unroot to stock 100% safely? even the 100% garuntee RUU thread seems iffy. this seems like, in theory, would work (untouched nandroid combined with stock recovery) and i dont see how it could mess up
but then again, my senior membership is only due to having to fight back the flamers, and am truely still a noob, so what do i know?
thanks in advance!

Yes this is for CDMA hero, because it's in the CDMA Hero200 wiki and the CDMA hero part of the forum. The screenshot is to illustrate the stock recovery image.
Thanks, though, I'll edit to provide clarification

rt1oo said:
Yes this is for CDMA hero, because it's in the CDMA Hero200 wiki and the CDMA hero part of the forum. The screenshot is to illustrate the stock recovery image.
Thanks, though, I'll edit to provide clarification
Click to expand...
Click to collapse
thanks so much!
your help is very appreciated!

sinistermeshes said:
just wanted to report an [email protected] response (ive played with a friends eris, and agreed, the phone depicted in the OP is most certainly not the eris)
and ask if you knew of any ways to unroot to stock 100% safely? even the 100% garuntee RUU thread seems iffy. this seems like, in theory, would work (untouched nandroid combined with stock recovery) and i dont see how it could mess up
but then again, my senior membership is only due to having to fight back the flamers, and am truely still a noob, so what do i know?
thanks in advance!
Click to expand...
Click to collapse
I can tell you that I have used the RUU several times. I am very anal about my phone so every time the paint chips off of the power button I take it in and get it replaced. This has happened several times along with my speaker blowing and the charging port not working. Every time I take it in i RUU just to make sure the warranty dont get cancelled. I have never had a problem using the RUU to unroot.

animal7296 said:
I can tell you that I have used the RUU several times. I am very anal about my phone so every time the paint chips off of the power button I take it in and get it replaced. This has happened several times along with my speaker blowing and the charging port not working. Every time I take it in i RUU just to make sure the warranty dont get cancelled. I have never had a problem using the RUU to unroot.
Click to expand...
Click to collapse
Then you're one of the lucky majority. I've used the RUU on my phone 6 times and every time it's gotten the 110 error. This is on 2 different phones and several OS's and computers. I've used dfbonney's method to restore it to stock 5 times (yes I replaced one phone) and it worked fine.

The phone pictured is the Android Developer Phone 2 (Google Ion) btw: http://phandroid.com/2009/06/05/google-ion-coming-soon-as-adp2/

smw6180 said:
Then you're one of the lucky majority. I've used the RUU on my phone 6 times and every time it's gotten the 110 error. This is on 2 different phones and several OS's and computers. I've used dfbonney's method to restore it to stock 5 times (yes I replaced one phone) and it worked fine.
Click to expand...
Click to collapse
I am not trying to discredit you at all. I am just stating my experiences. If your way works good then great for the people that use it. I say the more the merrier.
Thank you for the guide and for helping out the community smw.

animal7296 said:
I am not trying to discredit you at all. I am just stating my experiences. If your way works good then great for the people that use it. I say the more the merrier.
Thank you for the guide and for helping out the community smw.
Click to expand...
Click to collapse
Whoops. You took that the wrong way. And it's not my guide it's dfbonney's, I just tested a few things with him. I simply meant that there's no potential harm (that I found after multiple test and TRYING to break the phone) that can come from that method. I was also pointing out that most people DON'T seem to have problems with the RUU to stock method..but for those that do there's a way out that's harmless.
That's all I meant

smw6180 said:
Whoops. You took that the wrong way. And it's not my guide it's dfbonney's, I just tested a few things with him. I simply meant that there's no potential harm (that I found after multiple test and TRYING to break the phone) that can come from that method. I was also pointing out that most people DON'T seem to have problems with the RUU to stock method..but for those that do there's a way out that's harmless.
That's all I meant
Click to expand...
Click to collapse
No problem. I have a rare ability to not get mad over the internet. Its all good.

animal7296 said:
No problem. I have a rare ability to not get mad over the internet. Its all good.
Click to expand...
Click to collapse
Good to hear. 'cause text doesn't work well sometimes.
Ok, shutting up now. Sorry for the off-topic posts.

I've been able to RUU successfully once, then my USB port broke (only charge, no USB data) (weird...) so then I scoured the forums and found a bunch of different places with a bunch of different steps so i cleaned it up, bundled the files all together and made things pretty, and listed it in the wiki for all to use

This method worked great for me. Thanks to dfbonney and rt100 for gathering the info in the first post.

This is a riskless way of going back to stock right? I'm not going to brick my phone? lol

HTC Magic , bricked, known solution?

Hello everyone. I need some assistance since i've tried everything and nothing is beeing possible. I've got a friend with a phone , he run the oficial HTC Magic Vodafone update, and happened that the system blocked at the update of system.img.
It had before acccording to the owner HTC RUU 1.88.531 Vodafone Edition (Do you know where i can find this RUU? )
Appeared this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to root with orange root method, but doesnt let pass the system.img
i tried to reflash, doesnt pass the system.img
Tried to downgrade rom, doesnt get past the system.img.
Tried in fastboot (not possible perfect SPL)
Tried a ROM of another country same brand. Not possible either.
Doesnt let me flash from Hboot on SD card either. (Havent tried goldcard method yet)
Any suggestions? Thank you!

Far as 'brick' its not a true brick until you can no longer get into fastboot and also can't get into recovery. But far as RUU, not sure never had to deal with that, was it originally a vodaphone?
Exact details on what the device originally was may help, as opposed to trying everything in sight and risking actually creating a real brick.

I might be wrong, but that looks like an HTC Magic prototype.

jgcaap said:
Tried in fastboot (not possible perfect SPL)
Click to expand...
Click to collapse
According info at screen can you post image when you use fastboot commands
Try download Amon_RA recovery last version for 32A magics
go to fastboot-mode (Turn off, then turn on by pressing Back + Power)
run:
Code:
fastboot flash recovery recovery.img
where recovery.img - last version of Amon RA recovery H (H = 32A)

http://forum.xda-developers.com/showthread.php?t=659403
A bunch of RUU's.

Doenst let me flash hboot but i'll try flash recovery again. I'll ask my friend to try this, but i remembered to he try go into the android recovery mode, when he presses home+power, it appears this screen. But we'll try again =p
Accoridng to my friend , he bought this phone to another person. I can provide anything you might need to help analyse, such as SN etc.
He said this was a Vodafone Magic from Portugal, a 32A. (I personaly ever saw a DVT 32A , only 32B, and in my opinion he flashed wrong ROM beside of letting beeing flashed when goes to flash the system.img it gives an error saying isnt possible to writte).
I tried to download from the RUU list 3 Roms, none of them worked, all gave id error. I tried from HTC portugal, there are 2 situations:
1) flashing a 3.405xx , he flashes Hboot, radio, but at system, he gives error
2) Flashing a 2.3xx rom , he flashes System.img and stays there at 0 %
3)Flashing a 1.88.xx ROM he stays at 0 %
I was considering a brick .. but i'll wait your opinion thank you for this wonderfull assistance

I have exactly the same problem and I2m also stuck in the RUU screen. Moreover I also tried the goldcard method and it doesn't work either. I guess there is no solution yet for this problem. I even suggested 50 USD donation but still no solution.
http://forum.xda-developers.com/showthread.php?t=682444. This is my thread if there is a solution you may see there.

This usually happens when a 32B is flashed with the 1.76 SPL. Has been posted numerous times.
JTAG fixes this
Wrong forum by the way

one question, i know is possible to convert 32 A to 32B but not 32 B to 32A. But in wich conditions does this change the name in the bootload? Thank you

I had a similar heart stopping situation. I used a euro RUU (I'm on a Canadian Magic) with a gold card to fix it. From there I could root and flash back to what I wanted. Choose your RUU carefully and you can get it back.

thank you for your help i'll try this method tomorow Great support as always!

jgcaap said:
D
1) flashing a 3.405xx , he flashes Hboot, radio, but at system, he gives error
Click to expand...
Click to collapse
What exactly error did you have?
Note: If you are using RUU, it is creating log on computer (i forgot folder-name, something with ruu)

the phone is not mine i have to check once i'm with him. If creates a log, do you know wich folder is in?

jgcaap said:
the phone is not mine i have to check once i'm with him. If creates a log, do you know wich folder is in?
Click to expand...
Click to collapse
C:\ruu_log

I would love to know how to fix this too. Im in the exact same boat and everything. I know this is an old thread but seems this is the only person who has the same problem as me. Has there been a fix yet? Lets keep this alive and figure out how to fix this.

This morning I experienced the same thing, looking like a picture that you upload.
My solution is to install again via the PC with the correct RUU for your devices and my magic WORKED again..
you must be know your the correct RUU for your device

N204life said:
I would love to know how to fix this too. Im in the exact same boat and everything. I know this is an old thread but seems this is the only person who has the same problem as me. Has there been a fix yet? Lets keep this alive and figure out how to fix this.
Click to expand...
Click to collapse
What kind of phone do you have? Is it a 32A, 32B or does it have a 3,5mm audio jack on top? Please post your fastboot info here!
Go to http://shipped-roms.com/shipped/Sapphire/ and find the right RUU for your phone. Check if the RUU is for your phone! There's a thread on this forum explaining which ROM is for which phone - http://forum.xda-developers.com/showthread.php?t=659403
It might also be a good idea NOT to use a goldcard, so that you don't install the wrong one.

I have a mt3g with the 3.5mm jack and ive pretty much tried every RUU under the sun and nothing seems to make any head way. It keeps saying model ID error, and nothing ever starts loading. It will load the RUU onto the phone but dosent unpack anything
And everytime i try to do a fastboot boot of the RUU.zip it just stays there and says booting and nothing happens. It will show the green bar on the side of the phone when it loads and then nothing.
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
OCT 21 2009, 22:33:27

Oh, there's your problem: you're using the new radio (6.35) on a device that only works with the 32B one No wonder it won't boot!
Borrow a friend's phone, make a goldcard and follow the tutorial at http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Without a goldcard I'm afraid you're pretty much stuck, sorry!
Bonus points: make a goldcard and use a RUU that's actually made for your phone to fix it Find the right RUU at http://forum.xda-developers.com/showthread.php?t=659403 under "T-Mobile myTouch 3G 1.2". This will take you back to the stock ROM, unrooting your phone.

So is the phone i need to make a gold card on just need to be running the android system or does it need to be an HTC or the exact same phone. I got a buddy with a moto backflip on at&t , wonder if i can do it on his

Can't find a solution - S-On,***Locked*** - want to install Rom's

Sorry, I have tried searching for the last two nights but can't find a solution to this. I'm sure this has been covered before but I'm stumped if I can find the right link.
My Desire S is currently like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone was 6 months old before I got it so I'm not sure it's not been rooted before. Phone is unlocked to any network (AFAIK) and unbranded. Software is 2.10.401.8
Where I'm trying to get to is that I simply want to be able to install customs roms (MIUI) from a recovery. I've got a Desire HD which I rooted, ClockworkMod'ded (can't remember how though) and installed MIUI on a year back but this Desire S seems more complicated. I'm no XDA Jedi, I'm looking for layman's guide, a simple list of do what's and do not's......any help much appreciated.

Downgrade your HBOOT using the methods from the INDEX. I don't recommend using the HTCDEV method.

uqadwe said:
Downgrade your HBOOT using the methods from the INDEX. I don't recommend using the HTCDEV method.
Click to expand...
Click to collapse
What INDEX are you referring to? If you mean the "Complete tutorial for the beginners......." I have tried using this method but it refers to phones with HBOOT 0.98.0000, 0.98.0002 but mine is 2.00.0002 and this method doesn't work for this HBOOT. This has been my issue as there seems like a lot of contradictory info this and I don't want to brick the phone.

http://forum.xda-developers.com/showthread.php?t=1146601
You have three methodes to downgrade your version of hboot to a rootable one.
Read some threads from there and it's more likeli you will avoid a brick

Edit: I guess you were referring to this index http://forum.xda-developers.com/showthread.php?t=1146601......are the guides up to the minute or do I need to dig into the posts?

UNLOCK your Bootloader by HTCDev (S-ON - Security On) (HBOOT>2.0)
[GUIDE][01 MAR 12] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 using HTCDEV unlock method
[GUIDE] Stuck at HTC logo/boot loop? Just flashed custom ROM after using HTCDEV unlock?
[GUIDE][13 JAN 12] How to Downgrade Latest Hboot 2.00.0002>> without using HTC Dev V2
[GUIDE][05 JAN 12] downgrade HBOOT 2.00.0002 to 0.98.00000 without using HTCDEV unlock
[GUIDE][18 NOV 11] Official HBOOT 2.00.0002 Downgrade to OLD HBOOT
Click to expand...
Click to collapse
is this clearing the picture for you???
The first post has sufficient info for you to do the job, but i will recommend to read as much as you can to be fully prepaired for the downgrading process and to know what
problems can appear and how can you evoid them.

uqadwe said:
is this clearing the picture for you???
The first post has sufficient info for you to do the job, but i will recommend to read as much as you can to be fully prepaired for the downgrading process and to know what
problems can appear and how can you evoid them.
Click to expand...
Click to collapse
avoid using HTC DEV and just downgrade the HBOOT like the post before said.
Once the HBOOT has been downgraded you can unlock via revolutionary.
If you really want a complete noob guide check out "all things root" on the androidforums.com under Desire S
It gives some good backup info to the fantastic one here on the XDA but its probably easier to understand for a layman Do your research and you will be fine

Which corner do I turn down now??
jacmeister said:
avoid using HTC DEV and just downgrade the HBOOT like the post before said.
Click to expand...
Click to collapse
Dohhhh, too late (hand slaps forehead). I tried and tried to get the downgrade method in the link to work but it simply wouldn't for me and I went over it with a fine toothed comb numerous times. So, as I was drowning in all the useful links and posts I'd found on here I ended up (naively) believing that it would be much more straightforward to use the HTCDEV.com unlock method. So, I successfully unlocked the phone using that method then read that flashing ROM's is a real PITA and all I want to have is something simple like CWM installed from where I can flash any ROM I want to without hassle. So, I decided to relock the phone using the same HTCDEV.com and now have the following:
*** RELOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04-M
eMMC-boot
Aug 22 2011, 15:22:13
.....and now I have absolutely no idea where to go now. I'm completely lost. I've spent the last few hours endlessly searching to find a situation that matches mine and that gives a logical solution but without any joy...........Like I said I just want some type of recovery installed from where I can backup/restore and flash MIUI/CW9 etc. Anyone able to through me a life ring?
This is SO annoying because I'm far from a technology noob but damn this s**t is getting less straightforward than it ever was. Imagine how many more people would come over to Android if it were way more simple. Guess it's the phone manufacturers making things more difficult. Anyway, keep up the good work all you technical Jedi's, you're efforts are very much appreciated........anyway, just a thought.

Did you read the post on androidforums.com ??
Sent from my HTC Desire S using xda premium

jacmeister said:
Did you read the post on androidforums.
Click to expand...
Click to collapse
Tbh, I didn't, wish I had. I had so many XDA root/unroot/unlock/lock/relock/hboot links open I just ended up in a vortex of confusing (and often contradictory) info so I just grabbed what I thought was the first secure lifeline I found but which was the wrong one I guess. Should have just put down the phone, picked my beer back up and watched the match highlights. You live and learn.
I've been over to the all things root link and I can't find a solution which solves my current predicament.
To clarify the phone is currently *** RELOCKED ***, S-ON and HBOOT-2.00.0002. How do I get from here to having CWM installed and ready to load ROM's?

Follow the instructions in this guide and everything should be cool.
http://forum.xda-developers.com/showthread.php?t=1399331
Then once you downgraded your HBoot you can unlock via revolutionary

jacmeister said:
Follow the instructions in this guide and everything should be cool.
http://forum.xda-developers.com/showthread.php?t=1399331
Click to expand...
Click to collapse
This is the method I tried but it just didn't work for me. The main issue was running trying to run ./zergRush as it wouldn't run. There was a post in there (page 9) that stated that the if it didn't work you needed to "push the source file not the b binary" and that to solve this you need to "download just the source, look for the binary/executable in the thread" so I followed the link and looked everywhere but I could only find a zip file and a .c file, no executable or batch files. Any idea where this file is located?
Also this method specifically states that it's a downgrade without using HTCDEV but I have now done this so wasn't sure if trying again in a *** Relocked *** or *** Unlocked *** (back through HTCDEV) state would brick the phone. Again, it's not a magic bullet solution, there are still a few if's and but's and I can't afford to trash my phone.

You are the only problem. The method is working well(done it at least three times miself).
You didn't took any advice into consideration so this is my last reply and hope no one answers anymore as you really don't want to read and think for yourself.
The relocked messege is permanent(using 2*****bootloader will only be unlocked or relocked)
As the previous user told you allready you have to first downgrade and second s-off using revolutionay.
Good luck!(considering your "skills" you will need it)

uqadwe said:
Good luck!(considering your "skills" you will need it)
Click to expand...
Click to collapse
Nice attitude. With respect, you have no idea about my 'skills' or anyone else's for that matter although you assume plenty. I'd love to meet up to discuss this further sometime, send me a PM why don't yah...........remember, talk is cheap, and so is your general attitude towards anyone else who doesn't have the word on everything Android. Checked some of your previous posts. Might be a surprise for you to learn that not everyone has the time to dedicate to the subject, a lot of us just dabble, but if I had the same attitude towards my clients (who know generally know very little about Architecture) as you do towards all non-techno's on here then I'd have no practice and no business or clients. Take a leaf.
Whatever, for anyone else who might be able to help and as mentioned above the link to download zergRush leads only to a zergRush.c or zergRush.zip. There are no batch files or executables there. When I tried $ ./zergRush.c I got:
./zergRush.c: 6: Syntax error: "(" unexpected

I for one i am a sales man. I do have the skills to talk a win over a client.
You don't fit that category and i allready tooked the time to explain but you didn't bother to read my post(so you are in this situation).
I replied to your questions with some little clarifications in three ocasions. Jacmeister offered his help, you ignored that to.
What more do you want.
Here's an idea, send me your phone and i will do the job. Is that good enough? Or would you like me to come at your place to resolve it? Please be serious and stop the very small talk.
And the help you need is only in your hands.

uqadwe said:
I for one i am a sales man. I do have the skills to talk a win over a client.
You don't fit that category and i allready tooked the time to explain but you didn't bother to read my post(so you are in this situation).
I replied to your questions with some little clarifications in three ocasions. Jacmeister offered his help, you ignored that to.
What more do you want.
Here's an idea, send me your phone and i will do the job. Is that good enough? Or would you like me to come at your place to resolve it? Please be serious and stop the very small talk.
Click to expand...
Click to collapse
Didn't you say that would be your last post? It'd be great if you heeded your own advice.
So you're a salesman? Yeah, that fits.
For the record I didn't ignore anyone's posts. I tried what appeared to be the most suitable solution suggested and it didn't work so I tried something else which partially worked but didn't solve the issue so I asked for advise from those in the know but still didn't get a solution which worked for me. I've read plenty on a subject I didn't want to get up close and personal with and still haven't found a solution. Reading through many of the threads there are plenty in a similar boat. Answering my questions isn't just helping solve my issue but is helping others. But then isn't that the idea of a forum, i.e. a place to share ideas, impart knowledge and offer advice.
It would be helpful if you kept out of this now as you're extensive knowledge is just getting in the way your ability to converse on a reasonable level. Small Talk yah say, I should coco.

what do you do with a person that doesn't follow repeated advice?
I really don't understand why do you still try to make us understand that your case is special, yes you sure are one of a kind, but not in the good way.
Those guides worked for a lot of users, you are one of the small number that didn't succeed, and gues whous fault is it?

HI there, this might help, i am a noob, so those who knows better, please correct me if i'm wrong..
I tried to S-OFF my HTCDev unlocked DS, i wiped cleaned the ROM and followed instructions and all, cut long story short, i locked my bootloader with no ROM installed and I couldn't even go to recovery, only on bootloader page..
so i visit the HTCDev site again, and unlock it again, and then i could go to my recovery.. from there, it was a matter of copying the custom ROM and flashing it and i was able to use it again (i was so scared at that time that i may not be able to use the DS again)
after that, i went back to S-On unlocked
So i followed one of the thread mentioned in the INDEX thread, specifically the one dated 18 NOV 11
Follow that closely step by step, i repeat, step by step..
and again, if you already relocked your device and can't get to CWM, just go to HTCDev, and unlock it again, start from the beginning.. and after you have done so, then follow the guide mentioned above..
I know it works because i was in the same exact shoes as you before, Re-Locked, and can't get back to recovery.. just unlock it again and you are good..
(however, as usual, i take no responsibility if anything goes wrong, this is what i did and i just want to share and help you, so proceed with utmost caution )

This is what has worked for me but it involves unlocking of bootloader via htcdev.
As always good to mention do everything at your own risk and do some reading before you start tinkering with your phone.
- Go to htc dev and unlock your bootloader
- Boot your phone in to bootloader.
- Flash recovery (4EXT recommended)
- Flash any rom which is rooted ( I flashed Europe Stock pre rooted)
- Bacause you are HTC Dev unlocked for bootloader you have to flash boot.img file which comes with every rom from fastboot "fastboot flash boot boot.img"
- This time you will have to flash boot.img from fastboot
- Follow steps here to downgrade http://forum.xda-developers.com/show....php?t=1604255
- Run revolutionary and gain s-off your bootloader will be 6.98,,,
- Upgrade HBOOT using http://forum.xda-developers.com/show....php?t=1679338
- Now you have latest hboot and s-off and you can flash any rom

[q] help with htc sensation root and installing custom rom etc.

Hi guys!
So i'm new to the whole idea oof rooting my phone, but as i saw the possebilities that comes with a rooted phone i simply couldn't say no!
so i spent most of the day reading up on what i have to do for the whole root thing to work and this is what i found:
well let us start off with what i want to achieve with my phonee, I WANT to change the ROM and kernel cuz of well we all know the the stock rom can get a bit boring after a while and cuz of the decreased battery time that i have been getting out of my device. i also noticed some slowing down of the proccesor(apps lag and crash and takes longer to launch) so that is why i want to root my phone, make it smoother and nicer, simple as that.
what i know about my phone:
HBOOT version: 1.27.000
firmware 3.33
andriod version 4.0.3 (dont know if its relevant or not rly )
no carrier, bought right out of the store with no restrictions to any one operator/carrier
so back to the rooting!
i found the guide for how to turn s-off with the Juopunutbear and the wire trick(haven't tried anything yet tho). what i dont rly get is why i am doing this, is it so that i later on can gain root rights or is it so that i can acces a certain function i my phone that is needed when flashing roms and kernels?
i havent rly understood how the acctually rooting takes place, and that i guess, is my main question here, how do i go about and what is important to think about when doing it?
i think i got the flashing on lock down with the installing of the zip file in sd-card directory and the starting the phone using volume rocker and power button and wiping the old rom before installing the zip from sd card. (FEEL FREE TO CORRECT ME IF IM WAY OUT OF LINE). But before that i read that it's important to do a NAND/ i guess it's a backup, how is this done?
i know that it's nobbish for me to ask this since there is a few guides out there already but they are all written for people with some pre-knowledge about rooting, atleast that is what i think xD so if someone could take time and help me with this i would be happy to write a guide for the person who has basicly zero knowledge about phones what so ever.
and the flaming and blaming I guess comes along with the terretory so feel free to take a swing at it m8's.
would as i said earlier appriciate it alot and i'm willing to give back the stuff that u guys teach me
if someone would help me in person that is fine too, we can go about it on skype, teamspeak, or send me a e-mail, or pm and we can talk further
sorry for the long post, and remember im new , not retarded xD
CheerZ!!!

hi mate
you have 2 options to root your device
first option is:
use this guide
http://forum.xda-developers.com/showthread.php?t=1631861
just after unlocking bootloader(step 1) it will tell you that requires factory reset
after finishing from here then go here and flash this zip from recovery
http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip
it will give you root
second option:
use juopunutbear method to S-OFF the device and then root
see here
http://forum.xda-developers.com/showthread.php?t=1661631
before starting this guide backup everything from your sdcard to pc because during the wire trick it will erase it
in first option you will remain on S-ON

Q
rzr86 said:
hi mate
you have 2 options to root your device
first option is:
use this guide
http://forum.xda-developers.com/showthread.php?t=1631861
just after unlocking bootloader(step 1) it will tell you that requires factory reset
after finishing from here then go here and flash this zip from recovery
http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip
it will give you root
second option:
use juopunutbear method to S-OFF the device and then root
see here
http://forum.xda-developers.com/showthread.php?t=1661631
before starting this guide backup everything from your sdcard to pc because during the wire trick it will erase it
in first option you will remain on S-ON
Click to expand...
Click to collapse
Hi mate!
first of all thank you for your response, clears alot up for me acctuallly
still some questionmarks that needs a bit of straightening
1. with option 1 will i be able to flash this rom? http://forum.xda-developers.com/showthread.php?t=2115520 and do i need anything special to run it? like for example a different kernel or something? or i read something about CID or something that needs to be changed? also does this ROM come with a custom kernel, if s o that would be great, saves me the time to go find a good one and flashing that one too( as u might have understood im not keen on messing around too much with new stuff )
2. what benefits are there with using s-off and if im not giong to switch around much after im done with flashing is it neccecary to do the s-off
(im kinda unsure about the whole wire trick and if im going to be able to do it and so forth)
3.will i be able to unroot the phone after i rooted it and will i be able to revert to the old stock ROM if i want to (just want to know in casae something happends) like a backup that can be flashed easily
4. will i be able to use stuff as ROM-manager and Titanium backup without having the s-off function
Once again i appriciate the time you took to answer me and it helps me alot
i think im soon ready to unlock this son of a b**** phone lol

i found this as i was browsing some and it seems pretty easy to follow but not sure if it's working and the post date is from september 2012
is it legit or is it outdated and wrong?
link to guide:
ht.tp://theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000/
(remove the dot between the HTTP)

lolman96 said:
i found this as i was browsing some and it seems pretty easy to follow but not sure if it's working and the post date is from september 2012
is it legit or is it outdated and wrong?
link to guide:
ht.tp://theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000/
(remove the dot between the HTTP)
Click to expand...
Click to collapse
As far as your hboot is 1.27, you can root the Senny in the same way.
Spit out from an HTC Sensation XE, a revived device while was dying due to lack of support, with TeamVenom, and other astonishingly amazing developers' benignity...

ashkan-khatar said:
As far as your hboot is 1.27, you can root the Senny in the same way.
Spit out from an HTC Sensation XE, a revived device while was dying due to lack of support, with TeamVenom, and other astonishingly amazing developers' benignity...
Click to expand...
Click to collapse
hi and thanks for your answer
so just to clear things up, the link that i posted will work as far as rooting the device goes?

lolman96 said:
Hi mate!
first of all thank you for your response, clears alot up for me acctuallly
still some questionmarks that needs a bit of straightening
1. with option 1 will i be able to flash this rom? http://forum.xda-developers.com/showthread.php?t=2115520 and do i need anything special to run it? like for example a different kernel or something? or i read something about CID or something that needs to be changed? also does this ROM come with a custom kernel, if s o that would be great, saves me the time to go find a good one and flashing that one too( as u might have understood im not keen on messing around too much with new stuff )
2. what benefits are there with using s-off and if im not giong to switch around much after im done with flashing is it neccecary to do the s-off
(im kinda unsure about the whole wire trick and if im going to be able to do it and so forth)
3.will i be able to unroot the phone after i rooted it and will i be able to revert to the old stock ROM if i want to (just want to know in casae something happends) like a backup that can be flashed easily
4. will i be able to use stuff as ROM-manager and Titanium backup without having the s-off function
Once again i appriciate the time you took to answer me and it helps me alot
i think im soon ready to unlock this son of a b**** phone lol
Click to expand...
Click to collapse
1.yes you can flash this rom and probably comes with custom kernel too
it can be flashed from recovery
2.with S-OFF you are fully unlocked
you can flash also different firmwares,radios,rils(with S-ON you can't)
with S-ON you are limited on flashing roms and kernels only
3.to return into completely stock condition see here
http://forum.xda-developers.com/showthread.php?t=1672425
also before flashing a new rom make a nandroid backup from recovery just in case(it will backup your current rom)
4.yes you can i think
as for the guide you mentioned is the same as the first option but instead of clockworkmod recovery use 4ext recovery
4ext has smartflash feature(it is only for S-ON)
while flashing a new custom rom or kernel in S-ON devices it hasn't have the ability to write the boot partition by itself
smartflash does this job
in S-OFF devices doesn't require that

thanks again for your help. so this is what i can understand from your tips and guides that i have read:
1. i go to HTC dev and follow the steps to unllock my bootloader.
2. when im done there i go and download theese files :
http://download.chainfire.eu/324/Sup...erSU-v1.30.zip and https://www.dropbox.com/s/6ybcxyrpzv88uik/recovery.img
3. after im done with the HTC dev unlocking i should have theese files in my C drive under android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. then i should paste the recovery.img that i downloaded earlier into the andriod directory
5. i found theese steps in the link u guys posted:
----
i am now done with flashing 4EXT recovery from wich i will be installing my new ROMs and kernel
6. I have to enable the 4EXT recovery ---> from what i understand this step i only do once before im rooted and after the root i can enable the 4ext to do it for me every time i flash a new ROM.
7.i shall now install the actuall root file doing it like this:
--- and I am now rooted!!!!1 (atleast i hope so lol)
8 FLASHING OF THE ROM
8a. this is where i have some thoughts. do i have to flash a custom ROM before enableing permanent 4EXT by downloading the file from their website and following theese steps :
or can i do this first.
9 well anywayz presuming that i install the ROM first i go about it like this -->OBS! before i flash anything i have to make a backup. i already done a backup of my contacts, pics, apps and all data on my phone, now i have to make a "nandroid" backup via turning my phone on into bootloader and then going into recovery and now im not sure what to do accually cuz couldn't find anything after this......
perhaps this is how shall go about it?:
or like this:
BUT instead if the named ROM i will be installing the CM 10.1 by Kang or something cant remember the name atm
what i fail to grasp/understand is wheter to use rom manager or not and the benefits of using it. so some pointers and tips would be appriciated there
i shall now have a fully rooted phone and a custom kernel and ROM installed!!!???
when all is done and i managed to root and so forth i'll prolly make a more well written guide and also make a video and perhaps even a glossary of terms so people can unlock the full potential of their phone.
i appricite all the help i can get and be pls tell me is any step is important not to screw up and or if i understood it wrong.
i also appologize for the sloppy writing im writing in a speed
CheerZ

in sort steps
1)htcdev unlock method
2)flshing 4ext recovery(put the recovery.img in the folder where you have adb anf fastboot files)
3)install the supersu.zip from recovery(put the zip in the root of your sdcard)
4)you are rooted.done:good:
now if you want to install a custom rom
1)put the rom.zip in the root of your sdcard
2)boot to recovery
3)make a nandroid backup(just in case)
4)format all partitions except sdcard from recovery
5)enable smartflash from recovery(go to tools and at the bottom you will the smartflash option)
6)flash the rom
7)done:good:

rzr86 said:
in sort steps
1)htcdev unlock method
2)flshing 4ext recovery(put the recovery.img in the folder where you have adb anf fastboot files)
3)install the supersu.zip from recovery(put the zip in the root of your sdcard)
4)you are rooted.done:good:
now if you want to install a custom rom
1)put the rom.zip in the root of your sdcard
2)boot to recovery
3)make a nandroid backup(just in case)
4)format all partitions except sdcard from recovery
5)enable smartflash from recovery(go to tools and at the bottom you will the smartflash option)
6)flash the rom
7)done:good:
Click to expand...
Click to collapse
didnt quite get that part...
and what about wiping that old ROM before flashing a new one?(mby thats exacly what point 4 is saying lol)

lolman96 said:
didnt quite get that part...
and what about wiping that old ROM before flashing a new one?(mby thats exacly what point 4 is saying lol)
Click to expand...
Click to collapse
yeap mate we are saying the same thing hehe

haha oke ty

[HELP] Difficult z710a and I can't figure it out. Want a challenge?

This phone of mine's been through the wringer, and I'm just not savvy enough to get it updated to today's standards. I could really use your help.
A few years ago, I used the Sensation AIO Kit v1.1 to make this Canadian HTC Z710A phone use 4.03 Jellybean, and it's been that way since. Recently, I thought I'd go a step further to bring it to Cyanogen 12. That didn't work (the "forever load circle" happened), so I went back and tried it again with C 11. Again, same result ("f.l.c."). I went back, and after a -LOT- of trial and error, I finally accomplished getting XE with Audio Beats to work....
.....Except, it wouldn't read my wifi hardware whatsoever. I heard this happens sometimes, and a solution is to restore the phone to a factory stock setting and retry from there.
I'm back where I started, at 4.03 Jellybean (Sense v 3.6; Software 3.32.666.13). Something corrupted / screwed up along the way and now I only have access to half(?) the apps that I once had, so the phone is not usable as-is despite regaining wifi control once more. I still have full access to the bootloader and I can install any recovery onto it easily (thanks to Sensation AIO 1, 3, and 4).
So this is where I am, and this is what I just can't get past, and I'd like it if you treated me like a beginner because I'm just not grasping this part:
How do I acquire the proper stock image/rom/kernel? Where do I place it on the SD card? What recovery program should I install? Once it is reverted to stock, what procedures to I need to do to bring it to the best, strongest, full out powerhouse it can be -- as in, what is the greatest custom rom that can be installed?
I'll do my best to amend this post with information as you request it from me.
I really want to thank anyone who can help me here. I'm not quite the intermediate techie that I pretend to be in front of my friends and family, especially when I'm asking such a beginner question in front of you all. I do know that the community here is really strong, so I anticipate good things to come.
(final edit): This post is completed and SOLVED. A huge thank you to user rzr86 for singlehandedly guiding the way through this problem. Please read through all these posts in this thread to glean the trials and tribulations I faced to make it succeed.

intermedE8 said:
This phone of mine's been through the wringer, and I'm just not savvy enough to get it updated to today's standards. I could really use your help.
A few years ago, I used the Sensation AIO Kit v1.1 to make this Canadian HTC Z710A phone use 4.03 Jellybean, and it's been that way since. Recently, I thought I'd go a step further to bring it to Cyanogen 12. That didn't work (the "forever load circle" happened), so I went back and tried it again with C 11. Again, same result ("f.l.c."). I went back, and after a -LOT- of trial and error, I finally accomplished getting XE with Audio Beats to work....
.....Except, it wouldn't read my wifi hardware whatsoever. I heard this happens sometimes, and a solution is to restore the phone to a factory stock setting and retry from there.
I'm back where I started, at 4.03 Jellybean (Sense v 3.6; Software 3.32.666.13). Something corrupted / screwed up along the way and now I only have access to half(?) the apps that I once had, so the phone is not usable as-is despite regaining wifi control once more. I still have full access to the bootloader and I can install any recovery onto it easily (thanks to Sensation AIO 1, 3, and 4).
So this is where I am, and this is what I just can't get past, and I'd like it if you treated me like a beginner because I'm just not grasping this part:
How do I acquire the proper stock image/rom/kernel? Where do I place it on the SD card? What recovery program should I install? Once it is reverted to stock, what procedures to I need to do to bring it to the best, strongest, full out powerhouse it can be -- as in, what is the greatest custom rom that can be installed?
I'll do my best to amend this post with information as you request it from me.
I really want to thank anyone who can help me here. I'm not quite the intermediate techie that I pretend to be in front of my friends and family, especially when I'm asking such a beginner question in front of you all. I do know that the community here is really strong, so I anticipate good things to come.
Click to expand...
Click to collapse
if you want to return back to stock see here
http://forum.xda-developers.com/showthread.php?t=1672425
everything are well-explained
note: if you are on S-OFF leave it as it is

if you want to return back to stock see here
http://forum.xda-developers.com/showthread.php?t=1672425
everything are well-explained
note: if you are on S-OFF leave it as it is
Click to expand...
Click to collapse
I did as you suggested, taking screenshots and camera pics the whole way. I found the only applicable RUU exe and set my phone to a ***RELOCKED*** state prior to running it. Then, I received this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imgur Xl1sSg8.png
So, I clicked cancel and returned here to update this status. I'd love to hear any suggestions. Please let me know if there's anything I should add as far as details go. Thanks.
(I DID say this would be difficult, eh?)

intermedE8 said:
I did as you suggested, taking screenshots and camera pics the whole way. I found the only applicable RUU exe and set my phone to a ***RELOCKED*** state prior to running it. Then, I received this image:
imgur Xl1sSg8.png
So, I clicked cancel and returned here to update this status. I'd love to hear any suggestions. Please let me know if there's anything I should add as far as details go. Thanks.
(I DID say this would be difficult, eh?)
Click to expand...
Click to collapse
which one did you try?
are you on S-OFF?

which one did you try?
are you on S-OFF?
Click to expand...
Click to collapse
By "which one did you try", do you mean the RUU exe?
I downloaded RUU_Pyramid_BM_1.35.666.1_Radio_10.50.9007.00U_10.12.9007.21_2M_release_200555_signed as it was the only one to feature "Pyramid", "BM", and "666" in the filename. That's the program I ran.
Here's a question that I may have misconstrued: When the program states "Image version:" and there's no further text listed, is the program stating "look at the visual image we've provided of a phone and see if it matches", and not "here's an .img version of your phone's software"?
Because, yes, that IS a visual image of my z710a phone in the upper left. I was expecting a series of .img (image) ISO-type files to be listed in that open white space beneath.
Furthermore, the program asks "Select one below:" as if there are many options to choose from, while the only option is "Update". It's terribly worded and confusing.
Lastly, my phone was in an S-ON state when I began this post, and it's still in that S-ON state now (photo below).
imgur VhuK8zi.jpg
So, what is my next move from here?

intermedE8 said:
By "which one did you try", do you mean the RUU exe?
I downloaded RUU_Pyramid_BM_1.35.666.1_Radio_10.50.9007.00U_10.12.9007.21_2M_release_200555_signed as it was the only one to feature "Pyramid", "BM", and "666" in the filename. That's the program I ran.
Here's a question that I may have misconstrued: When the program states "Image version:" and there's no further text listed, is the program stating "look at the visual image we've provided of a phone and see if it matches", and not "here's an .img version of your phone's software"?
Because, yes, that IS a visual image of my z710a phone in the upper left. I was expecting a series of .img (image) ISO-type files to be listed in that open white space beneath.
Furthermore, the program asks "Select one below:" as if there are many options to choose from, while the only option is "Update". It's terribly worded and confusing.
Lastly, my phone was in an S-ON state when I began this post, and it's still in that S-ON state now (photo below).
imgur VhuK8zi.jpg
So, what is my next move from here?
Click to expand...
Click to collapse
since you are on S-ON you can't downgrade
you need an ics ruu.exe
but i don't think that exists any with your firmware version(i am not sure though)
i suggest to unlock again the bootloader
flash a custom recovery(i suggest 4ext recovery)
flash vipers rom 5.3.0 (link in my signature)
then use rumrunner method to S-OFF the device
after that change your cid to supercid
and in the end use any ruu.exe you want
about wifi issue check the pins in the back cover which are responsible for the wifi
lift them up gently

since you are on S-ON you can't downgrade
you need an ics ruu.exe
but i don't think that exists any with your firmware version(i am not sure though)
i suggest to unlock again the bootloader
flash a custom recovery(i suggest 4ext recovery)
flash vipers rom 5.3.0 (link in my signature)
then use rumrunner method to S-OFF the device
after that change your cid to supercid
and in the end use any ruu.exe you want
about wifi issue check the pins in the back cover which are responsible for the wifi
lift them up gently
Click to expand...
Click to collapse
I looked for an ICS RUU like you said, and found this one:
OTA_PYRAMID_ICS_BM_3.32.666.53-3.32.666.13_R_release_2907247e88uydtji4gz02b.zip
However, as you can see, it's an OTA file (I'm assuming "Over The Air"). As it isn't an RUU file, I'm not certain what the best way to proceed from here is, and I would appreciate advice on that.
Also, I can verify that the WiFi pins are in no way a problem. Rather, I think you misinterpreted my statement. The upgrade to C12 previously just didn't have the software connection established. The hardware is perfectly fine and works ideally.
I look forward to any additional help on this, and thank everyone for taking time to help out.

intermedE8 said:
I looked for an ICS RUU like you said, and found this one:
OTA_PYRAMID_ICS_BM_3.32.666.53-3.32.666.13_R_release_2907247e88uydtji4gz02b.zip
However, as you can see, it's an OTA file (I'm assuming "Over The Air"). As it isn't an RUU file, I'm not certain what the best way to proceed from here is, and I would appreciate advice on that.
Also, I can verify that the WiFi pins are in no way a problem. Rather, I think you misinterpreted my statement. The upgrade to C12 previously just didn't have the software connection established. The hardware is perfectly fine and works ideally.
I look forward to any additional help on this, and thank everyone for taking time to help out.
Click to expand...
Click to collapse
try to flash that zip via fastboot
fastboot flash zip <<the name of the zip>>
if it doesn't work then do it from ruu mode
from bootloader type fastboot rebootRUU
then the above command

try to flash that zip via fastboot
fastboot flash zip <<the name of the zip>>
if it doesn't work then do it from ruu mode
from bootloader type fastboot rebootRUU
then the above command
Click to expand...
Click to collapse
Well, I first tried to flash via the aforementioned fastboot flash zip OTA...zip command, but there was an error and it failed.
Next, I attempted to flash via the recovery menu through the Update Via Zip On SD menu selection, of which I was able to take a photo of the resulting error on screen:
imgur z1aEOGS.jpg
So the question I have before proceeding with the suggestion of using fastboot rebootRUU (and is that the actual command, with proper spacing?), is: Do any of those bits of text on the screenshot contain pertinent revelations to this procedure that might make me want to take a different tactic? Should I try installing the vipers rom 5.3.0, do the rumrunner/S-OFF technique, and change to supercid BEFORE attempting the fastboot rebootRUU command?
If anyone wants to lay out a series of commands for me to follow from here, I'd really appreciate it.
I do apologize for such a difficult restoration. I knew it was going to be rough. Thanks for all your patience.

intermedE8 said:
Well, I first tried to flash via the aforementioned fastboot flash zip OTA...zip command, but there was an error and it failed.
Next, I attempted to flash via the recovery menu through the Update Via Zip On SD menu selection, of which I was able to take a photo of the resulting error on screen:
imgur z1aEOGS.jpg
So the question I have before proceeding with the suggestion of using fastboot rebootRUU (and is that the actual command, with proper spacing?), is: Do any of those bits of text on the screenshot contain pertinent revelations to this procedure that might make me want to take a different tactic? Should I try installing the vipers rom 5.3.0, do the rumrunner/S-OFF technique, and change to supercid BEFORE attempting the fastboot rebootRUU command?
If anyone wants to lay out a series of commands for me to follow from here, I'd really appreciate it.
I do apologize for such a difficult restoration. I knew it was going to be rough. Thanks for all your patience.
Click to expand...
Click to collapse
i think the error has something to do with the cid
actually i suggest to go for vipers rom then S-OFF
it is far more easy way

i think the error has something to do with the cid
actually i suggest to go for vipers rom then S-OFF
it is far more easy way
Click to expand...
Click to collapse
Well, it didn't quite work.
ViperS/C2 5.3.0 (your link) wasn't downloading for whatever reason, and I'm on limited bandwidth so I couldn't keep spending 3 hours to have it stop downloading at 150mb in. Instead, I downloaded 5.2.1 and the 750mb file came in within a steady 30 minutes.
In recovery mode, I wiped all the necessary things that needed to be wiped (dalvik, etc) and then installed V 5.2.1. The ROM saw the phone as a z710e (and not as the z710a it actually is), but the installation proceeded anyway.
imgur 8xpQhhx.jpg
It asked to reboot, and I said yes, and now we have this.
imgur 3eKdqez.jpg
It's been on this HTC boot screen for over an hour now.
I have to run around town for the next several hours, and I'll leave it as is, stuck on the HTC boot logo. When I return (if there hasn't been any change), I'll reboot the phone back into recovery and go from there.
I could use some advice at this point. Difficult phone is difficult.

intermedE8 said:
Well, it didn't quite work.
ViperS/C2 5.3.0 (your link) wasn't downloading for whatever reason, and I'm on limited bandwidth so I couldn't keep spending 3 hours to have it stop downloading at 150mb in. Instead, I downloaded 5.2.1 and the 750mb file came in within a steady 30 minutes.
In recovery mode, I wiped all the necessary things that needed to be wiped (dalvik, etc) and then installed V 5.2.1. The ROM saw the phone as a z710e (and not as the z710a it actually is), but the installation proceeded anyway.
imgur 8xpQhhx.jpg
It asked to reboot, and I said yes, and now we have this.
imgur 3eKdqez.jpg
It's been on this HTC boot screen for over an hour now.
I have to run around town for the next several hours, and I'll leave it as is, stuck on the HTC boot logo. When I return (if there hasn't been any change), I'll reboot the phone back into recovery and go from there.
I could use some advice at this point. Difficult phone is difficult.
Click to expand...
Click to collapse
because you are on S-ON and need to flash the boot.img via fastboot command after rom installation
otherwise use 4ext recovery and enable smartflash exactly before flashing the rom

because you are on S-ON and need to flash the boot.img via fastboot command after rom installation
otherwise use 4ext recovery and enable smartflash exactly before flashing the rom
Click to expand...
Click to collapse
Success! Messaging you from Chrome, via the WiFi on this working Viper ROM z710... what is this now, an a or an e? Who knows.
I restored back to my recovery, downloaded the most recent 4EXT from your link and made that my new custom recovery. From there, I started Superflash immediately before loading this ROM again, and it works. It all works.
Thank you very much for helping me throughout.
I think my next plan of attack is to find and use the rumrunner to S-OFF the device. Then, install the fun bits.
I'll post any follow ups that snag if they happen, but for the moment you've solved my difficult phone. Thank you very much.

intermedE8 said:
Success! Messaging you from Chrome, via the WiFi on this working Viper ROM z710... what is this now, an a or an e? Who knows.
I restored back to my recovery, downloaded the most recent 4EXT from your link and made that my new custom recovery. From there, I started Superflash immediately before loading this ROM again, and it works. It all works.
Thank you very much for helping me throughout.
I think my next plan of attack is to find and use the rumrunner to S-OFF the device. Then, install the fun bits.
I'll post any follow ups that snag if they happen, but for the moment you've solved my difficult phone. Thank you very much.
Click to expand...
Click to collapse
your device still remains a z710a. any custom rom doesn't change that
for rumrunner method see here
http://forum.xda-developers.com/showthread.php?t=2751187
note: if your only goal was to solve the wifi issue let me tell you that you are done

Just a follow-up, no need to reply.
I thought I'd let everyone know that the phone works fine for what it is. The memory is pretty low, but I knew that going in.
I had some trouble with battery life, but there is some amazing posts elsewhere on this site for managing battery life in the Viper rom, and by following those guides I was able to extend the phone's duration by three or four times longer.
Thank you, rzr86. Your assistance was invaluable.
Take care.