Hello!
I wanted to flash another radio.img onmya HTC Ones C2 (VilleC), and I got this error:
Code:
fastboot flash radio radio.img
sending 'radio' (22541 KB)...
OKAY [ 3.015s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.824s
To explain, I have unlocked bootloader and installed custom TWRP recovery. I believe that radio is for this phone cause I have unpack it from official RUU for HTC VilleC. Any ideas?
Ok I've managed to make flashable zip, and i have succesfully flashed it with TWRP. But strange thing happened that Baseband numbers are still the same. So I have deceided to tray manually flash new radio, with "dd" command, again everything went well but still no change in baseband. I have also flash rcdata.img, still no change. Is it possible that on One S radio can't be flashed manully but only with running RUU??
qzem said:
Ok I've managed to make flashable zip, and i have succesfully flashed it with TWRP. But strange thing happened that Baseband numbers are still the same. So I have deceided to tray manually flash new radio, with "dd" command, again everything went well but still no change in baseband. I have also flash rcdata.img, still no change. Is it possible that on One S radio can't be flashed manully but only with running RUU??
Click to expand...
Click to collapse
What is your hboot version? On the s4 if you are on certain hboots you can't flash radios and it does exactly what you are describing.
Sent from my Nexus 7 using xda app-developers app
I have HBOOT version 2.09.0001.
Sent from my HTC One S using xda app-developers app
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 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
Hi guys, first off I searched all over to find anyone who had the same problem, alas no luck so I decided to post this up if anyone can help. If my dumb ass missed or searched wrong to find the correct link please post it and remove this post. So I have been hacking and modding video game consoles for 5 years, with no problems whatsoever, until I decided to go to phones XD I wanted to root and flash my htc one x which is:
RE-LOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
originally a telus canadian phone. I flashed the phone to cyanogen and the flash took 3 seconds, as soon as I saw it take 3 seconds I knew what I had just done. I've been searching desperately for a RUU or OTA, called into HTC and Telus and they were of no help of course, HTC helped me clear my cache, restore system settings, and all this other fancy work but without any luck. I have tried going into recovery mode but it does not work from bootloader, my phone turns on, goes past the HTC logo then a phone with a little green arrow pointing at the phone appears for a couple mins before being replaced with a red triangle with an exclamation mark inside of it. I have downloaded the OTA and RUU for my phone, neither come with .exe files when I extract them, only boot.img files which I have tried to flash using a hex downloaded from this website but everything keeps failing. If anyone has any advice or a link to a step by step guide too fixing this it would be greatly appreciated, thanks,
Sam.
Once again if there is already a post like this go ahead and remove this I do not mean to spam the website!
How do you expect to flash anything with a locked bootloader?
Sent from my HTC One X using xda app-developers app
exad said:
How do you expect to flash anything with a locked bootloader?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
As I said its been RELOCKED, I can easily unlock bootloader again, when I flashed it was unlocked, only after messing up I decided to relock it
spikypsn said:
As I said its been RELOCKED, I can easily unlock bootloader again, when I flashed it was unlocked, only after messing up I decided to relock it
Click to expand...
Click to collapse
What you're going to want to do is flash the stock recovery and then run the ruu. Then go through the unlock process. I am not sure what exactly your problem is, but this should fix it.
RollTribe said:
What you're going to want to do is flash the stock recovery and then run the ruu. Then go through the unlock process. I am not sure what exactly your problem is, but this should fix it.
Click to expand...
Click to collapse
I ran the RUU and it comes up with this error XD, would you happen to know what the problem is? I tried reflashing Telus stock RUU and rogers RUU with the same radio, both came up with the same error, I also ran the OTA;S one for telus and one for rogers and they both did not work
sending 'zip' (644729 KB)...
OKAY [ 29.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 99.287s
K:\One_X_ATT_All-In-One_Kit_v3.0\data>
spikypsn said:
I ran the RUU and it comes up with this error XD, would you happen to know what the problem is? I tried reflashing Telus stock RUU and rogers RUU with the same radio, both came up with the same error, I also ran the OTA;S one for telus and one for rogers and they both did not work
sending 'zip' (644729 KB)...
OKAY [ 29.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 99.287s
K:\One_X_ATT_All-In-One_Kit_v3.0\data>
Click to expand...
Click to collapse
Hmm, while the toolkit should do it for you, that is the error encountered when your bootloader is not unlocked.
RollTribe said:
Hmm, while the toolkit should do it for you, that is the error encountered when your bootloader is not unlocked.
Click to expand...
Click to collapse
Awesome, did exactly that and I got 1 step closer but not exactly there yet =)) it gives me this error when i flashed the .zip file now, I am using the 3.17 telus OTA to flash with, btw I cannot figure out a way to mount my phone to my computer so I cannot install the zip or recovery on the phone, any tips would be great, thanks once again guys
sending 'zip' (644729 KB)...
OKAY [ 29.587s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.802s
C:\Users\Yahya\Downloads\One_X_ATT_All-In-One_Kit_v3.0\data>
Installed Cricket update for 4.22/Sense 5.
Downgraded hboot to 2.0 from 2.21.
Running unlocked/SuperSU/SuperCID.
When flashed splash screen under 4.12, no errors. Now when attempting getting unable to write error.
Checked for putting in to PL80IMG.zip but uncertain of android info format to make it work.
Used info file from hboot downgrade but gave invalid build error.Any suggestions would be appreciated.
BTW, Device is seen in ADB.
C:\Android\ADB>fastboot devices
HT36HS701349 fastboot
C:\Android\ADB>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)...
OKAY [ 0.223s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.257s
DOrtego said:
Installed Cricket update for 4.22/Sense 5.
Downgraded hboot to 2.0 from 2.21.
Running unlocked/SuperSU/SuperCID.
When flashed splash screen under 4.12, no errors. Now when attempting getting unable to write error.
Checked for putting in to PL80IMG.zip but uncertain of android info format to make it work.
Used info file from hboot downgrade but gave invalid build error.Any suggestions would be appreciated.
BTW, Device is seen in ADB.
Click to expand...
Click to collapse
are you s-off ?
Yes, S-Off carried over from 4.12 to 4.22
DOrtego said:
Installed Cricket update for 4.22/Sense 5.
Downgraded hboot to 2.0 from 2.21.
Running unlocked/SuperSU/SuperCID.
When flashed splash screen under 4.12, no errors. Now when attempting getting unable to write error.
Checked for putting in to PL80IMG.zip but uncertain of android info format to make it work.
Used info file from hboot downgrade but gave invalid build error.Any suggestions would be appreciated.
BTW, Device is seen in ADB.
C:\Android\ADB>fastboot devices
HT36HS701349 fastboot
C:\Android\ADB>fastboot flash splash1 splash1.img
sending 'splash1' (750 KB)...
OKAY [ 0.223s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.257s
Click to expand...
Click to collapse
use the android-info.txt from the OTA you received.
place it in the PL80IMG.zip with the splash1.img and try again
Sent from my C525c using Tapatalk
OTA info attempt
Built the zip with 7zip and "Store" option to create.
Copied to root of SDCARD.
In hboot, it looks and reports it as being "Wrong zipped image" giving only option to press power to reboot.
This method worked on hboot downgrade you sent me to use.
russellvone said:
use the android-info.txt from the OTA you received.
place it in the PL80IMG.zip with the splash1.img and try again
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
The new HBoot has some changes to it, and will take time for people to find these changes and update them on XDA. Trials and errors
Sent from my K2_CL using Tapatalk
Solved
Was able to update via zip.
Had in root of Internal SD when should have been External.
The little things that cause biggest problems.
Thank you.
Modding.MyMind said:
The new HBoot has some changes to it, and will take time for people to find these changes and update them on XDA. Trials and errors
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
Trials and errors lol
Sent from my K2_CL using Tapatalk
I am trying to restore my phone obviously but when I try to use the RUU it keeps freezing at the update progress screen, but the bar never shows up. Any ideas?
Tried a different cable, and now I am getting error 155, (The rom update utility couldn't update your android phone.)
The reason this is such a problem, is because I can't get intpo TWRP, it gives me the twrp loading screen, but then softboots loops over and over into the twrp loading screen. I flashed recovery.img a couple of times and still can't get it working.
Basically at this point I feel like it's RUU or bust.
tootone said:
I am trying to restore my phone obviously but when I try to use the RUU it keeps freezing at the update progress screen, but the bar never shows up. Any ideas?
Click to expand...
Click to collapse
RUU will boot you into [fastboot's OEM rebootRUU] mode. Do you mean there is not a green progress bar? What ROM ver are you currently on?
Sent from my HTC Sensation using Tapatalk
eduardog131 said:
RUU will boot you into [fastboot's OEM rebootRUU] mode. Do you mean there is not a green progress bar? What ROM ver are you currently on?
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes no green progress bar. Currently there is no rom, because I cannot get into twrp. I edited my original post with some additional info.
Another update. I finally got into twrp, and now I just need a rom to flash I believe.
I have flashed a rom still no luck.
I flashed stock recovery, and relocked my bootloader. and tried the RUU again still getting error155. if anyone has a TWRP nandroid or a rom I could try that would be amazing.
bad english
tootone said:
Another update. I finally got into twrp, and now I just need a rom to flash I believe.
I have flashed a rom still no luck.
I flashed stock recovery, and relocked my bootloader. and tried the RUU again still getting error155. if anyone has a TWRP nandroid or a rom I could try that would be amazing.
Click to expand...
Click to collapse
Check this out i had the same problem than you, and this was the answer
First at all restore this backup with TWRP
http://forum.xda-developers.com/showthread.php?t=2734434
ICS preferred,
FLASH BOOT.IMG with Fastboot
Second if you can start up your HTC,
flash stock ICS
recovery.img with fastboot.
http://forum.xda-developers.com/showthread.php?t=2317379
then you can update via OTA.
Send me a message if you have problems
SORRY FOR MY BAD ENGLISH.
omarmando said:
Check this out i had the same problem than you, and this was the answer
First at all restore this backup with TWRP
http://forum.xda-developers.com/showthread.php?t=2734434
ICS preferred,
FLASH BOOT.IMG with Fastboot
Second if you can start up your HTC,
flash stock ICS
recovery.img with fastboot.
http://forum.xda-developers.com/showthread.php?t=2317379
then you can update via OTA.
Send me a message if you have problems
SORRY FOR MY BAD ENGLISH.
Click to expand...
Click to collapse
I am trying the first method you sent me, but which boot.img are we talking here?
Ics Bolt.img
Sent from my C525c using XDA Free mobile app
There is an encrypted Rom.zip pulled from the actual RUU itself posted for K2_CL.
Using fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Rom.zip
Give it time. Could take ten minutes or longer until it is complete. Had a guy do it over on AF and he has his phone back now.
Sent from my C525c using Tapatalk
Modding.MyMind said:
There is an encrypted Rom.zip pulled from the actual RUU itself posted for K2_CL.
Using fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Rom.zip
Give it time. Could take ten minutes or longer until it is complete. Had a guy do it over on AF and he has his phone back now.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yeah that fails with
C:\adb>fastboot flash zip Rom.zip
sending 'zip' (616945 KB)...
OKAY [ 23.035s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 92.353s
tootone said:
Yeah that fails with
C:\adb>fastboot flash zip Rom.zip
sending 'zip' (616945 KB)...
OKAY [ 23.035s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 92.353s
Click to expand...
Click to collapse
What shows on your device screen when doing it?
Also, if you are S-On and was on 4.2.2 prior to your device giving problems then it will fail because the RUU is 4.1.2 and would require a "downgrade" which can only be achieved if S-Off.
With that said, I went back up on this thread and saw you are having problems with TWRP. Make sure you are using the correct one. Should be 2.7.0.2d or 2.7.0.2c. If attempting to flash another version and you are on 4.2.2 then you will get boot problems with the recovery.
In addition, make sure your bootloader isn't locked if S-On while messing with TWRP or that will cause a security problem on your device.
Sent from my C525c using Tapatalk
Modding.MyMind said:
What shows on your device screen when doing it?
Also, if you are S-On and was on 4.2.2 prior to your device giving problems then it will fail because the RUU is 4.1.2 and would require a "downgrade" which can only be achieved if S-Off.
With that said, I went back up on this thread and saw you are having problems with TWRP. Make sure you are using the correct one. Should be 2.7.0.2d or 2.7.0.2c. If attempting to flash another version and you are on 4.2.2 then you will get boot problems with the recovery.
In addition, make sure your bootloader isn't locked if S-On while messing with TWRP or that will cause a security problem on your device.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
bootloader is unlocked but I am s-on maybe that is causing all of my problems. I will see what I can do to remedy that. Well nevermind, I can' t s-off without a working rom, and I can't get a working rom without s-off.
tootone said:
bootloader is unlocked but I am s-on maybe that is causing all of my problems. I will see what I can do to remedy that. Well nevermind, I can' t s-off without a working rom, and I can't get a working rom without s-off.
Click to expand...
Click to collapse
Hmm, well, there is one thing I know for sure and that it that you are definitely able to restore your phone, so I'm pretty sure that some attempts being made In regards to trying other methods are possibly not being done exactly like they should.
This device is VERY hard to wreck and I have done LOTS to my phone and have always been able to bring it back to life in 5 minutes or less.
Sent from my C525c using Tapatalk
I am fairly certain I am doing it right. My mistake here was not doing a backup before I flashed anything. Let me go through what I had tried.
The RUU, I run it with my bootloader locked and I get error 158, I run it unlocked, I still get error 158.
I have tried the rom from the RUU, fastboot into ruu mode, transfer it, and I get an error
I tried putting PL80IMG in the root of my sd, it seems to flash correctly but it boots in white htc quietly brilliant screen. and flash boot.img for that rom.
I restore a rom via TWRP boots into white htc quietly brilliant screen.
and countless other things.
What about the other backups for boost (older than 4.2.2), does none of them work?
tootone said:
I am fairly certain I am doing it right. My mistake here was not doing a backup before I flashed anything. Let me go through what I had tried.
The RUU, I run it with my bootloader locked and I get error 158, I run it unlocked, I still get error 158.
I have tried the rom from the RUU, fastboot into ruu mode, transfer it, and I get an error
I tried putting PL80IMG in the root of my sd, it seems to flash correctly but it boots in white htc quietly brilliant screen. and flash boot.img for that rom.
I restore a rom via TWRP boots into white htc quietly brilliant screen.
and countless other things.
Click to expand...
Click to collapse
1. RUU won't work because it's 4.1.2 and you were on 4.2.2. The RUU has the HBoot in it and your device will not allow the HBoot to be downgraded because you are S-On. Only time you can use an RUU is if it is equivalent to 4.2.2 which one does not currently exist for us.
2. PL80IMG.zip's only work for those who are S-Off. Which is why it won't work for you.
3. When you restore your device using TWRP you ALSO have to rename boot.emmc.win to boot.img and flash it using fastboot:
Code:
fastboot flash boot boot.img
-- This is because, once again, you are S-On and cannot write to your boot partition EXCEPT using fastboot. You could using dumlock but to get dumlock initially set up for the first time would require your device to be able to load an OS so for you that is currently out of the question.
You must restore your device using a twrp backup, AND NOT REBOOT THE SYSTEM when it is done.
Instead, reboot the bootloader, and using fastboot, flash the boot.img which comes with the twrp backup as I just stated earlier.
Then you may reboot.
That will ALWAYS work, so if it fails, then this is an end user problem.
Sent from my C525c using Tapatalk