Hello Guys...
I have a bit of a situation with my phone. I bought a second hand HTC One M7 few weeks ago and yesterday my 2 years old daughter managed to change the screen pattern. First I thought awwww thats soo cute :angel: I will deal with the pattern latter.... But despite a lot of attempts I was unable to get pass the pattern... and decided to do a factory reset... I get into bootloader, select recovery and phone rebooted into bootloader. I select Factory Reset and phone rebooted into bootloader again. and now situation started to worry me... So here is what I have done so far:
Get unlock token from HTCDev but it stuck on final stage of s-off
Found that phone has no recovey
Unable to open pattern lock
USB Debugging is NOT enabled
So basically with s-off I can not install custom recovery.
Details:
***TAMPERED***
***RELOCKED***
***Security Warning****
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T .35.3218.16
OpenDSP-V35.120.274.0718
OS-7.17.666.7
eMMC-boot 2048MB
Jan 30 2015,13:34:11.0
FASTBOOT GETVAR ALL:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.666.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3870mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Need Suggestions... Thanks
Aerocaria said:
Hello Guys...
I have a bit of a situation with my phone. I bought a second hand HTC One M7 few weeks ago and yesterday my 2 years old daughter managed to change the screen pattern. First I thought awwww thats soo cute :angel: I will deal with the pattern latter.... But despite a lot of attempts I was unable to get pass the pattern... and decided to do a factory reset... I get into bootloader, select recovery and phone rebooted into bootloader. I select Factory Reset and phone rebooted into bootloader again. and now situation started to worry me... So here is what I have done so far:
Get unlock token from HTCDev but it stuck on final stage of s-off
Found that phone has no recovey
Unable to open pattern lock
USB Debugging is NOT enabled
So basically with s-off I can not install custom recovery.
Details:
***TAMPERED***
***RELOCKED***
***Security Warning****
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T .35.3218.16
OpenDSP-V35.120.274.0718
OS-7.17.666.7
eMMC-boot 2048MB
Jan 30 2015,13:34:11.0
FASTBOOT GETVAR ALL:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.666.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3870mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Need Suggestions... Thanks
Click to expand...
Click to collapse
Since your phone isn't brand new and its bootloader already was unlocked before (hence the RELOCKED and TAMPERED flags), your problem is most likely caused by the previous owner relocking the bootloader with a custom recovery installed. You can't boot a custom recovery if the bootloader is locked/relocked and the factory reset function as well as the bootloader unlock are managed by the recovery. This problem can easily be solved by flashing the stock firmware or by flashing a RUU. Obviously, flashing a RUU will wipe everything from your phone but anyway a factory reset would have also wiped everything.
The RUU for your phone version is here:
https://www.androidfilehost.com/?fid=95916177934542816
Follow instructions from this thread (post #1) to flash it.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Don't hesitate if you have any questions or problem flashing the RUU,
btw, usb debug status doesn't matter, its only needed for adb connectivity when booted in the OS. You still have fastboot connectivity when booted in the bootloader even if debug is turned off.
alray said:
Since your phone isn't brand new and its bootloader already was unlocked before (hence the RELOCKED and TAMPERED flags), your problem is most likely caused by the previous owner relocking the bootloader with a custom recovery installed. You can't boot a custom recovery if the bootloader is locked/relocked and the factory reset function as well as the bootloader unlock are managed by the recovery. This problem can easily be solved by flashing the stock firmware or by flashing a RUU. Obviously, flashing a RUU will wipe everything from your phone but anyway a factory reset would have also wiped everything.
The RUU for your phone version is here:
https://www.androidfilehost.com/?fid=95916177934542816
Follow instructions from this thread (post #1) to flash it.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Don't hesitate if you have any questions or problem flashing the RUU,
btw, usb debug status doesn't matter, its only needed for adb connectivity when booted in the OS. You still have fastboot connectivity when booted in the bootloader even if debug is turned off.
Click to expand...
Click to collapse
Thanks a lot... everything worked like a charm... Hugss
Related
I have the Google Play Edition HTC One 32 GB. I've had it for months and I love the device- I did some rooting early on because I had bad experiences with old android locked down UIs, but I found I loved the google experience and didn't really need it. I was able to sideload the 4.3 ROM a while back, but when it came time to get the 4.4 rom it wouldn't accept it. I somehow decided a factory reset would reset it to how I got it, and that is apparently not the case.
So now what I have is a phone with 4.2.2 and it is not accepting OTA updates - when I try the ota update it gives me the red Error! Android, and when I try to push an RUU zip I get a 99 Unknown Error. I think the issue may be because somehow in this process my device got switched back to S-ON, I'm not sure when that happened.
I'm not sure where to go from here- I somehow have an Unlocked Bootloader with S-On HBOOT-1.54. Right now my bootloader says the following:
Code:
*** TAMPERED ***
*** UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
What I would like to get to somehow is a 4.4 android device that can accept future OTA updates. I don't need the device to be rooted. If anyone could help me with some next steps I'd really appreciate it.
If I have messed up the device too far, is there some standard set up procedures I can take that will just get it back to how I originally received it? Any advice would be appreciated. Thanks!
Also if it helps here is my fastboot getvar all:
Code:
22:54:55 willretina-pc: /web/svc-cerebro $ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <redacted>
(bootloader) imei: <redacted>
(bootloader) meid: <redacted>
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4061mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
There are a lot of issues reported in trying to get to 4.4 so tread carefully.
Under no circumstances should you lock the bootloader. Your best bet is to s-off and run 4.4 ruu zip.
That worked thanks! I'm now on 4.4 with s-off and I should be all set for the next ota.
Sent from my HTC One using Tapatalk
Hello all,
I've tried as much as I could find on the internet but I have been unable to restore my HTC One in order to receive OTA updates.
I had unrooted it (but not installed a new ROM or anything) months ago, but I could not install OTA updates as the phone always booted into the bootloader once a restart was needed, so the updates were never able to complete.
Since I don't need it to be rooted anymore, I've decided to just re-lock it and restore it completely. However, I keep having issues.
I am in the UK and have bought the HTC One M7 unbranded and use it on a 3 network. Right now the phone is unlocked with S-OFF.
Here is my getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [redacted]
(bootloader) imei: [redacted]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My bootloader says:
Code:
***TAMPERED**
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.56.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1 (4.19.401.9)
eMMC-boot 2048MB
Feb 7 2014,01:06:01.14313
I have tried installing a RUU as well as a recovery rom downloaded from htc1guru.com, both as .exe and .zip. The exe just won't work, quitting with an unspecified error message (155, if I remember correctly). Using "fastboot flash zip" always returns "FAILED (REMOTE:24 parsing android-info fail)".
I'm in developer mode and enabled USB debugging as well... I really don't know what I'm doing wrong. All I want was to get OTA updates!
For what it's worth I've been trying this on Windows 8.1, USB 2.0. I will try on Windows 7 tomorrow just as my very last resort.
Any help will be much appreciated. Thank you!!
biluinaim said:
Hello all,
I've tried as much as I could find on the internet but I have been unable to restore my HTC One in order to receive OTA updates.
I had unrooted it (but not installed a new ROM or anything) months ago, but I could not install OTA updates as the phone always booted into the bootloader once a restart was needed, so the updates were never able to complete.
Since I don't need it to be rooted anymore, I've decided to just re-lock it and restore it completely. However, I keep having issues.
I am in the UK and have bought the HTC One M7 unbranded and use it on a 3 network. Right now the phone is unlocked with S-OFF.
Here is my getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [redacted]
(bootloader) imei: [redacted]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My bootloader says:
Code:
***TAMPERED**
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.56.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1 (4.19.401.9)
eMMC-boot 2048MB
Feb 7 2014,01:06:01.14313
I have tried installing a RUU as well as a recovery rom downloaded from htc1guru.com, both as .exe and .zip. The exe just won't work, quitting with an unspecified error message (155, if I remember correctly). Using "fastboot flash zip" always returns "FAILED (REMOTE:24 parsing android-info fail)".
I'm in developer mode and enabled USB debugging as well... I really don't know what I'm doing wrong. All I want was to get OTA updates!
For what it's worth I've been trying this on Windows 8.1, USB 2.0. I will try on Windows 7 tomorrow just as my very last resort.
Any help will be much appreciated. Thank you!!
Click to expand...
Click to collapse
Windows 8.1 is ok if your hboot is above 1.55
flash this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
or
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
Android_info failed just means you had a RUU that did not match you MID/CID ..you can edit the android_info.txt to match your phone and it should flash fine.
Thanks for your reply!
I had actually just downloaded that RUU overnight on my Win7 PC - tried it just now and it surprisingly worked on the first try Maybe the copy I had on Win8.1 was corrupted somehow, since it's the same file and the android_info.txt was the same.
My phone has now been flashed and the bootloader just says UNLOCKED (no security warning... yet!). Am I good to go or should I re-lock it/turn S-ON before starting to use it as normal, and install the OS updates?
biluinaim said:
Thanks for your reply!
I had actually just downloaded that RUU overnight on my Win7 PC - tried it just now and it surprisingly worked on the first try Maybe the copy I had on Win8.1 was corrupted somehow, since it's the same file and the android_info.txt was the same.
My phone has now been flashed and the bootloader just says UNLOCKED (no security warning... yet!). Am I good to go or should I re-lock it/turn S-ON before starting to use it as normal, and install the OS updates?
Click to expand...
Click to collapse
Ota can be flashed on unlocked boot loader and s- off ...make sure you have stock recovery and no missing stock files or apps.
Sent from my HTC One using XDA Free mobile app
biluinaim said:
Thanks for your reply!
I had actually just downloaded that RUU overnight on my Win7 PC - tried it just now and it surprisingly worked on the first try Maybe the copy I had on Win8.1 was corrupted somehow, since it's the same file and the android_info.txt was the same.
My phone has now been flashed and the bootloader just says UNLOCKED (no security warning... yet!). Am I good to go or should I re-lock it/turn S-ON before starting to use it as normal, and install the OS updates?
Click to expand...
Click to collapse
Do not Go s-on ...Ever
and theirs no need to relock anything
HI there,
I know nothing about this stuff but i got a rooted phone. I followed the instruction on a YouTube video (never again) but for some reason the RUU gets stuck at 5%. Now I cant go back and its stuck on bootloader. What should i do?
When i go on recover or factory reset the bootloader just comes back up
I tried the uk 02 RUU
The phone is htc one M7
Any help would be greatly appreciated!!
I have tried searching for this problem but the solution i can find needs access to the phone.
***Tampered***
***Relocked***
***security warning***
m7_ul PVT SHIP S-on RH
HBOOT-1.57.0000
Radio-4t.28.3218.04
OpenDSP-v32.120.274.0909
os-
emmc-boot 2048MB
I have attached pictures about errors on RUU
I'm not familiar with the Window GUI tools but it is possible that your RUU is not compatible with your HBOOT version. Try using an old RUU, possibly a JB (4.2) version.
What's the RUU version you are trying to use anyway?
nukedz said:
I'm not familiar with the Window GUI tools but it is possible that your RUU is not compatible with your HBOOT version. Try using an old RUU, possibly a JB (4.2) version.
What's the RUU version you are trying to use anyway?
Click to expand...
Click to collapse
His phone is S-ON so he can't use a 4.2 ruu (its a downgrade). He must flash same or higher version ruu as his current firmware. We can't know his firmware version because twrp wiped the os version form the bootloader (blank os-).
If he remember what the firmware version was then he could flash a ruu of the same or higher version (if any) or he could restore same version nandroid backup. I know there is a lollipop RUU for O2 in the general section but not sure if it can be flashed on s-on phone cause it doesn't seem to be an official RUU (combined).
Otherwise he can flash custom roms or even flash custom rom, achieve s-off and then he can use any RUU he wants.
thuvcasio said:
HI there,
I know nothing about this stuff but i got a rooted phone. I followed the instruction on a YouTube video (never again) but for some reason the
RUU gets stuck at 5%. Now I cant go back and its stuck on bootloader. What should i do?
When i go on recover or factory reset the bootloader just comes back up
I tried the uk 02 RUU
The phone is htc one M7
Any help would be greatly appreciated!!
I have tried searching for this problem but the solution i can find needs access to the phone.
***Tampered***
***Relocked***
***security warning***
m7_ul PVT SHIP S-on RH
HBOOT-1.57.0000
Radio-4t.28.3218.04
OpenDSP-v32.120.274.0909
os-
emmc-boot 2048MB
I have attached pictures about errors on RUU
Click to expand...
Click to collapse
post fastboot getvar all
so we can suggest possible RUU
remove imei and serial from getvar
yatindroid said:
post fastboot getvar all
so we can suggest possible RUU
remove imei and serial from getvar
Click to expand...
Click to collapse
sorry for the extremly late reply gave up on it but now need to fix this.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I have tried for hours to get this information such noob shouldn't have messed with this in the first place
thuvcasio said:
sorry for the extremly late reply gave up on it but now need to fix this.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I have tried for hours to get this information such noob shouldn't have messed with this in the first place
Click to expand...
Click to collapse
Flash the 7.18.206.2 ruu from here
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Read the flashing instructions first, use htc_fastboot to flash, when flashing the phone will reboot part way through and continue. Leave it alone 10-15 minutes and be sure it says finished.
mb_guy said:
Flash the 7.18.206.2 ruu from here
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Read the flashing instructions first, use htc_fastboot to flash, when flashing the phone will reboot part way through and continue. Leave it alone 10-15 minutes and be sure it says finished.
Click to expand...
Click to collapse
it has taken me 2 days and couple of flashes and got it working again, thanks a bunch for pointing me in the right direction buddy!:good:
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Sean1971 said:
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Click to expand...
Click to collapse
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
alray said:
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
Click to expand...
Click to collapse
Great thanks for your help, I will give that a try today.
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Sean1971 said:
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Click to expand...
Click to collapse
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
alray said:
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
Click to expand...
Click to collapse
Thanks for your help, really appreciate it. See I said I was out of my depth ....
I tried Toweroot and that wouldn't work for my device, so then tried Kingroot and that sorted it so I was able to run Sunshine and I now have it S-OFF and Unlocked, I can now try to get it back to stock and get it network unlocked.
Good Morning Everyone,
first of all, thanks for everything I am a member since the HTC Touch HD times, where XDA enabled me to keep that device until 2015!!
Now I have a problem with the Desire 500 single sim of my wife... I just want to restore the phone to full stock to lend it to her mother so she can stay in contact with 21th-century technology (Whatsapp, ...).
Some time ago a messed a little with this device unlocking the bootloader and installing TWRP recovery, the idea was (as probably all the owners know) to install a light version ROM to have a little more space for applications, time wasn't on my side and therefore I had to leave the phone for a while, but as I can remember in working condition (still with the stock ROM).
I had some time to finish the work and a week ago a took out the phone again having a not very good surprise:
I can access now only the bootloader
Recovery send me in fastboot mode
Factory Reset send me in fastboot mode
Classic boot get me to the HTC green logo on white background without doing nothing
Fastboot commands are correctly taken
I am unable to flash whatsoever
I have to charge the phone with the batch file, but with manual booting in bootloader, otherwise, the script does not work
I am unable to relock the bootloader (the fastboot OEM lock throws a "too many links" error and fails)
The command fastboot OEM rebootRUU reboot the device, but not in RUU mode.
The bootloader is still unlocked 1.03.0001
The phone is S-ON
The OS line in the bootloader is empty
Flashing recovery throws "remote:image updated error"
Bootloader INFO
Code:
*** UNLOCKED ***
Z4U PVT SHIP S-ON RL
HBOOT-1.03.0001
RADIO-14.16.36Q4.22
OS-
eMMc-boot
Jul 8 2014, 19:15:10.0
fastboot getvar all
Code:
C:\Users\xxx>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0001
(bootloader) version-baseband: 14.16.36Q4.22
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH449WE0XXXX
(bootloader) imei: XXX
(bootloader) meid:
(bootloader) product: z4u
(bootloader) platform: HBOOT-8x25Q
(bootloader) modelid: 0P3Z11200
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e9f20193
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I think I almost checked all the internet, any suggestion simply does not work.
I tried to flash different recoveries, ROMs, RUUs... nothing works.
I need to consider the device bricked or do you guys have some other idea to try resolving the problem?
Thanks even if you spend some time for reading...
Bye
NP