Database Users

Rogers root & Cyanogen mod - confused!

[ I'll send 10$ via Paypal to the person who can get me running on Cyanogen ]
Right, so I'm trying to install CyanogenMod on my Rogers HTC Dream. I've managed to get to SPL 1.33.2005.
I'm following this guide:
http://forum.xda-developers.com/showthread.php?t=544654
I've extracted both image files to the root of my SD card from the "givemeroot.zip" which are "radio.img" and "recovery.img" but am at a loss on how I should proceed from here. Specifically, the following statement:
"IMPORTANT: make sure you have the rom you'd like to install in the root of your sd card as update.zip (YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE UPDATE.ZIP TO GET ONE)"​
Is CyanogenMod considered a "rom", or am I confused? I have CM's zip file on my desktop as "update-cm-4.2.5-signed.zip" - does that mean I need to simply rename it to "update.zip"? Any help here would be graciously welcome!
Cheers!

http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
This is the guide I followed and was much easier to follow.

fattyl said:
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
This is the guide I followed and was much easier to follow.
Click to expand...
Click to collapse
That tutorial still confuses me and constantly loops you back to other articles, which in turn do the same. I'm still not where what exactly I'm expected to do at this stage.
[EDIT] I should clarify. I'm not sure what "if" applies to me in point 5. I've installed the 1.33.2005 CPL but do not believe the phone is rooted.

Ah crap, did see that you weren't rooted, sorry, but I haven't rooted in a long time and cant help you with rooting, sorry, but after you get rooted, if you have RA's recovery or Cyanogen's recovery, you can pick "Apply sdcard: Choose zip", if not, just rename update-cm-4.2.5-signed.zip to update.zip and flash it as normal using "Apply sdcard: update.zip"
Hope this helps.

Rogers, heres your root
haykuro said:
---
hyeprofile requested i link to his rooting for dummies guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
---
edit: almost forgot to include the gr33tz! D:
this hack brought to you by dream_kill, and myself.
---
edit: for those of you that don't know how to get to SPL 1.33.2005 i recommend reading here: http://forum.xda-developers.com/showthread.php?t=532224 (under Rooting Rogers).
---
(note: this is for the dream, the method works for the magic you just need to flash a magic compatible recovery.img)
This requires that you use SPL 1.33.2005. (this is safe on all rogers dream devices.)
so if you don't have that already, go get it here.
once you are at SPL 1.33.2005 (AND ONLY THEN)
download this
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like.
IMPORTANT: make sure you have the rom you'd like to install in the root of your sd card as update.zip (YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE UPDATE.ZIP TO GET ONE)
boot into spl and fastboot (power off, hold camera button, power on, press the back arrow to get into "fastboot" mode)
type in the following:
Code:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
POWER OFF (not reboot, power it off) THE DEVICE. (you can do this using the corresponding button [it says it on the screen] or just pull the battery [make sure everything is done flashing of course])
(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)
now hold down the HOME button and power it on, you should boot into recovery mode now, go ahead and ALT+S to flash your rom, and enjoy! now you can flash anything you see in the forums
EDIT:
So i noticed people were talking about reverting back (not sure why you'd want to )
Regardless, heres the original radio (3.22.20.17) and the original recovery (WARNING: UNROOTED) from rogers dream:
http://www.stevebirstok.com/android/losemyroot.zip
Code:
fastboot flash radio rogersradio.img
fastboot flash recovery rogersrecovery.img
fastboot erase system -w
and flash the update.zip found somewhere on this forum ;P
EDIT 2:
as far as this ram / memory loss goes:
C:\Users\haykuro\Desktop>sha1sum radiog1.img radioion.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radiog1.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radioion.img
radiog1.img is the radio.img i provide in the givemeroot.zip, radioion.img is straight off here there are no specific radios between 32A and 32B boards, so that isn't why you're losing memory. i'm trying to figure it out, so if anyones willing to do some testing and post results, please do so.
Click to expand...
Click to collapse
Once you do that:
1. Upgrade your recovery image to the latest Amon-RA(Link in my sig)
2. Use it to partition your sdcard w/ a FAT32, 512MB ext3 and 96MB linux-swap(backup anything you want first)
3. Put on the latest CM(flash the HTC rom and then the CM ROM as per instructions in the CM thread)
I also recommend you get the latest radio and SPL...if they're the same for rogers as they are on the G1, links in my sig. Not absolutely necessary, but nice to have so you can run any ROM you want.

has anyone tried this guide? http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
apparently it is supposed to take me from stock rogers to cyanmod rooted i got all the way to the end where in my cmd i type erase system -w that works but when i type the next command flash system system.img it says cannot load system.img..... has anyone used this guide and can offer help? ive gone over all the steps over and over im certain i havnt missed anything

You can try verifying the checksum that is posted on the HTC download page or you could just try downloading it again in case something is corrupt.
You could also try flashing an update.zip that doesn't contain the radio. I think someone posted one a while back on the forum. Also I think if you would just skip that step your phone would still work but you would just be missing the google apps like maps. This is better than no phone for now and you can try to get it to work later.

Can't downgrade MT4G?

Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk

You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.

Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ

One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s

Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?

You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.

Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.

Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.

Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....

How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.

OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....

Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.

Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.

As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.

Nexus S Official factory images for 9020t & 9023

http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4

^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)

No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.

^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.

The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.

if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?

I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023

Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?

HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.

i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307

goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...

First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html

Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.

is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?

mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App

I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.

[RUU][GUIDE][Virgin Mobile] HTC Desire 816 Go Back To Stock! (a5chl)

This is the official RUU file for the HTC Desire 815 a5_chl, the variant for Virgin Mobile. I got it straight from HTC's website and re-uploaded it for you guys.
Download links:
KitKat RUU
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7Qa1ZxN29oZWN1Y00/view?usp=sharing
Rom.zip File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QNXVfUkZwUlhYSzg/view?usp=sharing
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
Lollipop RUU
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QclowVm9RQ1J1RjQ/view
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
If you are rooted and on a custom ROM, this RUU will still work, you just need to follow some steps.
1. If you can flash a stock backup, do it, just to be safe.
2. Open up super SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can RUN the EXE file provided in the download section above. Just follow the instructions the program tells you and everything should run smoothly from there.
6. Profit.
Now, if you don't like the exe, you can also flash the RUU from your phone, without the need for a computer. However you will need an external SD card and the Rom.zip file I've provided above.
1. If you can, flash a stock backup, just to be safe.
2. Open up SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can remove the external SD card from the device, and take the Rom.zip file, rename it to "0P9CIMG.zip" and place it on the ROOT of the sdcard.
6. Reboot into Hboot, and as it's rebooting put the sdcard back in the phone. It should automatically detect the RUU file and flash it.
7. Profit.
Download stock recovery HERE.
If you'd like mirrors for the files tell me.

Thanks !

Recovery Issue
I The provided StockRecovery.img will not flash for me apparently because of signature verification. I tried downloading multiple times on phone and PC which is old Windows Vista and may be bad at downloading. Though the file size after download always seems correct. I did restore my stock backup at first BUT it re-roots after reboot.
Fastboot in cmd:
C:\Windows\System32>fastboot flash rec
ery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.886s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.064s
Recovery won't start. It shows for A second the "this build is for development purposes only..." flag like from CWM and goes back to bootloader. I should be able to flash A custom recovery again though. Do you know of any "official" recovery downloads for Virgin Mobile A5? I don't know what it is but I have always had trouble finding and flashing stock recoveries for my HTC phones. Even on XDA's DevDB page.
I then tried the RUU exe and that got stuck at "sending... 1/7", assuming because of no recovery. Weird thing is bootloader shows "OS- (1.50.652.3)" in red but it boots to what i had before.
I have not tried to let hboot attempt to install rom.zip.

CrazyJ36 said:
I The provided StockRecovery.img will not flash for me apparently because of signature verification. I tried downloading multiple times on phone and PC which is old Windows Vista and may be bad at downloading. Though the file size after download always seems correct. I did restore my stock backup at first BUT it re-roots after reboot.
Fastboot in cmd:
C:\Windows\System32>fastboot flash rec
ery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.886s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.064s
Recovery won't start. It shows for A second the "this build is for development purposes only..." flag like from CWM and goes back to bootloader. I should be able to flash A custom recovery again though. Do you know of any "official" recovery downloads for Virgin Mobile A5? I don't know what it is but I have always had trouble finding and flashing stock recoveries for my HTC phones. Even on XDA's DevDB page.
I then tried the RUU exe and that got stuck at "sending... 1/7", assuming because of no recovery. Weird thing is bootloader shows "OS- (1.50.652.3)" in red but it boots to what i had before.
I have not tried to let hboot attempt to install rom.zip.
Click to expand...
Click to collapse
That's odd. It worked flawlessly for me...

CrazyJ36 said:
I The provided StockRecovery.img will not flash for me apparently because of signature verification. I tried downloading multiple times on phone and PC which is old Windows Vista and may be bad at downloading. Though the file size after download always seems correct. I did restore my stock backup at first BUT it re-roots after reboot.
Fastboot in cmd:
C:\Windows\System32>fastboot flash rec
ery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.886s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.064s
Recovery won't start. It shows for A second the "this build is for development purposes only..." flag like from CWM and goes back to bootloader. I should be able to flash A custom recovery again though. Do you know of any "official" recovery downloads for Virgin Mobile A5? I don't know what it is but I have always had trouble finding and flashing stock recoveries for my HTC phones. Even on XDA's DevDB page.
I then tried the RUU exe and that got stuck at "sending... 1/7", assuming because of no recovery. Weird thing is bootloader shows "OS- (1.50.652.3)" in red but it boots to what i had before.
I have not tried to let hboot attempt to install rom.zip.
Click to expand...
Click to collapse
Are you making sure to flash the stock recovery BEFORE re-locking bootloader?

*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Even tried to Download the OTA Normally. Nothing works.

Duh
Thanks. Saw "relocked" on the bootloader and realized I should sleep more.
Updated with exe and now have A fresh phone.
Is there anything special in the update?

jayblaze406
Today, 08:51 PM
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Even tried to Download the OTA Normally. Nothing works.
3/7 right now on the .exe. thanks. hope this works

jayblaze406 said:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Even tried to Download the OTA Normally. Nothing works.
Click to expand...
Click to collapse
Can you get into recovery? If your having the same problem I did then foxydrews suggestion helped.

CrazyJ36 said:
Can you get into recovery? If your having the same problem I did then foxydrews suggestion helped.
Click to expand...
Click to collapse
The .exe just worked perfectly. the OTA Installation from my notification bar kept failing. THANKS for this thread. I previously un-rooted. flashed everything stock. I'm good now. Phone just booted up! Now on the other hand, if ViPER4ANDROID worked on un-rooted phones, I wouldn't have to had gone through all of this lol (and if Google let you uninstall their crap apps).

jayblaze406 said:
The .exe just worked perfectly. the OTA Installation from my notification bar kept failing. THANKS for this thread. I previously un-rooted. flashed everything stock. I'm good now. Phone just booted up! Now on the other hand, if ViPER4ANDROID worked on un-rooted phones, I wouldn't have to had gone through all of this lol (and if Google let you uninstall their crap apps).
Click to expand...
Click to collapse
Glad you figured it out

Custom Rom will be up sometime this week for you guys then insertcoin may follow.

xXminiWHOOPERxX said:
Custom Rom will be up sometime this week for you guys then insertcoin may follow.
Click to expand...
Click to collapse
Just for the VM variant?

Thanks for posting this, had a bit of a scare with my desire this afternoon (ended up just reflashing a backup) but this'll be a good thing to have in my back pocket in case i need it

This saved me today as I was having an issue with a family member's phone not wanting to update OTA because I unlocked and rooted it. Your guide help me put it back to stock and it is now very much stable and usable again. Thank you.

Checksum Please?
FoxyDrew said:
This is the official RUU file for the HTC Desire 815 a5_chl, the variant for Virgin Mobile. I got it straight from HTC's website and re-uploaded it for you guys.
Download links:
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7Qa1ZxN29oZWN1Y00/view?usp=sharing
Rom.zip File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QNXVfUkZwUlhYSzg/view?usp=sharing
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
If you are rooted and on a custom ROM, this RUU will still work, you just need to follow some steps.
1. If you can flash a stock backup, do it, just to be safe.
2. Open up super SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can RUN the EXE file provided in the download section above. Just follow the instructions the program tells you and everything should run smoothly from there.
6. Profit.
Now, if you don't like the exe, you can also flash the RUU from your phone, without the need for a computer. However you will need an external SD card and the Rom.zip file I've provided above.
1. If you can, flash a stock backup, just to be safe.
2. Open up SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can remove the external SD card from the device, and take the Rom.zip file, rename it to "0P9CIMG.zip" and place it on the ROOT of the sdcard.
6. Reboot into Hboot, and as it's rebooting put the sdcard back in the phone. It should automatically detect the RUU file and flash it.
7. Profit.
Download stock recovery HERE.
If you'd like mirrors for the files tell me.
Click to expand...
Click to collapse
i know we are not supposed to request or ask for ETA's i have seen you all over this forum foxy drew and first want to say thank you but i must ask do you think you could provide us with a MD5Checksum In the OP so we can have something match it against it would really suck to attempt to RUU an invalid zip file for people who are not rooted, i only ask because i am assuming you still have the original file on your computer , if not , i would be happy to download the one from htcs site and yours and verify them and provide it to you , if this is not something you are willing or able to do , well i still thank you for all your effort ,

Failed First Time
Think it was because i was rooted and made to many system changes to the framework jar and build.prop and other various changes, when running RUU it caused fastboot to crash just want every one to know if this happens just run the RUU or the .Zip file again and it should work the second time around not sure if it was already mentioned but everything in this guide seems to have worked just thought i would add my experience.
Thank you so much i made so many system changes it was impossible to OTA and i just wanted to get rid of the notification i dont really care about the update (but did want it) i even tried changing my build number was still getting the notification thank you to the OP GREAT JOB

FoxyDrew said:
This is the official RUU file for the HTC Desire 815 a5_chl, the variant for Virgin Mobile. I got it straight from HTC's website and re-uploaded it for you guys.
Download links:
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7Qa1ZxN29oZWN1Y00/view?usp=sharing
Rom.zip File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QNXVfUkZwUlhYSzg/view?usp=sharing
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
If you are rooted and on a custom ROM, this RUU will still work, you just need to follow some steps.
1. If you can flash a stock backup, do it, just to be safe.
2. Open up super SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can RUN the EXE file provided in the download section above. Just follow the instructions the program tells you and everything should run smoothly from there.
6. Profit.
Now, if you don't like the exe, you can also flash the RUU from your phone, without the need for a computer. However you will need an external SD card and the Rom.zip file I've provided above.
1. If you can, flash a stock backup, just to be safe.
2. Open up SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can remove the external SD card from the device, and take the Rom.zip file, rename it to "0P9CIMG.zip" and place it on the ROOT of the sdcard.
6. Reboot into Hboot, and as it's rebooting put the sdcard back in the phone. It should automatically detect the RUU file and flash it.
7. Profit.
Download stock recovery HERE.
If you'd like mirrors for the files tell me.
Click to expand...
Click to collapse
i download the rom.zip three different times three different computers all hard wired connections attempted a Linux distro and windows used multiple compression tools 7zip, build in , peazip, winzip , and a few others and the rom file just fails to open , i was however able to extract it from the RUU by running it and pulling it from the temp directory ( i will not post a guide to tihs and you can easily google the procedure or just think about it hard enough if you are technical enough

[email protected] said:
i download the rom.zip three different times three different computers all hard wired connections attempted a Linux distro and windows used multiple compression tools 7zip, build in , peazip, winzip , and a few others and the rom file just fails to open , i was however able to extract it from the RUU by running it and pulling it from the temp directory ( i will not post a guide to tihs and you can easily google the procedure or just think about it hard enough if you are technical enough
Click to expand...
Click to collapse
That's the same way I got the Rom.zip. Your not supposed to open it up?
And don't quote the OP

Help me!!!
Can you help me to get this ruu file on HTC's website??The file broken on internet and didn't work on my desire 816X.
RUU file named 0P9CIMG_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_TW_1.54.709.2_Radio_1.101.1102.17.0506_10.20.4149.00L_release_388245_signed_2.zip
Also Thanks for posting !!!:good::good::good::good:

Warning - XT1060 Blur_Version.212.55.26 blocks custom recoveries

Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
mfastboot.exe flash recovery twrp-2.8.6.0-ghost.img
sending 'recovery' (9488 KB)...
OKAY [ 0.849s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.819s
Click to expand...
Click to collapse
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.

And you are booting straight to recovery after flashing via volume down and then volume up to select not the power button?

_litz said:
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
Click to expand...
Click to collapse
After you flash TWRP, at the command prompt type:
fastboot reboot-bootloader
I can't remember where I read it but some people said they had to do that to get the custom recovery to stick.
THEN unplug your device from your computer and reboot into recovery by scrolling down with the volume down button to highlight recovery and then hitting the volume up button to select recovery.

Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP ... to develop this process)
So ... the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.

_litz said:
Ok, figured this out ...
Click to expand...
Click to collapse
I think all that needs to happen is after you flash TWRP - you don't boot into recovery. Instead, reboot into bootloader mode. This has been a problem from the beginning for some people with their MX13's and not a new thing. I don't think it has anything to do with the update. Some people have to reboot into bootloader after flashing TWRP in order to get it to stick for some reason.

@_litz Please understand that @JulesJam is correct... the proper way to flash a recovery is as follows...
Start the phone to the Fastboot AP/Bootoader menu
using moto's fastboot (aka mfastboot) exectue the following...
mfastboot flash recovery RecoveryYouWishToFlash.img
mfastboot reboot-bootloader
Then use the volume/power keys to enter recovery.
Once in the recovery, it is safe to Reboot the phone normally.
that mfastboot reboot-bootloader step has been crucial for getting the newly flashed recovery (3rd party OR Stock!) to "stick" on the phone.
Flashing with RSDLite is over kill.

You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
That is because you are pressing the power button when you should be pressing the volume up button.

Yep ... ain't my first rodeo ....
It flat out refused to take recovery.
I had to back it back down to the old 4.4.4 version, reflash TWRP, then I simply applied the whole RSD package (sans recovery) to re-upgrade it to the new 4.4.4.
Worked like a charm.
(Plus it gave me a chance to extract the fxz from the moto manager app)

Travisdroidx2 said:
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
Click to expand...
Click to collapse
yes, that is what is happening.

See above ... this isn't my first time at this. Was not working as described.

_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
Was not trying to insult your knowledge. That is a very common problem that many do. So I had to ask.

_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
You needed to reboot into bootloader by typing fastboot reboot-bootloader after your flashed TWRP. THEN disconnect your phone from your computer and boot into recovery by using the volume down to highlight recovery and volume up to select recovery.
If you follow those instructions, you will flash TWRP fine. No need to go through that long drawn out process you came up with.

Probably should rename or delete this thread, since its fairly misleading.

Check in the /system partition for a file named recovery-from-boot.p or something similar. If that file is there it will reflash the stock recovery when you reboot, and I've seen it reflash when booting into recovery.

I just used the TWRP manager app from the Play store after reverting to stock recovery and installing the OTA. It worked perfectly the first time.
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
I'm curious as to what is different.. because the other day after flashing stock recovery back on my phone, taking the update to 212.166.3 KXA21.12-L1.26-3 which Verizon just pushed, I used those EXACT STEPS to put TWRP back on my phone and had no problems.

Beats me ... for me, it didn't work ...
So after I got things back onto the old 4.4.4 version, I put together the FXZ with the modified xml file, and simply re-updated, applying both the update, and TWRP, all in one go.
anyone else on old 4.4.4 can do the same thing if they wish, which was why I posted the links and the instructions.

not to bump this thread, but I had zero issues going from stock with 212.55.26 ota update installed and flashing twrp. it just worked like normal.
i would agree with @superkeest seems like this thread should get renamed.