Develop Bugs

Unrooting

Hi!
My phone broke and now I want to try to get it fixed with warranty. I'm not sure if warranty still is available if I use root so I want to unroot.
I have read that all I need to do is flash the RUU, but which one? http://forum.xda-developers.com/showthread.php?t=824357
And what will flashing it do? Will it remove CWM and everything else I was using to root? I remember that I flashed radio 2 times, had S-OFF and E-ON.
And then I will simply run System Update? Because it seems that RUU are firmwares that phones are shipped with.

yea, just flash a RUU.
Make sure you install the original RUU for the type of your DHD (i.e. WWE, Voda,T-Mobile...)
and if your phone is S-OFF, make it S-ON - S-OFF / S-ON GUIDE (guide for S-ON is at the end of the 1st post). Go into bootloader and make sure you have S-ON
--your recovery will be restored to original HTC recovery

Oh, but which RUU I need to flash? I remember I needed to do a downgrade and I think it was 1.72.405.3, not the R2, but I'm not sure.

Well, when you had your phone, was it branded?
if so, you need to find a brand-specific RUU.
If not, then WWE RUU is fine.
i would suggest the 1.32 FW (because S-ON requires temproot from Visionary+), then follow the guide to S-ON

What about radio? I have flashed the leaked gingerbread radio, wouldn't they be able to see that I have flashed a newer radio? Or the RUU flashes radio also?

RUU flashes radio too. But after flashing the RUU have a look into the bootloader, the device might still be S-Off. For S-On you need to root again and Use the easy radio tool to make S-On again. Then use the RUU again.

It still was S-OFF, but used Visionary and Easy Radio Tool to get S-ON. A brand new phone
Thanks!

Does it work the RUU to flash even if I come from an ext4 ROM (ARHD 5.1.9)?
Or do I need to format first by cwm 3.0.2.6 so that it is ext3 again?

No one any advice?

[Guide] EVO Revert to stock + S-ON after Gingerbread

This took me all day to figure out so I'm making a guide. The 2 Big problems I had were getting the S-on patch to work and the newer Hboot that came with gingerbread refusing to downgrade to an older PC36IMG.zip.
The main reason I wanted to return to stock was for a repair, last time i did everything except s-on and the guy noticed it and black listed my esn.
Make sure you are prepared before you continue! Once you flash your radio your phone wont boot into the OS.
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Download this file I got this off a youtube video for the incredible and replaced the files with their EVO specific counterparts
Open the zip and move flash_image and mtd0.img to your sdk/tools/ folder
boot into your custom recovery and mount /system/
open up a command prompt in your tools folder
(in windows7 hold shift and right click on /tools/ there will be an option to "open command window")
Run the commands in the commands.txt file. FYI you can paste into command prompt with right click.
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Click to expand...
Click to collapse
After this you can move your stock PC36IMG.zip to the root of your SD card and reboot into your Hboot Bootloader. If everything was done correctly it should now accept PC36IMG and downgrade to stock.

Great job! Do you think there will be an easier way in the future? I don't think I would be able to do this.
Sent from my PC36100 using Tapatalk

If you run the 3.70 RUU while still s-off, will it replace the hboot with an older version? It seems like it should, but I'm confused by the 6.16 hboot.
I haven't actually ran revolutionary, so this is all theory, but I thought unrooting/s-on would work like this:
Run the RUU for 3.70. I don't have much experience with RUUs, but if they don't include radios, you would then need to reflash recovery and downgrade the radio. After reflashing etc, then flash the s-on zip. Then rerun the RUU for 3.70 to get rid of your custom recovery, or run the RUU for 4.24, since once you're s-on you can't downgrade & every RUU will be a downgrade from 6.16 hboot.
Now this may be entirely wrong, but I was just curious if it would work. I've been rooted for a while, and unrooting and s-on would be much easier for me. Even though it sounds like a pain, it still sounds more noob friendly than the version in the OP.
Either way, great job on putting this together. I know that a lot of people are curious about unrooting from revolutionary, so hopefully you've cleared some confusion.
Sent from my PC36100 using Tapatalk

Sfork said:
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Click to expand...
Click to collapse
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.

Captain_Throwback said:
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.
Click to expand...
Click to collapse
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk

plainjane said:
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?

Captain_Throwback said:
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?
Click to expand...
Click to collapse
Hboot 6.16 will not downgrade or flash S-ON currently.

[Q] Bootloader version error

I have unlocked my OneX, root it using PaulBrien's method, and then stripped off all the sense stuff. I didn't install any custom rom all these while.
Then I decide to revert back to stock. I do the following
1. flash back stock recovery
2. lock back the one-x using fastboot oem lock
3. run the ruu executable.
It worked as I managed to complete the ruu flashing process, and proceed with the system upgrade OTA to 1.28
then, I had problem with the rooted 1.28 (again stock 1.28 rooted using Paul's version) so I did a CWM recovery back to my rooted 1.26 ROM.
Now, I decide to flash stock rom back to my OneX, I repeated the steps above, and instead I got this error from the RUU app.
Any reason what has happen? I even tried flash the 1.26 signed boot.img prior to step 3, but it still yield the same problem.
Thanks...

Since you updated to 1.28 you need the 1.28 RUU. When you updated it changed you hboot
Sent from my HTC One X using Tapatalk 2

I didn't know it change the hboot.
can I flash 1.26 hboot over?
strangely, I didn't have the problem the first time round, maybe something went wrong in between.

zenkinz said:
I didn't know it change the hboot.
can I flash 1.26 hboot over?
strangely, I didn't have the problem the first time round, maybe something went wrong in between.
Click to expand...
Click to collapse
i dont think so until we get S-OFF

this problem happen for me
you are only download other ruu
only other ruu download and enjoy

You need the 1.28 RUU as you've done the OTA 1.28 update.
If your version is 1.28.707.10, here is the RUU : http://bit.ly/IjzQwM
Else, please let us know your software version no. and someone will point you to the right RUU.

[Q] Can I install an OTA update for a version older than my phone with S-On?

So I got an M8 recently, unlocked bootloader with HTCDev and flashed a rom without upgrading the firmware, so later I restored my stock backup and downloaded the OTA update which was for 2.22.401.5. But my recovery wasn't stock so it wouldn't flash then long story short I soft bricked and did a factory reset from hboot.
So now I flashed stock recovery but since I factory reset my original backup was gone, and for some reason Wi-Fi does not turn on at all after I did the factory reset. I downloaded a TWRP backup from here http://forum.xda-developers.com/showthread.php?t=2710735 (The Telus one, I am with Telus) and when I go to download the OTA update it gives me the option to download and install 1.55.661.4 instead of the more recent version.
I am S-On and I have read that flashing an RUU for a firmware older than yours will hard brick your phone and I definitely don't want that, so what I'm asking is can I download and install this 1.55.661.4 OTA then install a more recent one afterwards or will that brick my phone? And if so how should I go about updating firmware?
Thanks

FormaldehydeSon said:
So now I flashed stock recovery but since I factory reset my original backup was gone, and for some reason Wi-Fi does not turn on at all after I did the factory reset.
Click to expand...
Click to collapse
Factory reset (wipe data, Dalvik and cached) by definition does not delete internal storage where nandroids are stored. Either you specifically went into TWRP Advanced Wipe settings and wiped storage (which wasn't necessary) or you did a factory reset in bootloader which on a modded phone may corrupt internal storage.
WiFi not working is a known issue with outdated firmware + 2.22 Sense ROM. So updated firmware will fix this.
FormaldehydeSon said:
I am S-On and I have read that flashing an RUU for a firmware older than yours will hard brick your phone
Click to expand...
Click to collapse
This is not correct. With S-on, flashing an older RUU will flash (version check will fail). With S-off, it will not brick the phone, and will actually work correctly (re-image the phone to the older RUU).
But its not clear to me whether your phone even has firmware/software that is "newer" than the RUU or OTA you are referring to. If the hboot and radio was never changed, and the ROM and recovery were returned to the "older" version, then nothing is in fact "newer" anymore.
RUU is actually a safer proposition than OTA in my opinion. But do you know for fact that an RUU exists for your version (not many versions do)?
OTAs with S-on, should work, but do you know for a fact that everything on the phone (ROM, recovery, hboot, radio, etc.) is now restored (or never changed) to whatever software number directly preceding 1.55? If not, with S-on the OTA will fail version check and not install. Further, if OTA is not installed in sequence, this actually is a brick risk (in contrast with RUU). Although the last part is probably only possible with s-off.

Thanks for the reply, how can I check the version of my recovery to make sure it matches my rom version number? I am using recovery downloaded from here http://forum.xda-developers.com/showpost.php?p=52734619&postcount=14 but the recovery doesn't mention a version number. Is it safe to assume that the recovery and nandroid backup linked in that post are for the same version, since they both came from the same person's backup?
In phone settings it shows my software version number as 1.12.661.17, and in hboot my radio is 1.16.2133156, hboot version is 3.16, but am I correct in assuming that my radio or hboot versions could not have changed, since I don't have s-off and haven't flashed anything other than the recovery and TWRP backup in the linked post? Do these version numbers match up properly for me to try downloading the OTA? Thanks again

FormaldehydeSon said:
Thanks for the reply, how can I check the version of my recovery to make sure it matches my rom version number? I am using recovery downloaded from here http://forum.xda-developers.com/showpost.php?p=52734619&postcount=14 but the recovery doesn't mention a version number.
In phone settings it shows my software version number as 1.12.661.17, and in hboot my radio is 1.16.2133156, hboot version is 3.16, but am I correct in assuming that my radio or hboot versions could not have changed, since I don't have s-off and haven't flashed anything other than the recovery and TWRP backup in the linked post? Do these version numbers match up properly for me to try downloading the OTA? Thanks again
Click to expand...
Click to collapse
I don't know how else to confirm recovery. But if you used the nandroid from that same post, its probably safe to assume they go together.
You are right that with S-on, you can't have modified hboot or radio. So if you haven't gotten any OTAs, and you were originally on 1.12 when you got the phone, those should be okay.
In this instance S-on is kind of a good thing. If the OTA finds anything amiss, it will just fail whatever security check and fail to install. Although S-on is the whole reason you're at this point in the first place.

I was able to install the OTA without problem, as well as download and install the 2.23 OTA, thanks for all your help!

I F*cked up (GPE 5.0 to Sense) Help!

I originally had a stock sense M8 (bought it first day) but since October, I changed my phone to GPE (GPE Firmware and everything) and have been using 5.0 eversince using SkyDragon rom. Ran into issues a few weeks ago, and i've been waiting hard to go back to sense and use the newer 5.0 sense version.
However, today I ran into multiple issues, I thought installing the latest Sense Lollipop firmware and installing the latest ARHD 5.0 rom would do the trick, sadly that did not work.
I flashed the latest sense firmware and the ROM only for it to boot saying my Data is corrupt and i have to reset my phone, i say okay(was going to do that anyway) but then I access my recovery (TWRP) and my Internal storage/Cache/Data will not mount. I tried going back to GPE (atleast so my phone would work) but I cant do that either because even with the GPE firmware, the data partition wont mount and my internal storage shows 0 MB in TWRP, now im just stick in a bootloop/bricked device for hours. Any help would really be appreciated...thanks a lot.

Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.

redpoint73 said:
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
Click to expand...
Click to collapse
Thanks for your reply, to get this clear:
I should flash the Dev Edition RUU from (http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777) (3.28.1540.5) and then update the firmware to 4.16.1540.8 by just flashing that separate zip. However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery(Im terribly sorry if this sounds dumb, but my phone is soft bricked and I really need to get everything right this time), Is that the case if I flash the dev edition RUU? Thanks again.

Austin3161337 said:
However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery
Click to expand...
Click to collapse
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).

redpoint73 said:
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
Click to expand...
Click to collapse
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all, is there anyway I can install the RUU by not really needing to connect the phone to the computer? (Put the file in the external SD and install it via the bootloader maybe?) Any tips on that? Thanks

Austin3161337 said:
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all
Click to expand...
Click to collapse
The phone doesn't need to boot into OS to run the RUU. It just needs to be able to get into bootloader/fastboot mode, which it can if the screen comes on.
If the device doesn't show on your PC, its a different issue. USB connectivity issue is almost always a driver issue. Install HTC Sync and HTC drivers, if you haven't already. Or uninstall and install them again.

I have a similiar issue. I had a tombile ruu.zip that a flashed as a 0P6Bimg.zip a kitkiat sense version for tmobile. Everything is cool and it runs fine. When I change cid and mid then flashed the sense lollipop firmware I lost my internal memory and twrp read storage as 0mb.
So idk

I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.

Austin3161337 said:
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Click to expand...
Click to collapse
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?

redpoint73 said:
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
Click to expand...
Click to collapse
I already had HTC Sync installed, had to boot into Fastboot USB for the thing to get recognized.