Database Info

[Q] Trying to flash radio and getting Failed remote not allowed

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

[SOLVED] Cannot use fastboot to install CWM

Hi,
I have a Desire S with the following information
Code:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011,14:58:38
FASTBOOT USB
...
When I tried to install CWM, I got the following error:
Code:
C:\>fastboot flash recovery cwm-4.0.1.4-saga.img
sending 'recovery' (4346 KB)...
OKAY [ 0.735s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.757s
Please help. Thanks!
=========================
Solution: I successfully changed to ENG with the HBOOT downloaded from http://forum.xda-developers.com/show....php?t=1113820
After that, successfully flashed the recovery from revolutionary's page using
Code:
fastboot flash recovery <recovery_file_name.img>
(*) remember to remote the <> sign

If I recall correctly you need to upgrade to the ENG bootloader first
Swyped from my Desire S using xda Premium

ben_pyett said:
If I recall correctly you need to upgrade to the ENG bootloader first
Swyped from my Desire S using xda Premium
Click to expand...
Click to collapse
Could you please help tell how to do that?
Thanks a lot!

The same way You were doing the recovery install.... Search for the hboot 0.98.2000 the rename the img to hboot.img (for simplicity) and place it with your fastboot flies, then boot your phone into fastboot and run the command;
fastboot flash hboot hboot.img
I'm unsure if this will help you, I'm just explaining how to change your hboot, but it shouldn't do any harm.

As you are soff you should be able to simply update to the ENG 98.2 using the following method
1) Copy the ZIP file containing hboot ENG to PG88IMG.zip into root of SD card
2) reboot into Bootloader, and answer yes when prompted where the PG88IMG will be updated.
Swyped from my Desire S using XDA Premium

ben_pyett said:
As you are soff you should be able to simply update to the ENG 98.2 using the following method
1) Copy the ZIP file containing hboot ENG to PG88IMG.zip into root of SD card
2) reboot into Bootloader, and answer yes when prompted where the PG88IMG will be updated.
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
Hi,
Where can I download that hboot ENG?
===========================================
Thanks, I successfully changed to ENG with the HBOOT downloaded from http://forum.xda-developers.com/showthread.php?t=1113820
After that, successfully flashed the recovery from revolutionary's page.
But, when I enter RECOVERY from HBOOT, it is still same - blackout, then vibrate, then the white screen with HTC - forever
Anyone help

[Q] Cant flash radio anymore

I went from custom to stock rom and then back to custom rom again.
After this I cant flash radios anymore.. Still have my S-OFF and obviously CWM. Flashing the ROM went without any problems, but flashing a new radio.. No go..
Tried to use adb as well as P58IMG.zip files, no chance.. Any ideas?
fastboot flash radio radio.img
sending 'radio' (22205 KB)...
OKAY [ 3.497s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 3.815s

Since your S-OFF I would try running the official RUU for your country/carrier, and then flashing radio via fastboot

Ossi said:
I went from custom to stock rom and then back to custom rom again.
After this I cant flash radios anymore.. Still have my S-OFF and obviously CWM. Flashing the ROM went without any problems, but flashing a new radio.. No go..
Tried to use adb as well as P58IMG.zip files, no chance.. Any ideas?
fastboot flash radio radio.img
sending 'radio' (22205 KB)...
OKAY [ 3.497s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 3.815s
Click to expand...
Click to collapse
You are soff but the bootloader is still locked. That's the issue you are having
So you can just flashed the jb_hboot.zip
From this site
http://unlimited.io/hboot-downloads/
Get the pyramid ics one and flash it.. Using the instructions/commands given in the same site
Once flashed using those commands
Then come back to bootloader using
fastboot reboot-bootloader
Then you can flash the radio
Sent from my pyramid.. Through blazing fast sonic waves

ganeshp said:
You are soff but the bootloader is still locked. That's the issue you are having
So you can just flashed the jb_hboot.zip
From this site
http://unlimited.io/hboot-downloads/
Get the pyramid ics one and flash it.. Using the instructions/commands given in the same site
Once flashed using those commands
Then come back to bootloader using
fastboot reboot-bootloader
Then you can flash the radio
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Silly me, ofc, while reverting to stock I used an official RUU, just had to flash an unlocked RUU and voila.. Been a while since I did this, so this part slipped my mind

HTCDev Bootloader unlock not working

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

[Q] Trying to get back to stock

Some info
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot getvar version-main
version-main: 2.20.502.7
finished. total time: 0.026s
And I have HBOOT-1.14.0002
I show
TAMPERED
RELOCKED
I can not seem to flash back to stock using htc_one_x_RUU_2.20.502.7_att_us_08022012.exe, it fails.
So then I get the rom.zip file from htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and run...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.983s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.433s
Im guessing this is because I followed the instructions (to relock the bootloader) before I ran htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
What would you recommend as my next step?
Im following this guide http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone

I was able to unlock the bootloader... Now Im stuck here...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.981s]
writing 'boot'...
OKAY [ 1.548s]
finished. total time: 2.531s
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.016s

"Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working due to system.img file being to large."
The error that you are getting seems to be indicative of a known issue. I am sure someone who knows whats up will be along shortly. At least you can take comfort in knowing you are not the only person with this issue. That is when things get scary lol.

Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita

timmaaa said:
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON and I do not have SuperCID.

LanceM said:
I am S-ON and I do not have SuperCID.
Click to expand...
Click to collapse
fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.010s]
finished. total time: 0.010s
fastboot getvar cid
cid: HTC__621
finished. total time: 0.003s

When I try and flash
1.85 or 1.83
I get this error
<T111504><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>

You can't RUU backwards unless you're s-off.
Sent from my Evita

timmaaa said:
You can't RUU backwards unless you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ok Tim... So what do I do to get 2.20 on the phone, stock...

If you're wanting to run the at&t RUU you'll also need the at&t CID. Otherwise you need to run the RUU that corresponds with the HTC__621 CID. Why is it the 2.20 in particular that you want?
Sent from my Evita

Im not stuck on 2.20. I just want the phone back to stock.

Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita

timmaaa said:
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
Click to expand...
Click to collapse
Well, that is my question... What RUU is compatible with my CID? And can I change the CID to work for an AT&T RUU, because it seems like 621 is a tawian RUU. If I can, what do I need to change the CID too?

Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita

timmaaa said:
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
Click to expand...
Click to collapse
No, when I got the phone a while ago, I rooted and superCID'ed it. It was changed to 1111111, but now for some reason it has changed to 621, which I dont quite understand and has caused quite an issue for me trying to go back to stock.

The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita

timmaaa said:
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
Click to expand...
Click to collapse
I bought the phone in San Antonio at an AT&T store.... Way back when the phone just came out...
At that point, after XDA had root and SuperCID, I did those... And put CM10 on it... Through many upgrades and tinkering, somehow the phone got the CID 621. An Asian CID, I did NOT do this.
Regardless, it is fixed now. I followed the instructions in this thread to change the CID back to 1111111. It worked, then what I did was push the recovery and boot from 2.20 to the phone, then re-locked it.
At this point, I ran the 2.20 RUU and it took... Then I ran the 3.18 phone and now... QHSUSB_DLOAD
Off to http://forum.xda-developers.com/showthread.php?t=1966850
Now downloading linux...
I will fix this damn thing lol!

You pulled a classic megadoug. S on super Cid ruu strikes again. JTAG is the only way to fix it now
Sent from my HTC One XL

Yep. S-on + SuperCID + jb RUU = brick. So you'll need a jtag repair. It's worth tying the unbrick method but nine times out of ten it doesn't work.
Sent from my Evita