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
Related
Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks
CoreOxide said:
Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks
Click to expand...
Click to collapse
Which version of Clockworkmod recovery did you fakeflash? There is an issue with the latest one that makes your SDcard unaccessible afterwards. It also mess up your USB.
Here is a thread that guides you how to fix it: http://forum.xda-developers.com/showthread.php?t=691639
I used the latest one, 2.5.1.7 I think.
Isn't there a way to restore the phone with the HTC software, sonething lite the iphone+itunes combo?
Is your sd card not being recognzed?
As you said you created a backup using rom manager before you flashed the new rom. So why dont you just enter hboot, go to recovery and the restore youre phone to the backup that you made using rom mabager before you flashed?
When I select "recovery" using the HBOOT I get a picture of a phone, and a red triangle with an exclamation mark. Does this mean I have to do the USB brick fix?
hmmm thats odd ... sounds like it could be a usb brick related issue, im not sure as i havnt had the same problem before or seen anyone else in the forum experiencing this problem.
I think you should read up more about the usb brick fix, hopefully there is something there that would be able to help you ... if its already known that the latest version of clockworkmod does give this problem then im sure its this and you would be able to find a solution to this problem.
Good luck
UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?
You need to wipe data when switching roms, this will fix the bootloop.
I would also suggest you flash a permanent recovery for ease of use. You need to use unrevoked to do this.
CoreOxide said:
UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?
Click to expand...
Click to collapse
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? Like the clockworkmod recovery? http://forum.xda-developers.com/showthread.php?t=839640Use 2.5.0.7 and not 2.5.1.2 (has the fail you most likely see now). If correct update.zip on SDcard, try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
You are accessing fastboot by holding vol down while powering your phone on. Select fastboot. Plug your USB. Download the Android SDK or only fastboot.exe. Run this command from cmd: "fastboot oem enableqxdm 0". You should get a return command like "okay", and your SD card should be accessible again. Now you will need to follow the guide and fix your USB. However, you should be able to flash a new ROM now when your SDcard is accessible again, or just restore the nandroid backup that gave you this problem to begin with
Update: post #30, weee!
jmelhus said:
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? If so try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
Click to expand...
Click to collapse
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?
CoreOxide said:
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?
Click to expand...
Click to collapse
Do you have a mem reader for windows/linux? Look if you have the file or not. If you don't have it, copy it there. If it's there, you have a problem with accessing the SDCard.
I would say, If I were you, I would try to "repair" the SDcard with the fastboot command first. Most likely, your ROM will boot again when it can read from your SDcard.
Other options would be to try to push the update file with ADB in Android Recovery. Most likely you can't push it either since your SDcard most likely is inaccessible. Try fastboot
Download Android SDK for Windows here: http://dl.google.com/android/android-sdk_r07-windows.zip
MD5: 69c40c2d2e408b623156934f9ae574f0
Unzip the file. Open CMD, navigate to the tools folder in SDK. Issue the command.
Source: http://developer.android.com/sdk/index.html
I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?
CoreOxide said:
I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?
Click to expand...
Click to collapse
You can get your update.zip file from here: http://forum.xda-developers.com/showthread.php?t=839640
Download the 2.5.0.7 zip file and rename to update.zip. Put on root of SDcard and apply sdcard: update.zip in android recovery. From here, go to nandroid, restore, and select your backup.
Doesn't the Update.zip file suppose to be a zipped ROM?
Not necessarily. A zip can flash a lot of different things. I'm not that much into it. But it all depends on the content of the zip file.
How do I " go to nandroid"?
CoreOxide said:
How do I " go to nandroid"?
Click to expand...
Click to collapse
Don't remember what it's called exactly. But when running update.zip (clockworkmod), you should have a restore menu somewhere...
Thanks a lot man! recovering right now.. will update when done.
About that S-ON thing, will the Unrevoked reflash option "Remove phone security" take care of this? Is there a risk in re-rooting?
I want to add some notifications sounds and the "system" folder is write protected
EDIT:
The restore works just fine!
Hi Guys,
Since the time I Flashed the 4Ext Recovery 2.1, I am having very slow Bootloader..
When I power off my Phone and click Power + Menu to enter Bootloader I get this message on HBOOT at statu
Searching for PBDIA99.ziip
No image Found!!
Searching for PBDIAG99.nhh
No Image Found!!
Searching for Pxxxx.zip
Wrong Image!!
...........
........
Click to expand...
Click to collapse
This process like takes 30-40 secs now.. at first this screen used to appear for a second or two... but now its taking hell lot time and slow...
There is no .zip file in SDcard...
Whats wrong?
it always does that "search" for those files so don't worry about it, but never takes THAT long.. if you're S-OFF try flashing a new Hboot, could help.
If you're not S-OFF, then S-OFF using this, get different Hboots from here and check the MD5's with the tool attached - always check md5 of critical files before flashing as you can brick your phone.
bortak said:
it always does that "search" for those files so don't worry about it, but never takes THAT long.. if you're S-OFF try flashing a new Hboot, could help.
If you're not S-OFF, then S-OFF using this, get different Hboots from here and check the MD5's with the tool attached - always check md5 of critical files before flashing as you can brick your phone.
Click to expand...
Click to collapse
actually I had done S-OFF some 2 months back and it was working fine.. The $Ext recovery i flashed is also working fine... takes atleast 10 secs to show the Recovery screen but still shows...
But it was after flashing this 4Ext recovery I got this error of Slow booting... it never hapened before it..
BTW I had flashed the recovery using Terminal Emulator... At first I tried using .zip file by lacing in SD card but it didnt work so I extracted the recovery.img file and flahed with terminal emulator...
Can it be possible that 4Ext recovery is causing this error...
not entirely sure... but you could always try flashing a different recovery.. try the one from my signature and put it where in the tools folder of your android sdk for ease..
Code:
cd\
cd android-sdk/tools
fastboot erase recovery
fastboot flash recovery recovery-RA-desire-v2.0.0-CM.img
you can use cmd or use fastboot commander.. whichever is easier for you
jjdoctor said:
actually I had done S-OFF some 2 months back and it was working fine.. The $Ext recovery i flashed is also working fine... takes atleast 10 secs to show the Recovery screen but still shows...
But it was after flashing this 4Ext recovery I got this error of Slow booting... it never hapened before it..
BTW I had flashed the recovery using Terminal Emulator... At first I tried using .zip file by lacing in SD card but it didnt work so I extracted the recovery.img file and flahed with terminal emulator...
Can it be possible that 4Ext recovery is causing this error...
Click to expand...
Click to collapse
Maybe when you was trying to flash the recovery with PB99IMG.zip in HBOOT you then forgot to delete the file and it keep detecting it and trying to flash?
Just my 5 cents.
bortak said:
not entirely sure... but you could always try flashing a different recovery.. try the one from my signature and put it where in the tools folder of your android sdk for ease..
Code:
cd\
cd android-sdk/tools
fastboot erase recovery
fastboot flash recovery recovery-RA-desire-v2.0.0-CM.img
you can use cmd or use fastboot commander.. whichever is easier for you
Click to expand...
Click to collapse
If i just Place the Stock Hboot PB99IMG_stock.zipfrom alphrev site (after renaming to PB99IMG.zip) and enter Bootloader.. will it flash the Hboot auto?
and after flashing do I loose my ROM and all apps?
jjdoctor said:
If i just Place the Stock Hboot PB99IMG_stock.zipfrom alphrev site (after renaming to PB99IMG.zip) and enter Bootloader.. will it flash the Hboot auto?
and after flashing do I loose my ROM and all apps?
Click to expand...
Click to collapse
yes, just make sure to put it in the root of your sdcard. you "wont" lose all your data but you may be put into a bootloop because of the partition changes so do a nandroid backup
bortak said:
yes, just make sure to put it in the root of your sdcard. you "wont" lose all your data but you may be put into a bootloop because of the partition changes so do a nandroid backup
Click to expand...
Click to collapse
Hmmm... Don't think there will be partition changes since its same Stock Hboot I am reflashing...
Got to make backup now...
jjdoctor said:
Hmmm... Don't think there will be partition changes since its same Stock Hboot I am reflashing...
Got to make backup now...
Click to expand...
Click to collapse
oh yeah true, but it's still got practise to have a nandroid backup just in case, so you don't loose your data
SOLVED
Thanks to jjdoctor, this was solved for me (was taking 2 mins plus for each of the 4 checks, totalling aprox 12mins for bootloader to run) by formatting the sdcard in my phone using 4ext recovery. I took a nandroid, copied off the sdcard contents, formatted the card (ext4 and fat32), and then restored the card contents, and then restored the nandroid. Works perfectly now.
jjdoctor fixed his/hers by creating the partitions using gparted on PC and then re-formatting in the phone, but I just formatted it straight on the phone. Hope it help someone else.
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.
None of the "similar" threads have people with this problem. I can access Recovery (Clockwork Mod v5.8.4.0), I can do everything within Recovery, full wipe, erase dalvik cache etc, BUT it still will not get past "HTC quietly brilliant".
I got into this mess by trying to flash a kernel. I think the battery was about 15%.
I can mount the sd card via usb, so I'm going to extract the back-up I did before getting into this bootloop.
I've tried this:
If you have Custom ROM on or nandroid backup internal SD card
Reboot in recovery (If your still in fastboot, choose "Reboot Bootloader" and then go into recovery)
Restore a Nandroid Backup or flash Custom ROM
Reboot and go into fastboot
Clean cache in fastboot
Click to expand...
Click to collapse
ANd this
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
Click to expand...
Click to collapse
I haven't tried relocking yet. This is the ultimate last resort. Is there a way to know what percentage my battery is?
Any help greatly appreciated before I throw it at the wall and replace with an S3 :silly:
I've got 3737mV
JagSem said:
I've got 3737mV
Click to expand...
Click to collapse
try reflashing boot.img
fastboot erase cache
fastboot flash boot boot.img
o m f g
I have been stressing to absolute hell and back because I was messing around with kernels and managed to bollocks it up. It never occurred to me to extract the boot.img from the backup and flash that through hboot at the same time doing the backup. THANK YOU!! :good::good::good::good::good::good:
JagSem said:
o m f g
I have been stressing to absolute hell and back because I was messing around with kernels and managed to bollocks it up. It never occurred to me to extract the boot.img from the backup and flash that through hboot at the same time doing the backup. THANK YOU!! :good::good::good::good::good::good:
Click to expand...
Click to collapse
Glad u got it sorted
Very Similar Problem - Please Help!
I was wondering if anyone can help me. I have the same problem, all it says is 'HTC Quietly Brilliant' and it is stuck in a reboot cycle.
I was watching a YouTube tutorial on how to flash CM10 onto my One X (I do have ClockworkMod and all of that stuff installed already). Everything was going well, but the video only briefly (for maybe a second) mentioned the fact that you have to put the CM10 zip folder onto the phone storage before you flash the boot.img. I went on and followed the steps and tried to flash the boot.img, but as I said earlier, all the phone will do is reboot over and over again. I have charged it to full battery so this should not be a problem when I go to fix it.
I would be really grateful for any help on the subject as I contacted the person who made the tutorial, and he has not responded. Thanks in advance.
Just an update if anyone has the same problem as I did, all I had to do was go into ClockworkMod and go to:
Mounts and Storage > Mount USB Storage
Then, just connect the device to your PC and put the zip folder on phone storage. Then, flash the boot.img, and install the zip from SD card in ClockworkMod. Hope this helps.
Havoc2510 said:
Just an update if anyone has the same problem as I did, all I had to do was go into ClockworkMod and go to:
Mounts and Storage > Mount USB Storage
Then, just connect the device to your PC and put the zip folder on phone storage. Then, flash the boot.img, and install the zip from SD card in ClockworkMod. Hope this helps.
Click to expand...
Click to collapse
which boot? i've same problem!! where i can find boot.img?
thank's in advance
br
How to install Custom ROM on HTC One X.
agentot said:
which boot? i've same problem!! where i can find boot.img?
thank's in advance
br
Click to expand...
Click to collapse
First off, I'm sorry if you already knew most of the instructions below, or if you are an experienced user. I'm just writing the full steps out so that any user, novice or otherwise, can follow the steps and get their phone working. I will also assume that your phone is already rooted and has ClockworkMod installed.
Before anything else, make sure you have HTC Sync downloaded so that you have the drivers.
Okay, when you are trying to install a custom ROM, you have to put the full zip file on the phone storage. What I would do is create a new folder in C: drive called 'Android' or 'HTC ROM' or whatever you want to put. For the rest of the answer, I will call it AndroidF (android folder). Copy this zip folder into AndroidF. If you go into the zip folder (don't unzip it), you should find a disk image file called 'boot' or 'boot.img'. Copy this out so that it sits in AndroidF too (do not move it!). Once it is in AndroidF, rename it boot.
Once you have done this, go into the bootloader and go to recovery. This will take you to ClockworkMod. From there go to:
Mounts and Storage > Mount USB Storage
Then, connect the phone to your PC and put the zip folder onto the phone. Then, tap unmount, and go back to the bootloader. Click fastboot, and make sure that it says 'Fastboot USB'. If not, just unplug the phone and plug it back in again, and this message should be there. Leave the phone once this has happened.
Go back to AndroidF, and hold shift, right click and choose "Open Command Window Here". Command Prompt should pop up. Then type the following,
fastboot flash boot boot.img
If this works, skip to the next paragraph. If not, type fastboot flash boot boot.img.img. This should then work.
Go back to the phone, and select HBoot. Then go to the recovery from here. Once in the recovery, go to:
Install zip from SD card > Choose zip from SD card
Find the zip file and install it. And voila! Your phone should be running whatever ROM you have picked. If you have any more problems, message me back and I will try and help as well as I can
You can use "adb push" and "adb pull" in recovery to copy files from and to your phone, but you have to mount sdcard from recovery first.
to browse storage directly on the phone you can use "adb shell" and then "ls" and "cd directoryname" to find file which you want to copy from the device.
Hi
I am completely new to developing and have managed to brick my HTC One X.
I need to record calls as part of my job so i tried to follow this guide http://forum.xda-developers.com/showthread.php?t=1663642
However, somehow i completely bricked my phone and i didnt make any back ups.
So far i have managed to do the following:
1. Unlock the phone via HTCdev
2. Get to the fastboot screen
3. fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
4. fastboot flash boot boot.img (from the file 3.16.110.4 which aparantly is the correct file according to CID TMOB-005)
5. fastboot erase cache
6. Then reflash recovery 'fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img'
After the above steps, my phone is now stuck on the HTC Quietly Brilliant screen.
I have been reading threads for the last two days but nothing seems to be working which is probably due to my lack of understanding.
I would be grateful for any assistance.
Thanks
imdense said:
Hi
I am completely new to developing and have managed to brick my HTC One X.
I need to record calls as part of my job so i tried to follow this guide http://forum.xda-developers.com/showthread.php?t=1663642
However, somehow i completely bricked my phone and i didnt make any back ups.
So far i have managed to do the following:
1. Unlock the phone via HTCdev
2. Get to the fastboot screen
3. fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
4. fastboot flash boot boot.img (from the file 3.16.110.4 which aparantly is the correct file according to CID TMOB-005)
5. fastboot erase cache
6. Then reflash recovery 'fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img'
After the above steps, my phone is now stuck on the HTC Quietly Brilliant screen.
I have been reading threads for the last two days but nothing seems to be working which is probably due to my lack of understanding.
I would be grateful for any assistance.
Thanks
Click to expand...
Click to collapse
you don't need to flash recovery twice. are you trying to get it back to stock or do wish to install a custom rom?
nogotaclue said:
you don't need to flash recovery twice. are you trying to get it back to stock or do wish to install a custom rom?
Click to expand...
Click to collapse
Trying to get back to stock.
imdense said:
Trying to get back to custom rom.
Click to expand...
Click to collapse
okwell decide which rom you want and download it, once it's downloaded double click the zip and copy the boot.img then paste it into your fastboot folder. next copy the rom to your sdcard, to do this start recovery and select mount usb storage then copy the file from pc to sdcard. now start bootloader and fastboot erase cache, then fastboot flash boot boot.img, then again fastboot erase cache. then go back into recovery and flash the rom. when its finished flashing wipe the cache and dalvic cache then reboot
nogotaclue said:
okwell decide which rom you want and download it, once it's downloaded double click the zip and copy the boot.img then paste it into your fastboot folder. next copy the rom to your sdcard, to do this start recovery and select mount usb storage then copy the file from pc to sdcard. now start bootloader and fastboot erase cache, then fastboot flash boot boot.img, then again fastboot erase cache. then go back into recovery and flash the rom. when its finished flashing wipe the cache and dalvic cache then reboot
Click to expand...
Click to collapse
Sorry I meant to say return to stock. Can I assume the same instructions apply?
you edited while I was typing, Use this guide,http://forum.xda-developers.com/showthread.php?t=1859714 but please read everything before you attempt anything
disappointed cksbodu
nogotaclue said:
you edited while I was typing, Use this guide,http://forum.xda-developers.com/showthread.php?t=1859714 but please read everything before you attempt anything
Click to expand...
Click to collapse
I took your advise to look at the guide again. However, I have checked for an automatic install RUU but there isnt one available for my phone.
I have to download the correct RUU onto my PC and follow some instructions similar to yours for the Custom Rom. However, when i install the zip from the SDcard, it states the below error:
-- Installing: /sdcard/3.16.110.4.zip
Finding update package...
Opening update package...
E:Cant open /sdcard/3.16.110.4.zip
(bad)
Installation aborted
Do you know why this is happening.
I have tried it now with a 3.16.110.4.zip & filmware.zip (for my phone).
Thanks for your help.
imdense said:
I took your advise to look at the guide again. However, I have checked for an automatic install RUU but there isnt one available for my phone.
I have to download the correct RUU onto my PC and follow some instructions similar to yours for the Custom Rom. However, when i install the zip from the SDcard, it states the below error:
-- Installing: /sdcard/3.16.110.4.zip
Finding update package...
Opening update package...
E:Cant open /sdcard/3.16.110.4.zip
(bad)
Installation aborted
Do you know why this is happening.
I have tried it now with a 3.16.110.4.zip & filmware.zip (for my phone).
Thanks for your help.
Click to expand...
Click to collapse
I have now fixed this problem with a Nandroid recovery. Thanks for your help.