Database Develop

Need help, Not sure what to do!

Hey guys so another newb fail here, essentially I rooted my phone and installed a cmd rom and messed my phone up. Went through all the steps in trying to fix it, ruu etc but the ruu was out of date? Or my phone needed a different version. Anyway now my internal storage isn't mountable and I can't do anything. Very worried I ruined my phone! Does anyone have any advice?

A little more info would be helpful. Like what ROM exactly did you flash? Were you on the latest 1.31 RUU? Did you try flashing a 1.29 RUU?

babymatteo said:
A little more info would be helpful. Like what ROM exactly did you flash? Were you on the latest 1.31 RUU? Did you try flashing a 1.29 RUU?
Click to expand...
Click to collapse
It was this rom http://forum.xda-developers.com/showthread.php?t=2356654
once I installed that everything went wrong, but I found a way to reboot because I made a backup and it saved to my phone and then i installed them7spr-RootBox-JB-houstonn rom, that worked for a bit but I had no service at all. So I tried to do the RUU trick but didn't realize the numbers didn't match the 1.31 as it prompted (it was 4 in the morning and I was really worried so I tried everything) so that crashed and my bootlock was locked, I then unlocked it again and when I tried to turn it on it would just load the rootbox rom's loading screen then power off. But in short yes, I was on 1,31 and tried flashing to 1.29

Got a little update, so I downloaded http://forum.xda-developers.com/showthread.php?t=2368907 and went into cmd and typed in fastboot flash recovery boot.img and got it to start loading the rom but it crashes after about 2 minutes. I can't go into recovery mode anymore, I'm assuming the flash wiped it clean? No idea what to do next. Any insight would be amazing!

1. Never flash ROMS that aren't made for your phone. ARHD is made for GSM variants of the HTC One only. I believe ARHD was also available for CDMA in point in time, but not anymore
2. You can't go back to previous RUU's unless you have S-off
Have you tried to RUU to 1.31? Did you re-lock your bootloader first? If not, do that first and you should be fine.

babymatteo said:
1. Never flash ROMS that aren't made for your phone. ARHD is made for GSM variants of the HTC One only. I believe ARHD was also available for CDMA in point in time, but not anymore
2. You can't go back to previous RUU's unless you have S-off
Have you tried to RUU to 1.31? Did you re-lock your bootloader first? If not, do that first and you should be fine.
Click to expand...
Click to collapse
I haven't been able to find a 1.31 RUU, I relocked it but yeah. Just can't find the RUU

twozilla said:
I haven't been able to find a 1.31 RUU, I relocked it but yeah. Just can't find the RUU
Click to expand...
Click to collapse
I can help you when I get home from work
Update: Check PM
Sent from my HTCONE using xda app-developers app

Help too
bigdaddy619 said:
I can help you when I get home from work
Update: Check PM
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I can't seem to find the Sprint HTC ONE 1.31 RUU anywhere so I can use the program to fix my phone since I wiped the internal storage before pushing a rom to the device. OTG doesn't work. I have TWRP installed and I can get into fastboot, but adb isn't working at all. Any help??

srefsn said:
I can't seem to find the Sprint HTC ONE 1.31 RUU anywhere so I can use the program to fix my phone since I wiped the internal storage before pushing a rom to the device. OTG doesn't work. I have TWRP installed and I can get into fastboot, but adb isn't working at all. Any help??
Click to expand...
Click to collapse
Follow the guide posted here
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

srefsn said:
I can't seem to find the Sprint HTC ONE 1.31 RUU anywhere so I can use the program to fix my phone since I wiped the internal storage before pushing a rom to the device. OTG doesn't work. I have TWRP installed and I can get into fastboot, but adb isn't working at all. Any help??
Click to expand...
Click to collapse
Check PM

Ruu to 1.29

I tried to RUU to 1.29 to go back to stock unrooted. I relocked my bootloader and went to install the RUU and it said Bootloader version error. Please get the correct Rom Update Utility. i am on 1.31. Any help is much aprreciated!!

XCrunner23 said:
I tried to RUU to 1.29 to go back to stock unrooted. I relocked my bootloader and went to install the RUU and it said Bootloader version error. Please get the correct Rom Update Utility. i am on 1.31. Any help is much aprreciated!!
Click to expand...
Click to collapse
You have to be S-Off

Follow this http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

EmSeeMAC said:
You have to be S-Off
Click to expand...
Click to collapse
is there a way to do this without recovery

XCrunner23 said:
is there a way to do this without recovery
Click to expand...
Click to collapse
I'm not sure, I'm trying to figure this out myself

I did it without recovery just a few hours ago due to new touch panel of 4.3. I booted into bootloader and ran the RUU while on Fastboot USB option! It'll go from there

XCrunner23 said:
I tried to RUU to 1.29 to go back to stock unrooted. I relocked my bootloader and went to install the RUU and it said Bootloader version error. Please get the correct Rom Update Utility. i am on 1.31. Any help is much aprreciated!!
Click to expand...
Click to collapse
I had the same problem. First time I tried I realized I forgot to relock my bootloader so I took care of that then the second time I tried it failed again with the same error you got. I've ruu before and never had this happen. Luckily my phone didn't get wiped.
Sent from my HTCONE using Tapatalk 2

If you are ever attempting to downgrade the firmware you n yet be S-Off. If you are S-Off then there is also no need to relock bootloader when running an RUU. Now, if you are attempting to go back to Locked without Tampered or Relocked then you must lock it before running RUU but I would honestly say that it is better to stay S-Off after doing it once because it is east to go back to S-Off and you don't need to be rooted to go back to S-Off and at the same time you will always be able to downgrade if need be if you want to unroot properly.
Sent from my HTCONE using Tapatalk 4

[Q] using RUU on HTC One M8 HK

I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!

cristhefur said:
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
Click to expand...
Click to collapse
You can use the RUU with S-ON as long as it is not an older version than what is already on your phone - I believe you are probably talking about 1.54.654.9 right? Check the about settings on your phone to see if you have upgraded from that (1.54.654.13 or 1.54.654.15 or the 2.16 something).
If the phone version is newer, you will not be able to use the RUU without S-OFF. Since you actually have the HK version, you will not need to change your CID. Successfully running the RUU will flash all the major partions, radios, and more and will bring you completely back to stock. It will also wipe your data/media partition (internal SC card) so make sure you backup anything you need to keep.

Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app

cristhefur said:
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
The RUU will actually remove the TAMPERED banner because that flag is in mmcblk0p6, named "pg2fs", which is one of the images that the RUU overwrites. UNLOCKED, if you have it, will remain because that flag is mmcblk0p2, named "pg1fs" which does not get overwritten by the RUU. It can be removed by hex editing that block with an echo command http://forum.xda-developers.com/showthread.php?t=2708571
If you are already unlocked, rooted, and have version 1.54.654.9, I would highly suggest you run sunshine and get S-OFF before you run the RUU and update the OTAs; who knows if that exploit will be blocked in further updates.

I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app

cristhefur said:
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Not sure since I did it on .9, but I would definitely try it - in fact, if you are on 15, the only way you will be able to run the .9 RUU is if you S-OFF.
Sunshine will not ask you to pay until it has run compatibility tests and verified that it can get S-OFF on your phone - so run it and if you see the message to pay, you are good to go. Having S-OFF just makes things SO much easier.
Just follow the directions on the sunshine site http://theroot.ninja/ and run it entirely from the phone; couldn't be easier. You will need to sideload the APK, easiest if you just run the command "adb install SunShine-latest.apk" after making sure Unknown Sources is checked in your phone settings.

Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app

cristhefur said:
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
It's the other way around - look a few posts up - there's a "not older than your phone's version" in front of that statement.
To be clear, the .9 RUU will not work on a .15 phone if you are S-ON, you must be S-OFF to do that. However, if you had a .15 RUU (which doesn't exist) it would work on a .9 phone.
Sorry about the confusion. That is just one of the benefits of being S-OFF (not to get sidetracked but my favorite benefit is being able to flash from hboot or fastboot rebootRUU with the bootloader locked)

Ah yes, I see that now- my mistake. I guess I'll s-off tomorrow afternoon then. Thank you very much for your help!
Sent from my 831C using XDA Free mobile app

It's encouraging that the Sunshine devs recently made fixes to deal with Sprint 4.4.3 M8 devices - that's version 2.16.654.4 which is higher than yours, so I think you have a good chance of success. Good luck!

Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.

AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
I'm fairly certain that if you're S-on you can only run a RUU with the same software & firmware version that's installed on the phone. It was that way on the EVO LTE and I'm fairly certain that's how it is now.
Sent from my HTC M8

you may want to try http://firewater-soff.com/ first, if nogo, then sunshine
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
nope, you can't flash a older RUU if you're s-on

Oh ok...my apologies.
Is there a reason that my phone boots directly into the bootloader every time that I relock it?
I am unable to boot into anything after using fastboot oem lock, and it only loads the bootloader until I run the RUU (granted, this was before the latest update).

So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?

neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.

PillowMetal said:
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
Click to expand...
Click to collapse
Is it possible to flash the recovery from SD card or do I need to use my computer?

neudof said:
Is it possible to flash the recovery from SD card or do I need to use my computer?
Click to expand...
Click to collapse
When you download say TWRP from their webiste, you get an image file (IMG) that is meant to be flashed using fastboot from your computer. But you can rename it to "recovery.img", place that in a zip file along with an android.txt file with specific contents onto your external SD Card, and then you can flash it from the bootloader (if you are S-OFF). The file has to be specifically named as well - e.g., the Sprint HTC One M8 is "0P6BIMG.zip".
If you don't have an external SD Card, you may also be able to flash from the bootloader using a powered USB-OTG cable (like we did on the M7). Again, this is only if you are S-OFF, otherwise you will have to fastboot flash the image from your computer because bootloader flashes with S-ON have to be signed.
One last method that doesn't require S-OFF, is to copy the image file anywhere on internal or external SD cards, then use the "dd" command to copy the image over your recovery block (specific numeric device block depending on phone) using either your computer or a terminal emulator on the phone.
So yeah, you have options.

Update: I achieved S-Off as suggested, locked my boot loader using an adb command from another thread then ran the HK .9 RUU. I went through the 3 updates then took the phone to sprint, had no problems at all. Thanks for your help guys. :thumbup:

Trying to go back to stock. Failing...

Hello everyone,
I've been trying to get back to stock on my Sprint HTC One. I have tried using the RUU in this thread: http://forum.xda-developers.com/showthread.php?t=2795856 and no luck. I am HBoot 1.55, S-ON, and running a stock rooted rom that is on 4.4.2
So here is what I tried. I relock my bootloader and proceed to run the RUU, but 2 times I get stuck on 4% so I have no luck. I tried getting S-Off and maybe that could help me bring back to stock, but that did not work either. Really need to get this phone back to Stock, any help is appreciate it, no one responded in that thread so I'm asking here. Thanks in advance.

You'll need to flash the Full Firmware first.
If it still gets stuck try a different USB Port...USB 2 work best or try a different PC.

BD619 said:
You'll need to flash the Full Firmware first.
If it still gets stuck try a different USB Port...USB 2 work best or try a different PC.
Click to expand...
Click to collapse
That is what the video at the bottom of the first post on that thread is about, correct?
Don't I have to be S-Off for that? It says on the video that I have to, and I am not.

PaoloMix09 said:
That is what the video at the bottom of the first post on that thread is about, correct?
Don't I have to be S-Off for that? It says on the video that I have to, and I am not.
Click to expand...
Click to collapse
Use This Firmware
You will need to re-lock your bootloader (fastboot oem lock)
Flash firmware (follow the video)
Run the RUU and you will be back to stock.
You do not need to be s-off to do either.

BD619 said:
Use This Firmware
You will need to re-lock your bootloader (fastboot oem lock)
Flash firmware (follow the video)
Run the RUU and you will be back to stock.
You do not need to be s-off to do either.
Click to expand...
Click to collapse
Trying to flash it but it won't . Fails checking signature. "Signature verify fail"
Sent from crispy tocino

PaoloMix09 said:
Trying to flash it but it won't . Fails checking signature. "Signature verify fail"
Sent from crispy tocino
Click to expand...
Click to collapse
Did you re-lock your bootloader?
Is the firmware in your adb/fastboot/platform tools folder?

BD619 said:
Did you re-lock your bootloader?
Is the firmware in your adb/fastboot/platform tools folder?
Click to expand...
Click to collapse
Yes sir. Relocked, only that at the top it says "security warning." I renamed the folder to firmware.zip and it is on the platform tools folder. Did all the commands, but the second time I run the same command (like it says on the video) it gives me the error I mentioned and I don't even get the loading bar on the phone. Tried 3 times, no luck.
Sent from crispy tocino

Check PM

Same problem actually
BD619 said:
Check PM
Click to expand...
Click to collapse
I am actually having the same issue as described above, and cannot for the life of me figure out what I did wrong.
Any insight?

saxman126 said:
I am actually having the same issue as described above, and cannot for the life of me figure out what I did wrong.
Any insight?
Click to expand...
Click to collapse
So Hboot 1.55, S-ON, and can't go back to stock?
Go to this: http://forum.xda-developers.com/showthread.php?t=2658910
Download that RUU. Now, go into fastboot and relock your bootloader. Flash the firmware on that thread through fastboot, there's a video there showing you how. After that is done, go back to fastboot and you can run the RUU you downloaded from that thread. That's what I did and worked like a charm. Recommended if you use USB 2.0

PaoloMix09 said:
So Hboot 1.55, S-ON, and can't go back to stock?
Go to this: http://forum.xda-developers.com/showthread.php?t=2658910
Flash the firmware on that thread through fastboot, there's a video there showing you how. After that is done, go back to fastboot and you can run the RUU you downloaded from that thread.
Click to expand...
Click to collapse
Hi. You mean flash 4.06.651.4 version at first and then flash 5.05.651.2 version ? Is it update HBOOT from 1.55 to 1.56? What about warning message on that thread "***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)"
I have. Hboot 1.55, S-on, Custom ViperOne 7.0.1

kai82 said:
Hi. You mean flash 4.06.651.4 version at first and then flash 5.05.651.2 version ? Is it update HBOOT from 1.55 to 1.56? What about warning message on that thread "***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)"
I have. Hboot 1.55, S-on, Custom ViperOne 7.0.1
Click to expand...
Click to collapse
Just flash firmware 4.06.651.4 (you'll be on hboot 1.56) and then run that RUU. Don't worry about 5.05.651.2 firmware or RUU.
Make sure you relock your bootloader before anything.
Whenever the RUU is done and you're back in stock, you'll get the OTAs to 5.05.651.2, just telling you exactly what I did that worked, I also had a lot of trouble getting back to stock/unrooting.
Sent from crispy tocino

(Q) Restoring HTC M7 back to Rogers Stock.

Hi guys I have acquired a Rogers M7 that powers on but then just sits at a blank screen after boot. I can access fastboot and als flashed twrp recovery, I m on OS version 7.17.631.7 lollipop I believe, it is S-ON , HBOOT 1.61, I unlocked the bootloader using the HTCDEV.
I have tried to getting it past the blank screen by using the latest RUU I could find, 4.19.631.9 but that did not work, I think cause the s-on will not allow a downgrade, I also tried using the One_All-In-One_Kit_v3.1 to side load a zip but same problem, fails verification. I have also tried a nandroid back by copying it to the internal memory but still not working.
Can anyone help me fix this phone so it can be usable again? or provide me with an RUU that will work.
Thanks

carlos1984 said:
Hi guys I have acquired a Rogers M7 that powers on but then just sits at a blank screen after boot. I can access fastboot and als flashed twrp recovery, I m on OS version 7.17.631.7 lollipop I believe, it is S-ON , HBOOT 1.61, I unlocked the bootloader using the HTCDEV.
I have tried to getting it past the blank screen by using the latest RUU I could find, 4.19.631.9 but that did not work, I think cause the s-on will not allow a downgrade, I also tried using the One_All-In-One_Kit_v3.1 to side load a zip but same problem, fails verification. I have also tried a nandroid back by copying it to the internal memory but still not working.
Can anyone help me fix this phone so it can be usable again? or provide me with an RUU that will work.
Thanks
Click to expand...
Click to collapse
Right, you can't downgrade when S-ON. Relock your bootloader and flash the 7.17.631.7 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I would also recommend that you stop using toolkits and learn to use adb and fastboot directly from a command window. These tools are not up-to-date and will most likely cause some issues.

thanks
alray said:
Right, you can't downgrade when S-ON. Relock your bootloader and flash the 7.17.631.7 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I would also recommend that you stop using toolkits and learn to use adb and fastboot directly from a command window. These tools are not up-to-date and will most likely cause some issues.
Click to expand...
Click to collapse
I am familiar with adb commands but not with fastboot its elt, i do not remember using on my samsung phones or lg so I was having problems so i decided to be lazy. Thank for the reply will let you know how it worked out.

carlos1984 said:
I am familiar with adb commands but not with fastboot its elt, i do not remember using on my samsung phones or lg so I was having problems so i decided to be lazy. Thank for the reply will let you know how it worked out.
Click to expand...
Click to collapse
If you have already used adb then you won't have any difficulty using fastboot, it's basically the same thing and the commands to flash the ruu are posted in the link above. Just don't forget to use the fastboot version from that thread or it won't work.
Sent from my HTC One using XDA Labs