Database Develop

[Q] HBOOT 1.16.0000, known ROMs to work?

So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk

I know.. I have spoken to him.

jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.

Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?

Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.

katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening

no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?

katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome

no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..

Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.

Hopefully it works for him I couldn't help.

Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.

jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.

I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.

ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.

globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.

Ota 4.3 & twrp 2.6.3.0

I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?

I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767

generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
Click to expand...
Click to collapse
I have been all over the forums looking at this and came up with squat.
If I take the OTA will I loose root? Can't seem to find an answer to that.
I was running an earlier version of twrp and thought that might be the issue but after updating twrp I am still at the same place. The sprint update notifications are still coming.
If I find something I will post it here.

Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc

jziggy101 said:
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
Click to expand...
Click to collapse
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum

jziggy101 said:
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there.
Click to expand...
Click to collapse
You have to have stock recovery to take the OTA
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
Click to expand...
Click to collapse
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
jziggy101 said:
If I take the OTA will I loose root? Can't seem to find an answer to that.
Click to expand...
Click to collapse
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.

Aldo101t said:
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
Click to expand...
Click to collapse
Thanks for the replies. It's very confusing whether people are referencing the OTA update, or the tweaked, rooted downloadable update (http://forum.xda-developers.com/showthread.php?p=46110767). This forum should be friendly to questions when things are confusing.
Even with the two replies on this thread, it's still not clear to me if the downloadable (NOT OTA) updates can be flashed with a custom recovery, or what the procedure is for an S-On device regarding firmware and ROM updates. Sorry to offend anyone if they feel this has been answered somewhere in the forums, but it's still unclear to some of us.
EDIT: 
 @PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?

Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
If your not stock ota will mess you up big time. I just rooted my HTC one on sprint with the update that was on a swap out for bad speakers . Twrp isn't responsive if you use the one in toolkit. I downloaded 2.6.3 loaded it in the data folder of toolkit installed through the toolkit and bam... I got response out of Twrp. I'll find the link and post for you guys.
Sent from my SGH-M919 using Tapatalk 4

generosity21 said:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Click to expand...
Click to collapse
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821

http://techerrata.com/browse/twrp2/m7wls
This is the link for people who are stock and unlocking their phone. If you're using the toolkit put it in the data folder and rename to twrp. Be careful though the other files are the same name but in capital letters! Flash it and u will have responsive twrp and rooted 4.3 ota
Sent from my SGH-M919 using Tapatalk 4
---------- Post added at 02:10 PM ---------- Previous post was at 01:34 PM ----------
Anyone having poor reception?
Sent from my SGH-M919 using Tapatalk 4

PillowMetal said:
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
Tried this once more, and successfully got S-off without downgrading anything, as a few others have reported.
http://forum.xda-developers.com/showthread.php?t=2314582

Brand new device Stock 1.29 Rom Uninstalled SuperSU Unrooted for Updates
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone

upowersystems said:
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
Click to expand...
Click to collapse
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.

Twerp to Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Darn, no I did not flash the stock recovery. Also I read another thread said I needed to unroot!lol So I was back tracing my steps to unroot, so I thought.. I did save the original backup before installing Twerp 2.6.3 and rooting so its in there if I can get to it. I really dont know how to proceed from here. There are no options in the bootloader to proceed.

Twerp vs Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Do I need to figure out how to flash or return to stock recovery from Twerp or can I simploy flash the 1.29 ruu back in to the device for a return to stock?

Twerp 2.6.3
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks

upowersystems said:
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
Click to expand...
Click to collapse
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.

Current State
PillowMetal said:
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Click to expand...
Click to collapse
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.

upowersystems said:
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
Click to expand...
Click to collapse
If you don't want to go the RUU route, then the condition your phone is currently in would only require you to flash stock recovery from 1.29.651.10 (which I got from the actual OTA file). The problem is that your bootloader is now locked and your are S-ON, so you will not be able to flash stock recovery unless you unlock again. If you still have the unlock.bin file from htcdev, that will still work if was done on your current hboot version, otherwise, you would have to visit the site again. Then flash stock recovery, and relock bootloader again. Then the 1.31 update will succeed followed by the 3.04 update.
As far as S-OFF, if you ever want it, you should get it now before updating to anything - even 1.31 (as long as the date on your hboot is May 2013 or earlier). Because, you WILL get the new hboots when you update to 1.31 and 3.04 and since you are S-ON, you will be stuck with it. There is no guarantee that you will ever be able to get S-OFF again with the new hboots. People on hboot 1.54 have been waiting and clamoring for months and there has been no progress and other phones have never even been able to get S-OFF.
Using revone to S-OFF will not wipe your phone or remove anything, it does not require root, and it you do not need to be unlocked. I have performed it from the computer 3 times on Sprint phones and even have made a post about how to make it succeed. There is also a video showing how it can be done on the phone too via terminal emulator, but that method requires root.
Having S-OFF just makes life so much easier, but with it carries great responsibility because security has been turned off and you need to know what you are flashing or you can run into trouble. But as long as you can get to the bootloader, you can recover.

PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
On the att variant you don't need to relock the boot loader to ota.
Sent from my XT1058 using Tapatalk 2

[Q]Going from Safestrap/Kryptonite 4.4.2 rom to CM12?

I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.

llsmith said:
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
Click to expand...
Click to collapse
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.

Travisdroidx2 said:
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Click to expand...
Click to collapse
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?

llsmith said:
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
Click to expand...
Click to collapse
You should be familiar with flashing a custom recovery via adb if you have used TWRP on other devices. Once you have the bootloader unlocked you would need the correct recovery image of TWRP for the Moto X and then in bootloader mode use the command "fastboot flash recovery 'recovery.img'" where 'recovery.img' is the exact name of the file. If it flashed and it works properly then you could flash CM12 and Safestrap should be gone if you followed the flashing directions exactly. Don't forget to make a Nandroid of your current setup before you begin! Factory Resetting the device would be crucial if jumping from one ROM to another so it kind of takes care of itself.

Issue when flashing stock rom to run MM RUU

I am trying to update to marshmallow ( little behind I know). I have searched for my stock recovery and due to my CID number not being on the stock nandroid&recovery thread, it was a bit harder. I found a few posts elsewhere that Gabe a direct link to it, but I am running into a problem when flashing it. I may be doing something wrong, so hopefully someone can point it out, if I am.
When I flashed it the first time (to update to lollipop) everything went fine. But now when I flash it, I just get a little green progress bar that shows up at the upper right hand side of the bootloader screen. I have been using Windroid by the way, to flash said recovery. When windroid says it's completed, the phone reboots back to bootloader, and I am forced to re-flash TWRP.
Is this because I have the wrong recovery? Or am I missing a step in the process? You DO need a stock recovery to run the RUU, correct? My understanding of the process is:
Flash stock rom & recovery
Relock bootloader
Run RUU.
Please help. Thanks

If you are s-on all you need to do is re-lock bootloader and run the RUU.

Damn. See, I see all these other instructions and get confused. That's what I thought, but I was nervous to try it. The way I described would be for an OTA update, right?
Thank you, by the way

garyg199 said:
Damn. See, I see all these other instructions and get confused. That's what I thought, but I was nervous to try it. The way I described would be for an OTA update, right?
Thank you, by the way
Click to expand...
Click to collapse
I've never taken an OTA lol but as far as I know you need a stock rom (with nothing modified) and stock recovery in order for the OTA to go through without issues.
Easiest way to accomplish that would be to RUU 1 update before the current OTA.

How do I remove TWRP?

I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.

Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.

@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up

kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.

kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.

I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.

kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.

kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?

It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.

kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?

did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32

@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.

Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.

mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?

Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.