[GUIDE] **SPRINT CDMA HERO**Unroot without RUU / From SD Card - Hero CDMA Android Development

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

Related

Rooting the SPL 1.76.0009

Hey everyone..
U need to thank Orange_24 for this..
It took me a WHILE (3 hours of seaching intense) to find out how to root the 1.76.0009 so i thought i would make a new thread to help people .. but i found it deep in a forum in here
RUU:
4shared.com/file/MjOxJBX0/RUU_Sapphire_HTC_Europe_305401.html
Recovery RA-Hero
rapidshare.com/files/360227978/recovery-RA-hero-v1.6.2.img
Engineer's SPL 1.76.0007
4shared.com/file/211145376/3da88b40/update-hboot-1762007-signed.html
THIS METHOD WILL DELETE ALL DATA ON YOUR PHONE! Proceed at your own risk!
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
I did this to mine and it worked ..
Bowing before the community
EDIT:
since many people have problems with windows 7 an windows 7 x64 i will thank the LayZeeDK for writing this so i dont have to ..
First install HTC Sync. Then try these drivers: http://www.multiupload.com/RJRAYM75A2
Start > Devices and Printers > Right click 'Android Phone' > Properties > Click 'Hardware' tab > Press the one with 'Disk drives' type > Properties > Update Driver... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Have Disk... > Pres 'Browse...' > Browse to the drivers in the folder 'Vista_x64' to which I linked above e.g. 'C:\Users\Lars\Desktop\Vista_x64' > OK > Choose 'My HTC' or whatever it shows
Seems that the drivers in Vista_x64 worked for USB/Sync/RUU connection and the drivers in USB_MODEM_VISTA works for ADB connection. ADB is changed through Device Manager (Right Click 'Computer' > Manage > Device Manager).
TO ROGERS
mbk.2k3 wrote this so all credit goes to him! ..
to help the rogers folks: i had updated using the official Rogers update and thought i was stuck with the perfected SPL
I used the following method to get back my root (http://rootyourmagic32a.blogspot.com...htc-magic.html).
follow every step carefully.
then i downgraded radio and got an engineering SPL on using the following method (http://forum.xda-developers.com/showthread.php?t=605239)
i used adb shell heavily. it was daunting at first but once i got into it, it was smooth sailing and you build your confidence quickly (good for noobs like us)
will this get signature off so that i may use fastboot commands?
..
if u cant use fastboot commands it means you have a perfected SPL
this will root and and change SPL to an Engineers SPL
with an Engineer's SPL there will be no limitations
ah because i found people wich said that had a rooted phone with a sPL like the Eng but had Sig off. I already found some issues of some people here in XDA wich had that problem. It would be nice to encounter a solution for that.
..
i don't exactly know what u mean but this certainly works.. an i have used fastboot several times with it
How about for HBOOT-1.76.0007?
{
"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"
}
it dont work for me
It does work. Its old news.
You are doing something wrong.
This works, I did it on a friend's 32A that had the 1.76.0009 perfected SPL a few days ago. This info was taken from the first post of the huge thread of people trying out methods for rooting the 1.76.0009 SPL. Good idea making a new thread, that last one was a clusterfuck and the first post had missing links lol.
BTW, you didn't need a goldcard for this? I went through the trouble of making a goldcard because the old thread's instructions included making a goldcard. That coulda saved me a bit of time, lol. And I used Cursordroid's custom 32A recovery image, so this method works with that recovery as well.
Also, typo: "Engeeneers SPL 1.76.0007" should be "Engineer's SPL 1.76.2007"
eyegor said:
It does work. Its old news.
You are doing something wrong.
Click to expand...
Click to collapse
Very long ago, thanks Orange_24
i did something wrong, it did work now
hade154 said:
i did something wrong, it did work now
Click to expand...
Click to collapse
translated my tutorial
http://translate.google.pl/translat.../showpost.php?p=94518&postcount=1&sl=pl&tl=en
Click to expand...
Click to collapse
..
Very long ago, thanks Orange_24
Click to expand...
Click to collapse
yea i just did this to maybe save some people from going thru the extra hours of searching ..
Also, typo: "Engeeneers SPL 1.76.0007" should be "Engineer's SPL 1.76.2007"
Click to expand...
Click to collapse
yea thanks for correcting the typo btw
BTW, you didn't need a goldcard for this?
Click to expand...
Click to collapse
i didn't make goldcard .. thats why i did the long search for finding a method that didn't require me to do it
Very long ago, thanks Orange_24
Click to expand...
Click to collapse
as i said.. just to make new thread with it and lower the search time.. that's why there was put in the Build a shrine for Orange_24 in there
This is not the way to breaking the SPL for all Countries - just in case.
I guys Im from Australia and I accidentally update my magic to the 3.05.861.2 rom which had the perfected 1.76.0008 SPL im am happy to say that this method actually root the spl which in favour lets you go back to either 1.33.2010 or 1.76.2007 whichever you prefer
glad that you found my thread then ^^..
yea.. but i dont know why u should go back to the 1.33?
1.76 are for the new rom's
^^ your right its better to stay on 1.76.2007 but i decided to try out CyanogenMod CM5.0.7 and i'm loving it
madshabz said:
^^ your right its better to stay on 1.76.2007 but i decided to try out CyanogenMod CM5.0.7 and i'm loving it
Click to expand...
Click to collapse
yea you are right. CyanogenMod are some very good roms. but when he removed market from his newer roms i went over and found some other roms
Rogers
The Rogers update uses this perfected SPL correct? If so glad that a workaround has been found finally.
Question though: can I go back and forth freely? ie. if i follow the steps, root my phone, try a new ROM, and later want to go back to the Rogers update.
Thanks in advance!
hey
The Rogers update uses this perfected SPL correct? If so glad that a workaround has been found finally.
Question though: can I go back and forth freely? ie. if i follow the steps, root my phone, try a new ROM, and later want to go back to the Rogers update.
Thanks in advance!
Reply With Quote
Click to expand...
Click to collapse
yea u can go back and foward between the roms. don't know if rogers are perfected spl but if it is u have to do this every time you want to switch away from rogers

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

[GUIDE] One Click How to Root the GSM & CDMA Desire with Unrevoked 3.21

I first want to thank everyone at UnrEVOked for what they've done. I'm posting this because the UnrEVOked post doesn't really give any instructions. Its an easy enough root, but I know I've been there before and even the simplest things can be tough if things aren't laid out. So here's a step by step tutorial.
Due to some bugs, Unrevoked 3.2 was taken down shortly after being released, but the updated version is now LIVE! So obviously we're going to bring you a video tutorial on how to do it! Thanks to the guys at Unrevoked for giving us this simple solution to rooting the GSM & CDMA Desire.
LINK TO VIDEO WALKTHROUGH FOR HOW TO ROOT THE DESIRE
◄●REQUIRED DOWNLOADS●►
EVERYONE: Unrevoked3. Download the version for your OS.
WINDOWS USERS: unrEVOked modified USB driver
◄●How to Install HBOOT Drivers (Windows Users ONLY)●►
If you're using Windows, you're going to have to install the HBOOT drivers first. You can follow this video tutorial:
How to Install HBOOT Drivers
and follow along with these written instructions provided by the Unrevoked team:
Download the unrEVOked modified USB driver and expand it somewhere you will remember.
Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
Open Device Manager.
Click Start, then right click on Computer, then click Properties, then click Device Manager.
Under Other devices, you should now see the Android 1.0 device.
Right click on Android 1.0 and click Update Driver Software:
Click on Browse my computer for driver software.
Click on Browse and select the Android USB Driver folder on on your computer, click ok, then click next.
You should get a status bar indicating that the driver is installing. If you get any warnings, just click Ok.
Your driver should install.
Click Close and make sure Android Bootloader Interface is listed under Android Phone.
◄●Instructions●►
Make sure you downloaded Unrevoked3 for your OS.
If you're on Windows, make sure you "uninstall HTC Sync or any other program that might talk to the phone over USB (doubletwist, etc). They will cause problems" (Unrevoked.com).
Plug your phone into your computer with USB.
Drag down from the notification bar on your phone and select "Charge Only" and "Remember this"
Make sure your phone has USB Debugging turned on by going to Menu>>Settings>>Applications>>Development and checking USB debugging.
Run the Reflash application that you downloaded.
Unrevoked will run its processes. Follow the few instructions it gives and thats it!
You're now rooted!
By God you guys are awesome. I was following the XDA rooting tutorials talking about downgrading hboot and goldcards before coming across this. So, thanks to your collective awesomeness, I can run this tonight and be on my merry way. First, I take it I can't backup my current stock 2.2 ROM before I have rooted it with a custom recovery image that gives me Nandroid backup capability? I'm a backup fanatic, and annoying cautious, so any tips here on before, during and after would be welcome. Or can I just go ahead, and if there are problems, I can easily restore my phone to factory state? And some links to information about the next step of installing ROMs would be welcome too, I have no idea where to turn after rooting my phone.
PS - I will donate $5 to you and the awesome Unrevoked crew, it's not much but I hope it helps and that my encouragement of others to do the same will help too.
Hi,
Can I root the Desire equipped with SLCD, Froyo 2.2 & HBOOT 0.93.
I'm sorry if this question is redundant
D
DroidBois said:
By God you guys are awesome. I was following the XDA rooting tutorials talking about downgrading hboot and goldcards before coming across this. So, thanks to your collective awesomeness, I can run this tonight and be on my merry way. First, I take it I can't backup my current stock 2.2 ROM before I have rooted it with a custom recovery image that gives me Nandroid backup capability? I'm a backup fanatic, and annoying cautious, so any tips here on before, during and after would be welcome. Or can I just go ahead, and if there are problems, I can easily restore my phone to factory state? And some links to information about the next step of installing ROMs would be welcome too, I have no idea where to turn after rooting my phone.
PS - I will donate $5 to you and the awesome Unrevoked crew, it's not much but I hope it helps and that my encouragement of others to do the same will help too.
Click to expand...
Click to collapse
Really appreciate the feedback bro This shouldn't affect any of your data. I can't say go forward and guarantee you that nothing will happen (there's always the chance that something goes wrong) but you shouldn't have a problem. If you're extremely nervous though, you could use appbrain to backup the apps you use(though it won't backup your data) and export your contacts to your sdcard if you aren't saving them to google. You could also buy MyBackup Pro which backs up a lot.
Click the image in my sig for The Droid Demos. There are a few tutorials you can check out for after you've rooted. More will be coming every week
Feel free to ask any questions man. Good luck!
dsymbol said:
Hi,
Can I root the Desire equipped with SLCD, Froyo 2.2 & HBOOT 0.93.
I'm sorry if this question is redundant
D
Click to expand...
Click to collapse
You shouldn't have any troubles.
Hi,
Can i use this with froyo 2.2 OTA official. HBOOT 0.92.0001
or i still need to downgrade to HBOOT 0.80 ?
thanks
WooHoo!!!!! my phone is successfully rooted.
Thank you.
P.S. I skipped step 3.
2. Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
3. On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
4. Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
+1
iamhyoga said:
Hi,
Can i use this with froyo 2.2 OTA official. HBOOT 0.92.0001
or i still need to downgrade to HBOOT 0.80 ?
thanks
Click to expand...
Click to collapse
+1 wondering the same thing....
(btw, amoled screen here)
Yes, you can.
Thugsin313 said:
+1 wondering the same thing....
(btw, amoled screen here)
Click to expand...
Click to collapse
iamhyoga said:
Hi,
Can i use this with froyo 2.2 OTA official. HBOOT 0.92.0001
or i still need to downgrade to HBOOT 0.80 ?
thanks
Click to expand...
Click to collapse
nickiberli said:
Yes, you can.
Click to expand...
Click to collapse
nickiberli is right. You shouldn't have any troubles Report back!
Hmmm,
I have followed the above guide to the letter and it seems to go throught the motions but ends on an
"internal error couldn't find misc"
error message......
I am running a stock O2 Froyo Desire with HBoot .93.......Any ideas?
Hi guys,
1st time poster - be gentle!
Ive got a Desire with Froyo 2.2 OTA update and Hboot 0.93.
I have no option for hboot only
Fastboot
Recovery
Clear Storage
Simlock
Any ideas? Sorry im prob doing it wrong
chrisnic0 said:
Hi guys,
1st time poster - be gentle!
Ive got a Desire with Froyo 2.2 OTA update and Hboot 0.93.
I have no option for hboot only
Fastboot
Recovery
Clear Storage
Simlock
Any ideas? Sorry im prob doing it wrong
Click to expand...
Click to collapse
No you're not doing it wrong ^^ I got the same "issue" before i noticed that it activated HBOOT USB PLUG just by inserting the usb cable when in bootloader . After that i just installed the unrevoked usb driver , started my phone and ran unrevoked and it did magic on my phone rooting it in just a minute.
Hope this helps.
More info here guys http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
I'm already rooted, but will unrevoked also have a permanent recovery installed on your device? I'm still using fake flash now.
retr0sic said:
No you're not doing it wrong ^^ I got the same "issue" before i noticed that it activated HBOOT USB PLUG just by inserting the usb cable when in bootloader . After that i just installed the unrevoked usb driver , started my phone and ran unrevoked and it did magic on my phone rooting it in just a minute.
Hope this helps.
Click to expand...
Click to collapse
hi
unrevoked is not detecting my phone. i have it connected as charge only and also have usb debugging selected.
running win 7. any advice or help?
I'm also struggling to get Unrevoked to find my phone, infact when i plug the phone in i get an installer pop up for ADB?
And when i look under device manager next to other devices android bootloader interface is replaced with 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"
}
I've tried restarting unrevoked but with no success? (i'm running XP)
Can anyone confirm?
Will this work on HBOOT 0.93.0001 and radio 5.09.05.20_2
?
thanks
EDIT: confirmed myself, it works flawlessly. And I loved the portal reference during the rooting process, made me feel like a king.
For those having trouble connecting, try installing HTC Sync and then uninstalling it. There are drivers associated with it that are usually needed.
Same with me.
Can install the driver fine under WinXP (SP3).
In HBoot mode, there is an Android Bootloader Interface under Android Phone.
However when I reboot the Phone Windows XP finds a new device, the abovementioned ADB device and tries to install drivers for it. The drivers cannot be found, even manually browsing to the Android USB Driver folder does not help. I end up with the yellow acclamation mark, and the reflash utility waiting for the phone to be connected.
HBoot 0.93
Android 2.2
Software version desire 2.10.405.2
@djR3Z
Thx, that was the solution. Installed HTC-sync. First 4 packages were installed (drivers and stuff) Aborted when the actual HTC-sync.msi started installing. Now unrEVOked works like a charm
djR3Z said:
For those having trouble connecting, try installing HTC Sync and then uninstalling it. There are drivers associated with it that are usually needed.
Click to expand...
Click to collapse
Thanks, just giving that a go...
...
Got there in the end.

Bricked EVO This should help!!!!!

Ok so i did the hboot 2.2 root and got to after the unevoked forever and this is what i got from there i really hope this helps because i got partal root from this method
Ok so if u have got the radio failed pu you dont have a rom anymore so you need to do this
open my computer go to c drive go to user go to your username then up at the top go to the address bar and type in appdata so for mine it would say
c:\users\chris\appdata for something like that then when your in the app data folder you will see local click on that then you will see temp click on that now to make this easyer you sould erase everything in your temp folder that you can now
download the ruu 3.30 exe and when you get it downloaded go and load it up and when the program is ready for you to go through the steps of updating just dont touch it
Go back to your temp folder and you should see a couple more folders appreare in one of thoughs folders you will see another folder and like corecomp or something like that then you will also see dotnet well go to the other folder in that folder then go to the bottom and you will see (rom) move it to your desktop and rename it PC36img or what ever its suppose to be then erase the rom on your sd card and put this one on it and then go back into your bootloader and flash that one and it should work it did for mine the only thing is it will put you back on 3.30 the s-off will still be there if you have done the unrevokted forever this will also allow you to run the unrevoked 3.21 and it will give you a partial root with super user and i still have not been able to flash custom rooms but i am running superuser and root explorer and wireless tether on my eve and it is working good
So just to recap
If you have not got to the part where you can load unrevoked forever and you do my method you will return to stock and also unrevoked 3.21 will not work unless you have s-off
Now if you have s- off but cant get roms on your phone do this method and you will be able to get the stock rom on your phone then you can run unrevoked 3.21 for windows that is the one i did but it gave me superuser and it was flawless just do what it says.
have fun hope this helps get your phone back it did mine and 2 other so im sure it will work
download ruu 3.30 from here http://www.multiupload.com/U27BZXVWWI
WOW! I'm not even sure why I read this post in the first place but, having done so anyway... My head now hurts.
Mr. Madison, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.
okolowicz said:
WOW! I'm not even sure why I read this post in the first place but, having done so anyway... My head now hurts.
Mr. Madison, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.
Click to expand...
Click to collapse
Lmao.
Sent from my PC36100 using XDA App
{
"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 had to read this a few times but I followed it and it worked. Got my brick back up to stock. Not even the Sprint store was able to get a stock rom on it.
Thanks for the info.
You are a genius thank you, I just bricked my girls phone and your method worked perfectly I can now sleep in the bed tonight.LMAO
+1
Sent from my PC36100 using XDA App
Lifesaver!!!
I didn't find the directions hard to follow just some have to get through some grammatical errors and your go to go. Spent awhile doing all the other methods this worked first time, took 5 minutes. Wish I read this hours ago. Well done.
An easier way is to simply download the file that someone has already extracted
You can find them in the first link in my sig or in a few other threads that you can find with a quick search
Its because of threads like this that we spend hours searching for solutions to our problems.
People who don't know what they are doing, and think they do.
Try searching for linux help, you will then see my point.
good post, need more like it
helped so much thank you!
Just had to share the props
I boot looped a buds phone, and didn't backup the RA Amon that I just flashed, I only had nandroids in Clockwork Mod... therefore, no go in RA. This saved me some serious heart-ache! Flashed this, downloaded clockwork, and his phone was back to its previous state.
Now I just have to try it again when he'll let me... lol
Thanks for sharing!
He knows his stuff
THIS GUY IS A GENIUS..... I tried every method on here, nothing worked until now.
Monarky said:
i still have not been able to flash custom rooms but i am running superuser and root explorer and wireless tether on my eve and it is working good
Click to expand...
Click to collapse
Looking past all the convoluted, non-coherent instructions - sounds like you need to flash from the bootloader the updated AmonRa made especially for this process - then you'll be able to flash a custom ROM:
PC36IMG_Recovery.zip
here are step-by-step instructions:
1. Download the PC36IMG-Recovery.zip file from above.
2. Rename to PC36IMG.zip and place in the root of your sdcard.
3. Power off your Evo
4. Hold down the Volume Down button and then hold the power button until you get to the white bootloader screen.
5. IF it says "SUPERSONIC EVT2-3 SHIP S-OFF" THEN
Allow it to flash - will take awhile.
a. When prompted if you want to apply, choose Yes by pressing Up
b. When prompted to reboot choose Yes by pressing Up​ ELSEIF it says "SUPERSONIC EVT2-3 SHIP S-ON" THEN
YOU NEED TO GO BACK TO zikronix's HBOOT Guide AND FOLLOW THE INSTRUCTIONS SLOWLY AND CAREFULLY SO YOU CAN GET S-OFF - OTHERWISE YOU WON'T BE ABLE TO FLASH A CUSTOM ROM OR RECOVERY
YOU CAN PUT THE STOCK 3.30 RUU PC36IMG.zip INSTEAD OF THE RECOVERY ZIP ABOVE AND FLASH TO STOCK BUT THAT WILL BE ALL YOU HAVE AND YOU WILL BE BACK TO SQUARE ONE - BUT AT LEAST YOU'D HAVE A WORKING EVO​
6. You should be done and back to stock. Go ahead and try to follow zikronix's instructions again - slowly and carefully.
props
Worked first time. Thanks bro i love you
First reply to this thread had me laughing hysterically. But, I'm really glad to see it helped people. In fact, given how many it helped in such a short period, it probably should be stickied. But one should definitely heed xhausxs' post when reading.
Nice contribution, thank you.
Sent from my PC36100 using XDA App
Monarky said:
Ok so i did the hboot 2.2 root and got to after the unevoked forever and this is what i got from there i really hope this helps because i got partal root from this method
Ok so if u have got the radio failed pu you dont have a rom anymore so you need to do this
open my computer go to c drive go to user go to your username then up at the top go to the address bar and type in appdata so for mine it would say
c:\users\chris\appdata for something like that then when your in the app data folder you will see local click on that then you will see temp click on that now to make this easyer you sould erase everything in your temp folder that you can now
download the ruu 3.30 exe and when you get it downloaded go and load it up and when the program is ready for you to go through the steps of updating just dont touch it
Go back to your temp folder and you should see a couple more folders appreare in one of thoughs folders you will see another folder and like corecomp or something like that then you will also see dotnet well go to the other folder in that folder then go to the bottom and you will see (rom) move it to your desktop and rename it PC36img or what ever its suppose to be then erase the rom on your sd card and put this one on it and then go back into your bootloader and flash that one and it should work it did for mine the only thing is it will put you back on 3.30 the s-off will still be there if you have done the unrevokted forever this will also allow you to run the unrevoked 3.21 and it will give you a partial root with super user and i still have not been able to flash custom rooms but i am running superuser and root explorer and wireless tether on my eve and it is working good
So just to recap
If you have not got to the part where you can load unrevoked forever and you do my method you will return to stock and also unrevoked 3.21 will not work unless you have s-off
Now if you have s- off but cant get roms on your phone do this method and you will be able to get the stock rom on your phone then you can run unrevoked 3.21 for windows that is the one i did but it gave me superuser and it was flawless just do what it says.
have fun hope this helps get your phone back it did mine and 2 other so im sure it will work
download ruu 3.30 from here http://www.multiupload.com/U27BZXVWWI
Click to expand...
Click to collapse
wow great work thanks alot works great wow i was scared my brick gone thanks dude
You are tha Man
Monarky said:
Ok so i did the hboot 2.2 root and got to after the unevoked forever and this is what i got from there i really hope this helps because i got partal root from this method
Ok so if u have got the radio failed pu you dont have a rom anymore so you need to do this
open my computer go to c drive go to user go to your username then up at the top go to the address bar and type in appdata so for mine it would say
c:\users\chris\appdata for something like that then when your in the app data folder you will see local click on that then you will see temp click on that now to make this easyer you sould erase everything in your temp folder that you can now
download the ruu 3.30 exe and when you get it downloaded go and load it up and when the program is ready for you to go through the steps of updating just dont touch it
Go back to your temp folder and you should see a couple more folders appreare in one of thoughs folders you will see another folder and like corecomp or something like that then you will also see dotnet well go to the other folder in that folder then go to the bottom and you will see (rom) move it to your desktop and rename it PC36img or what ever its suppose to be then erase the rom on your sd card and put this one on it and then go back into your bootloader and flash that one and it should work it did for mine the only thing is it will put you back on 3.30 the s-off will still be there if you have done the unrevokted forever this will also allow you to run the unrevoked 3.21 and it will give you a partial root with super user and i still have not been able to flash custom rooms but i am running superuser and root explorer and wireless tether on my eve and it is working good
So just to recap
If you have not got to the part where you can load unrevoked forever and you do my method you will return to stock and also unrevoked 3.21 will not work unless you have s-off
Now if you have s- off but cant get roms on your phone do this method and you will be able to get the stock rom on your phone then you can run unrevoked 3.21 for windows that is the one i did but it gave me superuser and it was flawless just do what it says.
have fun hope this helps get your phone back it did mine and 2 other so im sure it will work
download ruu 3.30 from here http://www.multiupload.com/U27BZXVWWI
Click to expand...
Click to collapse
Bro you saved my ass big time I was with out my phone for 3 fxxxxig days do to a broken recovery and nothing was working and with the guidance of your thread my hard rate is pounding normal again . THANK YOU
No offence Mr.Madison but I never lol reading xda forums (very rarely) but I had to explain to my wife why I had tears in my eyes when she came in...and to make it better someone deciphered this madness and thanked you, so here is a thanks to you for the laugh! And the fix...
EVO...ROOT IT...DEEP FRY IT...LOVE IT TILL THE END¡

[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.

Categories

Resources