I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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: 4297mV
(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.109s
Use otg cable +USB mouse to control the phone
sent from my mobile device
update
I have my otg cable and im able to use the usb mouse with it but I am unable to check for the at&t software update... i click on it and it puls up for a second and then goes away... any ideas?
Idea
I read somewhere that I can flash firmware with s-on as long as i re-lock the bootloader and the mid and cid match on the firmware that i flash to it... this would be done in the ruu flash boot? does that sound right and would this allow me to either get the ota update or flash the correct ruu OR would it possible get my adb functionality back to my bootloader so i can s-off and flash a stock ruu?
medicsizzle said:
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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: 4297mV
(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.109s
Click to expand...
Click to collapse
You need to flash your touch drivers.
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
SaHiLzZ said:
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I can try but I am stuck in S-on would this be an issue? and I can flash from cwm and twrp would a stock nandroid help?
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
SaHiLzZ said:
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
Click to expand...
Click to collapse
You are the BEST! Thank you so much.. I have been racking my head trying to get this fixed... I am up and running again! My process
1. I had my phone unlocked bootloader, s-on, and twrp recovery
2. booted into trwp, and adb pushed the Guru stock installer
3. installed the zip, selecting to wipe data, no super user, and then I put the stock recovery and radios on
4. rebooted into bootloader and locked my bootloader
5. rebooted phone
6. ran the RUU that you provided me. (Thanks again)
7. phone booted up 100% working!!!!
8. Gave credit where credit was due!
Related
I have a genuine Htc One Google Play Edition Phone.
Get Vars :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
Phone was unlocked (fastboot oem unlock) and rooted 2 months ago.
Now I messed things up by trying to install the 4.4 OTA using TWRP. With the OTA, I get a nice blue-screen. I had a backup so the phone is booting correctly now.
I want to install a factory image. From what I can gather, this is not like a Nexus phone and I cannot simply use fastboot to get back to stock. I must use RUU. Now : for RUU to work, I need to be S-OFF.
I searched a lot and there does not seem to be a way to put a GPE to SOFF. I tried RumRunners but it fails saying I'm not rooted (which is wrong since I'm rooted) and I'm not running an unsecure kernel (which is true). - again, this is a factory GPE HTC One.. unlocked and rooted. That is all.
So, am I missing something? I'm running HBOOT 1.54. Can I get this phone to turn the security off?
Whatever you do, do NOT lock the boot loader. Can NOT unlock boot loader, otherwise.
deleted
SaHiLzZ said:
Whatever you do, do NOT lock the boot loader. Can NOT unlock boot loader, otherwise.
Click to expand...
Click to collapse
Yeah, I figured that much.
I was finally able to update to 4.4. I simply flashed the stock recovery and it worked.. BUT now my phone boot loops!
Restore your nandroid. Or issue fastboot erase cache and do a factory rest from bootloader.
"fastboot erase cache" is the first thing I did. That's the thing : all the recoveries I try boot loop. The only one working is the stock one! With the stock one I sis a factory reset. Still no go.
II see there are a lot of scenarious and ways to get your phone back to stock depending on the specific situation with your phone. well here's my phone. I'll be upgrading to an S5 here soon and plan on handing my phone down to my mom. I'd like to get it back to stock so when I bring to sprint there shouldn't be any issues getting it trasnfered over.
I am currently'
running the latest version of viper
It says S-ON on bootloader
HBOOT 1.57.0000
At the top it says tampered and unlocked
The recovery I am using is TWRP V2.8.1.0
Someone walk me through to this to get this thing to a point whre it looks like it has never been modified or send me to the appropriate guide. Thanks!
gravatrax1 said:
II see there are a lot of scenarious and ways to get your phone back to stock depending on the specific situation with your phone. well here's my phone. I'll be upgrading to an S5 here soon and plan on handing my phone down to my mom. I'd like to get it back to stock so when I bring to sprint there shouldn't be any issues getting it trasnfered over.
I am currently'
running the latest version of viper
It says S-ON on bootloader
HBOOT 1.57.0000
At the top it says tampered and unlocked
The recovery I am using is TWRP V2.8.1.0
Someone walk me through to this to get this thing to a point whre it looks like it has never been modified or send me to the appropriate guide. Thanks!
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" ? Remove your IMEI/MEID/SERIALNO before posting.
alray said:
can you post the output of "fastboot getvar all" ? Remove your IMEI/MEID/SERIALNO before posting.
Click to expand...
Click to collapse
Just stays stuck on "waiting for device" :/
gravatrax1 said:
Just stays stuck on "waiting for device" :/
Click to expand...
Click to collapse
Check your drivers in Windows device manager with the phone plugged in booted up and also in the boot loader, this is something your going to need to get working in order to get back to stock.
Seanie280672 said:
Check your drivers in Windows device manager with the phone plugged in booted up and also in the boot loader, this is something your going to need to get working in order to get back to stock.
Click to expand...
Click to collapse
When booted (into the OS) It shows a My Android Device in device manager, No errors of any kind. While on the bootloader it simply shows a "unknown device" in the USB tree. While in TWRP it shows the same thing as when booted into the OS.
gravatrax1 said:
When booted (into the OS) It shows a My Android Device in device manager, No errors of any kind. While on the bootloader it simply shows a "unknown device" in the USB tree. While in TWRP it shows the same thing as when booted into the OS.
Click to expand...
Click to collapse
You need to force the driver when in the boot loader then, just right click and select update driver, choose let me pick myself NOT let Windows search, it will fail, and from there go manual all the way till the driver is installed.
It should say myhtc in device e manager when booted and in recovery by the way, you can get the lastest drivers by downloading and installing HTC sync manager from HTC site, just be sure to uninstall HTC sync after the install from add remove programs, you should see HTC driver package just above it, leave that alone.
can u help me too
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.106
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(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.049s
cant s-off tried all ways ..
navjot2785 said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.106
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(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.049s
cant s-off tried all ways ..
Click to expand...
Click to collapse
There is only one method with a hboot 1.57 and it is Sunshine but it will cost $25.
i dnt have that much money .. any other way
navjot2785 said:
i dnt have that much money .. any other way
Click to expand...
Click to collapse
Unfortunately not!!!
any other way to revert back to stock 100% .so i can upgrade my firmware
navjot2785 said:
any other way to revert back to stock 100% .so i can upgrade my firmware
Click to expand...
Click to collapse
you can flash the same firmware that's on the phone now or higher
it has nothing to do with stock. If you want stock just flash a stock odex rom or find a nandroid of your carrier
i did had nandbackup of my rom .. am on s-on .. if i restore backup with twrp and change my recovery to stock and re lock my bootloader .. will my future updates will update my firmware to 7xxxxxxxxxx.. coz to update firmware rte now i need to be on s-off nd i cant s-off ..cant pay 25$
My mom is going to be the one using the phone. IS there any basically stock ROMS floating around out there? I just want to give the appearance when its booted up its stock. My only other concern is can the device be activated if its rooted and with a custom rom? Even the viper rom still maintains the auto activate feature it seems. I just want it to be stable for her so I don't have to constantly explains how to do things. As far as warranty goes she won't be maintain the equipment protection on the device so whatever happens to it is on her. I'm half tempted to see if there is something they might due about the cracked camera lense on it...I've had two htc ones so far and they haven't cost me anything to replace other htan the monthly insurance plan.
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.
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(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: 4297mV
(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.072s
adkz25 said:
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
Click to expand...
Click to collapse
Actually they guy there, me, was really busy in the past days and wasn't able to answer everyone. You can't imagine how much PM and Quote I had in the last week And yes I agree with you, its really hard to troubleshoot in that thread since there's so many discussions going on at the same time.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(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: 4297mV
(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.072s
Click to expand...
Click to collapse
Its a pretty uncommon problem. When flashing a RUU, all partitions (except some partitions that are unique to each devices) are flashed back to stock, even the bootloader which make me believe its not a corrupt bootloader problem. So if after flashing a RUU, your phone still have some problems, its most likely an hardware problem... If the RUU flashed fine there is nothing more you can do on the software side.... THe only thing I can think is to use Sunshine S-OFF to unlock your bootloader but unfortunately it cost 25$ to use Sunshine but at least it will bypass that "power button not working only in bootloader" problem
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
adkz25 said:
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
Click to expand...
Click to collapse
I would try the same method they are using in the Verizon HTC One forum, get temp root using kingRoot then launch sunshine
http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-OFF
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
adkz25 said:
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
Click to expand...
Click to collapse
Glad it worked!
Firmware files are flashed with fastboot in ruu mode:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip "file name".zip
fastboot flash zip "file name".zip
fastboot reboot-bootloader
Then go in recovery and flash the rom
Better to flash the latest firmware without stock recovery so you don't overwrite twrp recovery with the stock recovery.
Note that this firmware is the latest GPE firmware and that if you want to go back to stock rom using a ruu you'll have to reflash a hboot 1.57 or 1.61 firmware before running a 7.xx.xxx.xx Sense ruu.
GPE roms is perfect if you want something closer to a nexus experience, otherwise stay with a Sense rom.
Sent from my HTC One using XDA Labs
Hello everybody!
I am loosing my mind with this, would be grateful if someone could help me!
Received an HTC One M7 Nordic (HTC__Y13) version, HBOOT 1.61.0000, radio 4T.35.3218.16, ODSP 35.120.274.0718 OS.
Firstly, I unlocked the bootloader via HTCdev, then, as I did with other devices, installed CWM which I used to wipe just about everything and I installed LineageOS. (S-ON, Tampered, Unlocked bootloader). To my surprise, LOS didn't boot, booting back to fastboot. I gave it another try, reinstalling it, failed to boot again. Then I started trying the RUUs, and the farthest I could reach was the signature rejection at 4%. I am using a Mac with both Sierra and a windows XP SP3 VM in Parallels, which I also used to try with a myriad of toolkits made for this phone. In HTC Sync, although the phone is recognised, all info, like OS version, are blank.
Well, here I am with a device without OS which boots to fastboot and TWRP/CWM. Since the beginning of this adventure, I couldn't boot once to a ROM, and I lost 3 long nights on this already. I believe the only things I could have missed are: using the right RUU.exe or zip, or someway getting the phone S-OFF without using an OS, since I don't have one.
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
I am getting kinda afraid I may have bricked the phone. Could someone help me?
Thanks!
here is the "getvar" dump
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BRWxxxxxx
(bootloader) imei: XXXXXXXXXXXXXX
(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: 4278mV
(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!
wasserprojekt said:
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
Click to expand...
Click to collapse
You must use htc_fastboot.exe from a Windows pc, not the regular fastboot. Make sure you have the latest RUU for your cid/mid
Thanks for your answer. I was about to give up on this, but then I finally found the right RUU. There are so many variants it becomes a nightmare finding the adequate one, eve worse if version is not one of the best selling.
But, as someone may need this advice in the future, I'll leave a summary of the important steps in here:
Return to stock ROM (for S-ON & unlocked bootloader & tampered):
- relock your device;
fastboot oem lock
Click to expand...
Click to collapse
-find the adequate RUU;
(for HTC__Y13, it's the RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe)
-close all programs which may connect to phone (includes HTC sync, any fastboot or adb command window...), otherwise there will be no progress in the RUU;
-start the RUU with phone connected (VMs work - at leaset in Parallels with XP SP3).
Thanks to everyone.