Database Develop

[SOLVED] Google'd and Google'd but still need help

Hi guys
I have looked and looked but need some help
I have a HTC One which I successfully converted to a "stock" GPE with no problems, but I have found that I miss some little bit HTC Zoe for example.I can detect the device with ADB and can use oem writecid to change to HTC__001 which I need to flash the RUU.zip
I have tried tool kits and adb but I am having no luck with the following.
Changing the MID so I can flash a stock RUU
Unlocking the RELOCKED bootloader
I have S-Off
Below is where I am at the moment.
******RELOCKED*******
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT- 1.54. 0000
RADIO-4T. 21. 3218. 21
OpenDSP-v32. 120. 274. 0909
OS- 3.62. 1700. 1
eMMC-boot 2048MB
Dec 9 2013, 00:38:19. 0
Any help or guidance would be great

lspec230 said:
Hi guys
I have looked and looked but need some help
I have a HTC One which I successfully converted to a "stock" GPE with no problems, but I have found that I miss some little bit HTC Zoe for example.I can detect the device with ADB and can use oem writecid to change to HTC__001 which I need to flash the RUU.zip
I have tried tool kits and adb but I am having no luck with the following.
Changing the MID so I can flash a stock RUU
Unlocking the RELOCKED bootloader
I have S-Off
Below is where I am at the moment.
******RELOCKED*******
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT- 1.54. 0000
RADIO-4T. 21. 3218. 21
OpenDSP-v32. 120. 274. 0909
OS- 3.62. 1700. 1
eMMC-boot 2048MB
Dec 9 2013, 00:38:19. 0
Any help or guidance would be great
Click to expand...
Click to collapse
With S-OFF you don't need an unlocked bootloader tu flash in ruu mode.
so change your CID to HTC__001:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then use this tool to change MID back to PN0710000
you must use this tool from custom recovery so if you are on stock recovery, yes you will have to unlock bootloader again and flash latest twrp recovery.Unlock Via htcdev or with s-off method, as you wish.
then follow nkk71's guide to return to stock (linked in my signature below). Follow post #1 and #3 (use ruu.zip method) with 1.28.401.7 ruu.zip from htc1guru.com

Thanks for your help
alray said:
With S-OFF you don't need an unlocked bootloader tu flash in ruu mode.
so change your CID to HTC__001:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then use this tool to change MID back to PN0710000
you must use this tool from custom recovery so if you are on stock recovery, yes you will have to unlock bootloader again and flash latest twrp recovery.Unlock Via htcdev or with s-off method, as you wish.
then follow nkk71's guide to return to stock (linked in my signature below). Follow post #1 and #3 (use ruu.zip method) with 1.28.401.7 ruu.zip from htc1guru.com
Click to expand...
Click to collapse
I used HTCDev to get unlock, I have kept the unlock.bin but it doesn't seem to work now.....is that because I have changed CID and MID? Do i need to go back to HTCDev and get another unlock
Thanks for the quick reply...exactly what i needed a clear concise way ahead rather than me stumbling around with frustration

@lspec230 just to be sure you see that I have edited my above post with additional info
if you have more questions, just ask here. I'll be back in a few hours but im sure others members will assist you here.
---------- Post added at 06:14 PM ---------- Previous post was at 06:14 PM ----------
lspec230 said:
I used HTCDev to get unlock, I have kept the unlock.bin but it doesn't seem to work now.....is that because I have changed CID and MID? Do i need to go back to HTCDev and get another unlock
Thanks for the quick reply...exactly what i needed a clear concise way ahead rather than me stumbling around with frustration
Click to expand...
Click to collapse
You need a new unlock code each time

ARGH...Unlock not working
alray said:
@lspec230 just to be sure you see that I have edited my above post with additional info
if you have more questions, just ask here. I'll be back in a few hours but im sure others members will assist you here.
---------- Post added at 06:14 PM ---------- Previous post was at 06:14 PM ----------
You need a new unlock code each time
Click to expand...
Click to collapse
I went to HTCDev and got a new Unlock_code.bin with no trouble at all.
Used the following and all appears to push to the device but then nothing, I dont get the HTC Bootloader splash screen asking if i want to proceed.
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x8
6_64-20131030\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s

Forget about the bootloader unlocking. Change MID/CID and flash a full RUU!
Luckily you are soff
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
Also, are you rooted?

Still no luck
Not sure what's going on....I cant install TWRP on there to change the MID or Flash a stock RUU
I tried from ADB and for past experience from Samsung also copied it to the phone hoping I could flash from recovery, but there isn't an option for that.
Cant help but think the RELOCKED flag is causing the problems.
I will try a factory reset and cache/partition wipe and start again.
I suppose one option is to flash a RUU that will work with my current MID. Then start the process from there.....

lspec230 said:
Not sure what's going on....I cant install TWRP on there to change the MID or Flash a stock RUU
I tried from ADB and for past experience from Samsung also copied it to the phone hoping I could flash from recovery, but there isn't an option for that.
Cant help but think the RELOCKED flag is causing the problems.
I will try a factory reset and cache/partition wipe and start again.
I suppose one option is to flash a RUU that will work with my current MID. Then start the process from there.....
Click to expand...
Click to collapse
can you post the current "fastboot getvar all" (excluding IMEI and s/n) and I'll post a package for you.

getvar
nkk71 said:
can you post the current "fastboot getvar all" (excluding IMEI and s/n) and I'll post a package for you.
Click to expand...
Click to collapse
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-20
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3822mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
There you go...This has now got personal, I could stay with GPE but I amnow determined to get this to work!!
Many thanks for the help so far...really appreciate it

lspec230 said:
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-20
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
all: Done!
finished. total time: 0.066s
There you go...This has now got personal, I could stay with GPE but I amnow determined to get this to work!!
Many thanks for the help so far...really appreciate it
Click to expand...
Click to collapse
Here you go, download that, then
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3.zip
fastboot reboot-bootloader
-> enter TWRP, use Guru Bootloader Reset tool, or scotty's adb command to unlock

Thanks for your help
nkk71 said:
Here you go, download that, then
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3.zip
fastboot reboot-bootloader
-> enter TWRP, use Guru Bootloader Reset tool, or scotty's adb command to unlock
Click to expand...
Click to collapse
All sorted thanks so much for the help
Not sure if I will even understand but what was going wrong?
:good:

lspec230 said:
All sorted thanks so much for the help
Not sure if I will even understand but what was going wrong?
:good:
Click to expand...
Click to collapse
now follow @alray's instructions to change MID and CID, and flash stock Sense ruu.zip
remember to stay S-Off, and in my guide check "Not so FAQ #2" to see what was wrong.

ALL DONE!
nkk71 said:
now follow @alray's instructions to change MID and CID, and flash stock Sense ruu.zip
remember to stay S-Off, and in my guide check "Not so FAQ #2" to see what was wrong.
Click to expand...
Click to collapse
To all who helped many thanks.....now back on sense!! that was a mission!!

lspec230 said:
To all who helped many thanks.....now back on sense!! that was a mission!!
Click to expand...
Click to collapse
Congrats,
if you could also edit main thread title to include [SOLVED], thanks

One last question...OTA updates
nkk71 said:
Congrats,
if you could also edit main thread title to include [SOLVED], thanks
Click to expand...
Click to collapse
Followed your guide, and went S-On thinking i would get OTA's is this right?
I have included my getvar all
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-201310
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3227.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.20.401.1
(bootloader) version-misc: PVT SHIP S-ON
(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: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Also attached is my software info

lspec230 said:
Followed your guide, and went S-On thinking i would get OTA's is this right?
I have included my getvar all
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-201310
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-main: 1.20.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
Also attached is my software info
Click to expand...
Click to collapse
1- Why oh why did you go S-On?? You don't need S-On for OTAs
2- Why dint you read this: "---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead"
Okay so now you're S-On, bootloader locked or unlocked?
bootloader has to be locked or relocked, then go ahead and flash the 1.28.401.7 ruu.zip, then get S-Off!
then stay UNLOCKED and S-Off and take all the OTAs you like then report back
any reason you need S-On??

nkk71 said:
1- Why oh why did you go S-On?? You don't need S-On for OTAs
2- Why dint you read this: "---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead"
Okay so now you're S-On, bootloader locked or unlocked?
bootloader has to be locked or relocked, then go ahead and flash the 1.28.401.7 ruu.zip, then get S-Off!
then stay UNLOCKED and S-Off and take all the OTAs you like
any reason you need S-On??
Click to expand...
Click to collapse
Because I am a FOOL!!! I missed that by not reading properly....

lspec230 said:
Because I am a FOOL!!! I missed that by not reading properly....
Click to expand...
Click to collapse
okay, so slow it down a little, take a deep breath and no panicking or rushing things!!! okay?
Here's what you're going to do:
1- lock/relock bootloader
2- flash ruu.zip 1.28.401.7
3- DO NOT TAKE ANY OTAs
4- use revone, to get S-Off, and unlock your phone
Once that is done report back, if you have questions, please go ahead ask before doing things
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
lspec230 said:
Because I am a FOOL!!! I missed that by not reading properly....
Click to expand...
Click to collapse
PS: if ruu.zip fails, giving "signature fail" it's cause it's not signed and you are now S-ON.
in that case use RUU.EXE: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
no need to "downgrade hboot", just run the RUU.EXE, NOTHING ELSE and report back with a "fastboot getvar all"

lspec230 said:
Because I am a FOOL!!! I missed that by not reading properly....
Click to expand...
Click to collapse
alray said:
Follow post #1 and #3 (use ruu.zip method) with 1.28.401.7 ruu.zip from htc1guru.com
Click to expand...
Click to collapse
2) RUU.ZIP (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/ruu-zip-downloads/ <- this is now the preferred method instead of RUU.EXE
------> if you’ve found a RUU.ZIP proceed to post 3
---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead
Click to expand...
Click to collapse
hopefully you did not bricked your phone here,just take your time to read carefully next time

alray said:
hopefully you did not bricked your phone here,just take your time to read carefully next time
Click to expand...
Click to collapse
i don't think a brick is involved, but i guess i need to do some revisions about the S-On part (when it's needed and when not ), but as someone mentioned, the guide is "cluttered" already :crying:
@lspec230 any progress mate?

[Q] Can't flash rom

Hi guys! Can't launch my phone after bad flashing.
SDcard on phone is empty. Have read the forum, tried to flash using adb (push to sdcard, sideload), fastboot (rebootRUU). Tried diffrent recoveries, now have CWM 6.0.46 installed. I tried install ~5 diffrent ROMs. Usually i have no errors when installing but still can't launch phone. (Still endless load logo)
1. Recovery shows only 1795mb free spase (is it ok?)
2. When trying to type "fastboot erase *" commands have an error: failed <remote not allowed>
3. While installing Renovate SixthSense it gives me an error symlink:some symlinks failed on Toolbox step.
What shoud i do?

Output of fastboot getvar all?
sent from my mobile device

SaHiLzZ said:
Output of fastboot getvar all?
Click to expand...
Click to collapse
Here:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA349S900672
(bootloader) imei: 990001465442622
(bootloader) meid: 99000146544262
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4303mV
(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
all: Done!

MoHcmp said:
Hi guys! Can't launch my phone after bad flashing.
SDcard on phone is empty. Have read the forum, tried to flash using adb (push to sdcard, sideload), fastboot (rebootRUU). Tried diffrent recoveries, now have CWM 6.0.46 installed. I tried install ~5 diffrent ROMs. Usually i have no errors when installing but still can't launch phone. (Still endless load logo)
1. Recovery shows only 1795mb free spase (is it ok?)
2. When trying to type "fastboot erase *" commands have an error: failed <remote not allowed>
3. While installing Renovate SixthSense it gives me an error symlink:some symlinks failed on Toolbox step.
What shoud i do?
Click to expand...
Click to collapse
just push a rom you dowloaded to your phone
open command prompt an write
adb push ROM.zip /sdcard/.
or perhaps this thread can help you
http://android-revolution-hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html
or
http://android-revolution-hd.blogspot.com/2013/12/how-to-copy-rom-zip.html

What the heck are you doing here with a sprint HTC One but WWE edition firmware. OH you are so screwed...
sent from my mobile device
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
Luckily you are S-OFF. Please do not lock bootloader or go s-on. Just flash a SPRINT ruu!
sent from my mobile device

SaHiLzZ said:
Luckily you are S-OFF. Please do not lock bootloader or go s-on. Just flash a SPRINT ruu!
sent from my mobile device
Click to expand...
Click to collapse
Thanks a lot! But there one trouble left. It start workin, all warks goot exclude htc dialer. And phone rebooting each 5-10 minutes.
I didn't flash sprint firmware. Do i need to flash it?

SaHiLzZ said:
What the heck are you doing here with a sprint HTC One but WWE edition firmware. OH you are so screwed...
sent from my mobile device
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
Luckily you are S-OFF. Please do not lock bootloader or go s-on. Just flash a SPRINT ruu!
sent from my mobile device
Click to expand...
Click to collapse
where have you been?? you're missing all the ** flying around!! I even got my umbrella out!
MoHcmp said:
Thanks a lot! But there one trouble left. It start workin, all warks goot exclude htc dialer. And phone rebooting each 5-10 minutes.
I didn't flash sprint firmware. Do i need to flash it?
Click to expand...
Click to collapse
OP, nice screenshot, are you saying you have a Sprint M7 with HTC Sense 6?
"htc dialer. And phone rebooting each 5-10" means you're modem is not in the best of states!! so use an RUU for your model, and hope it brings it back to life!!

nkk71 said:
OP, nice screenshot, are you saying you have a Sprint M7 with HTC Sense 6?
Click to expand...
Click to collapse
I tried this one: Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed | myHUB
What shoud i install:
1) [ROM][STOCK]Sprint One Stock 3.04.651.2 Rooted | Odex | Deodexed
2) [Roms][ SPRINT ONE] Stock Rooted 3.05.651.6 - Odex & Deodexed
3) Eciptic One

nkk71 said:
OP, nice screenshot, are you saying you have a Sprint M7 with HTC Sense 6?
"htc dialer. And phone rebooting each 5-10" means you're modem is not in the best of states!! so use an RUU for your model, and hope it brings it back to life!!
Click to expand...
Click to collapse
All of this was because of wrong Radio. If someone have same trouble, just flash radio for your device.

[Q] HTC One M7 RUU IMG Error

Hey guys,
I recently got S-Off on my device and downgraded my HBoot to 1.44 and changed to SuperCID 11111111
The RUU i downloaded is " Sprint_HTC_One_m7wls_4.06.651.4_RUU"
The reason i need to go back to stock to see if i can get my Wifi and Bluetooth to start working again since it's stuck in "turning on mode" I have tried flashing new roms, radios, kernals, factory reset etc. No idea why Wifi and Bluetooth stopped working i just woke up one morning and it wouldn't turn on.
For some reason when flashing this RUUi keep on getting 158 IMG error? I have tried running as admin, and making sure phone is in Fastboot USB but still wont work.
Which RUU should i try, any help would be awesome as i would love to get my Wifi and Bluetooth working again, here are my phones details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4079mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks guys.

iAMuSIK said:
Hey guys,
I recently got S-Off on my device and downgraded my HBoot to 1.44 and changed to SuperCID 11111111
The RUU i downloaded is " Sprint_HTC_One_m7wls_4.06.651.4_RUU"
The reason i need to go back to stock to see if i can get my Wifi and Bluetooth to start working again since it's stuck in "turning on mode" I have tried flashing new roms, radios, kernals, factory reset etc. No idea why Wifi and Bluetooth stopped working i just woke up one morning and it wouldn't turn on.
For some reason when flashing this RUUi keep on getting 158 IMG error? I have tried running as admin, and making sure phone is in Fastboot USB but still wont work.
Which RUU should i try, any help would be awesome as i would love to get my Wifi and Bluetooth working again, here are my phones details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4079mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks guys.
Click to expand...
Click to collapse
Sprint_HTC_One_m7wls_4.06.651.4_RUU
Click to expand...
Click to collapse
this ruu isn't for your phone at all !
You have a M7_UL (GSM) not a M7WLS (sprint CDMA) !!
What was your original CID?
Your main-ver is .401 so you probably need a .401 ruu

alray said:
this ruu isn't for your phone at all !
You have a M7_UL (GSM) not a M7WLS (sprint CDMA) !!
What was your original CID?
Your main-ver is .401 so you probably need a .401 ruu
Click to expand...
Click to collapse
Its a good thing that RUU check for MID/CID... or I can't imagine posts from the amount of mis-match flashing.. :cyclops:

@iAMuSIK
From this thread:
You:
My HTC is a M7 on Optus Australia network.
Click to expand...
Click to collapse
so your cid was probably OPTUS001 and you need a .980 version
LS.xD:
Seems as there is no matching RUU
Click to expand...
Click to collapse
You:
So there is no Ruu for my phones carrier which does suck.
Click to expand...
Click to collapse
So why did you attempted to flash an incompatible RUU even if you already know there is none compatible for your phone?

I was
I was under the impression that if i was S-OFF and had SuperCID that i could run any RUU.
I know there is no RUU for my device hence why i wanted to get S-OFF and SuperCID so i could try another RUU, so this is not possible?
I have the nandroid backup for my device but when i flashed it Wifi and Bluetooth would still not work. Looks like i might have to send it into the shop for repairs.

iAMuSIK said:
I was under the impression that if i was S-OFF and had SuperCID that i could run any RUU.
Click to expand...
Click to collapse
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
Click to expand...
Click to collapse
I thought i did read everything, which obviously i missed a few parts. Since the nandroid backup didn't work ill take defeat and accept my Wifi and Bluetooth is possibly a hardware issue. Can't send phone in for warrenty since its "Rooted" so hopefully i can find a good repair center around my part of town.

iAMuSIK said:
I thought i did read everything, which obviously i missed a few parts. Since the nandroid backup didn't work ill take defeat and accept my Wifi and Bluetooth is possibly a hardware issue. Can't send phone in for warrenty since its "Rooted" so hopefully i can find a good repair center around my part of town.
Click to expand...
Click to collapse
try what I said above (post edited)

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.
Click to expand...
Click to collapse
Just saw your added info, thanks a lot mate. Will give his a try today and report back if it works, fingers crossed!

iAMuSIK said:
Can't send phone in for warrenty since its "Rooted".
Click to expand...
Click to collapse
you can go back to stock with your nanadroid backup using this guide: http://forum.xda-developers.com/showthread.php?t=2541082 en send your phone for warranty repair

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.
Click to expand...
Click to collapse
Just in the middle of doing this process now and im getting a error when trying to write CID.
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem writecid H
TC_001
...
(bootloader) fail: [writecid] Invalid cid
OKAY [ 0.013s]
finished. total time: 0.014s
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
EDIT: 2 underscores and not 1 lol.

So
@alray
So finally got the RUU but still not Wifi and Bluetooth working. Hardware issue it is. Thanks a lot for the help in getting this to work bud

[Q] Help M7 stuck in fastboot

Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ????
(bootloader) imei: ????
(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: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.

thintin said:
Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
Click to expand...
Click to collapse
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.

Seanie280672 said:
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Click to expand...
Click to collapse
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Click to expand...
Click to collapse
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l

thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Click to expand...
Click to collapse
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
Click to expand...
Click to collapse
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.

Seanie280672 said:
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Click to expand...
Click to collapse
Sure, I appreciate your help with this
<<<< Identifier Token Start >>>>
5A5F19A2F517CC2BEA0DDADB1C3924C7
FA7846F59B3E38FC5897B053899BA233
824B607DDBDD9CE31E453E48CBE4EF5C
8ECD29487C09FE311D30DA91386C56C5
FF130E636BA23977B05905925EB17FC6
3EBBCC1BFCB2383B1A7DAFDCBFBE0AA7
8DA65BF8F702E6F44F24743AFA8573EB
AE8D23E995EED6E7CBC5981CEBBAFC66
694176C863DB9858CC535ED2D3EC609C
043196ED2CDF60AC13DEBBB636AA348E
E748366B4CA16747C0593C363D6B98E2
81C2699B2D1D979E7ACAC97D4187788E
85AEA5F27B48A9F8278A0B49D0D3838B
92E2EDFE6B16EEEDE98F322D92294ED0
E43D1945184BBF8A0CB9661B92CB9E38
040AAF8857A0FC1A4C7682ACF8120340
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
I'm s-on BTW in case that makes a difference; never been s-off.

thintin said:
Sure, I appreciate your help with this
I'm s-on BTW in case that makes a difference; never been s-off.
Click to expand...
Click to collapse
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?

Seanie280672 said:
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Click to expand...
Click to collapse
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?

thintin said:
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
Click to expand...
Click to collapse
yes defiantly, download the attachment and click the link on the email to continue the instructions.

Seanie280672 said:
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Click to expand...
Click to collapse
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.

thintin said:
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
Click to expand...
Click to collapse
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?

Seanie280672 said:
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Click to expand...
Click to collapse
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1

thintin said:
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
Click to expand...
Click to collapse
ok good, also could you post a link to the O2 RUU you downloaded earlier

Seanie280672 said:
ok good, also could you post a link to the O2 RUU you downloaded earlier
Click to expand...
Click to collapse
GRRR!
Following firewater instructions...
adb reboot <–important!!!!
Click to expand...
Click to collapse
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
adb wait-for-device push firewater /data/local/tmp
Click to expand...
Click to collapse
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.

thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
Click to expand...
Click to collapse
try this version of adb and fastboot instead, sounds like its out of date and also check your device manager, make sure it says MyHTC when your phone is plugged in: http://forum.xda-developers.com/showthread.php?t=2588979

thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
Click to expand...
Click to collapse
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.

majmoz said:
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
Click to expand...
Click to collapse
Don't worry, I didn't type the important! bit
I'm not sure how much more time I want to spend trying to reset this device, maybe I'll just return it to O2 as it is and see if they even care that it's been unlocked!
I'll try the link you suggested and report back :tired:

Hi.
I think my guardian angel must have had a hand in this because I was only trying to reset the phone to return it due to the microphone not working. After all of these failed attempts I factory reset the current rom and bingo! Microphone working again and no need to return to O2
But thanks for all of the help you offered, I would have a lot less hair and more wrinkles without you.

[Q] Downgrade to KitKat+Root - Help?

So my M7 started heating up, chewing battery. Everything was fine with the first L update, but after the second one, something went wrong.
Now, I don't really want to do a factory reset - if I don't have to. And to be honest, it never helped with these random battery/cpu hogs in Android.
So!
- Could anyone link me the latest KitKat RUU? OR whatever I have to flash/install?
- The warranty is now gone for the phone, so I also want to root. How should I root? Via HTCDev? Sunshine?
If I can install KitKat somehow without losing files, I would just Sunshine - would save me tons of work (restore).
Thanks!
Ps.: I am not lazy, and I really tried to find the answers - but compared to how easy to flash an LG or Samsung, HTC looks like a spacecraft.
Seriously, while the two other have simple firmware files, and a simple app to flash, HTC got RUU, different unlocks, different firmwares, etc.
* I also thought about switching it to GPE, but honestly, 5.1 is not any better.
And it's the last update for the M7... it's a dead end anyhow.
KitKat will serve this phone perfectly fine for +1-2 years.

h8Aramex said:
- Could anyone link me the latest KitKat RUU? OR whatever I have to flash/install?
Click to expand...
Click to collapse
Impossible to tell without knowing your phone info. Post the output of "fastboot getvar all" remove imei and sn before posting.
- The warranty is now gone for the phone, so I also want to root. How should I root? Via HTCDev? Sunshine?
Click to expand...
Click to collapse
If your goal is to return to kitkat then
1- return to kitkat, how exactly will be determined after you have posted your "fastboot getvar all"
2- root the phone (unlock the bootloader, flash a custom recovery, flash latest supersu.zip)
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
If I can install Kitat somehow without losing files
Click to expand...
Click to collapse
RUU will wipe everything
Flashing a rom requires an unlocked bootloader, unlocking the bootloader wipes everything.
So you will lose your files, backup first.

Sorry for the noob question, command issued while in normal mode through ADB?
Or in fastboot through ADB?
alray said:
Impossible to tell without knowing your phone info. Post the output of "fastboot getvar all" remove imei and sn before posting.
If your goal is to return to kitkat then
1- return to kitkat, how exactly will be determined after you have posted your "fastboot getvar all"
2- root the phone (unlock the bootloader, flash a custom recovery, flash latest supersu.zip)
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
RUU will wipe everything
Flashing a rom requires an unlocked bootloader, unlocking the bootloader wipes everything.
So you will lose your files, backup first.
Click to expand...
Click to collapse

h8Aramex said:
Or in fastboot through ADB?
Click to expand...
Click to collapse
fastboot commands are always/can only be issued when the phone is booted in bootloader mode with "fastboot usb" red caption showing.
adb commands are/can only be used when booted in the OS with usb debug turned on or from a custom recovery no matter if usb debug is turned on or off.

alray said:
fastboot commands are always/can only be issued when the phone is booted in bootloader mode with "fastboot usb" red caption showing.
adb commands are/can only be used when booted in the OS with usb debug turned on or from a custom recovery no matter if usb debug is turned on or off.
Click to expand...
Click to collapse
Sorry for the delay.
(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.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------
(bootloader) imei: 1111111111111111
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4068mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
Click to expand...
Click to collapse
I want the latest 4.4 FW/ROM, preferably stock.
(But if that Revolution rom works fine, I am also fine with that one.)
--------------------------------
UPDATE:
Ok, so I thought I will try things by myself... it cannot be that hard.
I was wrong.
I am now more confused than ever.

h8Aramex said:
Sorry for the delay.
I want the latest 4.4 FW/ROM, preferably stock.
(But if that Revolution rom works fine, I am also fine with that one.)
--------------------------------
UPDATE:
Ok, so I thought I will try things by myself... it cannot be that hard.
I was wrong.
I am now more confused than ever.
Click to expand...
Click to collapse
Since that your phone is s-on you can not use a RUU to downgrade, you will have to unlock your bootloader, flash a custom recovery and finally flash a 4.4 rom. You'll will not be able to downgrade the firmware with S-ON, you can only change your rom.
to unlock the bootloader go at www.htcdev.com/bootloader and follow the instructions
once done flash a custom recovery, preferably TWRP 2.8.6.0:
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
boot in recovery and transfer the rom zip file you want to flash to your phone storage.
in twrp select "install" and flash your rom.

alray said:
////
Click to expand...
Click to collapse
Could you link me a 4.4 ROM, please?
Preferably Stock, HTC Sense one.
I checked the pinned thread, but every file is 404 (missing) by now, since it's a very old thread/post.
Thank you!

h8Aramex said:
Could you link me a 4.4 ROM, please?
Preferably Stock, HTC Sense one.
I checked the pinned thread, but every file is 404 (missing) by now, since it's a very old thread/post.
Thank you!
Click to expand...
Click to collapse
Stock 4.4.2 rom, latest version before lollipop (6.09.401.12)
https://www.androidfilehost.com/?fid=95916177934521261

Thank you!
I have managed to unlock + root (that wasn't really so hard, using Sunshine would have been harder). Will try to stay on L now, see if the reset helped with the battery drain. If not, it's time for Kitkat!