[Q] Can't boot to recovery, can't s-off - One (M7) Q&A, Help & Troubleshooting

Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.

eisteh said:
Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.
Click to expand...
Click to collapse
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?

herwegan said:
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?
Click to expand...
Click to collapse
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.

eisteh said:
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.
Click to expand...
Click to collapse
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.

iElvis said:
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.
Click to expand...
Click to collapse
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...

eisteh said:
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...
Click to expand...
Click to collapse
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).

herwegan said:
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).
Click to expand...
Click to collapse
Which would require s-off which doesn't work.

eisteh said:
Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Click to expand...
Click to collapse
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?

crushalot said:
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?
Click to expand...
Click to collapse
Yes, I did a manual reboot.
Revone is said to work without SU and therefore uses it's integrated rooting process. I'm not rooted otherwise, I'd rather have my recovery working and flash a custom ROM then
I tried to run revone like 10 times (on my old device it took me exactly one try), I will consider your tipps and try again.

Related

[Q] [HTC One] Bricked after 4.4 update

I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
I think I can recover the phone with instructions (I can't post URLs yet) that will install a different recovery and uses adb sideload. But it also erases the sdcard which I try to avoid.
So, Is there anyone who can advice me what to do? If it cannot be avoided that my sdcard will be wiped; so be it. But I will manage doing that, I'm looking for an alternative at the moment. I suspect that if I find the correct recovery version that it will "mount" the "sdcard" (which I think is an emulation because the HTC One has no sdcard??) will also allow me to recover my phone with sdcard intact. But I find it difficult to find the correct recovery.img. I've tried two versions *can't find numbers back right now, will post if needed*.
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
ruud.walraven said:
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
...
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
Click to expand...
Click to collapse
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
mbroeders said:
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
Click to expand...
Click to collapse
I should have mentioned that the other options (apply from phone and apply from cache) don't work either. One thing I am unsure about is if this is indeed the stock recovery.img I put back on. Is there a single recovery.img for HTC One, or a list where I can find which one came standard so I can put it back. My suspicion is that that recovery will work, although the guy I bought the phone from may have installed recovery/images that may have reformatted everything in a way that stock won't work any longer...
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
ruud.walraven said:
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
I've tried a whole range of things that didn't help. Don't want to preserve the sd card any longer.
Flashed recovery versions: 1.29.401.12, 2.24.401.8, 3.07.1700.1 and 3.58.1700.5.
Neither version was able to reinstall from sdcard. But I found out later that I may have done *something* to the sdcard (see CWM below)
Next I flashed CWM to try flashing a nandroid. However during the process I couldn't browse my sdcard anymore. Before flashing above recoveries I had CWM and then I could see all files. May have done something wrong.
After trying the mentioned nandroid a few times I realized that I am S-ON.
I have been trying to get S-OFF for the last few hours because I found a file I want to use on my phone (See htc1guru . com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/). I've looked at Moonshine, but my phone is not in the list of supported rom versions (1.29.401.12). I tried Revone, but get error = 1.
So now I'm not sure what to do next!!
mbroeders said:
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
you bought it from an idiot.
you can't properly convert to GPE with s-on. That's why your hboot, mainver and cid are all wrong for a GPE conversion.
I assume you're boot-loader unlocked? flash cwm or TWRP. Then restore this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
after restoring that nandroid try to s-off with revone and or rumrunner.
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
Rumrunner: http://forum.xda-developers.com/showthread.php?t=2488772
once your s-off you can properly convert your phone to GPE. The problem wasn't just that you flashed it with a custom recovery but that the phone was never in a proper state to receive OTA for GPE!
use the RUU from here once your s-off to convert to GPE 4.4 : http://forum.xda-developers.com/showthread.php?t=2358781
you'll also want to go supercid with fastboot oem writecid 11111111
ruud.walraven said:
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
Click to expand...
Click to collapse
I'm downloading all required files right now. In the meantime looking into everything to make sure to not further brick it once S-OFF. Tricky business!
ipfreelytech said:
you'll also want to go supercid with fastboot oem writecid 11111111
Click to expand...
Click to collapse
There's one question I found: according to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? (the latter I remember reading is supposed to be good too). In any case ... I suppose I can best follow your instructions and I can change the cid to whatever needed afterwards anyway.
edit: It took 1.5 hours to download the nandroid, but something must have gone wrong because the file cannot be opened by winzip nor 7z. After the failed opening of the file I've md5-ed the entire zip file and it doesn't match the checksum on the download link. So started download again...
I have a problem; the download stops at different points, never completing. Must be a problem in the connection or at htc1guru. Is there an alternative file/download/mirror I can use as well? Have searched google for the same file with no results.
I was finally able to download the file through FF. Every time the download failed I started again, but paused and replaced the .part file with the failed download. When you resume FF detects the last bit and resumes from there. Best part was that I got my Chrome 900+MB download and used that as .part file. So I could resume nearly finished. Ran the checksum to be sure nothing funny had happened because of my tinkering. To quote Borat: great success.
However, after restoring the nandroid through CWM I tried both Revone and Rumrunner. Revone fails error = 1 and Rumrunner assumes I start from my homescreen (which I can't). A bit unwise, but I tried anyway from both fastboot and CWM but in neither case will Rumrunner continue. It claims there is no ADB connection (even though the phone shows up in adb devices).
So I am stuck for now. Still looking at as many posts about S-OFF as I can to see if I find some vital piece of inof I missed or something I can still try. But for now I'd like some idea's how to achieve S-OFF..
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
SaHiLzZ said:
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
Click to expand...
Click to collapse
hboot has a date? Hboot is 1.44 and bootloader start screen says apr 12 2013, is that what you mean?
My version (1.29.401.12) is not supported by moonshine for as far as I can tell.
I also notice now that fastboot getvars bootmode says: fastboot. Shouldn't this be disabled for revone and/or rumrunner?
ruud.walraven said:
...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
...
Click to expand...
Click to collapse
Just a question: In a sense I can't have messed anything up that bad because I'm S-ON. So if I would install the 4.3 release that was on the device before I sideloaded the 4.4 OTA through CWM, wouldn't it just work because all things point to the correct places? Since I broke it with adb sideloading, I could restore the device probably just as well, right?
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
ziolooo said:
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
Click to expand...
Click to collapse
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
ruud.walraven said:
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
Click to expand...
Click to collapse
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
ziolooo said:
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
Click to expand...
Click to collapse
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
ruud.walraven said:
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
Click to expand...
Click to collapse
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
ziolooo said:
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
Click to expand...
Click to collapse
I already tried that.
ruud.walraven said:
...
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
Click to expand...
Click to collapse

[Q] RUU stuck at "checking headers"

I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).
Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk
Thanks for updating back. Don't S-ON.
SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk

[Q&A] |TOOL| HTC One Toolkit [M7] • v3.2.0

Q&A for |TOOL| HTC One Toolkit [M7] • v3.2.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for |TOOL| HTC One Toolkit [M7] • v3.2.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
McCovican said:
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
Click to expand...
Click to collapse
Were both files (firewater and temproot) in the same adb/fastboot folder?
4304
majmoz said:
Were both files (firewater and temproot) in the same adb/fastboot folder?
Click to expand...
Click to collapse
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need S-OFF to root. You just need a unlocked bootloader, custom recovery and SuperSU. Here are the instructions.
Also, I would use the raw adb and fastboot commands without the toolkit. I would recommend the Minimal ADB & Fastboot Tool. Most Dev's and OPs will give the commands for how to do certain things so you could just copy and paste. It also gives you more control on what is happening to your phone.
McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need s-off to root the phone. But with s-on you will be limited to flashing Roms, Recovery and Kernels. Firmware updates are possible but must be Signed firmware and can only be flashed with a 're-locked bootloader.
Just flash TWRP Recovery 2.6.3.3 boot to TWRP then reboot system from TWRP. You will be prompted to root the device Select yes. You may need to update binaries but that's it your done.
Better still just flash a prerooted Rom with TWRP. :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Bricked phone using tool
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(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: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.041s
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
???????????? fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(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: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
redlupine said:
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(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: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.041s
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
????????????fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(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: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
Click to expand...
Click to collapse
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu. http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu.
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
redlupine said:
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
Click to expand...
Click to collapse
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
I would however like to bring this to the attention of @nkk71 let's wait to see what he has to say on this subject
I've never seen a getvar so messed up so let's hope nkk71 has some idea :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
Click to expand...
Click to collapse
You are right, I'm posting this to the bricked help phone thread:
[Unbrick Service] Bricked Phone? Need Help? Look Here.
Lollipop
Hey,
I have a UK M7 (locked to H3G if that matters) currently running Android Revolution w/ Sense (rooted).
I have set my CID to 11111111 , I have S-OFF, HBOOT-1.56.0000 and I am looking load the OTA for the Google Play Edition (Lollipop 5.0.1) on to it using your tool. And then I will re-root.
Really I just wondered if anyone thinks that this is a bad idea for any reason.
htc one stock
I lost my stock back-up for warranty CID- VZW__001
OS- 1.10.605.10
I d like to return to full s-on stock for warranty make a new back-up
Then use tool kit to return to s-Off TWRP CAN you please help
help..
hello there OP , thankyou for the time you have put into this tool, im a noob with smartphones, and once tried 'windroid' one-click/aio type device from xda forums, it ended up with me unlocking the token thingy, but then it would not go frther, it actually put a cross X over the pic of a HDD or looked it, i quickly hit power off/one and it booted automatically into a factory install/reset kind of environment.. since then ive been to scared to even try rooting again... but your kit and hansoon one seem O.K , but my problem is, how do i find what version exactly of phone that i have, the thing lookes like the htc one x, i recall updating the rom couple of times now, so it is on kernel v3.* , but again, i need to somehow find this info and then try again using a app that actually works..i getting good reviews on your thread so i guess im hoping for some magic here, i know the questions ive asked are very nooby, but trust me i thought i had killed it, i remember unlocking the token id, i recall pasting this in and then it showed up as unlocked.. i have kept my .bin file handy if ever i re-needed it.. so i guess that part is done.. i would LOVE to run something wich doesnt kill the battery, as im experincing now is 1day lasting full charged..without many apps :S
i am sorry for the length of this question, its just i had a bad experience once, dont want that again.. but im hanging to try again... feel free to respond, or not respond, i know what im askingshould be here somewhere, although the model, if it is a one or one-x i guess is the only thing i am curious of..is how would i know because a couple of models looked very similar.. i THINK im running android 4.2.2 ,kernel 3.* , i beleive there is a couple.
i know there is a new exploit out for v3 kernel. would this not help make the tool 1000% proof.?? one wich i was told is now being used for android v5 wich apprently roots every device upto v5, so thats all v3/4 and 5 in one exploit...i have 'heard' that xda do have it and are using it for newer phones.. but what an oppurtunity,if this was added into your tool,it would be 100% proof on everything android.. just a thought but, you seem like a happpy go lucky cool op, so im just saying, if i was working on a tool, id work alot more on exploitation of the device/making sure there is no residual pains, and simply adding ballon like tips around the app kinda cool touch... i like your tools look, and i wish to use it.. but i dont want to endup being locked in phone..
i have htc one x , 32g, i believe :S it LOOKS exact same as the htc one-x,it was given to me as a one-x (sold to me),and at that stage,it was on ebay prettymuch on par with the other htc one-x,so it would be one-x im about 99% sure, i just now wonder about the updates i allowed the phone to perform,wich then changed android version/kernel.
I dont know if you have the answer i need, or answers if you wish to answer the entire post,because your going to get it,and really its you i want to ask anyhow, so its fine if it stays private, although since it is noobish, i guess you could go either way... i do raise some issues for some people to scared to get 'bricked' .. my phone uses vodaphones manager,wich i have uninstalled everytime it installs,now it has embedded itself though,and it only deletes down to un updated vodafone manager, i deleted every other voda app on there... so its basiocaallly a question of, do i go ahead with this version, or do i wait for something thats 100%.. im sure alot of people are like me, alittle hesitant to root..or had bad experiences.. ive rooted my samsung duo young fine, but the htc, well.. its got me sofar..i see all the one touch tools,i grabbed them, but wich one will actually work right.. remembeing i have used one wich was labelled windroid from xda ,it only made me paranoid as hell to use a working one, and then, i also think of exploitation, and i seriously wonder if your app can rooot an updated one-x on 4.2.2,and it does not go higher, it seems like two updates to get to this version,no updates now for about 6-12months,so i am looking here at a handful of exploits wich DO work and will root, ie; futex ; or asking you, if you think that would make your app even nicer,and erhaps a cleaner root process is achieved with something new, i know the one mentioned in UG came to xda,so,why is there no updated packs :?
i would hope that things got updated,maybe just me,but if theyre updating theyre firmware, then surely you must update your end to handle this... so is MY phone going to be o.k with this app, or do i wait and hope there is a newer expoloitation achieved ?
its a long post,, but i hope im getting through to some dev, theres alot to be done with these packs,specially with things like google play pad coming out, id like to buy one of those,but again,how do i trust apps wich have not been updated in ages...yet my phone has updated.. it just blurs the mind as to how you would get around kernel patches..i know android has many exploits,but not clean ones like the current one in use.. i will look in on this thread and hopefully someone will explain to me how to get the exact phone info, and alittle more info on how things getting rooted, ie; exploitation , and kernel images/links to GOOD working kernels already tested.. noobs like me dont want to test 5 types, we want one GOOD one
im sorry to write alot,but this is good topic ive been walking around for to long. i even have a spare iphone sitting here just for when i root the one-xx.i am confdent that if anyone will help me on this,its going to be xda forums, simple as that... i dont even bother reading many other blogs nomore,everything android is here..its a great little place,and i love it sofar.. exploring the roms,reading,wanting :[.. i will await some feedback. again, apologies for long post,but i trying to be thorough as i can on each issue. cheers.
dru
---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------
apologies for the long post... ofc i dont expect it to go public BUT it does raise some issues..i dont see all of xda forum yet, but every search sofar has yielded results..only areas i find lacking is the rooting devices actually explaining wich root method is being used, its not a necessity,but some root methods leave memory leaks/other bugs wich can be phone specific, ome wich dont do anything atall because they bypass aprotections properly.
IF there is a thread on exploiting, i will join there..someone has to be sharing the exploits,and so they should, but alittle more info could be given to public,i guess not all people care,they just want one-click, well, i care about what i stick in my phone, so flashing a custom rom, kernel to me is a big deal i expect done right once..
i look forward to some feedback on my htc issues.
Sense Rom for S-off?
Do I have to install a sense-based rom before i go on s-off with Firewater?
Greez philipp
s-off htc one x
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Griffmiester said:
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Click to expand...
Click to collapse
You are not at the right place, this is the HTC One forum (M7) not the One X (Endeavor or Evita)
If you have an Endeavor One X (Tegra 3 cpu variant) , S-OFF is not possible
If you have an Evita One X (XL) (Qualcom cpu variant), head to this forum: http://forum.xda-developers.com/one-x-att
will i be able to use the toolkit with this phone...
Click to expand...
Click to collapse
No this is not for the One X, anyway better to learn how to use ADB and Fastboot .
Do this toolkit work with last android update?
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
LucaBalzano said:
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
Click to expand...
Click to collapse
Then I would suggest spend a few days to learn. Even if it does work and something goes wrong you won't know how to fix it. Do the proper research and learn to do things the right way instead of using a tool kit.
HTC ONE X+
***LOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
HBOOT
SERIAL: FA2ASW105934
CANNOT GET OUT OF HBOOT SCREEN OR UE ADB FASTBOOT

[Q] Trouble unrooting my M7

Hello,
So I am trying to unroot my M7 and i have encountered and I thought I have overcome a number of issues. I feel that I should start from the beginning to give you all the best picture of my situation.
I purchased the phone used and it came with the pink camera issue. So after asking Mr. Google, who said that updating might solve the problem. I went ahead to try to update but only to discover that I cant because the phone is rooted.
Okay, so at that point, i decided that since I wont be benefiting from the rootedness of the phone, and spurred on with the news of a new update coming out soon, I decided to unroot and I found this guide.
htc-one (dot) wonderhowto (dot) com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
First problem I encountered was that was that adb could not find the device, so I installed the drivers. (took me a few hours)
After that I followed the guide and locked the device and turned S-on. up to this point, it is going smoothly.
Then I downloaded the RUU RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2,
Problem was that it was really slow to load and after i accepted the legal contract, it would suddenly shut down with no warning or explanation.
So I jumped into the literature and installed all the C++ things and then it worked. Sounds great. Big smile on my face, until it starts to freeze at 5% header 1/5.
Great. so that is where I am stuck.
When i am at cmd and type in
C:\Users\Andrew Lee\Downloads\Desktop>cd htcone
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp/
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
also I cannot quit bootloader on the phone. and when i go into device manager, it is under android USB devices, named my HTC and under other devices, there is two base system devices and both have the yellow icons next to it.
I have installed HTC sync in an effort to install the proper drivers and that did not work.
So I am in a pickle. I would prefer to unroot it but atp I dont care anymore, I just want to use the phone.
I have tried to use the zip RUU way of installing the RUU but because it cannot find the device, it is futile. When I plug in the phone, I do here the sound.
I am on Windows 7. I also have a Mac as an alternative.
If you have a Mac, I would use that! You don't have to deal with any driver issues on the Mac or on Linux, like the saying goes... It just works!(tm)
From what you posted, I see that you are S-ON with SuperCID, but I'm not sure what system you originally had, android version, ROM, etc. I assume you are on Telus, since you are trying to flash a Telus RUU. I also see you are trying to run revone.. Are you trying to get S-OFF, or unroot, or get the entire phone completely back to stock? What recovery do you have installed?
Also, FYI - adb doesn't work while you are in the bootloader.
commandaria said:
Hello,
So I am trying to unroot my M7 and i have encountered and I thought I have overcome a number of issues. I feel that I should start from the beginning to give you all the best picture of my situation.
I purchased the phone used and it came with the pink camera issue. So after asking Mr. Google, who said that updating might solve the problem. I went ahead to try to update but only to discover that I cant because the phone is rooted.
Okay, so at that point, i decided that since I wont be benefiting from the rootedness of the phone, and spurred on with the news of a new update coming out soon, I decided to unroot and I found this guide.
htc-one (dot) wonderhowto (dot) com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
First problem I encountered was that was that adb could not find the device, so I installed the drivers. (took me a few hours)
After that I followed the guide and locked the device and turned S-on. up to this point, it is going smoothly.
Then I downloaded the RUU RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2,
Problem was that it was really slow to load and after i accepted the legal contract, it would suddenly shut down with no warning or explanation.
So I jumped into the literature and installed all the C++ things and then it worked. Sounds great. Big smile on my face, until it starts to freeze at 5% header 1/5.
Great. so that is where I am stuck.
When i am at cmd and type in
C:\Users\Andrew Lee\Downloads\Desktop>cd htcone
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp/
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
also I cannot quit bootloader on the phone. and when i go into device manager, it is under android USB devices, named my HTC and under other devices, there is two base system devices and both have the yellow icons next to it.
I have installed HTC sync in an eff noort to install the proper drivers and that did not work.
So I am in a pickle. I would prefer to unroot it but atp I dont care anymore, I just want to use the phone.
I have tried to use the zip RUU way of installing the RUU but because it cannot find the device, it is futile. When I plug in the phone, I do here the sound.
I am on Windows 7. I also have a Mac as an alternative.
Click to expand...
Click to collapse
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
synt3k said:
If you have a Mac, I would use that! You don't have to deal with any driver issues on the Mac or on Linux, like the saying goes... It just works!(tm)
From what you posted, I see that you are S-ON with SuperCID, but I'm not sure what system you originally had, android version, ROM, etc. I assume you are on Telus, since you are trying to flash a Telus RUU. I also see you are trying to run revone.. Are you trying to get S-OFF, or unroot, or get the entire phone completely back to stock? What recovery do you have installed?
Also, FYI - adb doesn't work while you are in the bootloader.
Click to expand...
Click to collapse
I cant remember what is the original system it had But i think it was xposed.. It was the last application when it was listed alphabetically. The phone was originally telus, but I am on rogers. i was not sure with RUU to use so I used Telus because I read somewhere that because it is not gsm but cmda I needed to use telus (the article said sprint but I assumed that I would use telus) But, as I am on rogers, would I than need to have s-off and then install the RUU
I am trying to get it back to stock. Not for warranty purposes.
Also I do not know about recovery because when I chose recovery in bootloader, nothing happens.
Also thanks for replying, I really appreciate it,
stovie_steve said:
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
Click to expand...
Click to collapse
Thank you for replying, I did run writesecureflag 3 as per the instructions I was following (really regret it now, should have came here first)
I do not need to send in the phone for repair, the post just sounded more legitimate, I just want to have stock because all i do with my phone is the basic functions, I never saw a need to fettle around with it .
So, I assume from reading both posts that I need to unlock my bootloader again? Do i need s-off if I want to do stock RUU? Do i also need s-off if I want to use rogers on a telus phone?
Also, would sunshine allow me to install the stock RUU? It seems to only unlock and s-off
Thank you all for replying, I really appreciate it.
stovie_steve said:
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
Click to expand...
Click to collapse
Hi,
So i followed your instructions, and low and behold, it worked. I used Guru_Reset_M7_2.24.401.1
But problem is I cannot update, when i press update, it says that it is already updated.
How would I fix it so I can update?
Thank youuu
commandaria said:
Hi,
So i followed your instructions, and low and behold, it worked. I used Guru_Reset_M7_2.24.401.1
But problem is I cannot update, when i press update, it says that it is already updated.
How would I fix it so I can update?
Thank youuu
Click to expand...
Click to collapse
Are you now s off with an unlocked bootloader and did you run the sunshine app? If you did, you can run almost any RUU

[Fixed] Bricked Hboot 1.44 with RUU 1.31 (Explanation on how solved in OP)

[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(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: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.
toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you
alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...
nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(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: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(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: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.
alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:
alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?
nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.

Categories

Resources