Related
I installed 32A (6.35.10.18) radio on my Tmobile mytouch 32B by mistake.
Before doing this I had my phone rooted and SPL (1.33.2005 i think). Now fast boot shows its a 32A device . Now not able to run recovery mode.
I am not able to revert it back to 32B radio.
Tried to unroot but it says version is older(with gold card).
Some one please help me......
betaboy said:
I installed 32A (6.35.10.18) radio on my Tmobile mytouch 32B by mistake.
Before doing this I had my phone rooted and SPL (1.33.2005 i think). Now fast boot shows its a 32A device . Now not able to run recovery mode.
I am not able to revert it back to 32B radio.
Tried to unroot but it says version is older(with gold card).
Some one please help me......
Click to expand...
Click to collapse
You should be able to flash a radio image from fastboot. All you would need is to connect via USB. The phone will show 'fastboot usb' instead of 'fastboot'. You'll need the android sdk in order to go any further. Place the radio you want in the tools folder of the sdk so that it's easier to get to. Bring up a command prompt and navigate to the tools folder.
For me it looks like this:
cd\
cd androidSDK/tools
From there you'll need to make sure that the android drivers are installed properly. You can do this just by typing this:
fastboot devices
This will bring up a serial number if the drivers are installed correctly. If not you'll need to get the appropriate drivers. I believe I found mine during the gold card root process on the Unlockr's site.
As soon as your computer is talking to your phone it's simple.
In your command prompt simply type the following:
fastboot update <radio.img>
fastboot reboot
This will reboot the phone and it should reflash the radio. I've never had to do this so I don't know if it is going to work. Take these words with a grain of salt though... this could still brick your phone. Who knows? Next time just make sure you have the appropriate files. Especially when dealing with radio and spl. You're lucky your phone even turns on.
Good luck!
yeah i did the same last night, but mine is stuck with RUU USB and since the SPL is perfect i cant do anything as i get a signature verify fail or remote: can not do message
If you find a solution id be very interested.
Cheers.
Hi phantommusik,
Thanks for your response. This what I get when I do update radio.imp
"EOCD not found, not Zip
error: failed to access zipdata in '☺'"
No clue what it means
I am by no means an expert on the 32B Magic, but...
Try creating a Goldcard. There are instructions on this forum.
Then, even if your phone is stuck in RUU mode, you should be able to apply this RUU for the 32B Vodafone Magic.
http://forum.xda-developers.com/showthread.php?t=640283
I warn you though, you might end up with an unrootable phone. But at least it will work.
EDIT: Pay careful attention to these steps. Make sure a goldcard is in your phone before starting.
- Download and run the RUU executable
- When the wizard is at step 1, open a file search dialog
- Look for a file named rom.nbh (should be in %temp% folder)
- Copy the rom.nbh to another folder and rename it to SAPPIMG.NBH
- Close the wizard
- Copy the sappimg.nbh to the root of your SDCard
- Power down your phone
- Boot your phone while pressing "volume down"
- It will ask you to update (wait a bit till the question pops up)
- Press trackball to start update
- After update press trackball again to reboot
Sorry!
betaboy said:
Hi phantommusik,
Thanks for your response. This what I get when I do update radio.imp
"EOCD not found, not Zip
error: failed to access zipdata in '☺'"
No clue what it means
Click to expand...
Click to collapse
I know exactly what that means!!! It means I didn't give you complete instructions! My bad! When you are flashing anything from recovery or fastboot it has to be a .zip file or .nbh. I'm not entirely sure what needs to happen in order to get it to read it but you could try sticking that radio in a .zip file with NO COMPRESSION. You might want to take a look at some of the other threads in here to see what they have to say about putting just a radio in a zip file! I would suggest downloading a radio update that is already a zip file!
Hope this helps!
One friend of mine did exactly the same thing. I used the instructions on this post and I managed to get him his 32B Magic back.
becareful flashing this rom, it is perfected and you cant root it and if you can i wanna know how !
I tried updating the new RUU when in fastboot, but there was an error saying incorrect id.
Then I coppied rom.zip file and renames it to sappimg.zip, hboot hung when updating RADIO_V2.
Please help me, its ok even if cant root the phone.
gymmy said:
becareful flashing this rom, it is perfected and you cant root it and if you can i wanna know how !
Click to expand...
Click to collapse
Listen. If you really don't know, stop misleading people. You can't root this ROM, but you can install one that is already rooted. This ROM has the kernel fault that allows flashrec to install a custom recovery ROM. From then on you can do whatever you like with your phone, even revert it back to 32B. Amon_Ra's ROM for 32B Magic is a good place to start. Read here the post my friend wrote to thank me about getting his Magic back (It's translated from Greek, hence the bad English).
betaboy said:
I tried updating the new RUU when in fastboot, but there was an error saying incorrect id.
Then I coppied rom.zip file and renames it to sappimg.zip, hboot hung when updating RADIO_V2.
Please help me, its ok even if cant root the phone.
Click to expand...
Click to collapse
You' ll need a goldcard to use this. Stop doing things that can mess up your phone even more (like sappimg.zip etc). Just use the instructions in the link I posted before. About rooting please read my reply @gummy just above.
When I ran "RUU Sapphire HTC Arabic Etisalat" the installation got sturck at 77% (updating radio).
I removed the batter and plugged it back, now the phone got struck in RUU mode couldnt go to fastboot....... does it mean its bricked?
betaboy said:
When I ran "RUU Sapphire HTC Arabic Etisalat" the installation got sturck at 77% (updating radio).
I removed the batter and plugged it back, now the phone got struck in RUU mode couldnt go to fastboot....... does it mean its bricked?
Click to expand...
Click to collapse
Repeat the process with the RUU. It did the same thing, when I used it and after 1 or 2 tries the ROM was flashed properly.
Hi to all, i'm jauffre and i'm new in XDA. I have a problem and, as i searched all the forum without finding an answer, i need your help.
Last week i rooted my htc incredible s using the revolutionary tool, wich upgraded the hboot to 6.13.1002. i installed with the clockwork mod recovery tool a modded rom, and it was great. but sunday my phone crashed to the ground, and now the cover is broken (so i need to send it to the warranty).
i spent last day searching a guide for dummies to unroot the phone, and using the signed RUU (downloaded from this site) it appeared to work, but my htc is still s-off.
now, i know i need to downgrade the hboot, and i tried everything (i reinstalled froyo, updated the radio and then updgraded to 2.3.3), but this is still a problem.
please, help me!
Hey guys, this is the procedure i did to solve my problem. do it at your own risk.
first of all i must say that with this process i'll have the hboot back, but NOT the bootloader (so when you hold "volume back+power on" you will see the modded bootloader, not the stock one). i don't know how did you rooted your phone, what programs did you use, and i cannot assure you this procedure will work. if you're not sure, don't do anything.
first, you have to look for the original RUU of your phone (you can find it on this site). then follow this thread to find the rom.zip file (http://forum.xda-developers.com/showthread.php?t=790022), where you can find several files. you need the android-info.txt and the hboot_xxx.img files.
open the hboot.img file with a text editor; in the first line you can find many strange symbols, and after that there will be a string of numbers (that is the hboot version).
you have to know what version of hboot have you currently on your phone (if you used the revolutionary tool, it will be probably 6.13.1002) and simply change the hboot.img string so that the release number is higher (than the modded hboot; i.e. you can write 7.09.0000).
after that you have to make a zip file with the android-info.txt and the hboot_xxx.img file you have just modified, and if you have an incredible s, call it "pg32img.zip".
if you have another device, simply you can turn on your phone in the bootloader mode, and if there's a memory card the device will look for a file, which name appears (it's the code you need).
then put that pg32img.zip file on the root of your sd card, reboot in bootloader mode (volume down+power) and follow the instructions to do the upgrade. after that, if you restart in bootloader, you'll see that the hboot version will be 7.09.0000 (the same you wrote) and will be s-on.
now, search and download the latest version of "superoneclick" (an application that should root and unroot your phone), and start it. link your phone to the pc and start the unroot process.
when it is done, simply leave your phone linked to the pc and start the RUU.exe file you downloaded. start the update process and if you have done everything good, at the end you'll have your phone with the stock hboot and the s-on.
i'm not a serious programmer, i simply was really lucky (i really didn't know if that could have worked) but i did it. i don't know how did you do the root, and how does the superoneclick work, so i am not responsible for any bricked phone.
if you are not sure, simply send your device to the htc assistance (better pay than have a new paperweight).
good luck
download superoneclick select unroot and uninstall the superuser app.Oh and download and flash your phone's stock rom
ok, thank you for the help!
there's a little problem: at the end of the superone process it says me "superuser not found", so it can't be deleted.
so i remade the root (using superone) and unrooted; then installed the RUU, but nothing: it's still s-off. what can i do now?
i tried to make superoneclick work, but with no success... although i have installed the superuser.apk, the program still says me there's no SU, and can't unroot my device.
Any suggestions?
ok guys, i did it...
first i remade the root process, and flashed the superuser.apk. then i wanted to "upgrade" the hboot, from 6.13.1002 (revolutionary) to 7.13.0000 (simply i changed the 1 to 7 opening the hboot signed image with a text editor). then i launched superoneclick, and started the unroot process. at the end, i launched the signed htc RUU with gingerbread, and now i have my htc incredible s with s-on and hboot 1.13.0000.
=)
the last thing: does someone know hot to put the original htc bootloader?
cant someone build a uniform high performance rom
i added a guide to do the process go to the first post and read it all
thanks for the guide, just one confusion here, that after putting the pd****.img into the sdcard, i need to goto bootloader right? (not recovery)
Edit: worked in first attempt . Just one suggestion if you can replace word "Recovery" with "Bootloader" inorder to avoid confusion for other users
thank you fshami! i just corrected the guide
Hi I just tried following the guide posted on the first post using the android-info.txt and the hboot_xxx.img files received by the OTA update released recently as well as one downloaded from the net "OTA_Vivo_Gingerbread_S_hTC_Asia_India_2.12.720.5-1.36.720.1_release_190041sn70bk4icw74exvv"
On both occasions the bootloader update failed.
I am unable to install the OTA update. This has been downloaded quite a few times already and the phone just hangs with the android logo screen.
P.S. My phone is an Incredible S purchased legally in India around June 2011.
Thanks.
then put that pg32img.zip file on the root of your sd card, reboot in bootloader mode (volume down+power) and follow the instructions to do the upgrade. after that, if you restart in bootloader, you'll see that the hboot version will be 7.09.0000 (the same you wrote) and will be s-on.
Sorry my friend , but this don´t work....
Sorry.....
I thought this is what I was searchinf for years but...What if I have an USB issue? Like usb brick? So I cant connect my htc with the pc x.x for superoneclick
Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$
I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]
I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.
Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000
HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.
I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?
@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.
got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one
im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?
Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA
just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems
Getting this while trying to re-unlock evo 3d ics. hboot 1.58.
It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )
i got same problem w my Z3 plus hbot will work on my z3 plus????????
FIRST OF ALL:
These steps are NOT official/universal, these steps worked for me, and I followed several steps form several threads. READ them (bottom of this post) entirely to be sure you can do it without problems, and to be sure how to do it (use of fastboot, adb, etc...)
Also, here is only explained for Europe, search the proper files for other parts of the world.
Story:
I wanted to revert to stock my phone, so I followed this thread instructions:
http://forum.xda-developers.com/showthread.php?t=1460713
I downloaded the RUU_Saga_Europe_1.28..., I followed the thread that used "Android Flash" system. Opened it, selected engHBootOverARX.img, select "actually in fastboot" and Android Flash did its work, flashed the hboot.
Then I started RUU. In the middle of the process it gave me the "Wrong Bootloader Error" and closed. Now my phone is S-ON, HBoot 0.98.0000, I can only load fastboot.
I posted a question here hoping somebody help me.
Solution:
Ok guys, if you are in this situation, dont panic as I did, surely the way I solved this could help you.
If you tried the above, and now you are stuck on bootloader like this:
HBOOT 0.98.0000 (or .0002)
S-ON
fastboot.exe getvar version-main gives 12.10.401.5 (or so)
and RUU wont let you actualize your phone.
I did the following:
1) First of all I needed to upgrade the hboot. Since I had no adb nor recovery, I had to do it via fastboot. In order to do that I needed an hboot that comes algon a higher version than 12.xx..., otherwise it wouldnt let me flash it... In thread [1] there is a .zip OTA in post number 41 (thanks to chargetw) with an IP dir. Download it, and get the firmware.zip from inside. Now I had to flash that firmware from fastboot, in thread [1] jneapan explain how to flash it:
example:
fastboot.exe erase cache
fastboot.exe oem rebootRUU
fastboot.exe flash zip path\to\firmware.zip
2) Ok, I noticed the 2.00.0000 (or .0002) hboot version in fastboot. From here, I could go thru the HTCDev.com solution to unlock the bootloader. Easy steps flashing an auto-generated email-sended Unlock_code.bin, you will understand it when you get thru it.
3) Nice, I had an unlocked bootloader, I could flash a custom recovery. Choose one (I used [2], but you can use the one that you prefer). And flashed it with fastboot:
example:
fastboot.exe flash recovery path\to\custom\recovery.img
4) Once I had the custom recovery, it gave me several errors when trying to mount /cache. At first my heart stopped for a while, but then I read thread [3]. I followed that thread and noticed that the "dmesg | grep mmc0" command gave me no error, so I followed step 2 form that thread to restore my cache partition.
5) Then, I could flash safely any custom ROM. I chose a prerooted stock one. Search [4] for one of your like, flash whatever you want.
6) Aafter all that things, I wanted to get my phone reverted to stock, so I needed to use a RUU. Unfortunately, all RUUs gave me a bootloader version errors because my main-version was then 13.xx... In order to do that I followed the misc_version steps form [5]. Since my ROM was already rooted, I only followed step 2 from that thread's first post, then the step 5 to relock the bootloader, and finally the step 6.
After all this, the RUU finally finished installing, and now I have a complete stock ROM.
Thanks in first place to foX2delta for his fast response. Couldnt make it without him
Thanks to all the listed threads participants. Without reading their wiseness surely I would be with a stoneage phone.
Last of all thanks to the entire xda community, for letting this forums being the best of the world
Final words:
I have learned a thing: NEVER, EVER, follow the steps of ANY GUIDE (included THIS) without reading EVERYTHING very carefully. One bad thing and BOM!, you are screwed.
Threads list:
[1] http://forum.xda-developers.com/showthread.php?t=1412398
[2] http://forum.xda-developers.com/showthread.php?t=1484753
[3] http://forum.xda-developers.com/showthread.php?t=1284196
[4] http://forum.xda-developers.com/showthread.php?t=1146601
[5] http://forum.xda-developers.com/showthread.php?t=1318919
Can't seem to find the thread right now...... The thread goes...
What you need to do is flash a custom ota firmware.zip which has a main version higher than 12, it will then give you the 2. hboot which you can unlock , install a ROM,then change your main version etc.
Will find the thread in the morning.
Ok, I think that the thread you were looking for is this: http://forum.xda-developers.com/showthread.php?t=1412398
I read it all several times. I flashed the firmware.zip as you said, thanks to the chargetw post nº41, and now I have HBOOT 2.00.0002. So I went thru HTCDev.com and the unlocking process concluded successfully. Now what? I still cant boot to use adb and misc_version, and fastboot.exe getvar version-main is 13.10.401.8.
@Rostwildch
To to be sure, you hboot now says UNLOCKED right?
Now you have two routes...
They all start with flashing a custom recovery have a look here at section 1 Step 2 to install a recovery via fastboot. If you want 4ext you will have to find the image on this site somewhere.
Next will have to install a custom ROM.
Now you have a working phone and can now change your misc version and can downgrade (then s-off) to a older RUU or you can carry on using you Unlocked phone.
Phewww that was close :S
At last I could flash a custom recovery via fastboot (my fear of a bricked phone clouded my view so I didnt realize I had an unlocked bootloader... what a noob), then flashed a custom ROM, so now I have it functional.
I want it fully stock, so I think I should now use misc_version to use an old RUU, isnt it?
Thanks foX2delta, wouldnt fixed it without your help I'm going to edit first post to make a pseudoguide to help ppl in my situation.
Rostwildch said:
Phewww that was close :S
At last I could flash a custom recovery via fastboot (my fear of a bricked phone clouded my view so I didnt realize I had an unlocked bootloader... what a noob), then flashed a custom ROM, so now I have it functional.
I want it fully stock, so I think I should now use misc_version to use an old RUU, isnt it?
Thanks foX2delta, wouldnt fixed it without your help I'm going to edit first post to make a pseudoguide to help ppl in my situation.
Click to expand...
Click to collapse
Spot on, since you rooted already all you need to do is change the misc version, then install the RUU. Glad it all worked out. You also may need to lock your bootloader to install the RUU
foX2delta said:
Spot on, since you rooted already all you need to do is change the misc version, then install the RUU. Glad it all worked out. You also may need to lock your bootloader to install the RUU
Click to expand...
Click to collapse
Yep. Thanks foX2delta .
I have detailed all my process in first post so everybody can read it. Hope it helps someone. Let me know if I misspelled a word, or you dont agree with something.
I dont want this thread to get down. Seriously, and with more reasons now ICS is officialy being developed by HTC, a lot of people is going to do what I did. I just dont want them to make the same mistakes.
BUMP!!!
Thank you!
I followed your guide, and managed to recover my phone!
With me, the firmware.zip (extracted from OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210uj1q93xrps74xzje) didn't flash via fastboot, so I copied it to my micro sd and renamed it to PG88IMG.zip.
Now with my (officially) unlocked bootloader, I have now flashed [4 FEB 2012]HTC_Europe_2.10.401.9_Prerooted_Deodexed and will try to sell this phone to go back to WP7. (withdrawal symptoms )
Many, many thanks, Rostwildch!!!
[edit]
I decided to do step six, and have now managed to relock the bootloader + flash the original T-Mobile UK RUU.
Once again, thanks!
Rostwildch said:
I dont want this thread to get down. Seriously, and with more reasons now ICS is officialy being developed by HTC, a lot of people is going to do what I did. I just dont want them to make the same mistakes.
BUMP!!!
Click to expand...
Click to collapse
With the official ICS on its way, all you'd really need is to use any of the available Sense 3.0 RUUs to return to Stock.
Or wait 24 hours. I'd dare day that's the maximum lag time before an official/unofficial version becomes freely available for download on any number of Desire S forums clouding the web.
Perhaps another 24 hours for a fully rooted version to appear.
Hi guy´s I really got a huge problem.
I have the same situation like others in this thread, but I have an o2 branded device. So i could not flash recovery.zip because it´s the completely wrong version.
Any ideas I´m now stuck on HBOOT-0.98.0002 and s-on.
Please help me.
Thanks a lot
@coolbook1
M u s t m m m m a k e g o l d c a r d.... (said in a slow dying voice).
So yeah that's about it, you need to make a goldcard, if you have another android phone make it on that, or if you have a memory card reader you can use that on your PC.
Things you will need and to do
-A memory card (preferable a spare one), and also preferable smaller that 2GB
-A Phone/card reader
-Backup all the info on the memory card, we will be formatting it!
Creating a Goldcard on a working phone
Step 1) Get memory card CID and goldcard image
-Insert the memory card you wish to make into a goldcard into the phone.
-Go to Settings/SD and Phone storage on the phone and select 'unmount SD card'. Once the card is unmounted select 'Erase SD card'.
-Download and install 'Goldcard Helper' from the market.
-The app will run and give two CID's which are all ready reversed, write down the mmc2 number.
-Go to psas.revskills.de website here and enter your mmc2 CID and download the goldcard image (goldcard.img).
Step 2) Create the Goldcard
-Download 'HxD-Hex-Editor' from here and install it on your PC.
-Connect the phone to the PC in 'disk mode' i.e. view your SD card on the PC (Removable Disk).
-Open the Hex Editor (Run as Administrator if Vista/Windows 7)
-Select the 'Extra' tab and then 'Open Disk'. Under Physical Disk select your Removable Disk (your SD cad) and ensure 'Open as Read Only' is not selected and then select OK.
-Now goto the 'Extra' tab again and select 'Open Disk Image' and select the 'goldcard.img' file you downloaded early (Step 1). Press OK when prompted for Sector Size 512.
-You will now have two tabs open, one the SD card and the other the goldcard image, now to merge the two
-Go to the the goldcard.img tab and select 'Edit' then 'Select All' then 'Edit' and 'Copy'.
-Now go the you SD card tab and highlight offset 00000000 to 000000170 , and then 'Edit' and 'Paste'
-Lastly goto 'File' and select 'Save'
Allll Done......
You can also have a look here for a more modern/complex method
Or here (has a video).
Section 2 - Creating a Goldcard on the PC (Card reader)
Check here, kashoulis post 11 and you can also check here
foX2delta said:
@coolbook1
M u s t m m m m a k e g o l d c a r d.... (said in a slow dying voice).
Allll Done......
Click to expand...
Click to collapse
Excellent guide.
Couldn't have put it better myself.
I finally killed my Desire S after hours of restoring it. At the end I made the OTA Update and it freezes in Recovery Mode.
I pulled out the battery and now it´s death. I couldn´t even get any life sign.
So RIP Desires S.
Thanks fox2delta for your help...
Rostwildch: BIG THANKS for great description step-by-step. I believe no only me, but lots of users with the same issue, have problems to gather and apply informations from many topics.
One note for branded phones:
- before any action prepare golcard (with GoldCaldHelper.exe and standard card reader, method with Hex editing didn't work for me - card was not visible),
- do step 1 with goldcard inserted,
- after this - unmount it and keep safe for future use,
- like for step 6, when installing non-branded RUU.
It's a shame that it's easier to root the phone than it is to return it to stock..
HTC Desire S~Tapatalk
Think there's a easier way because RUU erase the recovery so re-flashing it might work as it didi to me:
http://forum.xda-developers.com/showthread.php?t=1488672
I have the exact same problem of this post, my main doubt is I think I can resolve anything with a GoldCard, but all the methods send me to http://psas.revskills.de/?q=goldcard, which is not working anymore, is there anyway to solve it?
neonoafs said:
I have the exact same problem of this post, my main doubt is I think I can resolve anything with a GoldCard, but all the methods send me to http://psas.revskills.de/?q=goldcard, which is not working anymore, is there anyway to solve it?
Click to expand...
Click to collapse
just checked and it still working
if you have problem with this link, you can post your CID here so other may help you to get goldcard.img
firstly, Im not asking for a detailed explanation of what to do here.. I can read up on various sections, but I do need steps to follow. This phone is the most complicated thing to flash, give me ODIN and a galaxy S any day.
Im trying to upgrade to the latet open Europe.HTC-SAGA 401_9 not a custom rom, my DS is the same Radio Version so thats ok.
After following the various guides, What I have so far is:
1) the Stock HTC 401_9 Rom from File Factory.
2) Ive downloaded Goldcard Helper, fitted my 2GB SD and gotten the reverse ID
3) Ive d/l'd the GoldCard Image for my DS reverse ID
4) Ive d/l'd the HexD editor for making the goldcard.
5) I know about having FastBoot OFF, USB debugging ON and the phone USB set to Disk Mode for making the Goldcard and the USB to "Charge only" when flashing.
So, now what. Can I just flash the HTC Stock 401, or do I root it first. My Hboot is 2.000.002 and its S-ON.
The phone has Virgin UK Software, but its not Locked.. Ive had both O2 and Orange sim cards in and they work fine.
I just need to know the 1, 2, 3 .. steps for flashing this stock rom
Thanks in advance
Always helps to write your full bootloader screen.
ben_pyett said:
Always helps to write your full bootloader screen.
Click to expand...
Click to collapse
Im all for protecting your product against time wasting "bricked" returns, but Whoever at HTC thought of this system wants slapped... hard, Bootloader says:
### Locked ###
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822. 10. 08. 04_M
eMMC-boot
Aug 22 2011, 15:22:11
HBOOT
Then it lists on screen:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Hope that helps and hope you can give some steps. Seriously, Ive looked on here for days but there seems to be so many questions about different aspects and parts of the flashing, its confusing.
Thanks in advance
First of all, forget all about radios you know from Samsung.
At htc you can use every radio on every rom, there are only 3 possibilities you need to change radio:
It is shipped with a ruu you want to use
You face issues with radio related hardware
You want to be up to date
Ok, now to your question.
At HTC the bootloader version is important (only at stock roms).
If your bootloader has the same or a smaller version than the one from the ruu and your device had no branding, just reboot to bootloader plug it to your pc, enable fastboot usb and start the ruu.
If a branding is present and you want to stay with it, do the same with the fitting ruu.
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Tectas said:
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Click to expand...
Click to collapse
Ok I used this guide for the goldcard:
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
So, because Im not changing anything about the kernel, just debranding to an offical ROM, once I set up my Goldcard, I activate debugging, copy the RUU 401_9 to SD Root of my Goldcard, click "Image CRC" from bootloader menu and it should install it.
Is that correct?.
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
NightOrchid said:
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
Click to expand...
Click to collapse
Image crc just checks your rom, got nothing to do with updating.
The ruu itself is a exe, means a windows program , do the steps i described before with fastboot, the only difference is that you need to create the goldcard before, otherwise the bootloader won't allow (if your lucky) you to flash the ruu with the different branding.
If it fails that way run the ruu without attached device as far as you can go without closing, don't close it and search for the rom.zip at your temp folder, copy it to another folder and close the ruu, rename it, copy it to the root of your sd and reboot to bootloader and let it flash it directly, just to say it, you also need a goldcard before you do it this way.
One additional thing, be sure you got a ruu for the desire s, i just say it, because your goldcard guide is for the desire, what is no real problem there, but a wrong ruu will always fail and if it won't lead to a brick at worst case.
Sorry Tectas.. Just wont work.. I created my goldcard, extracted the RUU, changed the rom name from "disk1" to PG88IMG as you said, copied to root of goldcard, selected Fastboot then bootloader, but it just doesnt detect any image or file.
I am struggling a little with your english because you are telling me too many different ideas, Im confused... instead of telling me.. just 1, then do 2, then do.. 3, but Thank you for trying, i appreciate your help..
I will try again later..
Small thing the file you copy to the sd card must be called (case sensitive) PG88IMG.zip
Swyped form ym Dersie S unsig XAD Permuim
First method:
1. Create goldcard
2. plug in your device
3. Reboot to bootloader and enable fastboot
4. Start the ruu at your desktop and follow the instructions
5. Enjoy
If it fails make sure the drivers are installed, by downloading and installing htc sync, but uninstall it straight after you installed it, the drivers will still be present but the program itself can cause problems with ruus and/or adb.
If it still fails, try the second method.
Second method:
1. Create goldcard
2. Start the ruu without attached device
3. Go on till the only remaining possibility is to close the program, but don't close it
4. hit the windows button + r, a window should pop up
5. Type %TEMP% into the textbox of this window and hit enter, the explorer should open up and show your temporary folder
6. Search for the rom.zip (make sure hidden files are down if you can't find it)
7. Copy it to another folder i.e. the desktop
8. Close the ruu
9. Rename the rom.zip to PG88IMG.zip (case sensitive)
10. Copy it to the root of your sd
11. Reboot to bootloader
12. Choose bootloader
13. Confirm the update with vol +
14. Let it update
15. Reboot by hitting power
16. remove the PG88IMG.zip, otherwise it will update your device every time you access the bootloader
17. Enjoy
Thank you very much tectas for taking the time to sort and explain this. The 2nd methord worked just fine. However, at the end of the update flash, bootloader said:
"image on device is newer, update aborted"..
It does say that my virgin software is 2.13.351... the image is 2.10.401, so, in computer world, the numbers 2.13 is newer than 2.10. This may not be the case of the ROM itself, becasue the date is 22 Aug 11, but theyve engineered it that way probably so you cant flash it Open Europe.
The great thing is, youve taught me about the desire s and how the flash updater works, plus I have a 2GB goldcard out of it for future custom roms.. so all is not lost.. thanks for the lesson, its much appreciated.. Im gonna have a go at routing next.
It would be great to sticky this or copy it as a very Basic guide to flashing an HTC Rom.
Many Thanks again Tectas
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
I have now found that my phone is actually Locked to Virgin Mobile (has a Virgin media splash screen on boot up). Sorry for the confusion about that:
I followed the advice of Tectas and followed this:
http://forum.xda-developers.com/showthread.php?t=1399331
everything went great until I got to the end of the procedure and I only go the
"$" which after typing line 5: adb shell /data/local/tmp/misc_version -s
said "access denied" then mentioned "blue flames".
On page 6 or 7 of that thread, someone mentions this "blue flames" as being a new security mod that HTC have implemented to stop modding at all.
Is this true?.
Also, Virgin mobile and other places have quoted me £15 to unlock my DS. £15 seems alot of money, but would an unlock help (would it be worth it) for me being able to flash both Stock and custom ROMS.
I do enjoy the challenges of modding, so to me this is frustrating.
cheers
The $ indicates you have no root access, i must confess i never heard about the blue flame before, but also have to say, i never got deep into the downgrade stuff, because i used xtc clip to unlock my device, which made my device s-off and debranded.
If those Sellers use the same method, your good to go and spend the money, it saves you from a few traps you can run into with other methods (i paid €20 about a year ago), but you need to be aware that this is a hardware unlock which is irreversible, what can bring problems at warranty purpose (but must not).
Your second choice would be to use htcdev at first step and get root and so on afterwards, the downside here is also warranty, because your device is stated as unlocked at the htc database and if you leave it this way and won't use it to gain full s-off you also need to flash the kernel for each new ROM yourself with fastboot, because the recovery got no write permissions there.
If the seller would also use htcdev, safe the money, you can do it yourself, at xtc i can recommend it, but it's your choice.
Thanks for the advice Tectas. The guy in the street said it would take about 1 hour.. not sure if that helps to know. I suppose with Virgin, theyll be removing their own locks, so the virgin way might be better.
Also, the phone was bought from a 2nd hand shop, it was an unwanted upgrade someone just traded in without using it, the box it came in and the outer shell of the phone has no branding whatsoever.. thats why i was confused about it being locked.
Anyway, Ill have a think about who to go with and ill ask which methord they use before I hand it over.
Thanks again.
Tectas said:
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
Click to expand...
Click to collapse
Its Done.. phew.. hehe. After I got back to Virgin 1.31, just used the goldcard with rom.zip and it worked fine. 1 thing though, doing it this way flashes the rom in 7 stages, so what ever you do, when it reboots after the 1st install, do not think its repeating itself.. leave it. i Nearly did that, anyway, I sorted things using this thread:
http://forum.xda-developers.com/showthread.php?t=1443636
As long as you follow it to the letter, it all goes fine, the whole thread is really good support as well, so if anyones interested, read through the whole 13 pages (so far).
Also had access to the phones Recovery menu, so wiped Cach partition and did a factory reset, also probably not necessary, but backed up my SD card and formated it under the new OS.. I find this is always good on a new rom, for the file table and prevents app errors.
Happy i now know how to flash a rom, didnt quite root it yet, just flashed a stock RUU first.. which is what you should do if, like me, your new to this.
Anyway, Open Eu 2.10.401.9 is sweet and slick smooth.
Have a good one all, Thanks Tectas.