Database Develop

The basics about Unlocked/Rooted HTC one?

Hi,
First of all, accept my apologies in advance if i sound a complete NOOB, cuz really I am. Im just looking for some help regarding the know-how of the phone I just bought.
We dont get locked phones in my country ( and by locked I mean like as u say these At&T and verizone or Sprint etc locked). I bought a silver HTC One and have been using it all fine and easy until I saw this blue HTC one( a used one) SO I exchanged my phone and now I have this blue HTC one...
The info from the software information is:
Android Version - 4.2.2
Sense - 5.0
Software number - 2.24.401.8
HTC SDK API level - 5.34
Kernel version - 3.4.1 - g28df0d6 [email protected] #1 SMP PREEMPT
Build number - 2.24.401.8 CL235216 release-keys
(guess thats all there is to tell)
But apparently it is not working as it should. And by that I mean I tried hard resetting it and a weird screen came on...
it goes like this ....
TAMPERED ... and so on... and then there were other options like to Fastboot, factory reset etc that I could select from the volume keys..
So i got afraid that things are a little bit more technical than I can handle so i dint reset it.
- Now, the thing is I want to know that if my phone is unlocked than what carrier it originally was - whether resetting will lock me to that carrier or not?
- Apparently my phone was rooted ( dont know for sure, although I downloaded the root checker from play store and it says that I have root access ) SO why was it rooted in the first place. CAN it be that by rooting, my phone was unlocked from the carrier?
- IF i want to return to stock, how can I do that?
- Will returning to stock render my phone useless?
- Im upgrading to And 4.3.. but is it safe to do that with the state of my phone...?
By now, Im sounding like a complete BUM even to myself... so... but I really need help...

Unlocked network is not the same as unlocked bootlooter. Rooting will do nothing with the network lock (although there are some apps that can network unlock using root).
As for the screen you saw, that's the recovery screen which is acces via power + vol up, that's normal and is where you can reset your phone. "TAMPERED" means that the bootloader was unlocked before (to allow ROM flashing) but has been relocked to try make it stock again. I guess that means you bought it second hand?
Follow this guide if you wish to return to stock: http://forum.xda-developers.com/showthread.php?t=2358738. Make sure to take note of your CID, which you can see at the top of the recovery screen or using CID getter, and getting the RUU that matches it.
Once you followed that guide you should have a completely stock device that's got a locked bootloader, S-On and without the TAMPERED flag (so HTC does not know it's been rooted) with the stock firmware. Then just boot into the phone, set it up, and check for updates in the settings and it will upgrade to the latest version for your CID (either 4.3 or 4.4).

Ok, according to the CID getter, my CID is HTC_001, so now,
I go find the RUU for the HTC_001 and then do all that what was said above. I wanted to ask one thing before doing anything.. I bought this phone second hand.. Yes.. how can i tell that whether its and international version or an unlocked version for some network. It has no tell-tale logos of any network on it. Is there any sure shot way of telling which one is it?
Here is the info from the TAMPERED screen.. just thought about posting it so that if could further help in anyway..
***TAMPERED***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 0-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.8
eMMC-boot 2048MB
Aug 9 2013, 16:15:36.0

CID tells you if it's been locked down to a carrier. HTC__001 (two _) is the unlocked UK version. So it's never been locked to a network, and I guess the previous owner just wanted to play around with cutsom ROMs.

I have managed to S-off my phone and downloaded the files required.. Im not sure about one thing.. is the kernel on my phone a stock one or what?
I have this Kernel version - 3.4.1 - g28df0d6 [email protected] #1 SMP PREEMPT
which one is it?

hey.. can someone point me out to the right RUU for my phone..?
Im tryin to match all these things but somehow one or the other stays diff..

rteepu said:
hey.. can someone point me out to the right RUU for my phone..?
Im tryin to match all these things but somehow one or the other stays diff..
Click to expand...
Click to collapse
You need the 1.28.401.7 ruu.exe from here http://www.htc1guru.com/downloads/ruu-file-downloads/
but you will need to downgrade hboot to 1.44 before.

Now.. DO I REALLY NEED TO REVERT BACK TO STOCK?
I mean, i just found mod (maximus HD) inside my phone and flashed that using cwm.
I have no problems so far and I do not have to send the phone back for warranty or anything, so do i really need to get back to stock? Cuz i think for that my expertise are lacking atm. I just wanted to update to the latest android... but figure i can do that using the same method i did for the maximus rom... no?
Any thoughts?

rteepu said:
Now.. DO I REALLY NEED TO REVERT BACK TO STOCK?
I mean, i just found mod (maximus HD) inside my phone and flashed that using cwm.
I have no problems so far and I do not have to send the phone back for warranty or anything, so do i really need to get back to stock? Cuz i think for that my expertise are lacking atm. I just wanted to update to the latest android... but figure i can do that using the same method i did for the maximus rom... no?
Any thoughts?
Click to expand...
Click to collapse
its up to you, if you don't have to send the device for repair then its not needed to revert back to stock and you can use your phone with the custom rom if you like it.

Hey, a quick question...
Will wiping the phone before flashing a custom ROM wipe my recovery image too? Im using TWRP. And just before hitting wipe, i thought what if this wipes my twrp as well.. So, I stopped and rushed here... anyone?
Here is what i was gonna do.. I moved the ROM zip into the internal storage of my phone --- > went into the recovery (TWRP) using GOO app ---> was gonna do the wipe (here is where I stopped) ---- %% after the wipe, i was going to "Find in Recovery "Choose zip from sdcard" choose appropriate zip file" and then follow the Aroma installers instructions ----%% reboot.
@alray
Thanks man..
As long as I have access to this forum, I feel brave enough to continue messing around with my phone.

rteepu said:
Hey, a quick question...
Will wiping the phone before flashing a custom ROM wipe my recovery image too? Im using TWRP. And just before hitting wipe, i thought what if this wipes my twrp as well.. So, I stopped and rushed here... anyone?
Here is what i was gonna do.. I moved the ROM zip into the internal storage of my phone --- > went into the recovery (TWRP) using GOO app ---> was gonna do the wipe (here is where I stopped) ---- %% after the wipe, i was going to "Find in Recovery "Choose zip from sdcard" choose appropriate zip file" and then follow the Aroma installers instructions ----%% reboot.
@alray
Thanks man..
As long as I have access to this forum, I feel brave enough to continue messing around with my phone.
Click to expand...
Click to collapse
No, wiping will not clear your recovery partition
Sent from my HTC One using xda app-developers app

[Q] Have I now botched my M7 beyond repair?

And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!

polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Looks like your OS is gone. Did you try and reflash twrp?
---------- Post added at 08:25 AM ---------- Previous post was at 07:55 AM ----------
24.531
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Try running this 3.24.531.3 ruu, instructions on page.
http://forum.xda-developers.com/showthread.php?t=2375223

Thanks very much folks. Somehow, I was able to reflash twrp. From there, I realized that one mistake I made was overlooking that I needed s-off activated before flashing the ROM. (I think that was the beginning of my difficulties.)
Before reflashing twrp, I tried the RUU suggestion (TY!), but that needed bootloader turned back on, which in turn needed s-off...quite a procedure.
Anyway, With s-off done (thanks to the very persistent rumrunner_HTC_0.5.0.zip !), a second flash attempt of the rom at http://forum.xda-developers.com/showthread.php?t=2341395 worked seemingly perfectly. I now just trying to figure out whether I can get wifi calling working reliably (should be able to in theory, and at least one poster in that thread says he's done so).
Getting the HTC one properly modded is not a simple process relative to my prior experiences. I'm grateful for the help!

All of that work in the beginning was not needed. All you had to do was unlock bootloader, S-Off, change CID to 11111111, and run the GPE RUU from HTC. That's it. I had an ATT version that saw every different incarnation of software and it was that easy every time. Went from ATT to GPE, to T-Mobile, to Dev Edition and back without a problem. Well, red triangles of death be damned, but it never slowed me down, and the only time I got those was when I mis-matched the recovery img, or tried an update with a HBoot higher that 1.44, those are the only thinga to watch for. Make sure your ducks are in a row and update away. Stock recovery and lower Hboot worked awesome. I probably should put together a master file of everything I have for DL because I have it all and would make life so easy if someone hasn't done it already.

[Q] Unmodded HTC One M7 stuck in boot loop, unable to facory reset or enter recovery

Hi guys, I have a completely stock HTC one m7 that one day decided to get stuck in a boot loop. I've tried going into the bootloader(?) and doing a factory reset, as well as accessing the recovery menu with no success. It just goes back into the loop.
I've been told that flashing it(?) in fastboot might help? I honestly have very little idea what to do when it comes to this, so I was wondering if you guys would be able to help me, and explain in fairly simple terms what I need to do.
I've looked through similar threads but most of them seem to be problems relating to already modded phones. I hope you guys can help!
Thanks.

Milo89 said:
Hi guys, I have a completely stock HTC one m7 that one day decided to get stuck in a boot loop. I've tried going into the bootloader(?) and doing a factory reset, as well as accessing the recovery menu with no success. It just goes back into the loop.
I've been told that flashing it(?) in fastboot might help? I honestly have very little idea what to do when it comes to this, so I was wondering if you guys would be able to help me, and explain in fairly simple terms what I need to do.
I've looked through similar threads but most of them seem to be problems relating to already modded phones. I hope you guys can help!
Thanks.
Click to expand...
Click to collapse
You can try a RUU (Rom Update Utility) we need the information in the bootloader screen to help you find the correct one for your device
Carrier / software version / hboot / and any other information you can give about the phone

clsA said:
You can try a RUU (Rom Update Utility) we need the information in the bootloader screen to help you find the correct one for your device
Carrier / software version / hboot / and any other information you can give about the phone
Click to expand...
Click to collapse
Ok, on the bootloader screen it says:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.16.61.1
eMMC-boot 2048MB
Aug 22 2014, 18:39:28.0
Click to expand...
Click to collapse
Thanks for the fast reply!
*edit* oh and my carrier is T-mobile in the UK

Milo89 said:
Ok, on the bootloader screen it says:
Thanks for the fast reply!
*edit* oh and my carrier is T-mobile in the UK
Click to expand...
Click to collapse
There is no RUU for 6.16.61.1 version and nothing that I can find online (nandroid backup or other useful files). You might want to unlock your bootloader at HTCDev.com, flash TWRP recovery 2.6.3.3 and then flash a custom rom like ARHD 84 and see if your device can boot.

I had the exact same issue, so I ran a RUU that had a slightly newer firmware since I had HBOOT 1.57 and S-ON. it apparently took the update but went straight back to a boot loop. Called HTC, they said there's most likely corrupted sectors in the boot portion and the device can't be repaired. Hope your problem isn't quite that severe.

[Q] M8: S-On, Unlocked and want to get back to Stock

Hello, I seem to have got myself into a fix and need to reach out to the M8 community for assistance. I purchased a lightly used HTC One M8 that appeared to be in near mint condition. The phone was unrooted, locked and S-On. Although, it did have the Harmen Kardon rom installed and it is not the HK model, which I found odd but nothing more. I verified that the phone could be added to the Sprint Network so all seemed good.
I immediately set about rooting it. I have owned a number of Galaxy phones and considered myself rather adept at rooting, loading new ROMs, updating firmware and troubleshooting in general. I would occasionally soft brick but I'd always fine a way out.
Rooting the HTC was just different enough that I skipped one critical step without realizing it an now I am stuck for the first time ever.
I used the HTC Dev site and the HTC All-In-One tool to unlock, root and install TWRP 2.8. Two things that I did not do, S-OFF and back-up my stock system image just in case. Now, while I have Viper 4.3.0 installed and running fine, and I can switch to at least one other ROM (Bare Bones 2.1), I seem to have no path to get back to a pure stock ROM if I need to do so. And that bothers me. =)
It seems from what I have read that using an RUU would be the easiest route however, that seems to be impossible from the S-ON position. I have tried Sunshine, but it refuses to work; giving errors something along the lines of it does not like my ROM load stock or something closer to stock. Which is why I tried Bare Bones. I looked at Firewater but it seems to have issues and is not really supported anymore. I have tried various command line scripts via miniADB but still nothing.
My understanding is that if I could get S-OFF, I could install the RUU and return to stock. I even tried flashing a stock nandroid BU but that did not work either.
I suppose I should not complain, it's not bricked and it has a cool ROM installed and I can activate it but I just hate that I made such a blunder and that I can't figure out how to fix it.
Any thoughts out there? Let me know if you need additional info. This is what my bootloader is showing.
Thanks in advance!
Software status: Modified
Unlocked
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
Radio-1.08.20.8916
OpenDSP-v46.2.2-00564-M8974_FP.0811
OS-
eMMC-boot 2048MB
Dec 2 2014,14:00:10.0
Running
ViperOneM8 4.3.0
Updated 1st March 2015

IgnatzMaus said:
Hello, I seem to have got myself into a fix and need to reach out to the M8 community for assistance. I purchased a lightly used HTC One M8 that appeared to be in near mint condition. The phone was unrooted, locked and S-On. Although, it did have the Harmen Kardon rom installed and it is not the HK model, which I found odd but nothing more. I verified that the phone could be added to the Sprint Network so all seemed good.
I immediately set about rooting it. I have owned a number of Galaxy phones and considered myself rather adept at rooting, loading new ROMs, updating firmware and troubleshooting in general. I would occasionally soft brick but I'd always fine a way out.
Rooting the HTC was just different enough that I skipped one critical step without realizing it an now I am stuck for the first time ever.
I used the HTC Dev site and the HTC All-In-One tool to unlock, root and install TWRP 2.8. Two things that I did not do, S-OFF and back-up my stock system image just in case. Now, while I have Viper 4.3.0 installed and running fine, and I can switch to at least one other ROM (Bare Bones 2.1), I seem to have no path to get back to a pure stock ROM if I need to do so. And that bothers me. =)
It seems from what I have read that using an RUU would be the easiest route however, that seems to be impossible from the S-ON position. I have tried Sunshine, but it refuses to work; giving errors something along the lines of it does not like my ROM load stock or something closer to stock. Which is why I tried Bare Bones. I looked at Firewater but it seems to have issues and is not really supported anymore. I have tried various command line scripts via miniADB but still nothing.
My understanding is that if I could get S-OFF, I could install the RUU and return to stock. I even tried flashing a stock nandroid BU but that did not work either.
I suppose I should not complain, it's not bricked and it has a cool ROM installed and I can activate it but I just hate that I made such a blunder and that I can't figure out how to fix it.
Any thoughts out there? Let me know if you need additional info. This is what my bootloader is showing.
Thanks in advance!
Software status: Modified
Unlocked
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
Radio-1.08.20.8916
OpenDSP-v46.2.2-00564-M8974_FP.0811
OS-
eMMC-boot 2048MB
Dec 2 2014,14:00:10.0
Running
ViperOneM8 4.3.0
Updated 1st March 2015
Click to expand...
Click to collapse
Relock bootloader then run ruu will restore back to stock or just flash a stock rooted rom prolly easier
Sent from 27.5244° N, 99.4906° W

joshuadub said:
Relock bootloader then run ruu will restore back to stock or just flash a stock rooted rom prolly easier
Sent from 27.5244° N, 99.4906° W
Click to expand...
Click to collapse
From what I have read, relocking the bootloader with custom recovery, ROM or kernel will result in the phone not booting. Is that true? I am nervous about doing that and still not being able to successfully restore stock with an RUU. Though, again from what I have read, I should be able to re-unlock and put things back.
Every guide I am seeing says that getting back to stock is really only possible with S-Off and that there is no way to get to S-Off from Unlocked. So, I am feeling that I am out of luck.

IgnatzMaus said:
From what I have read, relocking the bootloader with custom recovery, ROM or kernel will result in the phone not booting. Is that true? I am nervous about doing that and still not being able to successfully restore stock with an RUU. Though, again from what I have read, I should be able to re-unlock and put things back.
Every guide I am seeing says that getting back to stock is really only possible with S-Off and that there is no way to get to S-Off from Unlocked. So, I am feeling that I am out of luck.
Click to expand...
Click to collapse
The phone will still boot. Also, S-off is not necessary to get your phone back to stock. The entire point of a RUU would be lost if it only worked when S-off.

1.61hboot revert to stock

Hello all, I rooted my m7 a few weeks ago. For whatever reason I lost my backup after installing cm12. Now CM 12 is all I can get to work. Sense roms either reboot randomly every min or so (never made it through setup) or bootloop, or won't activate with sprint HFA. I want to ruu, but I've read I need to relock the boot loader and everything I've seen to do that requires s-off.
What do I need to do to get back?
1.61 hboot
Rooted
Unlocked/tampered
S-on
Also, why can't I get any sense rom to run?

cant get s-off with sunshine (what i have been told i need for my hboot vers) while im stuck in cm12...help plzzz

the5ifty said:
Hello all, I rooted my m7 a few weeks ago. For whatever reason I lost my backup after installing cm12. Now CM 12 is all I can get to work. Sense roms either reboot randomly every min or so (never made it through setup) or bootloop, or won't activate with sprint HFA. I want to ruu, but I've read I need to relock the boot loader and everything I've seen to do that requires s-off.
What do I need to do to get back?
1.61 hboot
Rooted
Unlocked/tampered
S-on
Also, why can't I get any sense rom to run?
Click to expand...
Click to collapse
You don't need to be s-off to re-lock or RUU and you must be on a stock rom for Sunshine to work.

new and need help!!!!!
hi new here in need of help i have a
--------------------------------
{Htc m7 sprint}
m7_wls pvt ship
s-on
HBOOT 1.61.000
radio- 1.01.20.1225
open dsp-v35.120.274.0718
os-6.23.651.6
emmc-boot 2048mb
---------------------------------
ok i have rooted lgs and samsungs flashed them and have comptly brick phones to were they wont even turn on.so im not the best but i do have a liitle nolgke of rooting. i do understand what it takes to safely do this. so i now have this htc it all started i needed it sim-unlocked.so i got boot loader lock off and rooted but the twrp i had flashed for it, the touch pad would not work so i put clockwork (6.0.3.3)on it. that seemed to work then my phone was rooted but keep getting binary error so i tried google play way with apks and none of them helped so i flashed update su to recovery then i went to boot back and stuck in a boot loop. so then come to find out my android secure .img is know missing and so i re locked bootloader and tried to flash a couple of the {RUU} i found wich doing all this threw fastboot and not one would past signature and all have failed. im totally dumbed on this and need help to get my phone up and going thank you