Related
So i was in the middle of following the steps in the s-off and perma root thread and i ran into a problem. Hope someone here is nice enough to help me out.
So i ran revolutionary and everything went smooth. I already had the clockwork mod zip in the root of my sd card so i just rebooted the phone into hboot. When i went into hboot it detected the pg58img file and ran it, it prompted me if i wanted to update and so i did. It rebooted the phone and then i went back into hboot. The hboot said it was 1.23 and said Locked instead of Revolutionary as it displayed previously.
When i try to run the pg58 file in hboot an error occurs and said it is not compatible and only asks me to power off. So now at this moment it displays 1.23 version of hboot and s-off and says locked.
What can i do after this point? Any help i can get would be fantastic, thanks.
You're still good.
You're locked out of some of the most advanced fastboot commands. But that's it.
You still have S-Off. ADB will still work. You can flash ROM's. Etc etc etc....
It's a known problem. But it's not really a problem.
It's not like you divided by zero and destroyed the fabric of the universe or anything.
This is a noob question but how would i install clockwork recovery? I thought i would try dl from market but it said i didnt have root permission(obviously)
Is there a thread that has a solution to my issue or maybe you can quickly guide me out of this? lol Just kind of confused as to what i should do next lol.
Look in the development section for a thread called guide to s-off.
Skip the s-off part since you've done that.
Go right to the part about installing recovery. Following the directions. It's incredibly easy. It'll take about 3 minutes.
Once you have clcokwork recovery you can flash custom ROMs. You don't actually have to root the stock ROM. (Though you should make a backup of it just for kicks. You can do it all through clockwork recovery)
Yea I tried it multiple times already. I have the pg58 file in the root of the sd and when i go to the hboot it says
"Model ID incorrect!
Update Fail!
Press <POWER> to reboot."
Thats the only option it gives me so i am not able to install clockwork recovery.
Do you have SuperCID?
no i do not, would that fix the issue? i thought that is just for installing any rom on the device. My issue is that i cant get recovery to work.
I would think that is the next step after i run the perma root zip.
jonslaught said:
no i do not, would that fix the issue? i thought that is just for installing any rom on the device. My issue is that i cant get recovery to work.
I would think that is the next step after i run the perma root zip.
Click to expand...
Click to collapse
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Cool, thanks. I will definately try this as soon as I get off work later today and post up a status regarding the issue
Sent from my HTC Sensation 4G using xda premium
aNYthing24 said:
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Click to expand...
Click to collapse
He doesn't have use of Fastboot commands. I am pretty sure they are needed for super CID. Let me check.
He can't super CID as Fastboot commands are used.
Have you tried to run the correct RUU.exe? I think that would change back your h boot. There are zips in the development section you can use to downgrade but you may need super CID to use them.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Rhiannon224 said:
He doesn't have use of Fastboot commands. I am pretty sure they are needed for super CID. Let me check.
He can't super CID as Fastboot commands are used.
Click to expand...
Click to collapse
Yes, he does. CID commands will work with 1.23.xxxx. I've done it myself. Advanced fastboot commands won't work (he can't flash a radio through fastboot).
aNYthing24 said:
Yes, he does. CID commands will work with 1.23.xxxx. I've done it myself. Advanced fastboot commands won't work (he can't flash a radio through fastboot).
Click to expand...
Click to collapse
So basic Fastboot commands work with h boot 1.23? Good to know, my bad.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Rhiannon224 said:
So basic Fastboot commands work with h boot 1.23? Good to know, my bad.
Click to expand...
Click to collapse
Yeah, I had SuperCID to flash the new firmware to use an ICS ROM, then changed it back to the T-Mobile one after. No worries, it's confusing.
aNYthing24 said:
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Click to expand...
Click to collapse
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
eagle_101 said:
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
Click to expand...
Click to collapse
Do you have the correct drivers installed?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
eagle_101 said:
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
Click to expand...
Click to collapse
What mode are you in when you are in adb?
Rhiannon224 said:
Do you have the correct drivers installed?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Click to expand...
Click to collapse
I have adb tools only.
im having the same problem, but i can access recovery and i flashed a ROM but my screen freezes during boot. when i go into bootloader is says locked, 1.23.0000 s-off i can access fastboot and recovery i just dont know what to do from here, i installed a ROM and it was successful but i cant get passed the beats audio screen during boot up.
eagle_101 said:
I have adb tools only.
Click to expand...
Click to collapse
Okay, I am not near a pc atm so I cannot look where they are located, if you have the adb tools you also need another program called Net Framework installed on your pc.
Make sure your phone is powered onvand usb debugging checked when plugged into pc. I find it easiest to hold the mouse over the adb tools folder, press alt & ctrl keys and right click on the mouse and choose open command window here. Now type the command "adb devices".
Good luck.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
shehade08 said:
im having the same problem, but i can access recovery and i flashed a ROM but my screen freezes during boot. when i go into bootloader is says locked, 1.23.0000 s-off i can access fastboot and recovery i just dont know what to do from here, i installed a ROM and it was successful but i cant get passed the beats audio screen during boot up.
Click to expand...
Click to collapse
First boot can take 10 minutes to load as the Davilk cache is being recreated. Also, did you perform a full wipe first and check the Md5 checksums, make sure your downloaded ROM is not corrupt.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Hi,
My phone freezes on the boot up screen (where T-mobile pops up) I know there are LOADS of threads on help for problems like that, but I think it's fair to say, I've tried quite a few of them (or at least looked to see if they could help me) but I'm still epically stuck I'll describe what i can in order, because I tried quite a few things..... -.-
I've got Htc desire S, from T-mobile UK
Hboot- 2.00.2002
I tried to root it to get pdroid, of course, found out that i needed to downgrade it to 0.98 for zergRush......got the "Hellions with BLUE flames" message so moved on to tacoroot. it was fine until i got permission denied at the last cmd code. (the posts on the thread suggested using zergRush if tacoroot did not work -.-)
this is the most problematic part i'm guessing. I gave up on those 2 and found this "guide-how-root-desire-s" on android forums, it uses revolutionary and cwm
But while i was trying out that, i found revolutionary-0.4pre4, which sounded alot easier therefore i alternated between both since the rev 0.4 made the guide a lot easier (took out half of part 1 and whole of part 2). I managed to finish, reboot.
At this point Hboot screen had ***locked*** on top and S-off, but it was still on 2.something
I realized I had a RUU left over from one of the previous guides....(RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed)
so thinking i had to use it (since i was still on hboot 2.00.something), I stuck my phone on fastboot USB and started RUU up. it ran smoothly and soon finished, I rebooted my phone to check if i was in 0.98, which i was,and happily booted up my phone. But i didn't notice S was ON. Next thing i know, I've frozen on the boot up screen, so i take the battery out, booted to Hboot.
Now i can't access recovery menu, factory reset, and i can't reboot since it freezes on "t-Mobile" screen.
Have i broken it for good? if not what can i do to fix it?
Sorry this was a bit wordy, i didn't know what was useful so i just put it all in (well as much as i can remember accurately)
-quick summary-
HTC desire S
T-mobile
Hboot: 2.00.2002 (now 0.98)
S-ON (now, managed to have it off at a point...)
zergRush > tacoroot > revolutionary + guide using cwm recovery > messing it all up cause i forgot to put rom in SD card + used RUU > mega stuck...
I'm completely new to this rooting and stuff, please help. Thanks
edit..
oh, i don't know if it'll help but on cmd (I've installed adb, fastboot correctly) adb commands do not work, and says something like "device not found" or "waiting for device". Fastboot DOES work when on fastboot USB only.
edit....
change hboot version listed here from 2.00.002 to 2.00.2002
carelessness
Have you tried changing your miscellaneous version then running the RUU again and then use revolutionary to gain S-OFF then flash any rom you want P.S >>>> FALLOUT is probably the best at the moment
Good luck.
Hi, Duty09
Thanks for the quick reply. how do i change my misc version?i can't "adb push" since my phone wont register with cmd.....adb devices show nothing. Do i stick it in root and flash from fastboot?
Thanks
Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100
Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA
Forcefire said:
Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100
Click to expand...
Click to collapse
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...
Eclipse_Droid said:
Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
I can't, because when i run revolutionary, it gives me "waiting for device". i've tried running it while in Fastboot USB, HBOOT USB PLUG, even during the frozen t-mobile screen..... is there another way of doing this?
iinock said:
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...
Click to expand...
Click to collapse
From what I recall, you just select "All Other Supported Models"
SimonTS said:
From what I recall, you just select "All Other Supported Models"
Click to expand...
Click to collapse
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??
iinock said:
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??
Click to expand...
Click to collapse
Did you type
/android/fastboot oem get_identifier_token
Click to expand...
Click to collapse
or
./fastboot oem get_identifier_token
Click to expand...
Click to collapse
SimonTS said:
Did you type
or
Click to expand...
Click to collapse
neither,
started up cmd, cd to file with adb, fastboot, and the other one. and typed in fastboot oem get_identifier_token
i've just tried both 2nd one gave me
'.' is not recognized as an internal or external command,
operable program or batch file.
the first one gave me
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.031s]
finished. total time: 0.031s
0.015s longer than fastboot oem get_identifier_token.......
Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Ignore that - just reread the thread. You did have v2.00.002, but you've changed it to v0.98 something?
Have a look here http://androidforums.com/desire-s-all-things-root/444571-unlock-using-htcdev-com.html
You need HBOOT v2.* upwards to use HTCDEV unlock method.
SimonTS said:
Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Click to expand...
Click to collapse
right now its 0.98.0000
it was 2.something, but after loads of attempts at tweaking, it changed. think it was the RUU i ran after revolutionary, guessing thats what messed it up as well. but that's just my blind guess...
problem is, i can't change it back, OR change it to anything
Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.
Forcefire said:
Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.
Click to expand...
Click to collapse
Thanks, will definitely try that when adb works again. but i can't do that yet since adb is not working with my phone, it wont show up on "adb devices" any commands given just get "waiting for device" as a reply
just found this thread that seemed to have a lot in common with my problem
http://forum.xda-developers.com/showthread.php?t=1412398
but i'm running in to problems with CID, tried to do it with gold card but still no luck (i think gold card is done properly...)
im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks
@iinock not sure if this will help but ive got a T-Mobile RUU if you need it or have you already tried this ?
and have you tried android flasher yet ?
iinock said:
im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks
Click to expand...
Click to collapse
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF
DuTY09 said:
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF
Click to expand...
Click to collapse
Thanks for the links.
I managed to fix my phone by using a different SD card as a gold card (used LG 1gb) then flashed OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210uj1q93xrps74xzje
now it works , got to try install rom and pdroid now
thanks for your help guys :good:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred
fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom
Hi there guys,
Not sure if any of y'all remember way-back-when, but at one point my AT&T One X went into (what seemed like) a bricked state. For 8 months, I didn't touch it, charge it, yada-yada-yada. About 2 weeks ago I decided to give it a go so I charged it for a half hour and the mo'fo' decided to work. I updated my ViperXL ROM to 4.2.0 because I enjoyed it for its features. Now I'm left to ask the question, do I have to update HBOOT to flash a JB 4.3 ROM? I'm still unsure because I feel like I remembered seeing somewhere that your HBOOT has to be a newer version to run 4.3.
Thanks and regards, worldindo1.
NOTE: My current HBOOT version is reading "1.14.002".
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
timmaaa said:
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa,
So just relock bootloader, RUU file, and then unlock it again? Do you know of anyone who has just the firmware upgrade files from the RUU so I can do it from my Linux laptop? Thanks a ton, now I know I wouldn't have any problems or possibly brick my device haha.
Regards, worldindo1.
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
timmaaa said:
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
Click to expand...
Click to collapse
Howdy,
I am S-Off thankfully haha. I used XFactor back when it was still current. But I thought the main purpose of an RUU was to execute:
Code:
fastboot oem rebootRUU
fastboot flash zip (firmware).zip
Back when I had done some work with the HTC One V, we used unruu (for Linux) or on the Windows side, explored the RUU's %temp% folder to get the firmware files. Could I still issue those commands safely or have they changed how the RUU works? As well, since I'm S-Off, do I just issue all of the usual commands (minus the "fastboot oem lock") or ? Just making sure to do all of my homework before I jump in haha.
Regards, worldindo1.
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
timmaaa said:
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
Click to expand...
Click to collapse
Sorry about that my mind just drew a blank. I mixed up xfactor with facepalm haha. Yeah I'm s-off and bootunlocked.
Sent from Marianas Trench.
Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French
As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.
Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.
Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?
Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822
Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?
Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.