Develop Bugs

[Q] Rom Manager - Failed to Seek

Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?

...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)

jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.

Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.

Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.

I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped

Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.

In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App

I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.

PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.

No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.

Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App

I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.

srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well

PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.

I've reached out to the developer. Hopefully we will hear from him soon.

Can you guys try clearing your download cache, and then reflashing recovery?

Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution

Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App

Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7

Replace framework-res.apk > Bootloop. Help!

Hi all!
I using root explorer to replace framework-res.apk
But now, my HTC Desire Z have a bootloop. I try to factory reset, wipe cache date, using update.zip but not not effective.
When I up rom in recovery (3e), the system show: E:signature verification failed
Help me fix the bootloop. Thanks!

well first off I hope you made a nandroid backup of your ROM before you did this. If so, just pull the battery, boot straight into recovery, and restore that nandroid backup.
Where did you get this framework-res.apk? did you edit it yourself? if so, what did you change? If you or someone else has changed anything decently major, the .apk needs to be re-signed. Looks like it wasn't.

Everybody help me!
I can't solve this problem

minhquang_ns said:
Everybody help me!
I can't solve this problem
Click to expand...
Click to collapse
Where did the framework-res.apk you are using to replace the stock on come from?
Or is the issue now just trying to get your phone booting again?

cjward23 said:
Where did the framework-res.apk you are using to replace the stock on come from?
Or is the issue now just trying to get your phone booting again?
Click to expand...
Click to collapse
I get framework-res.apk in Uot kitchen > Show all pickup file
I get one in this and replace. I didn't think about consequences

minhquang_ns said:
I get framework-res.apk in Uot kitchen > Show all pickup file
I get one in this and replace. I didn't think about consequences
Click to expand...
Click to collapse
Like I said in my first post that you didn't respond to, did you make a nandroid backup? If you didn't, you should at least have the stock framework-res.apk set aside to go back to? If you don't, and you can boot directly into recovery, then you're going to have to re-flash a fresh ROM in order to break the issues you caused with your current problem.
So if your phone is still bootlooping and you don't have a backup to go to, then follow the normal steps to flash a new ROM from recovery (this will probably be your only option if you don't have a backup):
1) download your ROM of choice
2) enter recovery, mount as USB storage
3) place ROM.zip on root of your SD card
4) install zip from SDcard > select ROM.zip
5) reboot
you'll probably lose your data, unless you flash the exact same ROM as you had before, there may be a chance that it won't.
Here's a lesson to be learned! Backup before messing with major things, and save the old framework-res.apk. And don't just willy-nilly flash random Uot Kitchen framework-res.apk's without precautions. It looks like you just got a framework-res.apk that wasn't signed properly and it messed your ROM up.

martonikaj said:
Like I said in my first post that you didn't respond to, did you make a nandroid backup? If you didn't, you should at least have the stock framework-res.apk set aside to go back to? If you don't, and you can boot directly into recovery, then you're going to have to re-flash a fresh ROM in order to break the issues you caused with your current problem.
So if your phone is still bootlooping and you don't have a backup to go to, then follow the normal steps to flash a new ROM from recovery (this will probably be your only option if you don't have a backup):
1) download your ROM of choice
2) enter recovery, mount as USB storage
3) place ROM.zip on root of your SD card
4) install zip from SDcard > select ROM.zip
5) reboot
you'll probably lose your data, unless you flash the exact same ROM as you had before, there may be a chance that it won't.
Here's a lesson to be learned! Backup before messing with major things, and save the old framework-res.apk. And don't just willy-nilly flash random Uot Kitchen framework-res.apk's without precautions. It looks like you just got a framework-res.apk that wasn't signed properly and it messed your ROM up.
Click to expand...
Click to collapse
Thank you, but I don't have clockmod recovery
When I using Recovery 3e (default), I choose "update.zip"
I try many roms but the system warning:
E: signature verification failed
FAILED TO VERIFY WHOLE-FILE SIGNATURE
Installation aborted.
Click to expand...
Click to collapse

.
minhquang_ns said:
Thank you, but I don't have clockmod recovery
When I using Recovery 3e (default), I choose "update.zip"
I try many roms but the system warning:
Click to expand...
Click to collapse
How can you not have cwm, there isn't another custom recovery for the DZ that I'm aware of.
Hang on, do you still have the stock recovery? OK so I'm going to assume you are actually rooted. Do you nave the eng hboot installed?
Do Androids dream of electric sheep?

cjward23 said:
.
How can you not have cwm, there isn't another custom recovery for the DZ that I'm aware of.
Hang on, do you still have the stock recovery? OK so I'm going to assume you are actually rooted. Do you nave the eng hboot installed?
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
I have HBOOT 0.85.009. How to flash a new rom with out clockmod

minhquang_ns said:
I have HBOOT 0.85.009. How to flash a new rom with out clockmod
Click to expand...
Click to collapse
You can't, you will need to install cwm.
Download rom manager, then select install clockworkmod recovery. Then boot your phone in to recovery and preform a wipe then flash custom rom.
Do you have s-off?
Do Androids dream of electric sheep?

cjward23 said:
You can't, you will need to install cwm.
Download rom manager, then select install clockworkmod recovery. Then boot your phone in to recovery and preform a wipe then flash custom rom.
Do you have s-off?
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
I have a boot loop, my Desire Z stopped in "HTC quietly brilliant" so I can't install cwm. I has been rooted phone.

minhquang_ns said:
I have a boot loop, my Desire Z stopped in "HTC quietly brilliant" so I can't install cwm. I has been rooted phone.
Click to expand...
Click to collapse
Ohh yeah, I forgot that. OK you will need to install recovery using fastboot. But to do that you will need to install the eng hboot. To do that please follow the instructions here http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html. But when you get to point 10 you will need to pull your battery out. And delete the PC10IMG.zip of your sd card.
Then reboot back in to bootloader and if all has gone well we will know have the DZ eng hboot installed.
The top line should now say vision eng s-off
You will then need to execute fastboot commands to install cwm. If you do not have fastboot installed download fastboot.exe from here http://developer.htc.com/adp.html and place in your platform-tools folder. You will is need the cwm recovery.img which you can get from here http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img and rename to recovery.img and place in your platform-tools folder
Open a cmd window and point it towards your platform-tools folder. Then we want to check fastboot is working, so make sure your phone is in bootloader and type fastboot devices and it should bring up your device serial number. Assuming that works type fastboot flash recovery recovery.img
All being well the recovery will flash then you will be able to boot in to recovery and flash a rom.
If you have any problems or are unsure about anything head over to the #G2ROOT irc http://webchat.freenode.net/
Do Androids dream of electric sheep?

cjward23 said:
Ohh yeah, I forgot that. OK you will need to install recovery using fastboot. But to do that you will need to install the eng hboot. To do that please follow the instructions here http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html. But when you get to point 10 you will need to pull your battery out. And delete the PC10IMG.zip of your sd card.
Then reboot back in to bootloader and if all has gone well we will know have the DZ eng hboot installed.
The top line should now say vision eng s-off
You will then need to execute fastboot commands to install cwm. If you do not have fastboot installed download fastboot.exe from here http://developer.htc.com/adp.html and place in your platform-tools folder. You will is need the cwm recovery.img which you can get from here http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img and rename to recovery.img and place in your platform-tools folder
Open a cmd window and point it towards your platform-tools folder. Then we want to check fastboot is working, so make sure your phone is in bootloader and type fastboot devices and it should bring up your device serial number. Assuming that works type fastboot flash recovery recovery.img
All being well the recovery will flash then you will be able to boot in to recovery and flash a rom.
If you have any problems or are unsure about anything head over to the #G2ROOT irc http://webchat.freenode.net/
Do Androids dream of electric sheep?
Click to expand...
Click to collapse
When I using fastboot recovery, cmd warning:
writing ‘recovery’… FAILED (remote: not allowed)
Click to expand...
Click to collapse
Similar, I type adb shell the system wanring:
error:devices not found
Click to expand...
Click to collapse

Android noob needs help! Universal good karma for anyone who can help find a fix!

Fairly noobed to android so need a little help (teething) haha,
I've tried to install a custom rom for my one x unlocked boot loader and installed clockwork mod touch recovery, downloaded android revolution hd and moved wipe script and android revolution zip to sd card, flashed the boot.img and run wipe script no problem.
But when I go to install the zip file I get greeted with
finding update package>opening update package>installing update>installation aborted... then nothing. If I reboot the phone the phone stays in the htc quietly brilliant screen.
Please anyone! Help a fella out, crack this and I'll be forever in everyone debt. Thanks.
Con

ConorL said:
Fairly noobed to android so need a little help (teething) haha,
I've tried to install a custom rom for my one x unlocked boot loader and installed clockwork mod touch recovery, downloaded android revolution hd and moved wipe script and android revolution zip to sd card, flashed the boot.img and run wipe script no problem.
But when I go to install the zip file I get greeted with
finding update package>opening update package>installing update>installation aborted... then nothing. If I reboot the phone the phone stays in the htc quietly brilliant screen.
Please anyone! Help a fella out, crack this and I'll be forever in everyone debt. Thanks.
Con
Click to expand...
Click to collapse
Try to disable the signature check and see if you're able to install it.

Your Rom zip files is corrupted. You have to verify md5 value and then you have to flash.
Goto fastboot and just flash the stock kernel.
Sent from my HTC One X using Tapatalk 2

Tried disabling the signature check with no luck same thing happens..Do you know where could I get the stock kernel from? Thanks again for your patience it is greatly appreciated!

When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..

ConorL said:
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
Click to expand...
Click to collapse
Use the automated batch file in ARHD Thread. Like he said it might be a bad download. Re-downloaded it and test it again.

Tried downloading the stock kernel again and same story... How do I use the automated batch file you mentioned? thanks..

Are you trying to flash a .zip in fastboot? What file have you renamed 'flash'?

I haven't renamed any files flash I've just been trying to flash the .zip file...Its been a major fail so far, thanks for everyone patience..

ConorL said:
I haven't renamed any files flash I've just been trying to flash the .zip file...Its been a major fail so far, thanks for everyone patience..
Click to expand...
Click to collapse
Re-download the file to PC
Send file to sdcard
Remove usb cable from HOX
Try again
Hope it helps

I can't get back into the os to move the files over to the sd card, every time i reboot I get the htc quietly brilliant screen...

after i download the file should i rename anything to get it to flash properly from fastboot? I can't get back into the os so i'm in bootloader trying to fix it..Cheers

Go to Bootloader select Fastboot
Download http://www.androidrevolution.nl/downloader/download.php?file=Flash_boot_6.0.0.rar and extract it. Then run the batch file.
Then go into Recovery and your SD card will be automatically mounted to your PC in Recovery mode
So copy the ROM and flash it again.
Make sure you don't select any custom settings on the first boot.

It still looks like your trying to flash a .zip in fastboot.
---------- Post added at 01:05 PM ---------- Previous post was at 01:02 PM ----------
ConorL said:
When i try to Flash the stock rom i get this message
sending 'flash' (9792 KB)... OKAY
writing 'flash'... FAILED (remote: not allowed)
xx-xxx-xx-22:bootloader connor$
anyone know what I'm doing wrong?? Thanks..
Click to expand...
Click to collapse
This. ^^^
Sending 'flash'.
What command did you write to get this error. And what was the filename and extension. It would really help to know what you tried to flash.

I had the same issue on Wednesday where I ran the wipe script then tried to flash the rom and it turned out to be a corrupt download (failed to follow instructions to my peril).
To resolve all that was needed was to re-download the rom, mount the sdcard and copy it over and reattempt the flash. In my case I couldn't mount the sdcard at first, so if you are having issues here I solved it by updating recovery as per this thread "[RECOVERY] TeamWin Recovery Project (twrp) 2.1.7 [2012-06-04]"
under the "One X Android Development section"

To send files to your sd with no os, either install the new recovery that has usb support or use
Fastboot boot name.IMG (this is recovery IMG)
While booting from fastboot like that it allows adb to be used then Just push
adb push Rom.zip /sdcard
That will push the Rom to sd then just install as normal.
You will need the adb files easy enough to find on google.
Sent from my HTC One X using xda premium

i made a compilation thread about this, have a check... might help you out..
http://forum.xda-developers.com/showthread.php?t=1692681

Some assistance is requested

Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!

If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.

robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV

the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not

You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse

master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..

You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse

master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.

I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse

master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?

It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse

master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!

Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.

Phone stuck on HTC quietly brilliant

Hey my phone is stuck on the loading screen after i tried to root my phone, if im honest i had no idea what i was doing i was just following a guide i found online and just thought it would all go alright but sadly it went terribly wrong. what i did was unlock the boot loader uses the htc website that the guide directed me to which went smoothly then i went into fastboot mode and ran the file install-insecure-windows from the folder i downloaded called r3-endeavor-insecurebootandroot. my phone restarted and the just froze at the loading screen. i have tried to run recovery and i just get a red triangle and i have also tried a factory reset and that just starts to load and then resets and is still stuck on the loading screen.
my HBOOT-1.39.0000
version-main: 3.14.401.31
Ive looked around alot for solutions to my problem but not found one that works.
I really need help but if im honest i dont know alot about what im doing and i know i should have just left it all alone
any help would be greatly appreciated

Relock your bootloader by fastboot oem lock
Download this file and run it with administrative rights - http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
You'll be back to stock.
Sent from my HTC One X using xda app-developers app

simonw89 said:
Hey my phone is stuck on the loading screen after i tried to root my phone, if im honest i had no idea what i was doing i was just following a guide i found online and just thought it would all go alright but sadly it went terribly wrong. what i did was unlock the boot loader uses the htc website that the guide directed me to which went smoothly then i went into fastboot mode and ran the file install-insecure-windows from the folder i downloaded called r3-endeavor-insecurebootandroot. my phone restarted and the just froze at the loading screen. i have tried to run recovery and i just get a red triangle and i have also tried a factory reset and that just starts to load and then resets and is still stuck on the loading screen.
my HBOOT-1.39.0000
version-main: 3.14.401.31
Ive looked around alot for solutions to my problem but not found one that works.
I really need help but if im honest i dont know alot about what im doing and i know i should have just left it all alone
any help would be greatly appreciated
Click to expand...
Click to collapse
Since you have already unlocked your bootloader, you can try installing a custom recovery Like CWM or TWRP. You can then download any custom rom posted in the xda thread and flash it. I personally recommend ViperX. Your phone will be better than ever. It seems like you are new to this so if you need my help flashing then simply ask.
You can also follow the instructions on torxx detailed thread
http://forum.xda-developers.com/showthread.php?t=2182792
HIT THANKS IF I HELPED!!
:good::good::good::good:

yes you are right i am very new to all this very pleased to hear that i haven't ruined my phone i would love to have a go at installing a recovery and a new rom. ill have alook at your thread guide you linked and see how i get on if i get stuck ill try the relocking way thank you all for the help

well i had alook at the tutorial and i managed to use the fastboot flash recovery and it seemed to work in cmd as it said
writing 'recovery'... INFOFormat partition SOS done.
what i don't understand is step 3 the actual rooting when i go to the bootloader and press power when on recovery it now just loads the HTC quietly brilliant screen again and i dont understand how to flash from recovery

simonw89 said:
well i had alook at the tutorial and i managed to use the fastboot flash recovery and it seemed to work in cmd as it said
writing 'recovery'... INFOFormat partition SOS done.
what i don't understand is step 3 the actual rooting when i go to the bootloader and press power when on recovery it now just loads the HTC quietly brilliant screen again and i dont understand how to flash from recovery
Click to expand...
Click to collapse
The recovery will start after the HTC screen. In the recovery, press install and select whichever zip you want to flash.
Sent from my HTC One X using xda app-developers app

i have managed to get the recovery page open but how do i get the superuser.zip file to appear on the list how do i get it onto the phone

simonw89 said:
i have managed to get the recovery page open but how do i get the superuser.zip file to appear on the list how do i get it onto the phone
Click to expand...
Click to collapse
Have you copied it from the computer??
If you have, then tap install and navigate to the folder to which you have copied it.
Sent from my HTC One X using xda app-developers app

causality ctrybor
i have copied it to the cd card and i have just worked out how to find that within recovery at last im slowly working things out the only problem now is when i run the superuser.zip from the recovery i get
installing: /sdcard/superuser.zip
finding update package...
opening update package ...
verifying update package...
E:signature verification failed
installation abourted

simonw89 said:
i have copied it to the cd card and i have just worked out how to find that within recovery at last im slowly working things out the only problem now is when i run the superuser.zip from the recovery i get
installing: /sdcard/superuser.zip
finding update package...
opening update package ...
verifying update package...
E:signature verification failed
installation abourted
Click to expand...
Click to collapse
Maybe a bad download?
Try downloading again. If it still doesn't work, try a different recovery. Personally, I used TWRP while rooting.
Sent from my HTC One X using xda app-developers app

If redownloading doesn't fix it.. use this SuperSU.zip
http://d-h.st/B2K

ahh you are golden ! that was exactly right i went and found another copy of super user and it downloaded perfectly thank you
just trying to install the viperX rom now see how this goes

am i right in thinking that once i have downloaded the viperX i just place it on my sdcard the same way i did the superuser and then just install it the same way from the recovery?

simonw89 said:
am i right in thinking that once i have downloaded the viperX i just place it on my sdcard the same way i did the superuser and then just install it the same way from the recovery?
Click to expand...
Click to collapse
Yes... However, you have to flash the boot.img from fastboot..
and before installing the rom.zip.. you have to wipe data/cache/dalvic from recovery.... Or use Super Wipe script : http://d-h.st/kG0

simonw89 said:
i have copied it to the cd card and i have just worked out how to find that within recovery at last im slowly working things out the only problem now is when i run the superuser.zip from the recovery i get
installing: /sdcard/superuser.zip
finding update package...
opening update package ...
verifying update package...
E:signature verification failed
installation abourted
Click to expand...
Click to collapse
I think I have found a workaround for your problem.
If you have installed TWRP recovery then you will notice that their is a check box labeled 'toggle signature verification'. Make sure it is unchecked(whichever works).
If this works then great.
Otherwise I suggest that you download a custom ROM and flash it.(My personal suggestion)
Everything will be fine. Don't worry.
Steps are as follows-
•Download the ROM you want to flash
•Open the ROM zip with an archive manager and extract the boot.img file out of it and place it in your fastboot directory
•Copy the ROM to your sdcard
•Now boot into bootloader and choose recovery with your volume keys and power button
•In recovery wipe data and cache, dalvik cache, factory reset,etc
•Now flash your ROM by installing zip from sdcard
•If this is finished, reboot and reboot into bootloader again
•Connect your phone to your PC in fasboot mode (choose in bootloader with power button)
•Open a cmd in your fastboot folder with your boot.img and type these two commands:
fastboot flash boot boot.img
fastboot erase cache
Then simply reboot your phone.
You can download ROMs from the development section.
PM me if you encounter any problems or need any help.
:good::good::good::good::good::good:

Finally
i got superuser from another source which worked like a dream and got it installed at last, then managed to flash the boot.img in the fastboot. then deleted all the data/cashe and installed venomX can finally turn on my phone after 3 days
thank you all so much for the help its been all really appreciated dont know what i would have done with out it