[Q] No OS Installed - One (M7) Q&A, Help & Troubleshooting

hi there, i do apologize for my english first of all. Im not new in all this stuff but i have one great question for you all: Recently i converted my One to GE edition and after a couple of months i wanted to install ARHD(im unlocked, s-off) but when i did it (in twrp and in cwm) my system partition seems just broken 30 mb only, and when i do reboot my phone it stucks on bootloader screen, i tryed arhd(different versions) stock rom, and none of these wont boot up my phone, only GE edition of firmware. (i have supercid also) what i can do to get back stock or ARHD?

AlexVendettA said:
hi there, i do apologize for my english first of all. Im not new in all this stuff but i have one great question for you all: Recently i converted my One to GE edition and after a couple of months i wanted to install ARHD(im unlocked, s-off) but when i did it (in twrp and in cwm) my system partition seems just broken 30 mb only, and when i do reboot my phone it stucks on bootloader screen, i tryed arhd(different versions) stock rom, and none of these wont boot up my phone, only GE edition of firmware. (i have supercid also) what i can do to get back stock or ARHD?
Click to expand...
Click to collapse
Try and format everything in cwm then sideload a rom...use the toolkit

ndmuni said:
Try and format everything in cwm then sideload a rom...use the toolkit
Click to expand...
Click to collapse
Thank you for reply, but i already did it with sideload and with oem rebootRUU, i tryed ARHD, Stock, S11(cyanogen), ViperOne. But i can install only GPE roms =/ other roms wont install system partition it remains 30mb.

AlexVendettA said:
hi there, i do apologize for my english first of all. Im not new in all this stuff but i have one great question for you all: Recently i converted my One to GE edition and after a couple of months i wanted to install ARHD(im unlocked, s-off) but when i did it (in twrp and in cwm) my system partition seems just broken 30 mb only, and when i do reboot my phone it stucks on bootloader screen, i tryed arhd(different versions) stock rom, and none of these wont boot up my phone, only GE edition of firmware. (i have supercid also) what i can do to get back stock or ARHD?
Click to expand...
Click to collapse
If you want to convert back to Sense from GPE I strongly recommend you return your device back to 100% Sense Stock by flashing an ruu first.
Then you can flash TWRP 2.6.3.3 Custom recovery and install ARHD. Make sure you use TWRP 2.6.3.3 though and not a newer version for trouble free install of ARHD.
If you can post your getvar all (with imei and serial numbers removed) I'd be happy to recommend an ruu and any further instructions you may need to complete the process successfully :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
If you want to convert back to Sense from GPE I strongly recommend you return your device back to 100% Sense Stock by flashing an ruu first.
Then you can flash TWRP 2.6.3.3 Custom recovery and install ARHD. Make sure you use TWRP 2.6.3.3 though and not a newer version for trouble free install of ARHD.
If you can post your getvar all (with imei and serial numbers removed) I'd be happy to recommend an ruu and any further instructions you may need to complete the process successfully :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
actually i didnt tryed am RUU!
(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) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(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

AlexVendettA said:
actually i didnt tryed am RUU!
(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) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(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
Click to expand...
Click to collapse
Follow my post here http://forum.xda-developers.com/showthread.php?p=56294415 to return your device to HTC Unbranded Sense. You don't necessarily need to change your cid but you won't get the ota updates with super cid. You can always change back to super cid once your done. Or just manually flash the firmware updates after the ruu.
Also incase you didn't know you don't and should not relock your bootloader to complete this procedure. Relocking is only for s-on phones and is in my experience is rather dangerous on a gpe converted phone so DO NOT relock your bootloader
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Related

Phone Gets to Setup and Reboots

The phone is a brand new HTC One. After unlocking the bootloader, flashing TWRP 2.6.3.3, rooting it, and flashing a rom (tried insert coin and Sinless), the phone gets past the HTC logo, past the Google logo (Google edition rom), shows setup for a second, and reboots. It would do this until the battery dies. I can get into recovery fine, and do anything other than boot the rom. I've tried multiple roms, multiple recoveries, etc. What should I do? Thanks for any help!
Can you issue fastboot erase cache in bootloader and do a wipe data in recovery before booting?
SaHiLzZ said:
Can you issue fastboot erase cache in bootloader and do a wipe data in recovery before booting?
Click to expand...
Click to collapse
Did both. We wiped the phone completely as well and did it from scratch and it has the exact problem.
Can you post your fastboot getvar all output? Remove Imei
SaHiLzZ said:
Can you post your fastboot getvar all output? Remove Imei
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3B5W907210
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3951mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
You need to be S-Off to run any google edition roms. Listed on the first post of both sinless and arhd GE thread.
SaHiLzZ said:
You need to be S-Off to run any google edition roms. Listed on the first post of both sinless and arhd GE thread.
Click to expand...
Click to collapse
So do you think it will work if we use a Sense rom?
Also can you get S-Off in my situation? How so?
I'm new to this. Thanks for your help. I really appreciate it.
Better question: can we expect run Rumrunner without a functional OS?
You should be on sense based rom for Soff, or ATT nandroid or backup. Reinstall ATT RUU if one available, or adb push a rom in recovery
SaHiLzZ said:
You should be on sense based rom for Soff, or ATT nandroid or backup. Reinstall ATT RUU if one available, or adb push a rom in recovery
Click to expand...
Click to collapse
Feeling really dumb for not trying a Sense rom. One just worked. Thanks for your help!

[Q] Rooting after 5.03.651.3 OTA Update Questions

Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
Can I gain Root on being on 5.03.651.3?
If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!
Rare5spd said:
Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
1. Can I gain Root on being on 5.03.651.3?
2. If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
3. Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!
Click to expand...
Click to collapse
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
ROOTING INSTRUCTIONS:
http://download.chainfire.eu/450/SuperSU/UPDATE-SuperSU-v2.00.zip
Try downloading that file and then flashing it in TWRP. I haven't tested this though as the ROM that I'm using is prerooted.
There's a video by fellow member @zedomax that tells you how to do this, although the SuperSU zip in his video is outdated as the video's made in 2013 , so I linked you the latest one above.
EDIT: Oh and the factory CID for the Sprint HTC One is SPCS_001.
Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!
Rare5spd said:
Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!
Click to expand...
Click to collapse
You could also use these commands if you are S-off
fastboot oem rebootRUU
fastboot flash zip recovery.zip
fastboot reboot
this could flash a recovery since you are S-off and flash back your stock recovery... Make sure you include an android-info.txt file...
In the android-info.txt file include this:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
with that txt file and a recovery be it stock or a custom you can do what you like.
StormyNight said:
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
Click to expand...
Click to collapse
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.
The Glow said:
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.
Click to expand...
Click to collapse
Huh, didn't know that. My apologies. By the way, you still be able to do it even when the next firmware update occurs.
Yesterday i tried to update my phone without success
fisrt i tried to install roms but it didnt work
then i tried to update my main version and fail also
then i dont know why i change mi CID number to HTC__001
it started to brick the screen turn gray but i solved it i don´t know how
but i noticed my phone changed to S-ON
i tried many times with many ruus to restore but i can´nt Problems CID and 152 images i locked before doing this
i insert a rom with the same rom 5.03.651.3 success at installing
it started good still the part i have to write language it stayed in HTC logo and then restart
Now im trying to get S-OFF and change my CID to another number but i don´t know wich
and try RUU again but i can not IT gave error and Rumrunner adb didnt find my device
i don´t know what else to do im also 2 days awake :crying:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA358S900105
(bootloader) imei: 99*****************
(bootloader) meid: 99***************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS sorry im not a native english speaker. try to understand me
i can understand english very well
THANX ALL OF YOU

[Q] Why is my phone confused?

When I try to flash any ROM that has M7SPR in the title, I get an error saying that my phone is the M7. But I have sprint and I am trying to get M7SPR becuase M7 ROM's make me lose data.
Background data:
M7_WLS
SuperCID
S-OFF
MID 20000
Basically my questions are:
1. What would cause my M7SPR to think it is a M7?
2. Is there a workaround to keep LTE with GSM ROMs?
3. If there is no workaround for the #2, how do I get my phone to flash M7SPR ROMs again where I can keep my at least my sprint data intact?
magni08 said:
When I try to flash any ROM that has M7SPR in the title, I get an error saying that my phone is the M7. But I have sprint and I am trying to get M7SPR becuase M7 ROM's make me lose data.
Background data:
M7_WLS
SuperCID
S-OFF
MID 20000
Basically my questions are:
1. What would cause my M7SPR to think it is a M7?
2. Is there a workaround to keep LTE with GSM ROMs?
3. If there is no workaround for the #2, how do I get my phone to flash M7SPR ROMs again where I can keep my at least my sprint data intact?
Click to expand...
Click to collapse
How are you flashing gsm Roms on this phone. They have different partitions.
I think you dun goofed your partitions. Try RUUing to the latest Sprint firmware and never flash a GSM ROM again.
I flashed a stock sprint RUU then while in bootloader, reflashed twrp 2.8, then flashed slimkat m7spr, now if I went back into twrp and tried to flash any other m7spr rom, I get a failure saying that this device is an m7 and this rom is for m7spr...
magni08 said:
I flashed a stock sprint RUU then while in bootloader, reflashed twrp 2.8, then flashed slimkat m7spr, now if I went back into twrp and tried to flash any other m7spr rom, I get a failure saying that this device is an m7 and this rom is for m7spr...
Click to expand...
Click to collapse
fastboot getvar all
Post results here.
Remove serial number and imei.
Also, if you want a response, remember to quote.
sauprankul said:
fastboot getvar all
Post results here.
Remove serial number and imei.
Also, if you want a response, remember to quote.
Click to expand...
Click to collapse
c:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.5555
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------------
(bootloader) imei: ---------------------
(bootloader) meid:-----------------
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(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
There you go, thank you for the advice regarding the response time and quoting.
magni08 said:
(bootloader) version-bootloader: 1.56.5555
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-main: 4.06.651.4
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
Your boot loader is outdated. Current is 1.57. Baseband is off, supposed to be 1.29(edit: I pulled this number from my butt, I meant 1.01) i think. Version is supposed to be 5.05. CID - set it to the default sprint, if that's not it.
sauprankul said:
Your boot loader is outdated. Current is 1.57. Baseband is off, supposed to be 1.29 i think. Version is supposed to be 5.05. CID - set it to the default sprint, if that's not it.
Click to expand...
Click to collapse
Have you got a url for the baseband? This is the only one I could find for this specific phone; http://forum.xda-developers.com/showthread.php?t=2406330 and they seem to be slightly outdated.
magni08 said:
Have you got a url for the baseband? This is the only one I could find for this specific phone; http://forum.xda-developers.com/showthread.php?t=2406330 and they seem to be slightly outdated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2795856
sauprankul said:
http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
I just flashed that RUU and the radio is still 1.01.20
magni08 said:
I just flashed that RUU and the radio is still 1.01.20
Click to expand...
Click to collapse
Still? It was 1.00.2 before the RUU.
Also did you change your cid?
magni08 said:
I just flashed that RUU and the radio is still 1.01.20
Click to expand...
Click to collapse
latest baseband is 1.01.20.0904_2
why would you super cid a sprint phone, it's pointless, because you can't flash GSM roms on a cdma phone,period.
sauprankul said:
Still? It was 1.00.2 before the RUU.
Also did you change your cid?
Click to expand...
Click to collapse
I guess i might have overlooked it, since it was 1.xx.2 looking quickly I thought it was no change. I have not changed the cid. From what I was reading that is considered supercid, which is supposed to bypass carrier specific ROMs. Making it much more difficult to brick.
magni08 said:
I guess i might have overlooked it, since it was 1.xx.2 looking quickly I thought it was no change. I have not changed the cid. From what I was reading that is considered supercid, which is supposed to bypass carrier specific ROMs. Making it much more difficult to brick.
Click to expand...
Click to collapse
Would you considering trying to change back to SPCS_001? (I think that's the right one)
I'm pretty sure changing CID doesn't allow you to flash GSM roms. Super CID only applies to GSM phones.
sauprankul said:
Would you considering trying to change back to SPCS_001? (I think that's the right one)
I'm pretty sure changing CID doesn't allow you to flash GSM roms. Super CID only applies to GSM phones.
Click to expand...
Click to collapse
Can anyone confirm that SPCS__001 is the correct cid for sprint m7? I am down to try it, but I want to be sure that's all.
I do appreciate your help as well!
magni08 said:
Can anyone confirm that SPCS__001 is the correct cid for sprint m7? I am down to try it, but I want to be sure that's all.
I do appreciate your help as well!
Click to expand...
Click to collapse
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: ****
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001 //here is the CID
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
sauprankul said:
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: ****
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001 //here is the CID
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I put my cid back to SPCS_001 and tried another M7SPR rom (http://forum.xda-developers.com/spr...t/5-0-lollipop-unofficial-cm12-m7spr-t2943941 this one specifically) and I get the same message:
This package is for device: m7spr, m7wls: this device is m7.
I also just tried the aokp (http://forum.xda-developers.com/showthread.php?t=2268789) same thing...
This is the only rom (http://forum.xda-developers.com/spr...ock-rooted-5-05-651-2odex-11-15-2014-t2941907) that actually works, rather frustrating.
magni08 said:
I put my cid back to SPCS_001 and tried another M7SPR rom (http://forum.xda-developers.com/spr...t/5-0-lollipop-unofficial-cm12-m7spr-t2943941 this one specifically) and I get the same message:
This package is for device: m7spr, m7wls: this device is m7.
I also just tried the aokp (http://forum.xda-developers.com/showthread.php?t=2268789) same thing...
This is the only rom (http://forum.xda-developers.com/spr...ock-rooted-5-05-651-2odex-11-15-2014-t2941907) that actually works, rather frustrating.
Click to expand...
Click to collapse
@BD619 any idea how this catch meachanism works? Like, what does it read? Seems like everything is set back to default for this one.
Actually did you run the RUU.exe (as opposed to flashing the firmware)? Or try to flash the latest stock ROM (4.4.3, 6.09)?
sauprankul said:
@BD619 any idea how this catch meachanism works? Like, what does it read? Seems like everything is set back to default for this one.
Actually did you run the RUU.exe (as opposed to flashing the firmware)? Or try to flash the latest stock ROM (4.4.3, 6.09)?
Click to expand...
Click to collapse
Sounds like the OP flashed the wrong recovery.
I would suggest run the RUU and start fresh.
OP you posted this in post 1 MID 20000 can you explain what that means?
BD619 said:
Sounds like the OP flashed the wrong recovery.
I would suggest run the RUU and start fresh.
OP you posted this in post 1 MID 20000 can you explain what that means?
Click to expand...
Click to collapse
The recovery is the latest from the twrp team straight from their site. I did try and revert back from 2.8 to 2.6 but it hung up at the htc loading recovery screen. From that hangup I reflashed the 2.8 I was using just to get something moving. I will look into the changing twrp and try something from there.
The MID 20000 is a reference to; modelid: PN0720000 to indicate that I was in fact using the sprint variant of this phone.
Thank you for the assistance.
magni08 said:
The recovery is the latest from the twrp team straight from their site. I did try and revert back from 2.8 to 2.6 but it hung up at the htc loading recovery screen. From that hangup I reflashed the 2.8 I was using just to get something moving. I will look into the changing twrp and try something from there.
The MID 20000 is a reference to; modelid: PN0720000 to indicate that I was in fact using the sprint variant of this phone.
Thank you for the assistance.
Click to expand...
Click to collapse
There is a version of twrp for every variant maybe you flashed one of the other variants by mistake (folks flash the M7_ul version all the time)
Official TWRP
tdhite version of TWRP (try this one first it has been polished a bit more then official)

[Q] Stuck in boot loop after HTC1GURU reset

I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Sklirg said:
I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Click to expand...
Click to collapse
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Could you post your fastboot getvar all please without the imei and serial numbers please.
Seanie280672 said:
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Click to expand...
Click to collapse
That makes sense.
Seanie280672 said:
Could you post your fastboot getvar all please without the imei and serial numbers please.
Click to expand...
Click to collapse
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3956mV
(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.077s
Thanks
Sklirg said:
That makes sense.
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3956mV
(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.077s
Thanks
Click to expand...
Click to collapse
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip
Seanie280672 said:
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
Click to expand...
Click to collapse
Thank you! This worked wonders.
Sklirg said:
Thank you! This worked wonders.
Click to expand...
Click to collapse
Your welcome, that's what we're here for :good:

M7 Trying to get back to stock-but need a helping hand

hey guys, i am now about to sell my m7 after over 2 years
a long time ago when i unlocked the boot loader, and installed tmrp i made a backup of my stock ROM. its been on a usb pen along time now. so today i used twrp to restore it. all when well i then decided to relock the bootloader using fastboot. in my ignorance i thought this was all i would need to do. upon reboot a rom update was found 6.09.401.10. i am currently 6.09.401.5. downloaded and restarted to install the update. recovery wouldnt load. okay that from the twrp flash replacing it. so of course onto xda to find a stock recovery. i believe i found it. but now i am worried- do i need to re unlock the bootloader? will i need to get the token again? or do i need the rru.exe 6.09.401.10? what is the best way to do this as unsure what to do next? as it will need ota updates. i have added my version info below just encase its needed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37WW905236
(bootloader) imei:
(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: 4197mV
(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
thanks in advance
bacon165 said:
hey guys, i am now about to sell my m7 after over 2 years
a long time ago when i unlocked the boot loader, and installed tmrp i made a backup of my stock ROM. its been on a usb pen along time now. so today i used twrp to restore it. all when well i then decided to relock the bootloader using fastboot. in my ignorance i thought this was all i would need to do. upon reboot a rom update was found 6.09.401.10. i am currently 6.09.401.5. downloaded and restarted to install the update. recovery wouldnt load. okay that from the twrp flash replacing it. so of course onto xda to find a stock recovery. i believe i found it. but now i am worried- do i need to re unlock the bootloader? will i need to get the token again? or do i need the rru.exe 6.09.401.10? what is the best way to do this as unsure what to do next? as it will need ota updates. i have added my version info below just encase its needed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37WW905236
(bootloader) imei:
(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: 4197mV
(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
thanks in advance
Click to expand...
Click to collapse
To flash a recovery, even if its the stock one, the bootloader must be unlocked. Unfortunately, unlocking the bootloader requires the stock recovery....
I would keep the bootloader locked and flash the latest RUU version for this phone (7.19.401.51). Look in the general section (in the sticky threads) there is one named "Lollipop RUU collection". You'll find that RUU at post #2 and instructions how to flash at post #1. Be sure to use the fastboot version (htc_fastboot) instructed at post #1 (you can't flash a 7.xx.xxx.x ruu with the fastboot version from the android sdk tools).
This is the link to the RUU. Install the file on PC (it is a big file) and connect your phone and run it.
Should return you to stock Lollipop 5.0.2 with Sense 6.
Download the right one for your variant:
htc.com/us/support/htc-one/news/ (Unlocked/Developer Edition)
htc.com/us/support/htc-one-t-mobile/news/
htc.com/us/support/htc-one-sprint/news/
htc.com/us/support/htc-one-verizon/news/
htc.com/us/support/htc-one-att/news/
alray said:
To flash a recovery, even if its the stock one, the bootloader must be unlocked. Unfortunately, unlocking the bootloader requires the stock recovery....
I would keep the bootloader locked and flash the latest RUU version for this phone (7.19.401.51). Look in the general section (in the sticky threads) there is one named "Lollipop RUU collection". You'll find that RUU at post #2 and instructions how to flash at post #1. Be sure to use the fastboot version (htc_fastboot) instructed at post #1 (you can't flash a 7.xx.xxx.x ruu with the fastboot version from the android sdk tools).
Click to expand...
Click to collapse
Thank you alray for your fast reply i am currently downloading 7.19.401.51 (signed version)
is it the downgrade instructions i need to follow?
Thank you for your reply
my version is the European (uk version)
i am currently downloading the 7.19.401.51 from xda, might take about 2 hours, i will keep you informed with my progress
thanks
bacon165 said:
is it the downgrade instructions i need to follow?
Click to expand...
Click to collapse
No, going from 6.xx.xxx.x to 7.xx.xxx.x isn't a downgrade.
Sent from my HTC One using XDA Labs
Hey Alray
I followed the instructions and the advised you gave me
my HTC M7 is now back up and running RUU installed no problem
thank you again for your guidance/advise
bacon165 said:
Hey Alray
I followed the instructions and the advised you gave me
my HTC M7 is now back up and running RUU installed no problem
thank you again for your guidance/advise
Click to expand...
Click to collapse
You're welcome
Sent from my HTC One using XDA Labs

Categories

Resources