[Q] 32A - fastboot "not allow" error, hboot won't work - myTouch 3G, Magic General

I have an old T-Mobile myTouch 3G Fender with the 3.5mm jack (32A, according to bootloader). I have a renewed interest in getting it up and running again. I don't intend to use it as a phone as I have an S3 as my daily driver.
Nevertheless, I'd still want to play around with different ROMS on this device and see how far I can take things. Unfortunately, it seems like I've already taken it to its limit. I have 106 tabs open in Chrome and have already stayed up far too late in the night these past couple of days trying to make things work.
Initially, the phone was working (albeit very poorly). I decided to hunt for a reliable, stable, no-frills ROM. I found one that needed RA-sapphire-v1.7.0. Before updating the recovery, I thought it would be a great idea to wipe the phone. Following this guide, I nearly downloaded the appropriate recovery. Instead of downloading the G version, I downloaded the H version. So now I have a ROM-less device with a recovery that won't boot and does nothing more than display the HTC Magic splash image. At least I have access to my bootloader!
But both fastboot and hboot seem to be completely useless. I am consistently getting the "not allow" error message whenever I try to use the flash or boot commands through my computer. I've tried using hboot by creating sappimg.zip files with the correct recovery.img and placing them on a 4GB Kingston Goldcard (which I set up using my S3. I've read that Kingstons tend to work more often than not), but it doesn't do anything. I've tried throwing in a Engineering SPL (named hboot.img) into the sappimg.zip file. Nothing. It reads the sappimg.zip file and loads it, but right after it says 'Checking file...', it just stops. No errors, nothing. The system isn't crashing, per se: the screen just clears and displays the hboot menu as if you had just booted into it, as if you never told it to do anything.
Here's some info about the device:
Code:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27
I think it would be possible to fix this if fastboot was working properly. But I can't use fastboot because I don't have a Eng SPL. And I can't seem to find out how to install it using hboot.
Any way out of this mess?

You can try to restore to stock by copying a sappimg.zip file (a type of operating system image) to the root of the sdcard, then start in bootloader mode and it should recognize the file and let you update the phone's rom to stock.
This is the sappimg for sapphire pvt 32a build 2.10.531.4
HTML:
http://www.4shared.com/zip/CgyRRX4O/stock-sappimg.html]stock-sappimg.zip
Just rename it to sappimg.zip and copy to the root of the sdcard

pmerced said:
You can try to restore to stock by copying a sappimg.zip file (a type of operating system image) to the root of the sdcard, then start in bootloader mode and it should recognize the file and let you update the phone's rom to stock.
This is the sappimg for sapphire pvt 32a build 2.10.531.4
Just rename it to sappimg.zip and copy to the root of the sdcard
Click to expand...
Click to collapse
This one seems to at least go past the "checking.." stage. But it says that it's an older version. Is there a way to trick it into thinking it is a newer version?
Secondly, what is it about this particular .zip file that it works? Can I just replace the hboot.img found within this file with a unperfected version?

Well, here's a new discovery I've made. I can unzip the sappimg.zip files no problem; however, once I've made the changes I've deemed necessary and after I've re-archived them, the bootloader will not go further than the "checking.." stage.
I've tried it with the stock image file above. I initially tried using the bare, unmodified file. It did get past the "checking" stage but it gave me an error message stating the main version is older. I then tried unzipping the file and immediately re-archiving after making no modifications. Theoretically, it should be the exact same file that produces the same results. But it doesn't: same problem as above. It won't proceed past the "checking."
Both Mac (via the "zip" command at the command line) and Windows (via WinRAR) have been attempted. I must be missing some sort of advanced archiving setting.
Any ideas?

Sorry to hear it didn't work my suggestion. I think that the older version rejection is the problem to solve to bring back the operation of the phone.
I read somewhere that there is a way to extract the files contained in the sappimg from a RUU update file, but the latest version I found is the same of the file I suggested. Maybe if you can find a later one then you could make a sappimg.zip from there. Make sure the files are intended for the specifications in the HBOOT screen: specially 32A and matching radio with hboot, otherwise you may brick the phone.
The problem with modifying and repacking is that the file has to be signed with HTC keys and those are almost impossible to find out unless you have a high rank job in HTC.

Related

MAGIC - 32A - S-ON (Signature Verification ON) & Memory Card not accepted now

I am getting similar problems as this user
http://forum.xda-developers.com/showthread.php?t=664124
But in my case i am having my radio and spl is correct.
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
Radio: 3.22.20.17
Click to expand...
Click to collapse
I have access to fastboot and recovery so far
I have tried many firmwares in this radio as well as 6.xx radio new one. Had no problems so far. I was running a ROM on this radio itself. Then i wished to switch back to cyanogen latest. So i wiped and tried flashing the following
1/ flashed first - defaged firmware
2/ updated cyanogen 15.1 over it
3/ flashed the port of 32A
After this on booting, phone was stuck @ htc boot screen. So i again came back to recovery, and tried flashing again. This time it said a signature fail on defaged firmware file as well as other files in it.
Tried few times and still same issue.
Tried formatting sd card mounting on phone - recovery usb. but then after that it is no more detecting. I tried partitioning fat32, ext2-512mb, swap 32mb, manually through paragon and put again, still memory card not detecting. I get similar errors
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
Click to expand...
Click to collapse
Just to know if it is a recovery issue, tried updating recovery in fastboot mode.
I get a similar error as below
INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
This is when i noticed, the S-ON on top, my phone signature verification was off, that is before all this my fastboot said
SAPPHIRE PVT 32A ENG S-OFF H
Click to expand...
Click to collapse
I dont know how it went from S-OFF to S-ON. And that is the reason why fastboot was not accepting anything
Then to update recovery i did adb push to /sdcard and then flashed from there. And then i got my recovery updated to 1.6.2. This confirms somewhere phone is able to write to memory card through adb, but i cannot use recovery to flash from it. memory card has no prob neither phone hardware
Still no use, memory card is not detected + cannot flash files.
My current scenario
-- my radio and spl is correct, i have recovery lates 1.6.2
-- phone has no rom now
-- i can access fastboot and recovery
-- my signatures - S-ON so cannot use fastboot to flash anything
-- memory card not detecting, tried 1-2 memory cards. All detecting on pc
didnt you forgot to flash samming.img? BEcause without that, it wont turn off. Try flash again, use a gold card if doesnt work. Download from here:
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
hope it helps
I did not forget to flash that, it was not something i wanted. My phone was a completely rooted phone with everything running perfect. I was just reinstalling cyanogen from start.
Regarding goldcard, I couldnot find my sdcard CID, so could not create it.
create a new one. Create gold card from the recovery option. You can coonect your SD card to your computer with the phone in recovery mode, there is a MS Connect menu, select that one. you can get the CID and do the process again.
If i were you i would run HTC update from a SPL edition wich would be able to root and do all over again for safe keeping.
how to create gold card from recovery ? my memory card is anyway not mounting on recovery now
regarding getting cid, on memory card reader i couldnot get cid, maybe my card reader is not worth providing such info
thirdly, i have tried updating using original ruu, it fails in the stage of update where it says rebooting into bootloader.
I tried the same in fastboot mode, normal mode and recovery. Nothing works, except 1 change that in fastboot mode, it turns the phone to stuck at the fastboot screen and i have to pull out battery.
Any other options ?
before starting the phone, you press Power+Home, and you'll have the custom recovery option right?
There is a option called: "USB MS-Toggle" activate it , From that option you can get a CID without any problem and recover everything
have you tried a G1 method?
http://www.krishnendu.com/my-g1-android/rooting-my-google-g1-htc-dream-t-mobile-uk-edition_137.html
jgcaap said:
before starting the phone, you press Power+Home, and you'll have the custom recovery option right?
There is a option called: "USB MS-Toggle" activate it , From that option you can get a CID without any problem and recover everything
Click to expand...
Click to collapse
I dont know whether its my english that u r nt following or you dint read my post carefully. i had mentioned in my posts that it is not mounting my memory card. In recovery when i do that i get an error
Can't mount /dev/block/mmcblk0
.......................
oh sorry . My english sometimes tricks me. the issue you are passing, there is sure a way out. Could you describe the exacly process you used for installing CM please?
jgcaap said:
oh sorry . My english sometimes tricks me. the issue you are passing, there is sure a way out. Could you describe the exacly process you used for installing CM please?
Click to expand...
Click to collapse
Just as we do any flashing. put to sd card and flashed through recovery in this order(PLZ READ MY FIRST POST COMPLETELY)
1. defaged firmware
2. cyanogen latest update over it (without rebooting)
3. 32A port
what did you had before as radio ? Hboot? Etc
Have you tried to download a oficially signed from HTC Hboot and in fastboot flashing it ?
try the following to see if works.
1)Link your Phone to your computer, run it in fastboot mode.
2)Run a HTC update (choose anyone)
3)Click next until the update confirmation part.
4) run %temp% and you'll find Rom.zip and rom1.zip , copy to a folder and unzipit. Close the update app.
5) collect the following files:
userdata.img
system*.img
Splashe*.nb0
recovery.img
radio.img
hboot*.nb0
boot.img
(The ons with * are the version of the following update you are applying)
6) Zip to a samppimg.zip, put on the SD card and enter in HBoot mode (Volume down+power)
PS: i dont know if works, and it might become worst but try at your own risk. Never passed throught that situation. Last optiion read: http://forum.xda-developers.com/showthread.php?t=655097 and follow the JTAG Hack option. I Dont know any other way.
please post here exacly what you have done:
http://forum.xda-developers.com/showthread.php?p=6243163#post6243163
Lets hope to try to see what we can do.

Cant root/update my HTC Magic .- S

Hi all, (first time posting)
I am trying to root my HTC Magic but so far nothing has succeded.
What I want:
I want +1.6 firmware and to be able to use 2.x OS with the newest apps in Android Marked. So far there is alot of apps not present when using firmware 1.5.
What I have tried:
I have created a "Goldcard" successfully but when Iam trying to update with the 2.53.707.2_-_sappimg (renamed to SappIMG.zip) it says "Main version is older" - update failed.
In Recovery Mode it wont continue, it just stock with the !(picture), i cant seem to get any menu up to flash and choose any recovery files.
Ive tried to downgrade:
from RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver
to RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver
I have used the all the guides I could fine to create Goldcards, recovery images. Using fastboot commands to flash from windows etc etc. Everytime I use fastboot write commands I keept saying fastboot failed, remote: not allow
Some of the guides I have used:
http_://_android-hilfe.de/root-hacking-modding-htc-magic/28434-how-wie-man-das-32a-magic-flashen-kann.html
http_://_forum.xda-developers.com/showthread.php?t=688262
http_://_wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32A_Firmware_to_CyanogenMod
Any help is much appreciated
Phone details:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009 15:56:29
Modelnummer: HTC Magic
Firmware version: 1.5
Basebandversion: 63.18.55.06JU_6.35.08.29
Kernesystem: 2.6.27-5b476e83
Versionnummer: 3.05.401.1 CL#95168 test-keys
Mod. edit: not dev related, moved to general
gl though
Hi guy,
If you are running RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_ NoDriver, you can do some step to root your phone.
You can continue step 4 in this guide: http://rootyourmagic32a.blogspot.com/2010/04/root-htc-magic.html
Zurog said:
Hi all, (first time posting)
What I have tried:
I have created a "Goldcard" successfully but when Iam trying to update with the 2.53.707.2_-_sappimg (renamed to SappIMG.zip) it says "Main version is older" - update failed.
Click to expand...
Click to collapse
I think, if it says "Main version is older", that you have not successfully created your goldcard. This happened to me when I rooted. I made two mistakes, which I can share.
1) Some SD cards cannot be edited to make goldcards. I had a sandisk, that I thought was making a goldcard, but it was not. However, when I used the same procedure on a kingston 2 gig, it worked perfectly.
2) The SD card that will become your goldcard must be in the phone when you type the "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" command. Otherwise, you will not make the correct goldcard.
I hope my mistakes can help you.
-bb
I also have this error.
* Phone details is exactly the same.
* GoldCard seems to be fine (is there a way to check it?) I bought a brand new 2GB Kingston.
* Fastboot gives the error failed, remote: not allow
* flash_image recovery recovery.img gives the error error opening recovery.img, no such file or directory
* When I reboot with adb shell reboot recovery I get to FASTBOOT USB in red and HTC Magic in white on a black screen. I guess this means I haven't gotten the recovery image installed.
* If I run ROM Manager from ClockworkMod I no longer get the Can only be run as root, but I get an error running privileged commands ?
* If I try Flashrec I can download the recovery image, but nothing else will happen. It will not backup anything or run anything I put in there.
* It doesn't matter if I enter anything in cmd in windows 7 or if I run it in an emulator window in the cell phone itself.
So where I stop is I seem to not get the recovery image started.
Any help? I'm all out of ideas!
If your getting Main Version is older, then your goldcard is hosed. The purpose of the goldcard is to bypass the version check. Format your goldcard to FAT32 and do not do a quick format (if you do it from Windows) and start over. This guide worked like a charm for me.

Can't install RA recovery onto rogers magic - please help

I am using this website, and am at step 6. Everything up to this point has been going well, but i cannot get the recovery image to copy over. BTW I have the recovery-RA-sapphire-v1.7.0H.img file i'm using. When I type to push the file to the SDcard, it says, the transfer failed because the file system is read only.
How do I fix this? I've restarted the phone, taken the SD card in and out, i've typed adb remount, and nothing is working.
. Open command prompt and go to the Tools folder in Android SDK that you downloaded to create the gold card.
Assuming that you have not changed the file name of the recovery, use the following commands:
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img (file name of the recovery you downloaded)
OK, i've got that working, now another problem...
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img (file name of the recovery you downloaded)
7. After the recovery has been flashed, go to the following link to download the ENG SPL for HTC MAGIC 32A (SPL: 1.76.2007)
http://www.4shared.com/file/21114537...07-signed.html
8. Now copy the SPL to your memory card.
adb push update-hboot-1762007-signed.zip /sdcard/
9. Restart your phone using the home + power key till it boots up into the recovery mode.
(or just type 'adb shell reboot recovery')
10. Using the 'Flash zip file' option from the recovery, select the SPL file from the memory card and flash the HBOOT on your phone
Now i've done most of that, but when I restart into recovery mode, it keeps on randomly rebooting even though I don't want it to. I clicked on 'flash zip file' and it just rebooted right away.
Now when I flashed the recovery, the command prompt said that it did it, BUT nothing happened on my phone, it was just sitting there and didn't say it was doing anything. Could this be a problem?
OK i kept trying, and finally i got it to go into 'flash zip file', I clicked on the correct zip file, but right after clicking the screen went black and it restarted.
Does this sound like it worked? How do I check to confirm if it worked and it's rooted?
Ok I did this, and it said ADB is already running in root in the cmd, so i think i'm good!!!
Thanks!
The easiest way to test if the device is rooted is to open another command prompt in the tools dir and type
adb root
If it returns that adab is already running in root, then you're all set.
So as i said, i installed the sapphire recovery, but now i'm reading on the wiki page that you need the HERO recovery file. I need to change the radio, but then it is saying i needed the HERO recovery.
This is so damn confusing why can't anyone get this all straight and not have so many different and totally contradicting methods.
http://wiki.cyanogenmod.com/index.p...agic32A_Firmware_to_CyanogenMod#6.35.x_Radios
The wiki here says to use the HERO recovery, but this thread only gives the sapphire recovery for the HTC magic.
http://forum.xda-developers.com/showthread.php?t=530492
Now to clarify i checked and i think i have successfully rooted, but the specs are this.
Sapphire PVT 32A ship s-on H
Hboot-1.76.0008
CPLD-12
RADIO-6.35.08.29
I'm told i need to change the radio now before I can install the cyanogen rom, is this true?
I can't find out what to do because no one seems to talk about the 1.76.0008 spl...
Any help?
OK so more playing and more following guides, I installed the HERO recovery tool (1.6.2), and updated the radio to 6.35.10.18, changed my SPL to 1.76.2007, and have my PVT 32A ENG S-OFF H setup.
I'm confused though, because I did all of this work so I can install the lastest cyanogen rom, but it says it can't use this version of the radio... what the hell?
Someone REALLY needs to fix these tutorials to be self consistant.
http://forum.xda-developers.com/showthread.php?t=605239
follow this, got it all done, then go here to get the cyanogen mod...
http://forum.xda-developers.com/showthread.php?t=673394.
What do I do now?? Do I downgrade my radio or just use a different rom?
thesmoth said:
OK so more playing and more following guides, I installed the HERO recovery tool (1.6.2), and updated the radio to 6.35.10.18, changed my SPL to 1.76.2007, and have my PVT 32A ENG S-OFF H setup.
I'm confused though, because I did all of this work so I can install the lastest cyanogen rom, but it says it can't use this version of the radio... what the hell?
Someone REALLY needs to fix these tutorials to be self consistant.
http://forum.xda-developers.com/showthread.php?t=605239
follow this, got it all done, then go here to get the cyanogen mod...
http://forum.xda-developers.com/showthread.php?t=673394.
What do I do now?? Do I downgrade my radio or just use a different rom?
Click to expand...
Click to collapse
Here is a link to a test kernel port file for CM 5.0.8 from Brian Crook. This should allow you to run CM using your current Radio. Like I say it's a test port and I haven't tried it but Brian is the one that does all the ports to the Rogers 3.x radios.
http://briancrook.ca/android/testing/
you'll need to download the file bc-5.0.8-6355-ebi1-signed.zip
You would use recovery to flash CM 5.0.8 then flash this kernel port file. After that don't forget to flash the gapps package that should be linked in one of the URL's that you already posted or you can get it here http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
PLEASE NOTE
Do not change your radio from it's current 6.x version without flashing the matching SPL for the new radio. If you fail to flash the SPL/Radio combination correctly you WILL brick your phone.

Can't flash HERCIMG.zip

Im using the fastboot method to flash the original sprint RUU in zip format.
I used:
-fastboot oem rebootRUU
-fastboot flash zip HERCIMG.zip (or HERCIMG, HERCIMG.ZIP, hercimg.zip etc etc)
But i keep getting "Error: cannot load "HERCIMG.zip" or whatever i type.
Stuff i tried:
*Unlocked bootloader to s-off - still wont let me flash and zip files from the bootloader. I'm 100% ive done this before several months ago, and i even used the same HERCIMG file that i left in the /sdcard main directory.
*Delete the old HERCIMG and download a new one from the dev section of the hero forums.
*Manually placed in root of sdcard by mounting the sdcard on my computer.
*Used adb to push the HERCIMG file to the root directory of sdcard
Anyone can tell me whats going on?
Also right now i have CM7, bootloader 1.47 unlocked.
Maybe i have a bad version of fastboot.exe? I copied it from /tools/ folder of android sdk and placed it in /platform-tools/ since it needed adbwinapi.dll which is located in that folder along with adb.exe
Thanks for any help
Ok guys. I have no idea whats up, but eventually i was able to fix by loading the unlocked bootloader and running the RUU.exe from windows. Still wasnt able to flash the HERCIMG.
I had a huge issue with HERCIMG not working for me. I noticed that I had HERCIMG.zip and changed it to HERCIMG.ZIP - make sure it is all caps on your sdcard, how it gets there does not matter, I copied it in windows. Next, you must boot into bootloader - there are many commands, but it has to be a white screen on your phone and text will scroll...at some point, it will ask you what you want to do with the file...This is all done on the phone. You must have s-off too. If you are not using the ENG hboot, I dont think fastboot will work, btw (and the eng hboot is 1.46)
Yup. Flash darchs eng-spl and you should be good to go. Oh and you have to take into account your radio/baseband ver. If its .29 then you have to flash it a certain way or downgrade your radio then flash it then hercimg your current radio again.
Locked & Loaded
Cool thanks for the help. Where can I get the eng-spl so i can flash from bootloader directly?
Well the last time I checked you have to flash it from recovery. If you search the hero dev section for it I'm sure you wil find it. Also I'd highly recommend Flashing it with Ra1.6/1.7 or Cwm2.5 and remember to check your baseband/radio version. If you can't find it let me know and I'll post it after church. But you should read as much as you can about the mod to get a better understanding of the risks and benfits of the mod.
Locked & Loaded
Don't forget that your SDcard has to be formatted to Fat32 so the bootloader can find it.
When I use/have used any HERCIMG.zip, I have never done it through fastboot, I have always done it by using the H-Boot screen. The HERCIMG.zip cannot say "HERCIMG.zip.zip (so don't name the zip file with a .zip in the name- check the details of the file to make sure).
If you are in the bootloader, press the volume button down to get into H-boot from the Fastboot or restart the phone (press volume and start button at the same time).
If you used Regaws to become S-off, then I know the H-boot method will work fine. As far as using fastboot commands, you would need to flash Darch's Eng Spl mod that changes the bootloader to 1.46.2. There is a thread by jasonmaloney that has to do with flashing an RUU from fastboot without being S-Off. This needs to be done from Windows, that's why jason includes fastboot.exe along with the RUU. Is the RUU you are using all images, or are there other files as well (binary types)?
Good Luck

[HOW TO]return to stock (gingerbread) from revolutionary or normal hboot(11/2/11)

READ THIS:
i have removed the dead multiupload links that have for some reason been causing an extreme amount of confusion. i thot the "mirror" following each link was self explanitory,but apparently not.
from this point forward,i will no longer respond to "links are dead" posts or PMs if i check them and find them to be working.
in other words,yes,the links are working.
___________________________________________________________________
the return to stock thread from 5/17 is outdated. it still works,but afterward youll need to allow your phone to OTA to mr2 if you want to be on the current firmware.
between the newer firmware,and having to execute extra steps if rotoed with revolutionary,the old thread seems to be causing some confusuion. i thot maybe it would help if i threw it up here as well
its geared toward a revolutionary rooter who doesnt have adb set up,so sorry if its a little insulting to more advanced users
last and not least,if you rooted old skool,and just need to flash mr2 files,just skip the part detailing getting the old 1.04.2000 eng hboot back. go directly to: Putting current stock firmware and s-on back onto the phone
as soon as the GB OTA hits for realeek i will update this with those files.
*please read all directions first. post up any questions you have before doing anythingyou are messing with your bootloader,wich is a vital part of your phones operation. screwing it up WILL make your phone an expensive paperweight.
how to unroot
the revolutionary method of rooting uses a sneeky hboot exploit,and replaces your stock 1.04.0000 or 1.05.0000 bootloader with a modified permanent hboot. it not only gives you all the same fashboot flash abilities as the original engineering bootloader,but it very effectively blocks other hboots for overwriting it. its good,as you will remain s-off if you accidentally flash a full RUU,or accept an OTA,but makes it a little trickier to remove.
for the time being, removal requires ADB to be set up and running and some commands entered in "fastboot" to to allow the permanent hboot to be overwritten. once an "s-on" tool is release,ill take th is part of this guide down.
if you rooted the old skool manual way and have adb setup and working,you can use this guide to remove the permanent hboot.
with Revolutionary,will come a new wave of rooters that have no clue what adb,or fastboot even are. for you folks, Sele and the crew in the "rescue sguad" at HTC Thunderbolt Forum have come up with a really clever way to get the adb basics,and the eng bootloader to flash,with minimal setup and confusion. with their permission,im borrowing it for our guide here.
*WARNING* no siginture or file checks will be done flashing the new bootloader in hboot or fastboot.fastboot will literally flash "lets golf" as a bootloader if you tell it to. DO NOT mess with your hboot unless absolutely neccessary to return to stock for warranty purposes. if youre just tired of being rooted,flash the gingerbread ruu to get back to unrooted firmware and factory recovery. leaving the revolutionary s-off bootloader in place is the safest,and best option,and will not affect your ability to recieve OTAs.
*AGAIN- if youre just following this procedure because youre tired of being rooted,skip this next section and leave the permanent hboot in place. jump to "Putting current stock firmware and s-on back onto the phone" and flash only the first "PG05IMG_no_hboot_2.11.605.9" file(you can flash the 2nd file too if you want,but the permanent hboot will block it )
Setting up adb and removing the permanent hboot if youve never used adb before
1)if you no longer have the htc drivers that you installed when rooting with revolutionary,download them again from here on revolutionarys website.
2)next download *link removed (mirror)to somewhere convenient that youll be able to find it,like your desktop,or a "downloads" folder. it contains the old eng 1.40.2000 s-off hboot,and the bare minumum tools to install it.
3)the following directions were using windows 7 and chrome browser. other OS may be slightly different-the end result is you want unzipped,inside tbolt folder to be on the root of your C: drive.
-find the tbolt.zipdownload
-click on tbolt.zip download and open it.
-inside tbolt.zip,there is a folder labled tbolt. drag it to the root of C:. inside tbolt is the unpermanent hboot and some adb tools.
4) charge your Thunderbolt to 100%
5)click on then "start" bubble in the lower left corner of your screen. type "command" in the search window and hit enter. this will open a small black command window.
6)enter the following command(by typing or copy/paste):
Code:
cd c:\tbolt
you should see your promt in the window change to: c:\tbolt>
7)enter the follwing command:
Code:
md5sums hbooteng.nb0
check the output on the command window. THIS IS VERY IMPORTANT. the command must equal exactly 6991368ee2deaf182048a3ed9d3c0fcb if it does not,STOP!. delete the tbolt.zip download,and the unzipped tbolt folder from C:,re download and try it again. again,do not procede if the output in your command number does not equal it exactly.
8)once the number matches,you can continue. copy and paste the following codes into the command window:
Code:
adb devices
the output should be your phones serial number
now enter:
Code:
adb reboot bootloader
this will cause your phone to boot into FASTBOOT mode,wich is a white screen with colored letters.
now enter:
Code:
fastboot devices
the result again,should be your phones serial number.
9) now youre ready to enter the command to unlock the permanent hboot and flash the new,non permanent one.
to unlock,enter:
Code:
fastboot oem mw 8d08ac54 1 31302E30
write the new hboot:
Code:
fastboot flash hboot hbooteng.nb0
if you select bootloader at this point from the fastboot menu, youll still see the permanent s-off hboot,so select reboot with the volume rocker and power button and let the phone reboot. after it boots,you can adb reboot bootloader again,or power off, then power on/vol down and check that your pink "UNLOCKED" or "REVOLUTIONARY" is gone and you have the old 1.49.2000 bootloader.
here is what you should see in the command window,the red are my inputs:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\tbolt[/COLOR]
c:\tbolt>[COLOR="red"]md5sums hbooteng.nb0[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\tbolt\]
hbooteng.nb0 6991368ee2deaf182048a3ed9d3c0fcb
c:\tbolt>[COLOR="red"][COLOR="red"]adb devices[/COLOR][/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT126S005970 device
c:\tbolt>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\tbolt>[COLOR="red"]fastboot devices[/COLOR]
HT126S005970 fastboot
c:\tbolt>[COLOR="red"]fastboot oem mw 8d08ac54 1 31302E30[/COLOR]
...
OKAY [ 0.006s]
finished. total time: 0.006s
c:\tbolt>[COLOR="red"]fastboot flash hboot hbooteng.nb0[/COLOR]
sending 'hboot' (1024 KB)...
OKAY [ 0.183s]
writing 'hboot'...
OKAY [ 0.219s]
finished. total time: 0.403s
c:\tbolt>
Putting current stock firmware and s-on back onto the phone
after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
1) PG05IMG_no_hboot_2.11.605.19.zip
mirror: https://rapidshare.com/files/271867813/PG05IMG_no_hboot_2.11.605.19.zip
md5: 334909756073760b3d7316e51a4ce837
2) *link removedPG05IMG_hboot_ONLY_2.11.605.19.zip
mirror:http://www.mediafire.com/?0z0rlzh9lrnh0qs
md5: d26b3253358407d459c654e6729a39ca
rename PG05IMG_no_hboot_2.11.605.19.zip to "PG05IMG",move to your sd card,and flash in hboot.
this is important! you must flash the PG05IMG_no_hboot_2.11.605.19.zip first
after successfully flashing that,you will be on unrooted gingerbread with an eng s-off bootloader. delete the PG05IMG file from your sd card. now place the PG05IMG_hboot_ONLY_2.11.605.19.zip on your sd card. check the md5. once youve verified it matches,you can rename PG05IMG and flash it.
again, only flash the hboot file after you have successfully flashed the rom.
now you are 100% stock on latest firmware. unrooted gingerbread 2.11.605.19 with *locked* 1.05.0000 s-on bootloader.
as always,be as cautious as possible doing hboot flashes,and follow directions in the http://androidforums.com/thunderbolt-all-things-root/353591-how-some-root-terminology.html to flash these files if youre unfamiliar with hboot flashing.
*please start a new thread before attempting this if any part of this confuses you. without a bootloader your phone is a paperweight,so we want to help you prior to making any mistakes
last and not least: if you have non working hard buttons,or no screen,see the directions in this thread on AF
Nice
Awesome Found that there is also another way you can use the same method from the original root instructions.
adb push yourhbootfilenamehere /data/local/
adb shell
dd if=/data/local/yourhbootfilenamehere of=/dev/block/mmcblk0p18
Then just put the stock image on your sd card and use
adb reboot bootloader
and flash your stock firmware
Hope this helps anyone looking for a slightly quicker way
Not sure if this is a problem but...
After I un-rooted last night and ran the 2.11.605.5 RUU, I now get a bright pink message at the bootloader saying *** LOCKED ***. Anyways, the device now states S-ON and I am running stock. Is the LOCKED message something to be concerned about?
no the locked message is just something new they put into it some people think it means they might put it in the list of officially unlockable devices soon check it out here htcdev.com/bootloader
ellis90009 said:
Awesome Found that there is also another way you can use the same method from the original root instructions.
adb push yourhbootfilenamehere /data/local/
adb shell
dd if=/data/local/yourhbootfilenamehere of=/dev/block/mmcblk0p18
Then just put the stock image on your sd card and use
adb reboot bootloader
and flash your stock firmware
Hope this helps anyone looking for a slightly quicker way
Click to expand...
Click to collapse
while i dont know that youll save any time doing it this way, this is certainly anotehr way to skin the cat if you have adb set up,and are fairly savy at using it,as there are alot of small details youre leaving out.
also i need to add a couple of things:
1)you will need to reboot your phone between
Code:
dd if=/data/local/yourhbootfilenamehere of=/dev/block/mmcblk0p18
and
Code:
adb reboot bootloader
as,rebooting imediately to bootloader will take you back to the revolutionary one. the new hboot is written on reboot.
2)be extremely careful with this. if you choose to flash a stock hboot rather than the engineering one,you risk a security warning if you flash the wrong hboot overtop of the wrong custom firmware. youll then be stuck with an s-on hboot and only be able to run newer RUUs to try and fix it.
if you really want to use this method,the safest way would be to run the RUU first. youll have to get a temp root shell(zergRush prolly will work),then run the command to replace the hboot that matches the firmware that you flashed.
CaptainStrange said:
Is the LOCKED message something to be concerned about?
Click to expand...
Click to collapse
as was said,this is just the new hboot. it does contain htcdev unlocksupport. thos that doesnt neccessarily mean they will ever give us a key not that it matters anyway,htcs "official unlock"only unlocks system,boot,and recovery,and is still an s-on hboot. better than nothing i guess,but since we have revolutionary and other root methods,theres no advantage to using the official unlock fomr htc.
updated OP for unroot to GB 2.11.605.5
This should be stickied. Thanks Scotty
Thanks for this. I am going to be upgrading my TB to a Droid RAZR and wanted to revert to complete stock, S-ON, unrooted for selling it on eBay. This worked perfectly.
just to be cleared to just go back to unrooted stock to receive future ota's is just follow this: will this take my s-off off..also can I reroot with revolutionary later..
the reason i want to go back to stock is the ota update notifications are getting annoying and persistent..
Putting current stock firmware and s-on back onto the phone
after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
1)PG05IMG_2.11.605.5_no_hboot.zip
md5: b7ebb0b208f704c84f1224de16e61a8e
2)PG05IMG_2.11.605.5_hboot_ONLY
md5: e6df3ae14523508868dc811ecc5d4b07
rename PG05IMG_2.11.605.5_no_hboot.zip to "PG05IMG",move to your sd card,and flash in hboot.
this is important! you must flash the PG05IMG_2.11.605.5_no_hboot.zip first
after successfully flashing that,you will be on unrooted gingerbread with an eng s-off bootloader. delete the PG05IMG file from your sd card. now place the PG05IMG_2.11.605.5_hboot_ONLY on your sd card. check the md5. once youve verified it matches,you can rename PG05IMG and flash it.
again, only flash the hboot file after you have successfully flashed the rom.
now you are 100% stock on latest firmware. unrooted gingerbread 2.11.605.5 with *locked* 1.05.000 s-on bootloader.
as always,be as cautious as possible doing hboot flashes. again,please post any questions before doing anything
Did you root with revolutionary? If you currently have the 1.04.2000 Eng hboot,then yes. That will get you to stock unrooted gb. If you plan to re-root,there are stock,rooted roms you can flash in recovery,that will also stop the ota notices.
Sent from my ADR6400L using XDA Premium App
Thanks so much. Appreciate
Sent from my Nexus S using xda premium
So is there anyway to accomplish this without being able to turn the phone on? Dropped my T-Bolt over the weekend, phone looks fine but the power button is now recessed. Tried popping it back out, etc. and no dice.
Tried setting up ADB, but it isn't recognizing my device. Not sure if USB Debugging was on before, but now I have no way of checking. Tried a few tricks I read online to get the phone to power on without the power button, but none have worked.
Thoughts?
id prolly not worry about it. if it wont power on,they wont know its rooted. i believe any hardware thats not working is fixed,then the phone is flashed with current firmware.
i do not believe they will fix the phone,then turn it on to try and catch you being rooted.
either way,since you dropped it,youre looking at an insurance claim anyway. and they could care less if its rooted or not
after doing that, can I roll back it to be S-OFF/ROOT?
edited to reflect the fact that I'm an idiot who just essily fixed the problem
Problems...
So i rooted with the Original root method I do believe and have had this phone for awhile, I followed the steps as stated but after I flash the H Boot and reboot to do the first PG05IMG I get No image, wrong image, so on and so forth... I have no idea what has happened, I even grabbed another Img file from Bliynd but it still does the same...
Never had a phone do this before, its like it see's the IMG but will not load/flash it... Any help would be awesome man, sry for the trouble...
Helpful info (?)
Mecha XD ENG S-OFF
Hboot-1.04.2000 (PG0510000)
MICROP-/
Radio-1.39.00.0627r
eMMC-boot
Feb 23 2011, 20:36:02
See attachment for pic of happenings lol So much easier
There is one more line of no Image or what not after whats on the pic, I guess I took it a lil to fast...
be careful! do not just blindly flash different images or RUUs. you need to use the files i listed,and make sure you flash them in the correct order.
if the PG05IMG is on the root of the sd card there are only 2 reasons its not found:
1)sd card not FAT32
2)incorrectly named
the phone must see "PG05IMG.zip" exactly. due to the way windows usually adds and hides file extension,its common to inadvertantely name to "PG05IMG.zip.zip" or in lesser cases just "PG05IMG". note that that is a zero,not a capital O
figure out which of those 2 is your prollem and your files will flash.
a1exus said:
after doing that, can I roll back it to be S-OFF/ROOT?
Click to expand...
Click to collapse
after doing what?
I know this is beyond dumb but since rooting with recovery anything I flashed was from cwr. How do I flash pg05img.zip from hboot? Will the phone then boot up allowing me to delete the file from file manager app or do I have to delete the first pg05img.zip from the computer?
Ok, so I originally rooted my phone using the ADB method. I used your stock RUU to unroot with S-off still off. My question is what is the easiest way to get root back with s-off already off and the original root bootloader?

Categories

Resources