[Q] going to stock fail... need 2.24.401.1 nandroid - One (M7) Q&A, Help & Troubleshooting

I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!

+1

Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium

No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app

LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.

AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app

ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.

AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app

ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol

ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo

Related

Google Play Edition RUU flash

Hi all, do I need to be S-OFF to flash the GPe RUU? Or do I need only unlocked bootloader?
The problem is, i'm on 4.2.2 WWE ROM full stock, and i noticed that, since revone doesn't work with HBoot 1.54, the only thing i can do is unlocking the bootloader via HTCdev.
Thanks to all will answer my question.
Sent from my HTC One using XDA Premium 4 mobile app
You need to be S-OFF to flash the full conversion RUU, but you can flash custom GPe ROMs if you want
EddyOS said:
You need to be S-OFF to flash the full conversion RUU, but you can flash custom GPe ROMs if you want
Click to expand...
Click to collapse
Does the full conversion allow the user to receive OTA updates from google? If so is there a guide for this somewhere? Currently running a rom myself and s-on. Don't want to muck anything up but it would be worth it if I could flash and then just permanently leave it be going forward.
Yes it does, although I downloaded it ans flashed it manually through the stock recovery as I cba to wait on Google to push it when I was running the GPe RUU last week
S-OFF
greenpants said:
Does the full conversion allow the user to receive OTA updates from google? If so is there a guide for this somewhere? Currently running a rom myself and s-on. Don't want to muck anything up but it would be worth it if I could flash and then just permanently leave it be going forward.
Click to expand...
Click to collapse
Forget it, if you are not S-OFF you cannot do it. Once a phone is upgraded to hboot 1.54 and has not been S-OFF
before the upgrade is stuck.
CC
cc999 said:
Forget it, if you are not S-OFF you cannot do it. Once a phone is upgraded to hboot 1.54 and has not been S-OFF
before the upgrade is stuck.
CC
Click to expand...
Click to collapse
Last check my HBoot was 1.4x
I got the phone last Friday then rooted and switch to Bigxie GP rom (ARHD sticks on boot) the day after.
I would like to get OTA updates so I don't have to manually grab everything and lose my data re-locking/unlocking bootloader each time when I do firmware updates (which I realize I will also need S-OFF for). I found the RUU guide so I may eventually go that route presuming the memory of my HBoot is correct...
OK
greenpants said:
Last check my HBoot was 1.4x
I got the phone last Friday then rooted and switch to Bigxie GP rom (ARHD sticks on boot) the day after.
I would like to get OTA updates so I don't have to manually grab everything and lose my data re-locking/unlocking bootloader each time when I do firmware updates (which I realize I will also need S-OFF for). I found the RUU guide so I may eventually go that route presuming the memory of my HBoot is correct...
Click to expand...
Click to collapse
OK then you are on 1.44 I would follow procedure for S-OFF.
With S-OFF you can do just about any flashing you want and you wil never
lose the S-OFF status. Once you gain S-OFF DO NOT RETURN to S-ON.
CC

HBOOT question

So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include? Does ARHD stick with older HBOOT?
If it does update hboot,
If I turn S-OFF right away, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version in case I need to turn S-ON?
Is it safe to turn S-OFF right now, and just leave it off, just in the case if my hboot gets updated or something - I can always revert to an older version.
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
rowebil said:
So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include?
If I turn S-OFF, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version?
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
Click to expand...
Click to collapse
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
squabbi said:
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
rowebil said:
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
Click to expand...
Click to collapse
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
squabbi said:
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
It's safe to go S-Off now and leave it off. hboot updates won't cause S-On
ARHD won't update your hboot.
If your hboot is updated, you must be already S-Off to downgrade.
You are on 1.44 right now. If you go s-off now, you will remain s-off even after accepting OTAs, and you can downgrade your hboot whenever you feel like. On the other hand, if you are s-on right now, and accept an OTA, you'll be upgraded to the locked down 1.54, on which you can't get s-off, nor can you downgrade.. What I suggest is going s-off right now, and doing whatever flashing you want to do.. Beware, with s-off, you can permanently brick(hard brick) your phone. If you ever want to go back to s-on, flash an RUU of ONLY 4.1.2. All roms work with s-off, so no need to worry
Sent from my HTC One using Tapatalk 4
rowebil said:
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
Click to expand...
Click to collapse
An ruu should, but if you don't want to factory restore, you can just flash the ruu.
Sent from my One using Tapatalk 4

[Q] GPe reversal / Software Question

Hi guys,
i currently have a UK Vodafone HTC One MID PN071000 fully converted to GPe, unlocked and S-OFF through Revone. I'm looking to go back to stock as per the following thread:
http://forum.xda-developers.com/showpost.php?p=43460011&postcount=2
I can't find a Vodafone UK RUU but can find a European 1.28.401.7 version. In the above thread he states that if you can't find your carrier RUU to flash a 1.29 ROM.
So, if I flash the 1.44 HBOOT and then run the 1.28.401.7 RUU, will this bring me back to stock (sense) or do I need to find a 1.29 ROM?
I know these have been done to death a bit but I didn't want to annoy the OP of the above thread by adding yet more pages to it.
Thanks in advance for any help on this
I'd flash the 1.28.401.7 RUU to get back to 4.1.2 and then restore a Vodafone stock Nandroid backup (or your own one you made before doing anything )
Then change the CID back to VODAP001 if needed, change the MID back to the EU handset and flash the stock recovery again and you should be good to go...depending on the Nandroid you can find perhaps do they OTA updates with the stock ROM until you get to a comparable version you can restore a nandroid with (if that makes sense)
EddyOS said:
I'd flash the 1.28.401.7 RUU to get back to 4.1.2 and then restore a Vodafone stock Nandroid backup (or your own one you made before doing anything )
Then change the CID back to VODAP001 if needed, change the MID back to the EU handset and flash the stock recovery again and you should be good to go
Click to expand...
Click to collapse
Cheers Eddy,
unfortunately I was a plonker and never backed up but i'm fine with it being on the standard EU software rather than Vodafone's own.. just want sense back. Main reason for asking was unsure if there was a different hboot for software prior to 1.29.
thanks again
Eldwafio said:
Cheers Eddy,
unfortunately I was a plonker and never backed up but i'm fine with it being on the standard EU software rather than Vodafone's own.. just want sense back. Main reason for asking was unsure if there was a different hboot for software prior to 1.29.
thanks again
Click to expand...
Click to collapse
Just stay S-Off !!
Don't go back to S-On EVER otherwise you won't be able to use RUUs etc.
No plan to go s-on, just want sense back
Sent from my HTC One using Tapatalk 2
Gah! Poxy error 170. Will investigate tomorrow
Sent from my HTC One using Tapatalk 2

[Q] Where do I start?

So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
From what I've read, having HBOOT 1.54 basically means that you can't S-off your device (as this is only available for 1.44). This means that you won't have access to deeper customisation for your phone (flashing different firmware and changing CID). CID determines what region your phone belongs to so this translates to how early you can get official OTA's as some regions get updates earlier than others. Also, if you want to fully transform your phone into a Google Edition HTC One, this is only open to units with a specific CID.
As for firmware, not really clear on what the differences between firmwares are but you can still flash different radios which are a component of firmwares (thus getting some of the benefits of newer firmware anyway).
That being said, you can flash the whole range of custom ROMs and kernels available on these forums provided that you've unlocked your boot loader. Directions for this can be found on the HTC website.
If you want an optimised stock ROM, try ARHD Sense which is basically your stock ROM with many performance improvements (especially when it comes to signal). For more customisation on Sense, you can try ViperOne.
Honestly there are so many excellent ROMs here that you can easily lose days trying every single one. The Google Edition ROMs are excellent too.
Hope this helps!
Sent from my HTC One using XDA Premium 4 mobile app
Thank you both for detailed replies! This helped me ease my mind on the HBOOT-thing. Thanks!
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Michiel0211 said:
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
Click to expand...
Click to collapse
All you have to do is unlock your bootloader via htcdev.com (note, this will wipe your data) and then flash a custom recovery. You can use this tool http://d-h.st/mas to simplify the process.
CoryTallman said:
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
sixty_oz said:
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
No matter what, you should stay s-off, it does not affect OTA's or RUU's in any way whatsoever. To flash any RUU, you need to be with a cid of 11111111
It's not possible for you to flash an ruu for something else and then flash the rogers ota I don't think

[Q] Developer Edition flashed to GPE, back to Stock?

I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
docdoc518 said:
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
Click to expand...
Click to collapse
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
n1234d said:
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
docdoc518 said:
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
Click to expand...
Click to collapse
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
so as long as the you are s-off, you can ruu to any version even if you are at 1.54 hboot?
n1234d said:
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
EddyOS said:
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
Click to expand...
Click to collapse
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
docdoc518 said:
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
Click to expand...
Click to collapse
Follow what eddy says, he's the man @eddy, how does the hboot version make a difference??
Sent from my iPod touch using Tapatalk
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
EddyOS said:
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
Click to expand...
Click to collapse
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
You should be fine on that HBOOT, just try it and if it works it works! If not, you'll get an error and then you just following the second post in the GPe conversion thread
docdoc518 said:
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
Click to expand...
Click to collapse
Yep, go ahead and try, if it gives you an error, post back.
AFAIK, the dev edition BS_US001 gets OTAs the quickest, so you could keep it at that. SuperCID will allow you to flash any RUU/OTA, even of a different region/MID/CID
Nope, you're not being a pain We're all trying to learn and help here
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
docdoc518 said:
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
Click to expand...
Click to collapse
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
EddyOS said:
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
Click to expand...
Click to collapse
Newbie move I suppose :angel: haha
I've been rooting and flashing ROMs on my Androids since the G1/Dream believe it or not, but with every new phone/manufacturer there's always new terminology and steps to be taken so I feel like I start over every single time, which honestly isn't much of a bad thing, keeps things exciting (even though HTC made the G1 but that was what feels like ages ago now)
Thanks again guys, it's hard not to feel intimidated but it's been an extremely pleasant experience learning from you. This is why xda is by far the best site you can find for these things.
Cheers

Categories

Resources