Tampered, ReLocked, Security Warning - Desire 816 Q&A, Help & Troubleshooting

my bootloader reads Tampered, Relocked, Security Warning. I'm just trying to install the latest OTA from Virgin Mobile. 249 .06 MB should be a substantial update, right??? unrooted my a5_chl. flashed stock Recovery from here http://forum.xda-developers.com/devdb/project/?id=3490#downloads . I even flashed my stock TWRP Backup (unfortunately, i only backed up System and Boot). I even flashed the stock_rooted backup from here at the forum to get the data (stock apps) back. unrooting and relocking the bootloader failed again. Unlocked the bootloader again just to wipe the data furthermore. Red Triangle when installing the OTA. Were any of you Virgin Mobile Users able to update to this version? Anyone with a Pure Stock nandroid Backup (TWRP or CWM)??

SOLVED
SOLVED! An official RUU.exe was released

great
jayblaze406 said:
SOLVED! An official RUU.exe was released
Click to expand...
Click to collapse
can you please provide the link of the official RUU
as i am experiencing a similar problem

If anyone will provide the solution here. I think we're all looking for a way to go back to a5chl stock. Anyone have a method? Link the stock RUU? Is that the one provided by HTC or something else?

marth141 said:
If anyone will provide the solution here. I think we're all looking for a way to go back to a5chl stock. Anyone have a method? Link the stock RUU? Is that the one provided by HTC or something else?
Click to expand...
Click to collapse
go to http://www.htc.com/us/support/rom-downloads.html and find the Virgin Mobile Desire 816. Just follow the .exe and your good!

the_Victorian said:
go to http://www.htc.com/us/support/rom-downloads.html and find the Virgin Mobile Desire 816. Just follow the .exe and your good!
Click to expand...
Click to collapse
Thanks man. This was incredibly useful. I was about to write everything I did here to get the RUU.exe to work until I realized that FoxyDrew had written basically everything here http://forum.xda-developers.com/desire-816/general/ruu-t2952058
For the sake of redundancy, I'm going to post my steps here.
1. Install CWM recovery and download the nandroid backup.
CWM Recovery.exe for ease
https://docs.google.com/file/d/0Bwq9Di4bqEXkMndWSjNBZjViTjA/edit
This guy has a nandroid uploaded for VM HTC Desire 816.
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470
Now to go through with this. Reboot to bootloader and go to fastboot usb. Run the recovery exe and let it flash on. Then make a clockworkmod backup. Part of this is because we like to have back ups to be safe, part of this is to make the backup folder where you're putting the nandroid backup.
2. Flash the nandroid backup
To clarify, this will not flash like a standard zip file. You'll need to extract it into that Clockworkmod backup folder that we would have made when you made the backup (This will be in your SD-Card). Extract the nandroid zip folder into the clockwork backup folder. DO NOT NAME IT TO ANYTHING ELSE. Here is why... How you'll flash this is by running it as a backup. Inside of your recovery you'll go to backup/restore and restore it. If you name it anything other than what it is named when you extract it, Clockworkmod will not get the right MD5s and will fail restoring every time. This is just how an MD5 work. (If the name is different, then it's clearly a "different file" so the MD5 just doesn't match.)
3. Reboot into the system and remove SuperSU.
This step may be a little annoying. You're going to go back into the operating system and it should be the stock VM rom. However, it'll be out of date. Because of all of our rooting/flashing goodness, we just aren't able to install OTA updates (or at least I never could). So, what you're going to do now is find the SuperSU app, go to settings, and tell it to go through with clean up for a permanent unroot. Let it do it's thing. If it takes longer than a 2 or 3 minutes, reboot your phone and do it again. SuperSU should close and be removed from your phone if the uninstall went right. Now, go back to bootloader.
3. Flash stock recovery, lock, and run RUU.exe
We're getting to the final stretch. In FoxyDrew's post here http://forum.xda-developers.com/desire-816/general/ruu-t2952058 he has the stock recovery listed. Download that and flash it with fastboot. Protip for Command prompt noobs, use win+r and cmd to open a command prompt, find your fastboot folder location and copy it then in command prompt type in cd and paste in the location. This way you'll be able to do everything there. Basically you're writing "cd c:/user/fastbootlocation" so your command line will always stay in that directory.
Anyways, flash on the recovery with "fastboot flash recovery [recovery file].img" let it flash. Once that is done, reboot back to bootloader (you don't have to, but I would just to be safe.)
Once back in bootloader run the command "fastboot oem lock" to relock your device. Now staying in bootloader fastboot-usb, run the RUU.exe that you can download from here http://www.htc.com/us/support/rom-downloads.html (Find the desire 816 from virgin mobile/sprint)
Run the RUU.exe and click through the prompts. Wait for it to finish it's job and viola you'll back onto an updated stock rom without root. Your bootloader will stay say that it is "RELOCKED" however, it will not have tampered or security warning on it.

marth141 said:
Thanks man. This was incredibly useful. I was about to write everything I did here to get the RUU.exe to work until I realized that FoxyDrew had written basically everything here http://forum.xda-developers.com/desire-816/general/ruu-t2952058
For the sake of redundancy, I'm going to post my steps here.
1. Install CWM recovery and download the nandroid backup.
CWM Recovery.exe for ease
https://docs.google.com/file/d/0Bwq9Di4bqEXkMndWSjNBZjViTjA/edit
This guy has a nandroid uploaded for VM HTC Desire 816.
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470
Now to go through with this. Reboot to bootloader and go to fastboot usb. Run the recovery exe and let it flash on. Then make a clockworkmod backup. Part of this is because we like to have back ups to be safe, part of this is to make the backup folder where you're putting the nandroid backup.
2. Flash the nandroid backup
To clarify, this will not flash like a standard zip file. You'll need to extract it into that Clockworkmod backup folder that we would have made when you made the backup (This will be in your SD-Card). Extract the nandroid zip folder into the clockwork backup folder. DO NOT NAME IT TO ANYTHING ELSE. Here is why... How you'll flash this is by running it as a backup. Inside of your recovery you'll go to backup/restore and restore it. If you name it anything other than what it is named when you extract it, Clockworkmod will not get the right MD5s and will fail restoring every time. This is just how an MD5 work. (If the name is different, then it's clearly a "different file" so the MD5 just doesn't match.)
3. Reboot into the system and remove SuperSU.
This step may be a little annoying. You're going to go back into the operating system and it should be the stock VM rom. However, it'll be out of date. Because of all of our rooting/flashing goodness, we just aren't able to install OTA updates (or at least I never could). So, what you're going to do now is find the SuperSU app, go to settings, and tell it to go through with clean up for a permanent unroot. Let it do it's thing. If it takes longer than a 2 or 3 minutes, reboot your phone and do it again. SuperSU should close and be removed from your phone if the uninstall went right. Now, go back to bootloader.
3. Flash stock recovery, lock, and run RUU.exe
We're getting to the final stretch. In FoxyDrew's post here http://forum.xda-developers.com/desire-816/general/ruu-t2952058 he has the stock recovery listed. Download that and flash it with fastboot. Protip for Command prompt noobs, use win+r and cmd to open a command prompt, find your fastboot folder location and copy it then in command prompt type in cd and paste in the location. This way you'll be able to do everything there. Basically you're writing "cd c:/user/fastbootlocation" so your command line will always stay in that directory.
Anyways, flash on the recovery with "fastboot flash recovery [recovery file].img" let it flash. Once that is done, reboot back to bootloader (you don't have to, but I would just to be safe.)
Once back in bootloader run the command "fastboot oem lock" to relock your device. Now staying in bootloader fastboot-usb, run the RUU.exe that you can download from here http://www.htc.com/us/support/rom-downloads.html (Find the desire 816 from virgin mobile/sprint)
Run the RUU.exe and click through the prompts. Wait for it to finish it's job and viola you'll back onto an updated stock rom without root. Your bootloader will stay say that it is "RELOCKED" however, it will not have tampered or security warning on it.
Click to expand...
Click to collapse
:good:

Related

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

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.

[Q] HELP! Cant flash Roms

Help my hox is lock on sentinel 4.75 and I cant flash any other rom onto it.
Every time I try to load another rom it crashed at the htc boot screen and never load (I have left it for up to 20 mins)
When this happens the only thing I can do is reload a nandroid of sentinel 4.75 and flash the boot image to return to my previous rom.
I have tried multiple roms including probam, sentinel 5.0, xenonhd and icj with no luck on any of them.
I am on Hboot 1.31 and have installed philz recovery.
Recently I found that my phone had no root access and had to reflash the rom - again the only one that worked was sentinel 4.75
Is there anything I can do to fix my phone to allow me to load another rom. Im finding different issues every time I reload sentinel and would really love to load something else.
Update the hboot
I am guessing that you are forgetting to flash the boot image included in the rom you desire to install.
For example you want to install sentinel v5.00.
update: forgot to mention that you need to update your hboot to run newer roms. you can find proper
hboot update files for your cid in xda forum. Credits to Mr Hofs for the reminder.
Follow these steps.
Technical terms:
adb or fastboot folder: a folder where you have fastboot.exe and adb.exe
HOX: HTC One X
preparation:
a. go to your fastboot or adb folder and rename any 'boot.img' to anything else, like sentinel475.img
b. download the zip file of the rom you want to install
c. copy this zip file into your HOX
d. open the zip file and copy the 'boot.img' file into your adb or fastboot folder
e. make sure your HOX has atleast 60% charge(50% is also fine)
Flashing procedure:
Reboot into recovery
Select 'wipe data/factory reset'
Select 'wipe data/factory reset for new rom' ( applicable to philz recovery only)
Then go back to main menu in recovery
Select 'install zip from sdcard'
Select the zip file, the one you copied to your HOX
Once it has been flashed properly
Reboot into bootloader
connect your HOX with your PC and make sure the HOX display shows 'fastboot usb' in red
open a command window and go to your fastboot folder
type in fastboot flash boot boot.img
type in fastboot erase cache
type in fastboot reboot
disconnect your hox and wait for 5 to 7 minutes for hox to boot into desktop
Thats it. I always follow these steps and everything is fine. You also have to flash gapps zip file but we need to get a proper rom
loaded first before we can do anything else. gapps is always flashable later so no worries about it.
BTW, does it say 'Unlocked' or 'Relocked' in your bootload on the top of the screen?
Can you post the steps you are following to flash other roms? May be you are missing some steps.
Most of the times, a rom will not boot if you don't flash the boot.img that came with the rom.
Thanks, and let me know your results
[Disclaimer: If you follow these steps then you automatically agree to not hold me and all xda forum staff and members responsible for
any damage that might have resulted following or not following these instructions properly or improperly.]
Leave the steps above for now. First give me the outcome of
Fastboot getvar version-main
Thanks rowlf I have installed a few roms before and am familiar with the installation process.
Sorry mistaken it is hboot 1.36
Mr hofs - the version is 3.14.707.24
In case you need cid is HTC__044
I suggest you run the ruu to get back to full stock and try to update via official ota.
http://www.androidruu.com/getdownlo...Radio_5.1204.162.29_release_296434_signed.exe
Get the hboot higher up.
Edit :
1.36 ? Thats fine for all roms. When you install a new one i always advice to do the full wipe manually. Factory reset, wipe caches and format cache,data and system ! Then install the rom.

Help with Android_revolution_HD - Wifi doesn't work, Wiping phone assistance

Hi guys!
I'm selling my HTC one m8 Today, and i would like to sell it with the newest version of android, so i installed ARHD 34.0 for HTC one m8 through twrp v2.8.4.0, and it installs without any errors but i can't toggle wifi when it boots up.
i was using One_M8_2.22.401.4_odexed before and i didnt get any OTA's which was very annoying.
what would be easiest to completely unroot my phone delete twrp and find a Stock rom.
Or fix wifi on ARHD 34.0?
i have searched for hours for a fix for either one i beg of your assistance
my HTC one m8 is european, so i guess the international stuff works for me.
and i have S-on
Thanks in advance !
Bombi22 said:
Hi guys!
I'm selling my HTC one m8 Today, and i would like to sell it with the newest version of android, so i installed ARHD 34.0 for HTC one m8 through twrp v2.8.4.0, and it installs without any errors but i can't toggle wifi when it boots up.
i was using One_M8_2.22.401.4_odexed before and i didnt get any OTA's which was very annoying.
what would be easiest to completely unroot my phone delete twrp and find a Stock rom.
Or fix wifi on ARHD 34.0?
i have searched for hours for a fix for either one i beg of your assistance
my HTC one m8 is european, so i guess the international stuff works for me.
and i have S-on
Thanks in advance !
Click to expand...
Click to collapse
Your firmwae is old and that's why wifi is not working.
You have 2 option either S-OFF or flash stock nand and do officail OTA upto 4.4.4 because 5.0 will arrive this week .
Post the result of "fastboot getvar all" and i will provide you backup link.
Hide imei and serial number before posting result of abve command,..
ahsan64 said:
Your firmwae is old and that's why wifi is not working.
You have 2 option either S-OFF or flash stock nand and do officail OTA upto 4.4.4 because 5.0 will arrive this week .
Post the result of "fastboot getvar all" and i will provide you backup link.
Hide imei and serial number before posting result of abve command,..
Click to expand...
Click to collapse
where do i find stock nand ?
should i take the stock nandroid backup from here ?
http://forum.xda-developers.com/showthread.php?t=2701376
and load it, would that do it ?
thanks alot for your response
Bombi22 said:
where do i find stock nand ?
should i take the stock nandroid backup from here ?
http://forum.xda-developers.com/showthread.php?t=2701376
and load it, would that do it ?
thanks alot for your response
Click to expand...
Click to collapse
Yes take nandroid form there and load it and update officially but remmeber to take backup of your own or any WWE base CID number .
ahsan64 said:
Yes take nandroid form there and load it and update officially but remmeber to take backup of your own or any WWE base CID number .
Click to expand...
Click to collapse
i cant see that .rar file in twrp Restore, tried to open the rar file and put the folder on Sdcard too but cant see it in Restore :s
how do i use that backup file ?
Bombi22 said:
i cant see that .rar file in twrp Restore, tried to open the rar file and put the folder on Sdcard too but cant see it in Restore :s
how do i use that backup file ?
Click to expand...
Click to collapse
You have to unpack it and place it inside the TWRP backup folder. If you can't see it then perhaps you're looking at the wrong storage location.
Check in both the internal and SD card. Else let TWRP "recreate" the directory for you, can easily do it by making a backup of just boot.
Make sure to copy the contents of the "serial number folder" into "your" own serial number folder(on device).
TWRP/Backups/serialnum/ serialnum is of course the serial number for your own device. Though the backups you download will have the serial number for a different device, which is why I said copy the contents of that folder and not the entire folder.
BerndM14 said:
You have to unpack it and place it inside the TWRP backup folder. If you can't see it then perhaps you're looking at the wrong storage location.
Check in both the internal and SD card. Else let TWRP "recreate" the directory for you, can easily do it by making a backup of just boot.
Make sure to copy the contents of the "serial number folder" into "your" own serial number folder(on device).
TWRP/Backups/serialnum/ serialnum is of course the serial number for your own device. Though the backups you download will have the serial number for a different device, which is why I said copy the contents of that folder and not the entire folder.
Click to expand...
Click to collapse
i have installed Stock Recovery and and done a factory reset but it didnt install the Stock rom that i thought it would do..
what do i do now ? how can i install this stock rom : 0P6BIMG_M8_UL_K444_SENSE60_MR_HTC_Europe_3.28.401.9_R_Radio_1.22.21331147A1.29G_20.67.4196.01_release_402839_signed-decrypted
with stock recovery and fastboot ? :s
Hey again, im still stuck with this issue
how do i flash twrp, with Fastboot ?, i have S-on. and it says that no devices is found in cmd when i run fastboot.exe
Bombi22 said:
Hey again, im still stuck with this issue
how do i flash twrp, with Fastboot ?, i have S-on. and it says that no devices is found in cmd when i run fastboot.exe
Click to expand...
Click to collapse
cmd you'll need to change directory to fastboot/adb folder. It'll be faster though to just open the adb folder, hold shift and right click anywhere in the white area of the folder(not on the files) and select open command prompt here. The command to check for the device isn't fastboot.exe, it's fastboot devices <<<Only if you're in fastboot mode, while in recovery or running Android system it'll be adb devices
You'll have to go to HTCDev.com and follow instructions on how to unlock your bootloader(I saw the other thread you made locking the bootloader ).
You can't flash a custom recovery if the bootloader is locked. So follow on screen instructions at http://www.htcdev.com/bootloader
On a side note to original question, the command to flash a custom recovery is fastboot flash recovery name_of_the_recovery.img <<<Recovery image file must be placed inside directory cmd is in, in this case, adb/fastboot folder.
BerndM14 said:
cmd you'll need to change directory to fastboot/adb folder. It'll be faster though to just open the adb folder, hold shift and right click anywhere in the white area of the folder(not on the files) and select open command prompt here. The command to check for the device isn't fastboot.exe, it's fastboot devices <<<Only if you're in fastboot mode, while in recovery or running Android system it'll be adb devices
You'll have to go to HTCDev.com and follow instructions on how to unlock your bootloader(I saw the other thread you made locking the bootloader ).
You can't flash a custom recovery if the bootloader is locked. So follow on screen instructions at http://www.htcdev.com/bootloader
On a side note to original question, the command to flash a custom recovery is fastboot flash recovery name_of_the_recovery.img <<<Recovery image file must be placed inside directory cmd is in, in this case, adb/fastboot folder.
Click to expand...
Click to collapse
Hey again mate !
i just unlocked my bootloader again and flashed latest version of twrp, installed the latest Android revolution 34.0 but the result is the same, wifi doesnt work. and i have the .401 firmware.zip but for some reason it doesnt want to flash it, i still have S-on but the Firmware might be really old too im not sure ?
Bombi22 said:
Hey again mate !
i just unlocked my bootloader again and flashed latest version of twrp, installed the latest Android revolution 34.0 but the result is the same, wifi doesnt work. and i have the .401 firmware.zip but for some reason it doesnt want to flash it, i still have S-on but the Firmware might be really old too im not sure ?
Click to expand...
Click to collapse
Yeah it's because you still didn't update the firmware for your device, so it won't work!
Download the TWRP nandroid backup(like mentioned before) and place it inside the TWRP backup folder and restore it. After it's restored, flash back the stock recovery and let it do OTA updates.
will it get the OTA's if i install .401 odexed and stock recovery ?
Bombi22 said:
will it get the OTA's if i install .401 odexed and stock recovery ?
Click to expand...
Click to collapse
I suppose your first post here probably answered that question for you already...
i was using One_M8_2.22.401.4_odexed before and i didnt get any OTA's which was very annoying.
Click to expand...
Click to collapse
Why try and make things more complicated than it needs to be. Download a nandroid backup, restore it, flash stock recovery and do OTA's. That's it...
yea but i didnt have stock recovery might be therefor i could'nt install the OTA's
i have deleted ARHD 34.0 now, im gonna find another nandroid backup now and figure out where to put it
should the nandroid backup be in zip ?
- Edit
i found a backup named 2014-10-25--04-09-42 KTU84L release-keys
where should i put it ?
Bombi22 said:
yea but i didnt have stock recovery might be therefor i could'nt install the OTA's
i have deleted ARHD 34.0 now, im gonna find another nandroid backup now and figure out where to put it
should the nandroid backup be in zip ?
Click to expand...
Click to collapse
No...I said it in post 6 already, unpack it(in other words, unzip it).
Once it's unzipped you'll probably see a folder named something like yyyy-mm-dd--hh-mm-ss BASENAME release-keys - for example 2014-10-15--23-07-49 KTU84L release-keys... Dates, Time and "BASE"(KTU84L) will obviously change. Inside that folder you'll find files like boot.emmc.win , system.ext4.win000 , recovery.log etc.
That entire folder "2014 [...] release-keys" must be placed inside your serial number folder. If you don't have one yet, create a backup of "Boot" only so that TWRP can create the directory for you. So when it's finished the directory will look something like this:
/storage/ext_sd/TWRP/BACKUPS/SH41RMW18761/2014-10-15--23-07-49 KTU84L release-keys/
Storage location might change depending on whether you use SD Card or not. Better to use it anyways. Of course Serial Number SH41RMW18761 is a made up serial number, your devices serial number WILL be different.
Once you placed it in the correct serial folder, you can go into TWRP, select the storage location(Like I said it'll be better to do SD Card) and TWRP should pick up the nandroid backup from there. Select it and swipe to restore.
BerndM14 said:
No...I said it in post 6 already, unpack it(in other words, unzip it).
Once it's unzipped you'll probably see a folder named something like yyyy-mm-dd--hh-mm-ss BASENAME release-keys - for example 2014-10-15--23-07-49 KTU84L release-keys... Dates, Time and "BASE"(KTU84L) will obviously change. Inside that folder you'll find files like boot.emmc.win , system.ext4.win000 , recovery.log etc.
That entire folder "2014 [...] release-keys" must be placed inside your serial number folder. If you don't have one yet, create a backup of "Boot" only so that TWRP can create the directory for you. So when it's finished the directory will look something like this:
/storage/ext_sd/TWRP/BACKUPS/SH41RMW18761/2014-10-15--23-07-49 KTU84L release-keys/
Storage location might change depending on whether you use SD Card or not. Better to use it anyways. Of course Serial Number SH41RMW18761 is a made up serial number, your devices serial number WILL be different.
Once you placed it in the correct serial folder, you can go into TWRP, select the storage location(Like I said it'll be better to do SD Card) and TWRP should pick up the nandroid backup from there. Select it and swipe to restore.
Click to expand...
Click to collapse
Thanks ill try that out !
should i change KTU84L to the BASENAME of the backup i made ?
my backup basename is LRX22C should i change the nandroid backup name from KTU84L to LRX22C ?
Bombi22 said:
should i change KTU84L to the BASENAME of the backup i made ?
my backup basename is LRX22C should i change the nandroid backup name from KTU84L to LRX22C ?
Click to expand...
Click to collapse
No just copy the folder in the serial number folder. Then go to TWRP, Select Restore, If you must select SD Card / Internal depending where you place nandroid, then Select the nandroid and swipe to restore.
BerndM14 said:
No just copy the folder in the serial number folder. Then go to TWRP, Select Restore, If you must select SD Card / Internal depending where you place nandroid, then Select the nandroid and swipe to restore.
Click to expand...
Click to collapse
the backup restoration went smooth but..
can i reset phone in Backup & reset under phone settings ? cause there is so tonz of crap apps that i cant delete in my menu :s
would it delete everything if i reset phone from settings ?
Bombi22 said:
the backup restoration went smooth but..
can i reset phone in Backup & reset under phone settings ? cause there is so tonz of crap apps that i cant delete in my menu :s
would it delete everything if i reset phone from settings ?
Click to expand...
Click to collapse
Yeah you can do a factory reset. It won't get rid of any "system" apps though. Facebook, Twitter and crap like that will stay there.

[A5_CHL] Need TWRP Backup

SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
end360 said:
SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
Click to expand...
Click to collapse
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
thoctor said:
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
Click to expand...
Click to collapse
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
FoxyDrew said:
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
Click to expand...
Click to collapse
Cool. You're the man.

Categories

Resources