return phone for warrenty - One (M7) Q&A, Help & Troubleshooting

I have custom recovery, bootloader unlocked and s-off. My phone does not power on anymore. Not a single signal. Not even the LED lights up when plugged into the charger.. I think i will send it to HTC. Is HTC able to spot that is it unlocked etc. ?

MICH_** said:
I have custom recovery, bootloader unlocked and s-off. My phone does not power on anymore. Not a single signal. Not even the LED lights up when plugged into the charger.. I think i will send it to HTC. Is HTC able to spot that is it unlocked etc. ?
Click to expand...
Click to collapse
If you unlocked it with HTCdev.com, then yes they will be able to. But usually unlocking the bootloader doesn't make the entire device stop working. They might blame you for over clocking or something, but there isn't anything you can do about it. You obviously can't re-lock it, so I would just send it in and hope that they don't care.

aooga said:
If you unlocked it with HTCdev.com, then yes they will be able to. But usually unlocking the bootloader doesn't make the entire device stop working. They might blame you for over clocking or something, but there isn't anything you can do about it. You obviously can't re-lock it, so I would just send it in and hope that they don't care.
Click to expand...
Click to collapse
The bootloader was unlocked before it stopped working. I was able to install the stock rom. I have i plan how i could make it completely stock.. but for my plan i need it to boot into recovery.

MICH_** said:
The bootloader was unlocked before it stopped working. I was able to install the stock rom. I have i plan how i could make it completely stock.. but for my plan i need it to boot into recovery.
Click to expand...
Click to collapse
You can't make it stock if you can't turn it on. Honestly, there is NOTHING you can do right now except send it in if the phone doesn't even get to the bootlaoder or RUU modes.
I don't think HTC will not fix it though. They should be fine with it.

aooga said:
You can't make it stock if you can't turn it on. Honestly, there is NOTHING you can do right now except send it in if the phone doesn't even get to the bootlaoder or RUU modes.
I don't think HTC will not fix it though. They should be fine with it.
Click to expand...
Click to collapse
Ok, i will send it to HTC and hope for the best thank you

I made the bootloader to show "locked" and flashed the stock recovery!
How to get s-on now?

Leave it s off
Sent from my GT-I9305 using xda app-developers app

nateboi81 said:
Leave it s off
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Are you sure? Do i have warranty with s-off?

MICH_** said:
Are you sure? Do i have warranty with s-off?
Click to expand...
Click to collapse
Well, it depends. Usually, HTC will only check for the TAMPERED flag and the bootloader status. But sometimes, they may have a problem with the phone being S-OFF.
I S-ON'ed my phone before giving it for warranty repair.
Anyways, whether u will S-ON the phone or not, ill tell u how to S-ON.
Put the phone in fastboot mode. On ur PC, open command prompt and type:
fastboot oem writesecureflag 3
Then, do what the screen shows
HOWEVER, DO NOT S-ON UR PHONE IF HBOOT IS 1.55 OR ABOVE. THE TAMPERED LOGO WILL RE-APPEAR

raghav kapur said:
Well, it depends. Usually, HTC will only check for the TAMPERED flag and the bootloader status. But sometimes, they may have a problem with the phone being S-OFF.
I S-ON'ed my phone before giving it for warranty repair.
Anyways, whether u will S-ON the phone or not, ill tell u how to S-ON.
Put the phone in fastboot mode. On ur PC, open command prompt and type:
fastboot oem writesecureflag 3
HOWEVER, DO NOT S-ON UR PHONE IF HBOOT IS 1.55 OR ABOVE. THE TAMPERED LOGO WILL RE-APPEAR
Click to expand...
Click to collapse
okay, i will try to get s-on. But how to do so? Does it work by just typing "fastboot writesecureflag 3" ?

MICH_** said:
I made the bootloader to show "locked" and flashed the stock recovery!
How to get s-on now?
Click to expand...
Click to collapse
fastboot oem writesecureflag 3
it will be S-ON

raghav kapur said:
Well, it depends. Usually, HTC will only check for the TAMPERED flag and the bootloader status. But sometimes, they may have a problem with the phone being S-OFF.
I S-ON'ed my phone before giving it for warranty repair.
Anyways, whether u will S-ON the phone or not, ill tell u how to S-ON.
Put the phone in fastboot mode. On ur PC, open command prompt and type:
fastboot oem writesecureflag 3
Then, do what the screen shows
HOWEVER, DO NOT S-ON UR PHONE IF HBOOT IS 1.55 OR ABOVE. THE TAMPERED LOGO WILL RE-APPEAR
Click to expand...
Click to collapse
I am on hboot 1.55... so no chace for s-on?

MICH_** said:
okay, i will try to get s-on. But how to do so? Does it work by just typing "fastboot writesecureflag 3" ?
Click to expand...
Click to collapse
Post the output after typing in that command. I don't remember TBH. But I will once u post the output
---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------
MICH_** said:
I am on hboot 1.55... so no chace for s-on?
Click to expand...
Click to collapse
Downgrade to 1.44. You can do so because ur S-OFF. Then type in that command to S-OFF
If u do it on 1.55, TAMPERED will re-appear and there will be no warranty

raghav kapur said:
Post the output after typing in that command. I don't remember TBH. But I will once u post the output
---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------
Downgrade to 1.44. You can do so because ur S-OFF. Then type in that command to S-OFF
If u do it on 1.55, TAMPERED will re-appear and there will be no warranty
Click to expand...
Click to collapse
How to downgrade?

MICH_** said:
How to downgrade?
Click to expand...
Click to collapse
Download this:
https://mega.co.nz/#!ORtGHIqT!qp1EZFa7jidXxO4DXhhdsiLL8SbDSA1FNJfoz9DgpIo
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44

raghav kapur said:
Download this:
https://mega.co.nz/#!ORtGHIqT!qp1EZFa7jidXxO4DXhhdsiLL8SbDSA1FNJfoz9DgpIo
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
Does the phone reboot after "fastboot oem rebootRUU" ?
the version is 1.29.401.12 but 2.24.111.3 is running on my phone. Does this matter?

edit android-info.txt to meet your phone CID & MID

moha_moha20106 said:
edit android-info.txt to meet your phone CID & MID
Click to expand...
Click to collapse
which lines should i change?
My CID is: T-MOB101
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MICH_** said:
which lines should i change?
My CID is: T-MOB101
View attachment 2662502
Click to expand...
Click to collapse
Don't change. Just add ur cidnum

raghav kapur said:
Don't change. Just add ur cidnum
Click to expand...
Click to collapse
So just add cidnum: T-MOB101 ?
And mainver shoud stay the same?

Related

first post need help returning to stock

hello every one this is my first post i need some help please.
i bought a htc one preowned and i have since been in settings and its running a custom rom
android revolution hd 12.1 by mike 1986
my phone cid is htc_001
how do i return it to stock htc os
i have read a few posts before posting here i no i have to re lock bootloader then flash the ruu
i was wondering is there an easier way to relock bootloader and flash the ruu could some one also point me in the right direction
to which ruu to download with a link if possible to download.
thanks in advance for any help u may give with some simple instructions that i can understand as this is new to me and do not want to
make a mistake.
thankyou.
Is it S-OFF at the moment?
EddyOS said:
Is it S-OFF at the moment?
Click to expand...
Click to collapse
says m7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4a.18.3263.15
openDSP-v26.120.274.0202
eMMC-boot
so im guessing so
You don't need to relock, if you're s-off you can run whatever RUU you like.
iElvis said:
You don't need to relock, if you're s-off you can run whatever RUU you like.
Click to expand...
Click to collapse
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Infamouslimey said:
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Click to expand...
Click to collapse
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Note that running a RUU will fully wipe the phone. So back up anything on it you want to keep.
iElvis said:
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Click to expand...
Click to collapse
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
You have superCID, which means any RUU will run. You have the generic European model. CIDGetter is pulling the original cid from some system file, but it doesn't reflect the actual cid.
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Infamouslimey said:
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Click to expand...
Click to collapse
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
iElvis said:
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
Click to expand...
Click to collapse
thank you very much for all your help great site with such helpful members.
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Infamouslimey said:
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Click to expand...
Click to collapse
No and no. You have to do those manually, and there is no need to here.
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Infamouslimey said:
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Click to expand...
Click to collapse
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
iElvis said:
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
Click to expand...
Click to collapse
thanks very much for all your help ill install the fastboot files anyway so if need them there there.
many thanks
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
N0wy0ud1e said:
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
Click to expand...
Click to collapse
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
iElvis said:
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
Click to expand...
Click to collapse
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
N0wy0ud1e said:
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
Click to expand...
Click to collapse
That goes away when you relock.

[SOLVED] Dead phone, RUU fails

The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Shu. said:
The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Click to expand...
Click to collapse
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
nkk71 said:
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
Click to expand...
Click to collapse
Okay, then that seems to be the issue, i'll try to relock, thanks!
Shu. said:
Okay, then that seems to be the issue, i'll try to relock, thanks!
Click to expand...
Click to collapse
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
nkk71 said:
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
Click to expand...
Click to collapse
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
If you have S-off you don't have to lock your bootloader to run a ruu.
Shu. said:
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
Click to expand...
Click to collapse
No problem :good:
Post back with your results so we know
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
I stand corrected
---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------
Shu. said:
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
Click to expand...
Click to collapse
with S-Off it's no problem to downgrade. where did you get the RUU, can you post link.
And what's the exact error you get?
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Shu. said:
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Click to expand...
Click to collapse
For other RUUs check this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
I find HTCdev way too confusing, as it clutters everything together, you can easily download a RUU for "HTC One S" instead of "HTC One" (aka M7)
And since you're S-Off downgrading is no problem

4.3 update, help needed

Hello there. I've been trying to do an ota update for my HTC One to android 4.3 for a while now and it hasn't been successful. Every time I check I get the "Your phone is up to date" message. I'm stuck on 4.2.2. I've tried contacting HTC about my problem, and apparently my device is the O2 version which according to them, hasn't received the update yet, although from my search, it seems that the 4.3 update has been on O2 since last November . I bought my device thinking it was the unlocked, worldwide version of the One; the place that I've purchased it from said nothing about it being an O2 device. Could it be that this has to do with the fact that when I setup my device, I choose my country (Jordan) instead of the UK? How can I update it to 4.3 without rooting it? Is there a way to change the country settings and check for an update? Thank you for your time :laugh:
Ibraheem Nofal said:
I bought my device thinking it was the unlocked, worldwide version of the One; the place that I've purchased it from said nothing about it being an O2 device. Could it be that this has to do with the fact that when I setup my device, I choose my country (Jordan) instead of the UK?
Click to expand...
Click to collapse
Has nothing to do with which country you choose, it depends on CID and MID; MID should be PN071000 (for M7_UL European model), and the CID you can see in the bootloader screen.
How can I update it to 4.3 without rooting it? Is there a way to change the country settings and check for an update?
Click to expand...
Click to collapse
You'll have to wait until O2 releases it.
nkk71 said:
Has nothing to do with which country you choose, it depends on CID and MID; MID should be PN071000 (for M7_UL European model), and the CID you can see in the bootloader screen.
You'll have to wait until O2 releases it.
Click to expand...
Click to collapse
Thank you very much for your reply. It's messed up that O2 would take this long to release such an update that's been rolling to the HTC One since October :crying:
nkk71 said:
Has nothing to do with which country you choose, it depends on CID and MID; MID should be PN071000 (for M7_UL European model), and the CID you can see in the bootloader screen.
You'll have to wait until O2 releases it.
Click to expand...
Click to collapse
I've just done another check, the update is supposed to have been rolled out since last November(source: O2 forums) , yet I keep getting the "your phone is up to date" message :/
Ibraheem Nofal said:
I've just done another check, the update is supposed to have been rolled out since last November(source: O2 forums) , yet I keep getting the "your phone is up to date" message :/
Click to expand...
Click to collapse
Can u give us a screenshot of bootloader, and a "fastboot getvar all" (without IMEI and s/n)
Sent from my HTC One using Tapatalk
nkk71 said:
Can u give us a screenshot of bootloader, and a "fastboot getvar all" (without IMEI and s/n)
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I just checked my bootloader and it says "tampered" on top. Although, I've never messed around with it or tried to unlock it. My device was new when bought, so this is very peculiar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ibraheem Nofal said:
I just checked my bootloader and it says "tampered" on top. Although, I've never messed around with it or tried to unlock it. My device was new when bought, so this is very peculiar.
View attachment 2506886
I didn't get what you meant by GetVar all info, how can I access those?
Oh and from clicking on recovery in the Bootloader menu I've just discovered that there's something called the ClockWorkMod installed on my device
Click to expand...
Click to collapse
well, here's the short version: whoever you bought your phone from (be that second hand, or even a shop), they unlocked bootloader (using HTCdev) and were playing around with it.
in either case, they should have informed you of the state of the phone they sold you.
now to get the phone back to something close to new (out of the box), how familiar are you with adb & fastboot?
i can help fix or convert your phone, but need to know how familiar you are with the above commands.
nkk71 said:
well, here's the short version: whoever you bought your phone from (be that second hand, or even a shop), they unlocked bootloader (using HTCdev) and were playing around with it.
in either case, they should have informed you of the state of the phone they sold you.
now to get the phone back to something close to new (out of the box), how familiar are you with adb & fastboot?
i can help fix or convert your phone, but need to know how familiar you are with the above commands.
Click to expand...
Click to collapse
I'm quite unfamiliar with them. It was my first time using it when I got the following Getvar info. Also, will this delete all of the data on my phone? And could it be that this was done in order to unlock my device on other carriers? Or will it work on all carriers even when reset to it's factory settings? I can't thank you enough for your help!
Ibraheem Nofal said:
I'm quite unfamiliar with them. It was my first time using it when I got the following Getvar info. Also, will this delete all of the data on my phone? And could it be that this was done in order to unlock my device on other carriers? Or will it work on all carriers even when reset to it's factory settings? I can't thank you enough for your help!
View attachment 2506979
Click to expand...
Click to collapse
1- no, it was not done to unlock from carriers! that would be SIM-Unlock, nothing to do with the phones bootloader unlocked
2- You wanna turn your phone into an unbranded WWE GCC Edition? would that be you're ultimate goal, or do you have anything else in mind, for example: using custom ROMs?
3- or do you just wanna keep it O2 branded?
nkk71 said:
1- no, it was not done to unlock from carriers! that would be SIM-Unlock, nothing to do with the phones bootloader unlocked
2- You wanna turn your phone into an unbranded WWE GCC Edition? would that be you're ultimate goal, or do you have anything else in mind, for example: using custom ROMs?
3- or do you just wanna keep it O2 branded?
Click to expand...
Click to collapse
Well, I guess it'd be nice to make it into a World Wide unlocked edition, unless that means delving more in technicalities(I'm afraid of bricking it) and not getting OTA HTC updates, in which case I'd want to return it into it's stock state with O2 branding.
Ibraheem Nofal said:
Well, I guess it'd be nice to make it into a World Wide unlocked edition, unless that means delving more in technicalities(I'm afraid of bricking it) and not getting OTA HTC updates, in which case I'd want to return it into it's stock state with O2 branding.
Click to expand...
Click to collapse
i'll get back to you tomorrow
there is always a risk, but quite minimal (IMHO), i'll PM you over the weekend. c u....
Ibraheem Nofal said:
Well, I guess it'd be nice to make it into a World Wide unlocked edition, unless that means delving more in technicalities(I'm afraid of bricking it) and not getting OTA HTC updates, in which case I'd want to return it into it's stock state with O2 branding.
Click to expand...
Click to collapse
1- So first things first, backup EVERYTHING to your PC!! If you're going to do this, then sooner or later you're going to wipe everything off your phone! (probably sooner ... actually very soon!)
2- Second thing is to get S-Off: you're still on hboot 1.44 (April 2013) and firmware 1.xx, so the easiest is to use revone, and in order to avoid unnecessary headaches, use the following ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
3- get s-off using revone: http://forum.xda-developers.com/showthread.php?t=2314582
4- once s-off, change your CID (ie Carrier ID) to unbranded WWE GCC: in bootloader/FASTBOOT USB
fastboot oem writecid HTC__J15 <-- two underscores
fastboot reboot-bootloader
5- (optional) want to remove TAMPERED and set phone to LOCKED? use this tool: http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
6- download and run this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after you run the above file, you're phone will be completely returned to "out of the box", model M7_UL (PN0710000) and WWE GCC (CID HTC__J15)
all done, enjoy the updates.
if you need help, or have questions let us know
nkk71 said:
1- So first things first, backup EVERYTHING to your PC!! If you're going to do this, then sooner or later you're going to wipe everything off your phone! (probably sooner ... actually very soon!)
2- Second thing is to get S-Off: you're still on hboot 1.44 (April 2013) and firmware 1.xx, so the easiest is to use revone, and in order to avoid unnecessary headaches, use the following ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
3- get s-off using revone: http://forum.xda-developers.com/showthread.php?t=2314582
4- once s-off, change your CID (ie Carrier ID) to unbranded WWE GCC: in bootloader/FASTBOOT USB
fastboot oem writecid HTC__J15 <-- two underscores
fastboot reboot-bootloader
5- (optional) want to remove TAMPERED and set phone to LOCKED? use this tool: http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
6- download and run this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after you run the above file, you're phone will be completely returned to "out of the box", model M7_UL (PN0710000) and WWE GCC (CID HTC__J15)
all done, enjoy the updates.
if you need help, or have questions let us know
Click to expand...
Click to collapse
I sincerely apologize if this comes off as a bit too noob-ish. But won't my phone restore all of my data off my HTC Account Backup once I'm done? If not, what's the best tool, in your opinion for backing it up on my PC?
Ibraheem Nofal said:
I sincerely apologize if this comes off as a bit too noob-ish. But won't my phone restore all of my data off my HTC Account Backup once I'm done? If not, what's the best tool, in your opinion for backing it up on my PC?
Click to expand...
Click to collapse
I personally never used (or at least restored) using HTC Backup, so I can't really say. I always use Titanium Backup (requires root) to backup apps+data and some settings.
HELP!
nkk71 said:
I personally never used (or at least restored) using HTC Backup, so I can't really say. I always use Titanium Backup (requires root) to backup apps+data and some settings.
Click to expand...
Click to collapse
I just started following your steps to get my HTC One back to stock but unfortunately during the flash it got stuck on the HTC Queitly Brilliant screen, so I 'ingeniously" resetted it into recovery and clicked on Factory reset, and now it's again stuck on that screen. I'm Scared sh**less here. Is this normal? Have I bricked my device? Is this fixable?
nkk71 said:
I personally never used (or at least restored) using HTC Backup, so I can't really say. I always use Titanium Backup (requires root) to backup apps+data and some settings.
Click to expand...
Click to collapse
Oh and whenever I try and access the recovery it reboots and gets stuck at the Queitly Brilliant screen
Ibraheem Nofal said:
I just started following your steps to get my HTC One back to stock but unfortunately during the flash it got stuck on the HTC Queitly Brilliant screen, so I 'ingeniously" resetted it into recovery and clicked on Factory reset, and now it's again stuck on that screen. I'm Scared sh**less here. Is this normal? Have I bricked my device? Is this fixable?
Click to expand...
Click to collapse
can you get to bootloader? then post a "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
can you get to bootloader? then post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Yeah sure. Here you go
Ibraheem Nofal said:
Yeah sure. Here you go
View attachment 2584910
Click to expand...
Click to collapse
next time please use copy/paste, screenshots are so hard to read, and by the time i'm responding, i've already forgotten what it says.
so hboot is still 1.44, and fw is still 1.xx, so still need to get s-off first
so for this exercise, we're gonna use CWM 6.0.4.5:
https://mega.co.nz/#!aRMQiZoL!X2id_V0xX3BU54fEKctKxzr4dutrHJLaZkHHBVbfevw
MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
then flash that in bootloader:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, once in recovery
adb push Android_Revolution_HD-One_9.4.zip /data/media/
^^ the ROM is posted earlier (credits to @mike1986.)
then "install" it in CWM.
and continue as instructed before to get S-Off.
nkk71 said:
next time please use copy/paste, screenshots are so hard to read, and by the time i'm responding, i've already forgotten what it says.
so hboot is still 1.44, and fw is still 1.xx, so still need to get s-off first
so for this exercise, we're gonna use CWM 6.0.4.5:
https://mega.co.nz/#!aRMQiZoL!X2id_V0xX3BU54fEKctKxzr4dutrHJLaZkHHBVbfevw
MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
then flash that in bootloader:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, once in recovery
adb push Android_Revolution_HD-One_9.4.zip /data/media/
^^ the ROM is posted earlier (credits to @mike1986.)
then "install" it in CWM.
and continue as instructed before to get S-Off.
Click to expand...
Click to collapse
I sincerely apologize, I didn't know that there's a different method for posting pictures. I take it those are all CMD commands? And I'm going to have to be in the Fastboot menu of the bootloader while doing this? And where should I place the clockwork recovery img?

[Q] HTC One M7 stuck at bootmenu, relocked bootloader with custom recovery.

Hi!
I've spent the last few days trying to restore my M7 to mostly stock.
I had TWRP recovery installed. Relocked the bootloader so I could run the RUU and now have a phone that gets stuck at the bootmenu.
The RUU says I'm using an incompatible RUU for my phone, and trying to push the rom.zip (extracted from the RUU) using adb gives me the following error: remote 02 data length is too large.
The phone is S-On, Relocked and on hboot 1.44.
I attached an image of the bootmenu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions? Thanks in advance.
arthurrrr said:
Hi!
I've spent the last few days trying to restore my M7 to mostly stock.
I had TWRP recovery installed. Relocked the bootloader so I could run the RUU and now have a phone that gets stuck at the bootmenu.
The RUU says I'm using an incompatible RUU for my phone, and trying to push the rom.zip (extracted from the RUU) using adb gives me the following error: remote 02 data length is too large.
The phone is S-On, Relocked and on hboot 1.44.
I attached an image of the bootmenu.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
If your trying to go back to 100% Stock you need the device to be s-off, if you just want Stock Software that should be achievable. Please can you post the output from command
Code:
fastboot getvar all
Please remove imei and serial numbers before posting. Your on hboot 1.44 so the chances of finding an RUU are good depending on your cid, mid and version main.
Your device won't boot because you have relocked your bootloader, you can't boot a custom Rom or recovery while relocked.
You will need it to be relocked to run an RUU though so you may aswell leave it that way until we know if there is an RUU you can use or not. If not you will need to unlock to flash a stock Rom.
Danny201281 said:
If your trying to go back to 100% Stock you need the device to be s-off, if you just want Stock Software that should be achievable. Please can you post the output from command
Code:
fastboot getvar all
Please remove imei and serial numbers before posting. Your on hboot 1.44 so the chances of finding an RUU are good depending on your cid, mid and version main.
Your device won't boot because you have relocked your bootloader, you can't boot a custom Rom or recovery while relocked.
You will need it to be relocked to run an RUU though so you may aswell leave it that way until we know if there is an RUU you can use or not. If not you will need to unlock to flash a stock Rom.
Click to expand...
Click to collapse
Thanks a lot for your quick reply!
I will give you the output of the getvar command when I get home (at work now).
My cid is HTC__E11 and model id is PN0710000.
The RUU is ran is: RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1.
I believe my version main to be around 1.2 or something (this is wat the RUU installer says i believe?).
I'll give you all the info when I get home.
Thanks again.
arthurrrr said:
Thanks a lot for your quick reply!
I will give you the output of the getvar command when I get home (at work now).
My cid is HTC__E11 and model id is PN0710000.
The RUU is ran is: RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1.
I believe my version main to be around 1.2 or something (this is wat the RUU installer says i believe?).
I'll give you all the info when I get home.
Thanks again.
Click to expand...
Click to collapse
Easy fix that RUU will work for you but you will need to flash a firmware update first. Again this will require you to be relocked so leave it that way.
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/2.24.401.8.zip
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
Download these 2 firmware packages and place them in your fastboot folder. Then flash them in RUU mode.
Code:
fastboot oem rebootRUU
--- *case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip 2.24.401.8.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip 2.24.401.8.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Repeat the process for the 3.62.401.1 firmware.
2.24.401.8 first followed by 3.62.401.1. Then run the ruu.exe on your pc while the device is connected to fastboot usb in the bootloader
Danny201281 said:
Easy fix that RUU will work for you but you will need to flash a firmware update first. Again this will require you to
Download these 2 firmware packages and place them in your fastboot folder. Then flash them in RUU mode.
Code:
fastboot oem rebootRUU
--- *case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip 2.24.401.8.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip 2.24.401.8.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Repeat the process for the 3.62.401.1 firmware.
2.24.401.8 first followed by 3.62.401.1. Then run the ruu.exe on your pc while the device is connected to fastboot usb in the bootloader
Click to expand...
Click to collapse
Thanks mate! Looks very promising, going to try it out tonight!
I'll let you know how it worked out
Hi. Before iam gonna create new post I have to ask here .
I have exactly same issue however I am on the latest hboot and firmware
S-ON
My hboot is : 1.57
Firmware : 6.09.401.10
Currently on CyanogenMod 11 but I would like to revert to stock and root my Phone to use XPOSED
thanks in advance
Sent from my One using XDA Free mobile app
arthurrrr said:
Thanks mate! Looks very promising, going to try it out tonight!
I'll let you know how it worked out
Click to expand...
Click to collapse
The reason the RUU failed is to do with HTC, for some reason they decided the kitkat RUU's should only work with hboot 1.55 or 1.56. Flashing those 2 firmwares will bring your device up to hboot 1.55 and the ruu should restore your device to stock with hboot 1.56 Kitkat 4.4.2 Sense 5.5. And you should be able to take ota updates up to the latest firmware and Rom.
If you've ever thought about going s-off it may be better to do it now before updating your firmware though. Once your on the latest firmware there is only one method to achieve s-off and it cost $25.
Where as revone should work for you with hboot 1.44. And it's free to use, But that's your decision to make. :good:
Danny201281 said:
The reason the RUU failed is to do with HTC, for some reason they decided the kitkat RUU's should only work with hboot 1.55 or 1.56. Flashing those 2 firmwares will bring your device up to hboot 1.55 and the ruu should restore your device to stock with hboot 1.56 Kitkat 4.4.2 Sense 5.5. And you should be able to take ota updates up to the latest firmware and Rom.
If you've ever thought about going s-off it may be better to do it now before updating your firmware though. Once your on the latest firmware there is only one method to achieve s-off and it cost $25.
Where as revone should work for you with hboot 1.44. And it's free to use, But that's your decision to make. :good:
Click to expand...
Click to collapse
Thanks, I need S-Off if i want to reset my counter and change Relocked to Locked and get my warranty back right?
Maybe I'll do that before updating the hboot to 1.55. After that, I can just follow the stept above?
Thanks for the heads up.
arthurrrr said:
Thanks, I need S-Off if i want to reset my counter and change Relocked to Locked and get my warranty back right?
Maybe I'll do that before updating the hboot to 1.55. After that, I can just follow the stept above?
Thanks for the heads up.
Click to expand...
Click to collapse
Yes to preserve your warranty you will need s-off to go back to 100% Stock. You should be able to get s-off with this toolkit http://forum.xda-developers.com/showthread.php?t=2364445
I'm not normally a fan of toolkits like this, but this is the easiest way to s-off hboot 1.44 that I know of :good:
Once your s-off you can update without fear of being stuck with s-on or a $25 fee not that I think Sunshine app isn't worth $25 but if you can do it for free now then may as well :good:
Danny201281 said:
Yes to preserve your warranty you will need s-off to go back to 100% Stock. You should be able to get s-off with this toolkit http://forum.xda-developers.com/showthread.php?t=2364445
I'm not normally a fan of toolkits like this, but this is the easiest way to s-off hboot 1.44 that I know of :good:
Once your s-off you can update without fear of being stuck with s-on or a $25 fee not that I think Sunshine app isn't worth $25 but if you can do it for free now then may as well :good:
Click to expand...
Click to collapse
Hmm it seems to be impossible to push revone since it the device doesnt boot up. Can i push and run revone in fastboot?
Edit: managed to find my unlock.bin file from htcdev. Unlocked it again. Device does not boot but i can get to recovery now. However, pushing the file gives the No file or directory error.
arthurrrr said:
Hmm it seems to be impossible to push revone since it the device doesnt boot up. Can i push and run revone in fastboot?
Edit: managed to find my unlock.bin file from htcdev. Unlocked it again. Device does not boot but i can get to recovery now. However, pushing the file gives the No file or directory error.
Click to expand...
Click to collapse
No you need a Rom on the phone to s-off. You can push this reset.zip using a custom recovery. http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Download it and put it in your fastboot folder and rename it rom.zip boot your phone to custom recovery. And push the Rom either with the toolkit or with adb command
Code:
adb push rom.zip /sdcard
Then you should be able to flash the Rom to your phone from recovery.
In the aroma installer choose options.
Stock Recovery = No
Stock radio = yes
Root = yes
Danny201281 said:
No you need a Rom on the phone to s-off. You can push this reset.zip using a custom recovery. http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Download it and put it in your fastboot folder and rename it rom.zip boot your phone to custom recovery. And push the Rom either with the toolkit or with adb command
Code:
adb push rom.zip /sdcard
Then you should be able to flash the Rom to your phone from recovery.
In the aroma installer choose options.
Stock Recovery = No
Stock radio = yes
Root = yes
Click to expand...
Click to collapse
Everything worked out! Really appreciate your time and effort!
Thanks Danny :good:
arthurrrr said:
Everything worked out! Really appreciate your time and effort!
Thanks Danny :good:
Click to expand...
Click to collapse
Your welcome, good to hear you got it sorted :good:
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
sonic_boom said:
Hi. Before iam gonna create new post I have to ask here .
I have exactly same issue however I am on the latest hboot and firmware
S-ON
My hboot is : 1.57
Firmware : 6.09.401.10
Currently on CyanogenMod 11 but I would like to revert to stock and root my Phone to use XPOSED
thanks in advance
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately there is no RUU you can use with s-on. You can flash the Stock Rom from this thread with TWRP. http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
And then flash the Stock Recovery http://d-h.st/6JL
That will get you back to stock and able to receive OTA updates :good:
Danny201281 said:
Your welcome, good to hear you got it sorted :good:
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
Unfortunately there is no RUU you can use with s-on. You can flash the Stock Rom from this thread with TWRP. http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
And then flash the Stock Recovery http://d-h.st/6JL
That will get you back to stock and able to receive OTA updates :good:
Click to expand...
Click to collapse
MAN you are superStar !! its actually working , just wondering, is there any point to relock my bootloader ? so if i flash stock recovery i should be able to get OTA etc ?
sonic_boom said:
MAN you are superStar !! its actually working , just wondering, is there any point to relock my bootloader ? so if i flash stock recovery i should be able to get OTA etc ?
Click to expand...
Click to collapse
Your Welcome :highfive:
No need to relock your bootloader, That's only for flashing RUU's or Firmware. Just flash the Stock rom and Recovery and your good to go. :good:

Htc One M7_UL Bricked , help please

hi all
i have a HTC One M7_UL
i updated my phone OTA from the setting , phone restarted , battry 0 and phone off
now im on the bootloader setting
i tried to unlock my phone bootloader to install a custom rom , but it failed in unlock process
then i tried to find a original rom for my phone and install RUU or original ZIP but i cant find the Correct rom
see this pictures please , this is all info you need to know
please help me ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello alishadlou,
here you could find stock roms from Google Play Edition and Firmware.
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
You could take a look here too:
http://forum.xda-developers.com/showthread.php?t=2358781
Hope that help you out.
Greeting
Crytix
alishadlou said:
hi all
i have a HTC One M7_UL
i updated my phone OTA from the setting , phone restarted , battry 0 and phone off
now im on the bootloader setting
i tried to unlock my phone bootloader to install a custom rom , but it failed in unlock process
then i tried to find a original rom for my phone and install RUU or original ZIP but i cant find the Correct rom
Click to expand...
Click to collapse
GPE devices must be unlocked using "fastboot oem unlock" not using htcdev.com
Your bootloader version (1.44) doesn't match your firmware version btw
But tell me, I see in your post history that you have bricked 6 different phones in 5 months... How is that possible ?
alray said:
Your bootloader version (1.44) doesn't match your firmware version btw
Click to expand...
Click to collapse
not to mention he has the HTC (white) hboot, not the GPE (black) one
that device was definitely S-OFF before
alray said:
GPE devices must be unlocked using "fastboot oem unlock" not using htcdev.com
Your bootloader version (1.44) doesn't match your firmware version btw
But tell me, I see in your post history that you have bricked 6 different phones in 5 months... How is that possible ?
Click to expand...
Click to collapse
very very thanks for your nice help ( i love the people who help each other like this .... )
my phone + my friends phone sometimes + love to change roms , try new things , and all of them , and maybe this will be my job for future .
and i treid that you said
but this error
check it please
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so. The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities. So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Google and HTC
BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
Click to expand...
Click to collapse
Greeting
Crytix
Crytix said:
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so. The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities. So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Google and HTC
Greeting
Crytix
Click to expand...
Click to collapse
the reason i want to unlock the phone , is that i want install custom rom to can use my phone !!!
phone is hang on logo now !!! and i couldnt find the RUU for my phone ( can you please help me find my correct ruu file ? then i install it and using phone dont need unlock any more
Crytix said:
You could take a look here too:
http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
Here you could find the stock ruu, firmware, bootloader and recovery.
alishadlou said:
the reason i want to unlock the phone , is that i want install custom rom to can use my phone !!!
phone is hang on logo now !!! and i couldnt find the RUU for my phone ( can you please help me find my correct ruu file ? then i install it and using phone dont need unlock any more
Click to expand...
Click to collapse
I don´t allow to link outside xda, because I´m low poster. Please use the external link in that topic linked above.
Greetings
Crytix
Crytix said:
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so.
Click to expand...
Click to collapse
The actual Hboot installed on OP's phone is a Hboot from a Sense based firmware (not a GPE hboot) like nkk71 noted. GPE hboot are black colored. The current firmware version installed (5.11.1700.3) include the 1.54 GPE (black) hboot (he is on 1.44). So its a Sense hboot on a GPE phone + not the right version number for the firmware installed, so its confirm what nkk71 said, that phone was previously s-off, someone flashed the wrong hboot and turned it back s-on.
That being said, you can only, on a "normal" GPE phone, unlock the bootloader using the "fastboot oem unlock" command as opposed to Sense firmware which must be unlocked using htcdev's unlock code. There is also a well known bug with newer GPE firmware (hboot 1.54+) making the bootloader not unlockable.
So in theory, since the phone is running a Sense Hboot, he should be able to unlock using htcdev's unlock code which doesn't seem to work. "fastboot oem unlock" method for GPE variant doesn't work neither.
In his situation, he probably can't unlock his phone because of the wrong hboot installed vs his current firmware version or since the phone was s-off at some point, he might have a custom hboot...
The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities.
Click to expand...
Click to collapse
And this is not applicable to the M7, all shipped M7 bootloader were unlockable and currently, the only M7 version that can't be unlocked is Verizon due to carrier demand.
So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Click to expand...
Click to collapse
Updating the firmware or flashing a RUU will not solve his problem with the not unlockable bootloader. He will definitively need s-off again.[...deleted...] I would try to flash the ruu and achieve s-off with sunshine.
alray said:
Updating the firmware or flashing a RUU will not solve his problem with the not unlockable bootloader. He will definitively need s-off again. I would try to s-off before trying a RUU and then if its not working, flashing the ruu and try to s-off again.
Click to expand...
Click to collapse
With hboot 1.44 it's possible to unlock and S-Off with revone.
@op could you get an adb connection to your phone? Recovery for example.
If not, I can't help you more. Sorry.
Crytix said:
With hboot 1.44 it's possible to unlock and S-Off with revone.
Click to expand...
Click to collapse
Just realized he can't do what I suggested above (I would try to s-off before trying a RUU ), the phone is bricked. Your phone must be able to boot in the OS to achieve S-OFF. So he will need to flash the RUU so the phone can boot and then if he still want to unlock his bootloader, he will need to use Sunshine S-OFF (hboot will not be 1.44 anymore after the ruu).
could you get an adb connection to your phone? Recovery for example.
Click to expand...
Click to collapse
You can only use adb commands from 2 places
1- from a booted OS with usb debug turned ON ---> not possible phone is bricked
2- From custom recovery ---> not possible bootloader is locked, even if he aleady had a custom recovery installed, he can't boot to it, bootloader must be unlocked to boot a custom recovery.
and anyway, adb connection won't help since all S-OFF exploits need a working OS to do the magic...
alray said:
Just realized he can't do what I suggested above (I would try to s-off before trying a RUU ), the phone is bricked. Your phone must be able to boot in the OS to achieve S-OFF. So he will need to flash the RUU so the phone can boot and then if he still want to unlock his bootloader, he will need to use Sunshine S-OFF (hboot will not be 1.44 anymore after the ruu).
You can only use adb commands from 2 places
1- from a booted OS with usb debug turned ON ---> not possible phone is bricked
2- From custom recovery ---> not possible bootloader is locked, even if he aleady had a custom recovery installed, he can't boot to it, bootloader must be unlocked to boot a custom recovery.
and anyway, adb connection won't help since all S-OFF exploits need a working OS to do the magic...
Click to expand...
Click to collapse
first of all thanks for nice explains and i know very good things now
wht i should i do now ? i dont know what RUU can i install on my phone , the version its not matter for me , i just want my phone back and can use it
help me please
i cant find the correct version and i dont know what ruu i can install on my phone
alishadlou said:
first of all thanks for nice explains and i know very good things now
wht i should i do now ? i dont know what RUU can i install on my phone , the version its not matter for me , i just want my phone back and can use it
help me please
i cant find the correct version and i dont know what ruu i can install on my phone
Click to expand...
Click to collapse
5.11.1700.3 ruu. Check in the general section there is a ruu sticky thread. At post 1 you'll find instructions how to flash the ruu and also the 5.11.1700.3 ruu
alray said:
5.11.1700.3 ruu. Check in the general section there is a ruu sticky thread. At post 1 you'll find instructions how to flash the ruu and also the 5.11.1700.3 ruu
Click to expand...
Click to collapse
<3 Tnxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <3
My Phone is up nowww
thankkk youu very much
tnx everybody
my phone worked nice , but yesterday , its turn off and no power
when i connect it to pc , its show this driver installing : qhsusb dload
what should i do now ?
help please ...
no help ... ? ....
Use charger to charge it till 100%.

Categories

Resources