Related
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
s-on is required for unlocking bootloader, s-off will go to disclaimer screen but wont respond if yes is selected, it will only say ***unlock*** (which it must, but it wont be truly unlocked, your phone needs to respond when selecting yes and MUST restart, if you need to remove battery, it wont be unlocked.
***Problem***: now I had s-off and ***LOCKED*** so I ran fastboot oem writesecureflag 3 to get s-on, unlocked through htcdev and heres the big problem:
Now:
***UNLOCKED***
HBOOT 1.49.0007 S-ON (RH - i think)
Cant change CID, flash recovery, doesnt read PG86IMG files, cant flash anything through fastboot, cant run RUU because of error 132 (signature error).
After trying to change CID with:
fastboot oem writecid HTC__621
Result =
gave a few errors
cidnum = 0202 ...???
Have hboot 1.49.0007, can unlock relock bootloader, have functioning ICS rom
fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.20.401.2
INFOserialno: HT23NV200556
INFOimei: 352647050653635
INFOproduct: shooter_u
INFOplatform: HBOOT-8260
INFOmodelid: PG863****
INFOcidnum: HTC__621
INFObattery-status: good
INFObattery-voltage: 5785mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.510s
so please help... any1...
cybergurken said:
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
Click to expand...
Click to collapse
You should not have done that.
Also, if you are S-Off that is really all that matters. There is not really any reason to unlock the Bootloader. If you were S-Off and wanted to have an unlocked bootloader you should have just found a hboot like the revolutionary one or engineering and flashed PG86IMG.zip and that would have given you Unlocked and S-Off.
For the most part, you never want to do the fastboot oem writesecureflag 3.
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Thnx 4 responding
mnomaanw said:
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Click to expand...
Click to collapse
Hi, no offence taken...
However, Im still a newbie @ all of this, however, I might be wrong but 3 q's
1. Why would it hang on the "yes" option
2. If I pull out baattery, it says ***unlocked*** but I have no access to recovery, even after custom recovery flash in fastboot, it cant/wont/doesnt boot into recvoery @ all, ref. "my other posts", why would that happen
3. What is the real difference between unlocking bootloader, and s-oof, I have read many posts and I figured getting both would be on the safe side...
and lastly, xd, why would a bootloader not read/detect a PG86IMG file, that is also another problem,
Once again, tnks very much
So I've been trying my damnedest for the past week to un-root my HTC One, but I can't seem to make any progress. Unfortunately, I believe I may have flashed the wrong ROM at one point, making my situation much worse. I think the kernel is totally wrong, the CID, and god only knows what else. I never S-OFFed, so I can't imagine i screwed things up too bad, but nevertheless, I have had no luck running a valid RUU in Windows nor gotten fastboot to successfully flash the stock rom zip. I have an AT&T HTC One M7, currently showing the following info:
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4184mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
All I want to do is un-root and restore the device entirely back to stock and somehow I've really messed my phone up. Total noob here, appreciating any direction and advice to get my phone back to it's original state. Can anyone help? Thanks in advance!
Move Thread
Would anyone know how I could move this thread to the more general HTC One board (http://forum.xda-developers.com/forumdisplay.php?f=2117)? Since this is not a carrier specific problem and nobody in the AT&T forum seem to know what to do either, it would make sense for more HTC One users to see this as they may have more advice. thanks
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
RespectTheTech said:
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
Click to expand...
Click to collapse
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
jinkus said:
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
Click to expand...
Click to collapse
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
RespectTheTech said:
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
Click to expand...
Click to collapse
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
jinkus said:
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
Click to expand...
Click to collapse
The Image versions I had didn't match either, but weren't off as far as yours. Mine was From 1.26.502.15 and To 1.26.502.12. So even though he says they have to match, They don't. Wondering if they problem lies with the Goog Edition ROM. Have you tried to clean install any of the AT&T ROM's? Curious if you are able to do that then it should let you Relock the bootloader and then Install the RUU. Hypothetically anyways.
Hey all, I know I know, I'm sure someone is going to tell me to search and figure it out, but I have and I cannot. I could REALLY use your help here.
I've used HTC phones since the G1, rooting, flashing, unlocking, etc, and nothing has been as unclear as this.
So here is my request. I need to send my phone back to T-Mobile for warranty replacement (the mic broke). I am rooted, and have the bootloader unlocked via the official HTC method.
Here is what I currently have on my phone.
Rom: ARHD 61.1
Bootloader: 1.55.0000
Baseband: 4A.21.3263.03
Firmware: 3.24.531.3
S-On (I did the rooting and unlocking and such before they had S-Off)
CIDnum: T-MOB010
ModelID: PN0713000
I just need to get back to stock (even if it says relocked or whatever) so I can send this back to them. Every post I've read, every video I've watched, all have directions that are for S-Off, or don't have downloads for what I have if the directions are for S-On. I've dug through the Gurureset stuff and can't seem to make heads or tails of it. Some of it seems to be close, but ends up usually being the 1.29 firmware which will break my touchscreen from what I've read.
Could someone explain what the best way of doing this is? I am willing to PAY you for the help, via paypal or whatever, if that's what it takes. Basically I just need to get back to a factory image/bootloader that can OTA so that if T-Mobile were to inspect it the only thing they'd really see is that it's been relocked.
Thank you so much for the help, I really appreciate it. :angel:
-Danny
I was also s-on and on 1.55. I had to use rumrunner to get s-off, then relock bootloader so that I could use a ruu to get back to bone stock JB.
danielelias90 said:
So here is my request. I need to send my phone back to T-Mobile for warranty replacement (the mic broke). I am rooted, and have the bootloader unlocked via the official HTC method.
CIDnum: T-MOB010
ModelID: PN0713000
Could someone explain what the best way of doing this is? I am willing to PAY you for the help, via paypal or whatever, if that's what it takes. Basically I just need to get back to a factory image/bootloader that can OTA so that if T-Mobile were to inspect it the only thing they'd really see is that it's been relocked.
Thank you so much for the help, I really appreciate it. :angel:
-Danny
Click to expand...
Click to collapse
Follow mike1986's guide on returning to stock. You can use the RUU from this post for Method 2. Good luck and for this method you don't have to be S-Off.
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off which I don't want to pay $25 to do.
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
From what I've read it seems you do in fact need to S-OFF to relock the bootlooader.
Here's the thing,if you S-OFF than you won't need to relock the bootlooader to achieve what your looking to do .S-OFF enables you to flash all sorts of variations assuming they are for your specific device.
I will tell you that the $25 spent to have a safe hassle free S-OFF exploit is worth every cent.
You do not need to s-off to relock the bootloader.
"fastboot oem lock" from adb command prompt connection, while in fastboot mode is all you need to do.
Put your recovery back to stock first for safety but RUU should do that for you, better safe than sorry though...
- Sent from a payphone ...
Iconic24 said:
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off
Click to expand...
Click to collapse
I don't know where you guys are getting this from. S-off is in no way required to relock the bootloader.
Further, s-off is not required to run an RUU (another common misconception, that I don't know where people get); unless you are trying to "break the rules" and either run an older RUU ("downgrade") or run another carrier's RUU.
Iconic24 said:
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
Click to expand...
Click to collapse
As long as you are using an AT&T RUU, you can run an RUU for any version number that is equal to or greater than the main version on the phone. The only thing you can't do is run an older RUU ("downgrade") with s-on.
But since you are on the oldest AT&T version (1.12) and there is no 1.12 RUU anyway; you can therefore run any AT&T RUU. This includes 1.58, 2.23, and any new RUUs that come in the future.
ruu
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x? However, shall I use RUU for 4.4.4 or 4.4..2? Thanks if anyone replies
?
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
xCellHD said:
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
Click to expand...
Click to collapse
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
innocencex said:
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x?
Click to expand...
Click to collapse
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
innocencex said:
shall I use RUU for 4.4.4 or 4.4..2?
Click to expand...
Click to collapse
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
redpoint73 said:
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
Click to expand...
Click to collapse
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Prvrt said:
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Click to expand...
Click to collapse
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
redpoint73 said:
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Prvrt said:
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Click to expand...
Click to collapse
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
redpoint73 said:
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
Click to expand...
Click to collapse
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Prvrt said:
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Click to expand...
Click to collapse
You previously indicated UNLOCKED. Does it say UNLOCKED near the top of the bootloader screen?
Also, please refrain from quoting my whole entire post; as it clutters up the thread. I know it's the default when responding. But just leave in what is directly relevant to your response, and delete the rest.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
hotspot problem
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Ashok_gajjala said:
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Click to expand...
Click to collapse
This forum section is for the M8, not the M9. Anything we say here about the M8, may or may not be correct for the M9.
have a simple question I'm on firmware 3.16.617.2 there is update 3.16.617.3 if I am s-on unlocked Bootloader and attempt to flash RUU advance to 3.16.617.3 from earlier .2 will this relock my Bootloader ? as I don't want to relock it again my goal is to stall unlocked S-on .
Hi folks,
I have M8_UL_CA S-OFF and I was wondering if I can flash M8_UL Europe roms to avoid bloatware?
"ROM" and "RUU" are two very different things; so please take care before using the terms interchangeably.
You should be able to run a Euro RUU. But you should be specific as to which RUU you want to flash (file name, source, etc.).
You will likely also need to change CID and MID in order to run the RUU, depending on what RUU exactly.