Related
I am having an issue upgrading my radio 10.56 to 10.58. I run the flash radio.img command and I get this error...
< waiting for device >
sending 'radio' (22189 KB)...
OKAY [ 4.123s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 4.143s
rebooting...
finished. total time: 3.300s
I have been googling around and I am seeing that I need Eng S-Off for other models of HTC phones, but I do not know if mine is on or off because it does not show on the fastboot screen. I am running AR HD 4.1.2 and I am having issue with cell signal.
Can anyone help?
In hboot (bootloader mode) does it have the pink revolutionary in the top?
If you s-off with revolutionary, then flash an ruu, you keep s-off, but lose fastboot.
Try running revolutionary again (it will error out, but you will get revolutionary hboot flashed), then your fastboot commands should work again.
Sent from my HTC Sensation 4G using XDA App
WiKDMoNKY said:
I am having an issue upgrading my radio 10.56 to 10.58. I run the flash radio.img command and I get this error...
< waiting for device >
sending 'radio' (22189 KB)...
OKAY [ 4.123s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 4.143s
rebooting...
finished. total time: 3.300s
I have been googling around and I am seeing that I need Eng S-Off for other models of HTC phones, but I do not know if mine is on or off because it does not show on the fastboot screen. I am running AR HD 4.1.2 and I am having issue with cell signal.
Can anyone help?
Click to expand...
Click to collapse
Hi,
You only need S-OFF to flash a radio.
Have you got the latest HYC Sync.
This will install the latest drivers you might be missing.
That fixed it! Thanks a million!!!
geoffcorey said:
In hboot (bootloader mode) does it have the pink revolutionary in the top?
If you s-off with revolutionary, then flash an ruu, you keep s-off, but lose fastboot.
Try running revolutionary again (it will error out, but you will get revolutionary hboot flashed), then your fastboot commands should work again.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
What am I doing wrong?
Ok, I have just read this post and updated my HTC Sync (I now have version 3.0.5579) and I am still getting the "FAILED (remote: not allowed)" error.
I have just flashed Android Revolution 4.1.6 and I was trying to install Radio_10.58.9035.00U_10.15.9035.02_2 over my current 10.43a.9007.00U_10.51.9007.27_M3.
What am I doing wrong?
Cryo
Phone: HTC Sensation
Rom: Android Revolution HD™ 4.1.6
Recovery: 4 EXT
Kernel: 3.6.35.14-Sensation-faux123-0.2.3r+
I also had problems with it. I did the revolutionary procedure again, ensuring that the process completely finishes (make sure you kill any processes listening to USB ports, like AppleMobileDevices, etc.)
After installing revolutionary again I could flash the radio.img
Basically, the Revolutionary procedure doesn't work properly. It's meant to reboot the bootloader automatically 3 times to complete the process. For some reason, it's broken and after the first reboot you'll get a 'communication error'.
Your HBOOT will still show S-OFF but it won't be the Revolutionaty HBOOT which unlocks the fastboot commands needed to manually flash a new radio.
As said above, keep running Revolutionary until it tells you it's done and then you're good to go. The safer way to flash a radio is to download it from the radio thread as a PG58IMG.zip and flash it via HBOOT
Hi, i have the same problem with the Android Revolution HD™ 6.0.2 rom. There was manual install instructions, i used the adb to restart in bootloader, but when i type "fastboot flash radio radio.img" i get the same error remote not allowed. Unfortunately i cant install revolutionary again, because looks like my hboot is 1.23 which is not supported (in the site the hboot goes up to 1.18 i think). Any idea how to apply the radio? (Radio_11.65.3504.00U_11.19.3504.29_2.rar)?
edit: the easiest way for me was to download the latest 11.x radio from the radio thread (http://forum.xda-developers.com/showthread.php?t=1178143) then replace its radio.img file inside the PG58IMG.zip with my file that is supposed to be flashed directly via adb. Then i place this zip file inside the sd card, reboot in boot loader and all is done without any errors etc.
Im having trouble updating the radio to 11.68.3504.00U_11.21.3504.13_2, it says every time i flash "failed remote not allowed". Im using HBOOT 1.23 ARHD 6.0.3
kolokoy said:
Im having trouble updating the radio to 11.68.3504.00U_11.21.3504.13_2, it says every time i flash "failed remote not allowed". Im using HBOOT 1.23 ARHD 6.0.3
Click to expand...
Click to collapse
that hboot cant do advance fastboot commands at the moment only 2 hboots can
1.17.x.x.
and the newset 1.27.x.x
I'm stuck
I got my Sensation back from repairs with 1.18 and pressed on and rooted. I now run rooted stock 2.3 with S-On but unlocked using HTC method (Revolutionary didn't work for some reason) and ClockWorkMod with SuperCID
This is where the problems started
I can't get S-Off
I have tried everything I can find (literally been on this for hours). I've tried:
Revolutionary 0.4pre4 (which fails to gain root - possibly because I've already got root)
HTCSuperTool (v3 of which appears to be broken, btw)
Downloading various firmwares and flashing them (using the PG58img.zip/bootloader method)
I've even tried running the RUU exe and pulling the rom.zip, renaming that and dropping that in the SD card
Running the RUU (both the latest T-Mobile UK and the latest ICS version)
The weird thing is that it reads the PG58img.zip files, loads them, starts to parse them then goes back to bootloader and doesn't read them again unless I reboot the bootloader
Update: Re-locked the bootloader and still can't run the RUU for ICS
Any ideas?
Anyone? Please help!
I've just been through all this after getting my phone back from repair. Mine came back with t-mobile branded rom version 1.50.110.2 and wouldnt s-off with revolutionary. Luckily the phone still had supercid so i flashed RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe and revolutionary finally worked. You can read my thread here http://forum.xda-developers.com/showthread.php?t=1538324
Thank you, I'll try that (if I can ever get a slot on the FileFactory download server...)
I've got a 1.17 hboot.img from Kohr-Ar (used in one of the PG58IMG.zips), could I use fastboot flash hboot hboot.img to flash that or would i be left with a brick?
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
pnlrogue1 said:
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
Click to expand...
Click to collapse
did u find any solution , i am exactly in same situation i also did exactly same thing now stuck
Try to run ruu ???
Sent from my HTC Sensation 4G using xda premium
Afraid not. I tried all sorts of things - best I can say is do NOT try to flash your bootloader using the fastboot method - found that out the hard way...
I think flashing an alternative ROM may help but I'm not sure. Maybe contact the devs of Revolutionary - it just wants a way of skipping the Zerging Root stage in V0.5...
Find my post and do it step by step run ruu then change cid
Sent from my HTC Sensation 4G using xda premium
Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
jezash said:
Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
Click to expand...
Click to collapse
Hi,
I am not sure where exactly you want to end up.
But if you wanted to get an ICS ROM on your phone,try THIS THREAD
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
jezash said:
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
Click to expand...
Click to collapse
Hi,
Have you got the necessary drivers installed to use ADB.
Try using THIS TOOLKIT
It has the drivers,and an unlock section.
first of all confirm your CID
fastboot getvar cid command will give you cid
if its supercid (unlikely) or any other which has ICS ROM for it ..then you are lucky
other wise try the HTCdev method again...no need to get the unlock_code again
just use the one you got previously ...then reboot and see..hopefully it works
hi, thanks for various suggestions.
have tried the HTCDEV method a couple of times without success. I never see the Confirmation Screen shown in step 13 on the HTCDEV bootloader unlock procedure.
Definitely have the HTC drivers installed, have previously used adb successfully from this PC. Plugged in my old HD2 (running Android) and adb devices finds it ok.
Checked my CID as suggested, it's T-MOB005.
Tried downloading the toolkit suggested by malybru and didn't get any further - I think it just does the same thing (runs the HTCDEV unlock process).
One thing that's odd. I tried flashing 4EXT Recovery from command prompt. A "loading" bar showed up on the right side of the screen of the phone like it was working, but then I get the "signature verify fail" shown above.
I guess I can't use Revolutionary S-OFF as I can't boot to Android.
What can I do? Should I try this: http://forum.xda-developers.com/showthread.php?t=1469296 - Edit - actually it seems like that still needs the HTC DEV unlock to work ... which seems to be my problem :-(
have tried the HTCDEV unlock method quite a few times now. In the command prompt it appears to work successfully, but I never get the Android-like confirmation screen (I think this must be because my phone will not currently boot to Android).
As I think I need to unlock before I can flash anything else, I am stuck. :-(
Does anyone have a suggestion for another way to unlock it?
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
jezash said:
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
Click to expand...
Click to collapse
Can you pop in the irc? We can do some last tries before you send it for repairs
Sent from my pyramid.. Through blazing fast sonic waves
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
jezash said:
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
Click to expand...
Click to collapse
EDIT:based on these values ..seems like something can be done..remember ..this is all to avoid extra money to get it repaired
can you post some more details?
fastboot getvar all (except IMEI and SERIAL NO )
Hi Ganesh,
Thanks for your reply. Here are the details from my phone:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.22.3504.07_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.34.206.1
INFOserialno:
INFOimei:
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: T-MOB005
INFObattery-status: good
INFObattery-voltage: 4032mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.480s
Cheers
now that we know that the stock rom flashed .(before brick)
get the 1.50 RUU and try to RUN it
how you do that
phone in fastboot ...connect it to pc and run the RUU.exe
if it still dint worked
then extract the rom.zip form RUU
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder and flash it manually
manual flash steps
1.fastboot erase cache (if its failing ...ignore it)
2.fastboot oem rebootRUU (black screen with silver HTC)
3.fastboot flash zip rom.zip (pastebin the output if failed)
4.fastboot reboot-bootloader (check the bootloader there ..changed or not )
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
EDIT: ok, so trying to run the RUU, it looks like it's going ok, starts sending the ROM to the phone, and then aborts with a ERROR [155]: UNKNOWN ERROR.
Will try the manual steps you gave.
jezash said:
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
Click to expand...
Click to collapse
yes try that first if it fails (both ways )
get the updated RUU
I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2
Click to expand...
Click to collapse
from football ^
and use that and repeat the rom flash again
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
2nd EDIT:
my bootloader displays HBOOT-1.27.0000 ... isn't the problem still that even 1.50 has an older HBOOT than this, and hence the rom flash fails?
jezash said:
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
Click to expand...
Click to collapse
yeah thats expected ...can you try one more thing ..can you just remove the hboot.nb0 file from the rom.zip (have a copy of it somewhere safe ..so that you can add later when required)
EDIT: also you need to edit the android-info.txt file ..change the HBOOT inside with te one you have i.e. 1.27.0000 then make the zip again then try flashing it sorry my bad there wont be HBOOT in the android-info.txt ..just cidnum ,modelid etc etc
then do the flash of rom.zip again
weird. I couldn't find that file in the rom.
the contents are as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT - oh, duh, the longer file name that ends as you said. sorry. will try now.
ok, tried this. unzipped, removed the hboot_Pyramid_8x60_1.17.0011_20110602_signedbyaa.nb0 file, rezipped. followed the four manual flash steps that you suggested, and got the following message in cmd:
C:\adb>fastboot flash zip rom.zip
sending 'zip' (375099 KB)... OKAY [ 50.217s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 100.357s
Football can get me a TMO-UK RUU 1.50. There is a cost, apparently. Hence wondering if there's a reason why 1.50 should work when 1.34 doesn't, give - if i understand correctly - that neither is HBOOT 1.27.
Hey there,
just today I got my Phone back from HTC for repairing the Display.
On the delivery paper was a notice that the mainboard was replaced and the phone now has a different IMEI.
As I now tried to gain an unlocked bootloader by using the HTCDev Method, I get the same error everytime:
Code:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.164s
I am 100% sure, that I didn't make a mistake while unlocking.
Do you have any suggestions?
Niklas
As far as I know if htc has changed your motherboard, the unlocking method on htcdev website is not going to work. You need to follow Ganeshp's guide to achieve S-OFF. It is in GENERAL section.
Yes after you get your motherboard changed HTC DEV meathod will not work
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
above users are right
motherboard replaced
which means different imei
so htcdev method won't work for you anymore
EDIT: Problem solved
Ok, thanks, finally got S-OFF and root working
I also installed 4ext Recovery, but my last backup was made using TWRP-Touch-Recovery.
When I now try to flash TWRP using Goomanager it doesn*t work, now i tried flashing it via fastboot and i also get an error
Code:
C:\Users\***\Desktop\Sensation\toolkit\Data>fastboot flash recovery recovery.i
mg
sending 'recovery' (5472 KB)...
OKAY [ 1.402s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.721s
Can I either convert my backups to 4ext format, or is there another possibility to flash twrp?
niklas1407 said:
EDIT: Problem solved
Ok, thanks, finally got S-OFF and root working
I also installed 4ext Recovery, but my last backup was made using TWRP-Touch-Recovery.
When I now try to flash TWRP using Goomanager it doesn*t work, now i tried flashing it via fastboot and i also get an error
Code:
C:\Users\***\Desktop\Sensation\toolkit\Data>fastboot flash recovery recovery.i
mg
sending 'recovery' (5472 KB)...
OKAY [ 1.402s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.721s
Can I either convert my backups to 4ext format, or is there another possibility to flash twrp?
Click to expand...
Click to collapse
you have that error because probably you don't have a patched hboot version
that's why the fastboot command fails
actually post the bootloader details to confirm it
rzr86 said:
you have that error because probably you don't have a patched hboot version
that's why the fastboot command fails
actually post the bootloader details to confirm it
Click to expand...
Click to collapse
Code:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
What do I need to do to solve this issue?
niklas1407 said:
Code:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
What do I need to do to solve this issue?
Click to expand...
Click to collapse
i dont know why your trying to unlock with HTC DEV your already S-OFF :s Download the Hboot i attatched its from unlimited.io and put it on the root of your sdcard and reboot into bootloader accept the flash and then flash any recovery and your away
do as above user said
that is the patched hboot version
Hello,
I have a Desire S, I think it has been first S-OFF with Alpharev (hboot 6.98-1002), and then a RUU has been patched (14.01.401.2). From now, the phone isn't able to boot anymore, I only have access to fastboot/bootloader
I've tried to flash the official hboot using fastboot flash hboot hboot.img
but it has not been flashed :
sending 'hboot' (1024 KB)...
OKAY [ 0.207s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.239s
I've tried with ENG HBOOT, also tried by puting PG88IMG.zip on my SD card, fastboot detect it, tried to flash it but again, bypassed.
I'm a bit lost now, maybe someone could help me
petoulachi said:
Hello,
I have a Desire S, I think it has been first S-OFF with Alpharev (hboot 6.98-1002), and then a RUU has been patched (14.01.401.2). From now, the phone isn't able to boot anymore, I only have access to fastboot/bootloader
I've tried to flash the official hboot using fastboot flash hboot hboot.img
but it has not been flashed :
sending 'hboot' (1024 KB)...
OKAY [ 0.207s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.239s
I've tried with ENG HBOOT, also tried by puting PG88IMG.zip on my SD card, fastboot detect it, tried to flash it but again, bypassed.
I'm a bit lost now, maybe someone could help me
Click to expand...
Click to collapse
I think this post is in the wrong section, you should post it on the Q/A section
oups my bad !
Don't repost. I've 'reported' your thread asking for it to be moved.
The problem is that the hboot version (6.98.x) is higher than 2.02.0002. Either flash the official hboot with the dd if= of= method, or flash an eng hboot with a lower version (0.98.x or 2.00.2002) (also with the dd method, instructions can probably be found in the hboot threads) and flash the RUU again.
Edit: another option would be to flash hboot 7.00.1002 by the PG88IMG.zip method, and then flash the PG88IMG.zip version of the Ics RUU (search the dev section).
Problem is, using the dd if= of= method requiere adb, which is not possible in my case, I only have fastboot.
edit : i'm trying with 7.00.1002 by PG88IMG.zip
Ok so 7.00.1002 using PG88IMG had worked, but my phone does not boot.
I'm trying to reflash RUU, see if it solves the problem. Or maybe I'm not flashing the correct RUU ?
Reflashing RUU and the phone is booting again !
Is there any way to get back to stock S-ON hboot ?
petoulachi said:
Reflashing RUU and the phone is booting again !
Is there any way to get back to stock S-ON hboot ?
Click to expand...
Click to collapse
I think the only way would be the dd method (probably best flash a lower version number eng hboot, then flash the RUU again and it should overwrite everything).