Related
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
Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
nurogo said:
Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
nkk71 said:
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
Click to expand...
Click to collapse
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
Click to expand...
Click to collapse
Anyone, please?
nurogo said:
Anyone, please?
Click to expand...
Click to collapse
use the 1.28.401.7 RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
follow guide linked by nkk71
nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) security: on
Thanks
Click to expand...
Click to collapse
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
nkk71 said:
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
Click to expand...
Click to collapse
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
nurogo said:
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
Click to expand...
Click to collapse
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
nkk71 said:
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
Click to expand...
Click to collapse
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
nurogo said:
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
Click to expand...
Click to collapse
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
nkk71 said:
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
Click to expand...
Click to collapse
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
nurogo said:
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
Click to expand...
Click to collapse
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
nkk71 said:
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
Click to expand...
Click to collapse
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
nurogo said:
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Click to expand...
Click to collapse
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
nkk71 said:
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
Click to expand...
Click to collapse
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
nurogo said:
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
Click to expand...
Click to collapse
The ruu will take care of that, it will wipe everything off your phone, including anything on the virtual sdcard
Sent from my HTC One using Tapatalk
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
nurogo said:
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
Click to expand...
Click to collapse
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
nkk71 said:
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Check it, but it stays the same..
Look at the image
nurogo said:
Check it, but it stays the same..
Look at the image
Click to expand...
Click to collapse
type dir in the command window
you probably see it's names RUU.zip.zip
I have an AT&T M7 flashed with Cyanogenmod 10 that I would like to restock. I've tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2, but that is not working.
I mean it starts to run and then after asking for aproval it desapears.
I also tried the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2, and this one runs but at the end it says that is not compatible with my phones firmware.
This is the phone info:
M7_UL PVT SHIP S-OFF RH
CID-CWS_001HBOOT-1. 56. 0000
RADIO-4T. 24. 3218. 09
OpenDSP-v32. 120. 274. 0909
OS-4. 18. 502. 7
eMMC-boot 2048MB
Jan 28 2014, 09: 32: 41. 0
What is the simpliest way to go back to stock?
Thanks in advance.
Getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
chiquito3 said:
I have an AT&T M7 flashed with Cyanogenmod 10 that I would like to restock. I've tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2, but that is not working.
I mean it starts to run and then after asking for aproval it desapears.
I also tried the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2, and this one runs but at the end it says that is not compatible with my phones firmware.
This is the phone info:
M7_UL PVT SHIP S-OFF RH
CID-CWS_001HBOOT-1. 56. 0000
RADIO-4T. 24. 3218. 09
OpenDSP-v32. 120. 274. 0909
OS-4. 18. 502. 7
eMMC-boot 2048MB
Jan 28 2014, 09: 32: 41. 0
What is the simpliest way to go back to stock?
Thanks in advance.
Getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Click to expand...
Click to collapse
you need to downgrade your hboot to 1.44 to flash 1.26.502.12
alray said:
you need to downgrade your hboot to 1.44 to flash 1.26.502.12
Click to expand...
Click to collapse
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
chiquito3 said:
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
Click to expand...
Click to collapse
use the 1.44 hboot from the .401 version.
chiquito3 said:
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
Click to expand...
Click to collapse
Did you check the md5 of the 4.15.502.7 ruu you downloaded?
Also if you have HTCsync installed then uninstall it. Doesn't do any favours when using ruu's :good:
I've downloaded the file from 2 different sources and the resilt is the same.
Sent from my SM-G900T using Tapatalk
chiquito3 said:
I've downloaded the file from 2 different sources and the resilt is the same.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Is the RUU quiting after you accept the license agreement , if so, its a windows error not an RUU error, read and do the fix below:
http://forums.androidcentral.com/htc-evo-4g-lte/363796-can-t-install-4-3-ruu-windows-7-8-1-a.html
post 18 fixed the problem for me, you need to download and install all one at a time with a reboot in-between each one, do not use windows update to update any of them.
Seanie280672 said:
Is the RUU quiting after you accept the license agreement , if so, its a windows error not an RUU error, read and do the fix below:
http://forums.androidcentral.com/htc-evo-4g-lte/363796-can-t-install-4-3-ruu-windows-7-8-1-a.html
post 18 fixed the problem for me, you need to download and install all one at a time with a reboot in-between each one, do not use windows update to update any of them.
Click to expand...
Click to collapse
Seems that you are right. I tried all the suggestions here but none of them worked on my PC. So Idecided to try on my laptop. The thing is that the RUU did run well but unfotunately it ends with an error 170 usb connection error.
The laptop recognizes the phone well so I cant understand the reason for the error.
chiquito3 said:
Seems that you are right. I tried all the suggestions here but none of them worked on my PC. So Idecided to try on my laptop. The thing is that the RUU did run well but unfotunately it ends with an error 170 usb connection error.
The laptop recognizes the phone well so I cant understand the reason for the error.
Click to expand...
Click to collapse
make sure the computer recognises the phone whilst the phone is both booted and in the bootloader with fastbootUSB showing on the phone screen.
Seanie280672 said:
make sure the computer recognises the phone whilst the phone is both booted and in the bootloader with fastbootUSB showing on the phone screen.
Click to expand...
Click to collapse
Ok guys I did it thanks to your help.
Now what is the prefered rooting method and should I take the OTA or not?
chiquito3 said:
Ok guys I did it thanks to your help.
Now what is the prefered rooting method and should I take the OTA or not?
Click to expand...
Click to collapse
yes take the OTA's, if you dont like the new Lollipop you can always just flash the RUU again to get back to the older versions as your s-off.
after you've done the OTA's, to root, just flash twrp recovery: http://dl.twrp.me/m7/twrp-2.8.5.0-m7.img and then flash the superSU zip from within TWRP recovery: http://download.chainfire.eu/696/SuperSU, complete root setup once the phone has started back up by opening superSU from your app drawer.
Seanie280672 said:
yes take the OTA's, if you dont like the new Lollipop you can always just flash the RUU again to get back to the older versions as your s-off.
after you've done the OTA's, to root, just flash twrp recovery: http://dl.twrp.me/m7/twrp-2.8.5.0-m7.img and then flash the superSU zip from within TWRP recovery: http://download.chainfire.eu/696/SuperSU, complete root setup once the phone has started back up by opening superSU from your app drawer.
Click to expand...
Click to collapse
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
chiquito3 said:
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
Click to expand...
Click to collapse
There is no lollipop for at&t yet, should be released soon
http://www.htc.com/us/go/htc-software-updates/#device-content
chiquito3 said:
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
Click to expand...
Click to collapse
alray said:
There is no lollipop for at&t yet, should be released soon
http://www.htc.com/us/go/htc-software-updates/#device-content
Click to expand...
Click to collapse
Yes during the Uh Oh announcement / interview they said they were shooting for an April 1'st update for AT&T M7
clsA said:
Yes during the Uh Oh announcement / interview they said they were shooting for an April 1'st update for AT&T M7
Click to expand...
Click to collapse
And I'm longing for that moment! Thanks again.
Since I did change the stock recovery to TWRP just for rooting the phone, could I still take the OTA upgrade or does it have to be done manually?
I also installed Xposed Framework and some HTC Modules.
chiquito3 said:
And I'm longing for that moment! Thanks again.
Since I did change the stock recovery to TWRP just for rooting the phone, could I still take the OTA upgrade or does it have to be done manually?
I also installed Xposed Framework and some HTC Modules.
Click to expand...
Click to collapse
you will have to return the phone to full stock to take an OTA update
clsA said:
you will have to return the phone to full stock to take an OTA update
Click to expand...
Click to collapse
I did something bad to the phone and would like to go back to stock can I use the RUU again and how? Because I tried and it gives a fastboot error a few seconds after starting. The RUU is actually a downgrade.
I was trying to mod the Weather widget to transparent and I ended without the widget and the phone goes to black and takes too long to come back to light the screen.
the error is htc.fastboot.exe has stopped working
chiquito3 said:
I did something bad to the phone and would like to go back to stock can I use the RUU again and how? Because I tried and it gives a fastboot error a few seconds after starting. The RUU is actually a downgrade.
I was trying to mod the Weather widget to transparent and I ended without the widget and the phone goes to black and takes too long to come back to light the screen.
the error is htc.fastboot.exe has stopped working
Click to expand...
Click to collapse
you can use my Guru_Reset to return to stock 5.x
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
If you want to keep custom recovery choose no to stock recovery during install and yes to Root
clsA said:
you can use my Guru_Reset to return to stock 5.x
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
If you want to keep custom recovery choose no to stock recovery during install and yes to Root
Click to expand...
Click to collapse
Thanks again for your reply!
How do I flash this one? can it be done through costum recovery?
chiquito3 said:
Thanks again for your reply!
How do I flash this one? can it be done through costum recovery?
Click to expand...
Click to collapse
Yes you flash it in TWRP same as a rom
[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.
I am trying to revert my Rogers HTC One M7 to stock configuration so that I can send it in to have the very VERY purple camera repaired. I started this process on Android Revolution HD 92 and after downgrading from hboot 1.57 to 1.44 I was following this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
However I am running into problems. I made it as far as using Guru to lock and un-tamper my phone however it froze at 0%. I am unable to boot into recovery on the phone, I just get a red exclaimation mark and a picture of a phone instead of recovery. I tried re-flashing the 1.29.401.12 recovery as well as the stock_155hboot recovery, both have the same problem.
When I try to do getvar all I get the following:
D:\HTC>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-OFF
(bootloader) serialno: HT34PW911661
(bootloader) imei: 354439053723369
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.067s
Click to expand...
Click to collapse
Why am I getting the status read failed error, and how can I get a working stock recovery back on my phone?
Any help would be appreciated, thanks in advance!
blue163 said:
I am trying to revert my Rogers HTC One M7 to stock configuration so that I can send it in to have the very VERY purple camera repaired. I started this process on Android Revolution HD 92 and after downgrading from hboot 1.57 to 1.44 I was following this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
However I am running into problems. I made it as far as using Guru to lock and un-tamper my phone however it froze at 0%.
Click to expand...
Click to collapse
What is freezing exactly? the RUU or the Guru bootloader reset tool?
I am unable to boot into recovery on the phone, I just get a red exclaimation mark and a picture of a phone instead of recovery.
Click to expand...
Click to collapse
No problem here, this is the stock recovery.
I tried re-flashing the 1.29.401.12 recovery
Click to expand...
Click to collapse
It doesn't make sense, why would you want to flash the 1.29.401.12 recovery if your phone is rogers?
Why am I getting the status read failed error,
Click to expand...
Click to collapse
This is a normal error on older hboot.
and how can I get a working stock recovery back on my phone?
Click to expand...
Click to collapse
Why do you need to access the stock recovery anyway?
alray said:
What is freezing exactly? the RUU or the Guru bootloader reset tool?
Click to expand...
Click to collapse
The Guru tool freezes at 0% after selecting to lock and remove tamper flag
alray said:
No problem here, this is the stock recovery.
Click to expand...
Click to collapse
I thought stock recovery was the android 3e recovery I am used to from other phones?
alray said:
It doesn't make sense, why would you want to flash the 1.29.401.12 recovery if your phone is rogers?
Click to expand...
Click to collapse
I thought that was the correct recovery for the 4.1.2 Rogers rom?
alray said:
This is a normal error on older hboot.
Click to expand...
Click to collapse
That's a relief!
alray said:
Why do you need to access the stock recovery anyway?
Click to expand...
Click to collapse
I am trying to send my phone back to have the camera replaced under warranty and I want it to be as close to stock as humanly possible to reduce the chance of my claim being denied.
Thanks for the help!
blue163 said:
The Guru tool freezes at 0% after selecting to lock and remove tamper flag
I am trying to send my phone back to have the camera replaced under warranty and I want it to be as close to stock as humanly possible to reduce the chance of my claim being denied.
Click to expand...
Click to collapse
So follow nkk71's guide but instead of using the guru bootloader reset tool use the alternative method (method 1 with adb commands)