I have unlocked and rooted my HTC One - no problem. Then I made a backup and flashed to a new ROM... before finding out that unless I s-off, it will just reboot over and over and over. Problem is that now I can't seem to s-off. I have tried:
REVONE
This gives me an error that appears to be because I have version 4.4.2 instead of 4.2.2. I have tried flashing to older ROMS (including an RUU version), but it still says 4.4.2. In there some way to flash the kernel or something?
RUMRUNNER
I am able to get this to sort of work, but the phone reboots at the same point each time, and interrupts the process.
FIREWATER
I can't even get this started because I can't get a stable boot with an internet connection... it reboots before I can get there.
RUU
I have tried to use an RUU, but I have Ubuntu (not windows), so I can't use the .exe. I can't flash the RUU (because I have to relock the bootloader), and can't seem to find a way to do this on Linux.
After a few hours a day for a week of trying different things, I am pretty comfortable with fastboot and adb, so if there is something manually I can do, I'm all for it. Otherwise, it seems that I need to revert back to stock somehow (or at least down to 4.2.2)... but I'm not having much luck.
Any ideas?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA341S900500
(bootloader) imei: 990001465191203
(bootloader) meid: 99000146519120
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
version 4.4.2
Update!
Ok - I was finally able to get s-off. I flashed to viperROM_One_v1.1.0.zip from here. That gave me an older version to work with revone. Because of the constant rebooting, I had also been trying to use revone from the recovery tool, but that doesn't work. By booting into the custom ROM and skipping everything on the setup, I was able to keep the phone one for long enough to use revone. I now have s-off!
But, I am still having trouble flashing ROMs. I jumped immediately into the lastest ViperOne ROM (6.2), and tried flashing with CWM recovery multiple times... but it would never boot. Then I tried EclipticOne (3.3), and could get to the boot animation, but then it gets stuck in a reboot cycle. I flashed the boot image from Ecliptic, but still the same thing.
I've also tried flashing an older ViperOne ROM (2.1) plus the boot.img from that one, and it just reboots over and over... never leaving the hboot screen.
At this point, I have two questions:
1) Is it a problem that my "version-main" is blank?
2) Do I need to flash/update my hboot?
Tried going back to stock, but the same thing
I have now tried going back to stock Sprint_HTC_One_1.29.651.10_Stock_Deodexed_05.17.13.zip, and flashed the boot image that goes with it. This *actually* does boot up into the setup... but then reboots itself before I can complete setup. Again...
I thought this whole time that the issue was s-on (maybe it was), but its STILL happening. Any thoughts?
FIXED
It turns out that one of the first ROMs I tried was a GSM, and that messed things up. I followed this tutorial and FINALLY got it working: http://forum.xda-developers.com/showthread.php?t=2503646
Related
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
To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ajr901 said:
To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3_radio_4a-19-3263-13_10-38j-1157-04_release_334235_signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_u..._signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Click to expand...
Click to collapse
Holy **** you are the man! That worked! How did you know that was going to work?!?!
Thank you soooooo much! I love you. I owe you one.
So I've been at this a few days - basically I need to restore my phone to stock because my phone is no longer recognized by HTC SyncMaster, which is where I backed up my phone prior to rooting (which I also encrypted with a password). Rather unfortunate. Have tried rolling back the drivers, installing new/old ones, etc, no luck.
Have tried several ROMs, RUUs (zips and exe's), etc., and the only ROM That seems to work is the Cyanogemod ROM that I used initially - I don't mind it, in fact, I like it, but I need my data back.
I've tried Firewater, the Dev Kernel, side-loading, Odexed (stock), CWN Nandroid Stock, etc. etc. etc. Nothing has worked.
So - a little help, please? I'm not sure what I'm doing wrong - when I sideload/load zip from SDCard, it eventually errors out, if it's not a ROM other than initial CWN. Also, my recovery image is CWM.
I think that the problem is that I have a very new OS/Firmware, and S-ON is preventing me from installing older versions. Does that sound about right?
(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: 5.11.666.8
(bootloader) version-misc: PVT SHIP S-ON
(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: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You can't downgrade an s-on device. Use sunshine for s-off
Thanks - It says I need a stock boot.img... I'm not sure yet where to get one. Tried using the boot.img from the "Stock" CWM zip and it didn't work. Tried to sideload, then upload to the SD Card, still geting an error.
Trying Rumrunner, but pretty sure it won't work.
Still scratching my head...
justpete said:
Thanks - It says I need a stock boot.img... I'm not sure yet where to get one. Tried using the boot.img from the "Stock" CWM zip and it didn't work. Tried to sideload, then upload to the SD Card, still geting an error.
Trying Rumrunner, but pretty sure it won't work.
Still scratching my head...
Click to expand...
Click to collapse
Yup CM won't do it, you need as close to stock Rom.as possible, try a kitkat version of maximusHD or ARHD, you will need to use twrp 2.6.3.3 recovery to flash them , if sideload isn't working then try pushing the Rom, failing that you could always pick up a usb otg cable quite cheap.
I've heard of people having problems coming from CM back to sense roms, once you get twrp on there you may have to wipe then format data, be aware though that this will wipe your entire phone so backup anything you need first, after the format, reboot back into recovery, your sdcard will now be empty, so push the Rom you downloaded to it and flash it.
Hi Guys.
I really need some help here and would really appreciate it as it's driving me up the wall for the past week. And I have combed through the forum looking for a solution before posting. So here goes.
I have a One M7 running on ARHD84 with 6.13.707.1 firmware. Learning of the coming OTA update for Lollipop, I decided to return to stock the best I can S-ON. Thus my nightmare begins.
1) I did a nandroid backup restore with a file named 2014-09-15--13-39-50 KTU84L release-keys (I don't have a nandroid backup of my own). It worked fine. Then I did the OTA update (6.13.707.4). It pops an error "Variant System Version".
2) Thinking it must be the nandroid issue, I went for guru reset 3.63.707.4 ROM and it installed with stock recovery and radio. Startup okay then I did the OTA update. It installed halfway and stopped to show a red exclamation error. I hard reset the phone and it went into a bootloop. It loops at the HTC logo. I went into fastboot, flashed twrp and got my phone back with the nandroid backup.
** Stock recovery goes into black screen.
3) Tried the nandroid again. Still Variant System Version.
4) Tried a lower guru reset 2.24.707.1 and it installed with stock recovery and radio. Startup okay and did the OTA update. It installed 1/3 and went into bootloop. This time it took me many many many tries to get back into bootloader.
** Stock recovery never happens, it just goes to black screen
5) Scoured the internet, came back a little wiser and tried the gurureset 3.63.707.4 again. This time I flashed the stock recovery again just to be sure. And this time, guess what.... same thing. Installs 1/3 and goes into the red exclamation mark. Only advancement was it did not go into bootloop.
My getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: pewpewpew
(bootloader) imei: blablablablabla
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(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
Would really appreciate if someone could help me out here. At my wit's end.
Thanks!
mojo1ne said:
Hi Guys.
I really need some help here and would really appreciate it as it's driving me up the wall for the past week. And I have combed through the forum looking for a solution before posting. So here goes.
I have a One M7 running on ARHD84 with 6.13.707.1 firmware. Learning of the coming OTA update for Lollipop, I decided to return to stock the best I can S-ON. Thus my nightmare begins.
1) I did a nandroid backup restore with a file named 2014-09-15--13-39-50 KTU84L release-keys (I don't have a nandroid backup of my own). It worked fine. Then I did the OTA update (6.13.707.4). It pops an error "Variant System Version".
2) Thinking it must be the nandroid issue, I went for guru reset 3.63.707.4 ROM and it installed with stock recovery and radio. Startup okay then I did the OTA update. It installed halfway and stopped to show a red exclamation error. I hard reset the phone and it went into a bootloop. It loops at the HTC logo. I went into fastboot, flashed twrp and got my phone back with the nandroid backup.
** Stock recovery goes into black screen.
3) Tried the nandroid again. Still Variant System Version.
4) Tried a lower guru reset 2.24.707.1 and it installed with stock recovery and radio. Startup okay and did the OTA update. It installed 1/3 and went into bootloop. This time it took me many many many tries to get back into bootloader.
** Stock recovery never happens, it just goes to black screen
5) Scoured the internet, came back a little wiser and tried the gurureset 3.63.707.4 again. This time I flashed the stock recovery again just to be sure. And this time, guess what.... same thing. Installs 1/3 and goes into the red exclamation mark. Only advancement was it did not go into bootloop.
My getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: pewpewpew
(bootloader) imei: blablablablabla
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(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
Would really appreciate if someone could help me out here. At my wit's end.
Thanks!
Click to expand...
Click to collapse
Try this TWRP backup https://www.bloglovin.com/blogs/xda-developers-5233323/stock-rom-6137071-asia-twrp-backup-3430002891 do not use the modified firmwqare, it will brick your phone as your s-on.
Give up with the Guru resets, they are failing because your bootloader is too new and even the OTA cant back flash your bootloader, those OTA's will be trying to install HBOOT 1.54 or something like that.
Seanie280672 said:
Try this TWRP backup do not use the modified firmwqare, it will brick your phone as your s-on.
Give up with the Guru resets, they are failing because your bootloader is too new and even the OTA cant back flash your bootloader, those OTA's will be trying to install HBOOT 1.54 or something like that.
Click to expand...
Click to collapse
Thanks for the reply man.
Unfortunately, that's the exact same backup I used in step 1. Get's the variant system error.
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
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.19.401.30
(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: 4275mV
(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
Phone is stating *unlocked* and *tampered* with S-ON.
Honest989 said:
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
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.19.401.30
(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: 4275mV
(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
Phone is stating *unlocked* and *tampered* with S-ON.
Click to expand...
Click to collapse
Edit your post above and remove your IMEI and Serialno, keep these numbers private.
ADB doesn't work from bootloader, only fastboot will. ADB is only available from a custom recovery or from a booted OS with USB debug enabled.
You'll first need a working recovery so reflash twrp recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Honest989 said:
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Click to expand...
Click to collapse
There is no 7.19.401.30 ruu, the latest one is 7.19.401.22 and can't be flashed on your phone since its a downgrae in version (requires s-off)
Unlock your bootloader and flash your custom rom.
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Honest989 said:
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Click to expand...
Click to collapse
You don't need s-off to flash a rom, if you want s-off for going back to stock using the ruu (downgrade) you'll first need a working rom. S-OFF can only be achieved from a working rom using Sunshine S-OFF
To push a rom to your phone, if you have a recent twrp version (2.8+) just boot your phone in recovery mode connected to your pc using the usb cable and you should be able to see your phone storage (like if it was a usb stick). just drag and drop your rom.zip to your phone and then in twrp select "install" and flash the rom. If you are one an older version of twrp, use adb to push the rom to your phone:
Code:
adb push name_of_rom.zip /sdcard
Thanks guys what solved it was:
Up to date version of TWRP
Latest version of Android revolution.
The reson it wasn't booting or providing some sort of DR was because I had somehow wiped everything from the phone. By way of complete fluke, I now have a rooted phone running on a completely clean install directory. Remind me to back up later on.