Going back to stock after GE conversion - One (M7) Q&A, Help & Troubleshooting

So today I turned on my phone and I have noticed that there is about an inch in depth line across the screen which isn't picking up touches anymore, so I rung HTC and it's going in for an in warranty repair on Monday. Of course, I need to convert it completely back to stock, but the only problem is I converted it to a Google Edition, changing the CID and, more importantly, the MID. I followed this thread when doing it originally, but I wanted to know if anyone knows if I can flash the same ENG HBOOT onto my GE phone and not have it brick on me? Then I can change my MID and CID back and flash the EU RUU for my phone and send it in on Monday with no issues...hopefully.
Or is there an easier way? Will they check the MID? I changed it to PN0712000 from PN0710000 and CID to GOOGL001 from HTC__001. If I just changed the CID and left the MID, would it matter? Would I still get OTA's on the stock Sense ROM on that MID?
Thanks in advance.
EDIT: So of course I've tried flashing an RUU in the meantime, but I can't. I've tried 2 of those .exe ones but they both fail, I'm assuming because of my changed model ID. I can't find an unencrypted one either that I can change the headers of so I can flash it...ugh. This is becoming a massive pain the bumholey.

RUU's fail because of MID? I thought if you have s-off any RUU would work? I need to know this too cause I might have to RUU and send in for warranty.

I don't know. But I've gone back to complete stock now, great! Of course, there's another problem FFS.
WiFi now doesn't work at all, it just says error. Fabulous. This only happened once it did a system update to the 1.29 update. Now it's asking me to update to 2.24, but I don't have enough data left on my usage to download it to see if it'll fix it, so now I don't know what to do. I've tried Googling this issue, and it appears as though some people might have had it, but I can't find a solution or anything. HALP!
EDIT: I reflashed the RUU and the WiFi is working again. I'm going to try the update again and see if it causes WiFi to not work again, if so then...I don't know what I'll do. Flash OTA's through CWM and see if it fixes it...?
EDIT2: And this time the WiFi works fine. Something must have happened the first time...but all's working fine now. Hooray! Apart from the screen, which is why I'm sending it back to HTC...

May I ask You how did You manage to go back to stock ROM? I'm on stock 4.3 GE Now. I've got S-OFF and bootloader locked. When I go to the fastboot mode and start the RUU (exe file) goes fine, but half way through (when It's moving the ROM to the internal memory) error shows up saying there are some (no specific details) problems that I can fix, but when I do all 4 fixing steps it doesn't help.
I've taken the stock Sense RUU from here
http://www.androidruu.com/index.php?developer=M7
M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe

I'd love to know how you accomplished this, I've got the same issue going on so I need to revert back to stock using an RUU, but it keeps failing.
can you give us the breakdown of how you did it?

Related

[Q] Can go back to ruu but can't get OTA updates

I downgrade my phone using the downgrade script and i can install roms, s-off and s*on again. Everything fine but getting OTA's. Even I use the Sense 2.1 roms, when I try to check updates it says "no update found" as I noticed I don't have any way to go back my first shipped rom. (Stickied post didn't have original turkish rom, I tried lots of them)
How can I get OTA updates again? I know this is not a big problem but I want to know it anyway.
I noticed the "CID" thing and I think problem is CID itself. Because my CID and RUU differences.. I didn't find any detailed explanation about it. For ex. Is it can be reverted if I change the CID? What is the best CID for the getting updates first? Or are there any other method for OTA?
Sorry if I miss anything.
Any thoughts?
Özgürce said:
Any thoughts?
Click to expand...
Click to collapse
Yes it is probably due to the fact that you are running a RUU that doesn't match your CID and region.
Unless you have SuperCID with a value of 11111111, you will only get notifications when your RUU and CID are correct for a region.

[Q] Htc ruu 1.28 not overwriting orange 1.28.61.7 even after s-off. Please Help

Hi, i am new here and after some help. Have just had my htc one repaired for the 2nd time (blown top speaker ee didn't repair properly so had to go to htc) so now want to go to stock htc_001.
I am on orange and been waiting for the 1.29 update (never going to come) so i carried out s-off on my phone this morning and changed the cid to htc_001. That all went okay and i relocked the phone and put it back to s-on. When i check the cid on the phone and with revone it says htc_001, so that all worked okay.
I downloaded the htc ruu 1.28 from xda and installed it, it when through the checking and installed it all (took about 15mins), i got no error messages it said update successful. The phone rebooted and was wiped clean and had to go through all the settings when you first get your phone. When i go to software version its still running 1.28.61.7 (the orange software) and when i check for updates it says none available. I have tried twice to install the ruu and both times it says successful but won't write over the orange software.
I am not sure what i have done wrong but some help to get my phone onto stock htc so i get timely updates and not having to wait for rubbish orange.
Any help would be greatly appriciated
Thanks Ashley
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
EddyOS said:
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
Click to expand...
Click to collapse
Thanks for the quick reply, I have just double checked it is HTC-001 the only thing i can think of is its because the orange version is a higher number to the htc. Would i have to install a ruu for a different area (asia maybe) and then put it back to HTC_001 and try to update to the 1.28 htc version? I wouldnt want it to be stuck on the wrong country version if it still wont update to the europe version.
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
EddyOS said:
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
Click to expand...
Click to collapse
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
saquib said:
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
Click to expand...
Click to collapse
Looks like I'm having the same issue - did either of you find a solution?
I ended up applying a nandriod backup to get 1.28.
Change cid to super cid 11111111.
saquib said:
I ended up applying a nandriod backup to get 1.28.
Click to expand...
Click to collapse
Cheers - guess I'll go that way too - don't suppose you have a link to the backup - unfortunately the BugsyLawson site is down
Sorry don't have a copy to hand, I also downloaded it from that site.
Ashes20vt said:
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
Click to expand...
Click to collapse
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Rex2369 said:
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Click to expand...
Click to collapse
I managed to sort it out, not sure how I did it really. I tried to flash it manually which it didn't do as it was playing games with me. I tried the ruu with supercid which it didn't work. I put it back to HTC__001 and relocked it then tried flashing manually again, it didn't work so tried afew times but no luck. So I tried the ruu one more time and it worked, I got the 1.29.401.12 ota straight away too. I think trying to manually flash it corrupted something so the ruu was able to overwrite orange. The phone nearly broke me and was about to give in but glad I kept at it though as orange updates are ridiculous.
Thanks to all that helped me with my error of not putting 2 underscores in the cid.
I am just hoping the 4.2.2 updates on my phone okay when it's released soon.

[SOLVED] Some questions about S-OFF and RUU

Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...

[Q] How do I convert a GPE to latest Developer Edition or Sense 6 rom

Thanks in advance for any help... I've searched and come up empty in terms of up-to-date stuff. I'm super-cid, unlocked bootloader, s-off (phone came that way off a private sale) with a RUU conversion to GPE. I want to take advantage of the sense 6 update especially the new battery saving mode. Really wondering weather:
1- downgrading firmware is still a thing coming from GPE and going to the latest Sense 6 roms
2- Weather I should use an RUU or try flashing a custom recovery and a wrong
3- Weather there's any other watch-outs I should know
Change your CID/MID accordingly for Dev edition and run the http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
This will get you going all the way to Sense 6 with a few updates. Do not LOCK boot loader or turn S-ON
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Without further details can't help
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Based on the google searches I've done, this is normal. The HTC RUU installation never actually finishes. You just need to wait until the progress bar stops moving, make a coffee, then reboot and hope you haven't just bricked the phone.
SaHiLzZ said:
Without further details can't help
Click to expand...
Click to collapse
See above--what happened to him is normal.
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
komienski said:
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
Click to expand...
Click to collapse
Change cid to BS_US001 and make sure mid is PN0712000
Sent from my HTC One using XDA Free mobile app

HTC__001 OTA Problem

So I'm no stranger to running RUU's on my device as the amount of times I have changed from Sense to GPE is ridiculous. However I have been thinking about getting the M8 so went back to stock sense, locked everything back up and put S-On. When I turn the phone on everything is fine as normal, and it starts receiving ota's, however it wont update past 4.3. Does anyone know if there are any issues with the HTC ota's for HTC__001? It also won't go past with super cid, yet when I unlock and S-Off again I can convert it to H3G__001(not what it should be but I am with the 3 network) it updates absolutely fine to sense 6, 4.4.2.
If anyone knows anything that might shed some light it would be most appreciated.
Thanks.
v28 said:
So I'm no stranger to running RUU's on my device as the amount of times I have changed from Sense to GPE is ridiculous. However I have been thinking about getting the M8 so went back to stock sense, locked everything back up and put S-On. When I turn the phone on everything is fine as normal, and it starts receiving ota's, however it wont update past 4.3. Does anyone know if there are any issues with the HTC ota's for HTC__001? It also won't go past with super cid, yet when I unlock and S-Off again I can convert it to H3G__001(not what it should be but I am with the 3 network) it updates absolutely fine to sense 6, 4.4.2.
If anyone knows anything that might shed some light it would be most appreciated.
Thanks.
Click to expand...
Click to collapse
That is very strange, got to be something to do with the HTC Servers, however, are you trying to update with super cid or with HTC__001 ? I ask as I e noticed that super cid isn't in any of the android info txt files for the 401 updates, I've returned to stock a few times, and never had any problems, but I always start from the 401 kitkat ruu which is 4.19.401.9
Thanks for the reply, I've used both Cid's in the past and both have updated to sense 6 no problem. The only reason I go back to such an early RUU is to S-On as after 1.28 if you try and S-On your phone becomes a paperweight.
Possibly a server thing I guess, but thanks again.
Sent from my Nexus 7 using XDA Free mobile app
Has anyone else in the UK on HTC__001 had this problem recently?
v28 said:
Thanks for the reply, I've used both Cid's in the past and both have updated to sense 6 no problem. The only reason I go back to such an early RUU is to S-On as after 1.28 if you try and S-On your phone becomes a paperweight.
Possibly a server thing I guess, but thanks again.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
no it doesn't become a brick, unless your using a modified firmware and then you should never s-on, what happens is after HBOOT 1.55 I think it is which will be 3.62.401.XX, if you s-on past that then you get the ***TAMPERED*** flag back.
Ahh ok thanks for that, always good to learn something new.

Categories

Resources