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 all,
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
What I've tried:
Getting S-OFF (no luck whatsoever with any tools)
Flashing stock recovery and kernel
Flashing stock recovery and kernel and applying the OTA manually via recovery
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update.
Someone, please guide me in the right direction! Step by step maybe?
Keep in mind there is no way I can't get S-OFF.
Huge thanks to anyone that can help. I'd be eternally in your debt!!
SmokinWaffle said:
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
Click to expand...
Click to collapse
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
What I've tried:
Getting S-OFF (no luck whatsoever with any tools) Any error message when trying to S-OFF? You must use the correct tool for your hboot version (probably firewater) + combination of the correct rom + kernel
Flashing stock recovery and kernel --> You must have stock recovery for ota, ota will not install using a custom one.
Flashing stock recovery and kernel and applying the OTA manually via recovery --> appyling the ota manually from stock recovery require s-off
Click to expand...
Click to collapse
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update
Click to expand...
Click to collapse
.
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Keep in mind there is no way I can't get S-OFF.
Click to expand...
Click to collapse
still not sure about this, unless you get the "whelp" message from firewater...
post the output of fastboot getvar all except the imei number and serialno
alray said:
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
Click to expand...
Click to collapse
Yep!
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Click to expand...
Click to collapse
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
alray said:
still not sure about this, unless you get the "whelp" message from firewater...
Click to expand...
Click to collapse
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
alray said:
post the output of fastboot getvar all except the imei number and serialno
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
SmokinWaffle said:
Yep!
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
Click to expand...
Click to collapse
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
alray said:
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
I'm guessing the ARHD steps are to try to get S-OFF?
SmokinWaffle said:
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
Click to expand...
Click to collapse
forget the ruu, your phone version is higher than the ruu. flashing a ruu (4.11.401.10) with a lower version than on your phone(4.11.401.11) require s-off.
I'm guessing the ARHD steps are to try to get S-OFF?
Click to expand...
Click to collapse
No, this is the latest stock rom(5.11.401.10) for your phone model (MID: PN0710000 and CID:HTC__001) including android 4.4.2 and sense 6.0
You can flash this stock odexed rom(5.11.401.10) from custom recovery, then flash the stock recovery(5.11.401.10) over the custom one and your phone will be stock and ready to take future ota update. You may also want to update firmware to 5.11.401.10
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
SmokinWaffle said:
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
Click to expand...
Click to collapse
stock kernel in included in the rom (boot.img) so if you don't flash any other kernel it should be fine.
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
Click to expand...
Click to collapse
firmware is all the low level code required for your phone hardware to works with the software (OS)
when speaking about HTC phone, firmware.zip include HBOOT(bootloader), BOOT(kernel), Recovery, Radio and some other stuff. if you want your phone to be 100% stock you need both stock rom + stock firmware to match the same version i.e 5.11.501.10
normally, the firmware is updated at the same time the rom version is updated (from an ota update) If you flash a rom, the rom will be updated but not the firmware.
Updating the firmware manually can be dangerous is you don't know what you are doing and flashing the wrong file. You can update firmware using this command from bootloader (with the correct firmware.zip package in the same folder you have adb and fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
also it looks like flashing a 5.x.xxx.x firmware over a 3.x.xxx.x firmware will brick your phone. from what i see, your phone should be on a 4.x.401.x version at the moment, so it theory it should be fine.
Fails on:
>>>setting permissions
set_metadata_recursive: some changes failed
E:Error in /data/media/0/one_5.11.401.10_odexed.zip
(status 7)
Tried 3 different versions of cwm. Bad rom download?
Thinking about it I just re read your above post, could it be because the firmware isn't matched? I read your 'it should be fine' as 'dont update the firmware' not 'its fine to update' which I think is what you meant...
Firmware is 4.19.401.11 however the rom is 5.11.401.10. Can't believe I overlooked this, guess firmware needs to be 5.11.401.10 for the rom to take?
SmokinWaffle said:
Tried 3 different versions of cwm. Bad rom download?
Click to expand...
Click to collapse
No you are using CWM thats the problem. always use TWRP 2.6.3.3
alray said:
No you are using CWM thats the problem. always use TWRP 2.6.3.3
Click to expand...
Click to collapse
Huh?
Is this a requirement of ARHD or....?
Just seems odd
Edit: success!! All seems to work. Thank you. She's overjoyed!!!
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
So I noticed that 5.1 came out for the GPE M7 around 2 months ago and I still haven't received my OTA update. Interestingly, all the articles I see mention it being an update for 5.0.1.... my GPE is on 5.0.2. Is that why I never received the update? If not, did I just miss it and they stopped pushing it or something? Where can I go from here to get the update OTA or otherwise? 5.0.2 has been horribly buggy from the start and my device is getting worse and worse as time goes on. I really need this update!
fyi, I did already post in the beginners thread and got no replies so I figured it may warrant its own thread.
Thanks!
mkid89 said:
So I noticed that 5.1 came out for the GPE M7 around 2 months ago and I still haven't received my OTA update. Interestingly, all the articles I see mention it being an update for 5.0.1.... my GPE is on 5.0.2. Is that why I never received the update? If not, did I just miss it and they stopped pushing it or something? Where can I go from here to get the update OTA or otherwise? 5.0.2 has been horribly buggy from the start and my device is getting worse and worse as time goes on. I really need this update!
fyi, I did already post in the beginners thread and got no replies so I figured it may warrant its own thread.
Thanks!
Click to expand...
Click to collapse
flash the 5.1 gpe ruu, will update your phone and set everything back to stock, backup your files before.
alray said:
flash the 5.1 gpe ruu, will update your phone and set everything back to stock, backup your files before.
Click to expand...
Click to collapse
Is that my only option now? Why did I not get the OTA update that others did?
mkid89 said:
Is that my only option now? Why did I not get the OTA update that others did?
Click to expand...
Click to collapse
Are you 100% stock gpe rom or not?
Post the output of "fastboot getvar all" (remove imei / sn before posting)
I bought this device used on ebay so I'm not 100% sure the history of it. I bought it as a GPE device and it even came with the google branded box (not a carrier box). I also received the 5.0.2 update OTA so it seems legit.
I'm at work right now and they disable the USB ports on our PCs here but I can run the adb command later if still necessary.
mkid89 said:
I bought this device used on ebay so I'm not 100% sure the history of it. I bought it as a GPE device and it even came with the google branded box (not a carrier box). I also received the 5.0.2 update OTA so it seems legit.
I'm at work right now and they disable the USB ports on our PCs here but I can run the adb command later if still necessary.
Click to expand...
Click to collapse
Afaik, there never was any 5.0.2 version for GPE, only 5.0.1 and then updated to 5.1
Yep post the "fastboot getvar all" later when you can, meanwhile go in settings --> about --> software info --> more. what is the build number?
I'm definitely on 5.0.2. Says so in the same section. I also don't see any information on an update for 5.0.2 for GPE M7 so I have no idea how I got it OTA.
Build #: LRX22G.H100 release-keys
alray said:
Post the output of "fastboot getvar all" (remove imei / sn before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.100
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1c33e16c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
mkid89 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.100
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1c33e16c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Click to expand...
Click to collapse
Strange, first time I see 5.11.1700.100. I know 5.11.1700.3 which is 5.0.1 and 6.04.1700.6 for 5.1.
And the ota update for 5.1 is from 5.0.1 to 5.1 (from LRX22C to LMY47O)
Is the bootloader still locked and no tampered flag? Maybe you should s-off the phone and update manually to 5.1
alray said:
Is the bootloader still locked and no tampered flag? Maybe you should s-off the phone and update manually to 5.1
Click to expand...
Click to collapse
still says "*** LOCKED ***" and says "M7_UL PVT SHIP S-ON RH" right below
So did I end up with some leaked OTA update or something that wasn't actually supposed to go out? Maybe that explains why my phone is so buggy now.
If I s-off and manually update I will lose everything right since there is no update from 5.0.2 to 5.1?
So I've managed to unlock the phone, installed custom recovery but I can't get S-Off which I believe is needed to flash the stock RUU back on.
Rumrunner and moonshine both fail... probably because my phone is on some weird rom/kernel that no one has ever planned for.
Is there a way to get S-Off without these utilities? Is there a different way to get back to a stock GPE RUU with OTA that doesn't require S-Off?
I thought about maybe flashing the 5.1 GPE rom and then trying to use rumrunner on that. After getting S-Off, I'd revert back to a stock GPE RUU setup to have OTA updates and hope I don't end up with this 5.0.2 update again. What do you guys think? At this point I'm almost considering just flashing the GPE+ rom and not worrying about OTA updates. I'd just hate to have to lose all my stuff every time I need to update the rom (if the developer even decides to continue updating it)
mkid89 said:
So I've managed to unlock the phone, installed custom recovery but I can't get S-Off which I believe is needed to flash the stock RUU back on.
Rumrunner and moonshine both fail... probably because my phone is on some weird rom/kernel that no one has ever planned for.
Is there a way to get S-Off without these utilities? Is there a different way to get back to a stock GPE RUU with OTA that doesn't require S-Off?
I thought about maybe flashing the 5.1 GPE rom and then trying to use rumrunner on that. After getting S-Off, I'd revert back to a stock GPE RUU setup to have OTA updates and hope I don't end up with this 5.0.2 update again. What do you guys think? At this point I'm almost considering just flashing the GPE+ rom and not worrying about OTA updates. I'd just hate to have to lose all my stuff every time I need to update the rom (if the developer even decides to continue updating it)
Click to expand...
Click to collapse
You could try cm10 and firewater to get s-off
Sent from my HTC One using Tapatalk
king_david43 said:
You could try cm10 and firewater to get s-off
Click to expand...
Click to collapse
Why CM10 and not CM11? Is firewater just known to work for sure on 10?
mkid89 said:
Why CM10 and not CM11? Is firewater just known to work for sure on 10?
Click to expand...
Click to collapse
It worked for me on cm10 when I got a replacement m7 back in December
Sent from my HTC One using Tapatalk
king_david43 said:
It worked for me on cm10 when I got a replacement m7 back in December
Click to expand...
Click to collapse
Thanks! Just to confirm so I don't go through the whole process only to hit a wall again... Is this the ROM you are referring to? http://forum.xda-developers.com/showthread.php?t=2272945
nvm, the download link on that doesn't even work. I'll just get it off the CM site unless you have a better suggestion.
mkid89 said:
Thanks! Just to confirm so I don't go through the whole process only to hit a wall again... Is this the ROM you are referring to? http://forum.xda-developers.com/showthread.php?t=2272945
nvm, the download link on that doesn't even work. I'll just get it off the CM site unless you have a better suggestion.
Click to expand...
Click to collapse
Yeah you can find them here https://download.cyanogenmod.org/?device=m7ul
Sent from my HTC One using Tapatalk
mkid89 said:
Rumrunner and moonshine both fail...
Click to expand...
Click to collapse
king_david43 said:
You could try cm10 and firewater to get s-off
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, try it yourself, you'll be redirected to sunshine website:
http://firewater-soff.com/
On hboot 1.54 you can try Rumrunner or Sunshine
Thanks for the info. I had actually figured that out on my own as soon as I started working on it. lol
I ended up paying for Sunshine and it worked even on my 5.0.2 rom so there was no need to switch over to CM.
Once I was S-Off, I was able to flash the non-rooted GPE RUU following the instructions here. Booted into it and it's currently downloading the proper update file via OTA LMY47O.H6
I still have no idea how I ended up with a 5.0.2 OTA update on a completely stock phone...
Hi Guys
Im new here so I hope I wont mess things up too bad, by posting something in the wrong place or something like that
I have a question about my Htc One M7 and I have been googling all day and either there is no easy solution or I am not able to find it...
So hopefully you can help me
My Htc One is at the moment completely stock. All I did was unlocking the bootloader as described by the htc-dev website.
I want to make a backup of my Stock Recovery, before I flash a custom one.
I tried to use this Guide: http://forum.xda-developers.com/showthread.php?t=2265618 to achieve that.
In step 7/8 it states ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)") that I should be able to boot a recovery without flashing it. But it also says that it might not work with higher hboots.
It seems that it wont work with my Hboot 1.56
Now my actual question: Is there any way to make a backup of the 100% Stock Recovery?
And please dont give me a link where i can download one, i would like to create a backup myself
If you find anything that is wrong with this post (spelling, location or somthing), please let me know.
Thank you for your help
hahamuntz said:
Hi Guys
Im new here so I hope I wont mess things up too bad, by posting something in the wrong place or something like that
I have a question about my Htc One M7 and I have been googling all day and either there is no easy solution or I am not able to find it...
So hopefully you can help me
My Htc One is at the moment completely stock. All I did was unlocking the bootloader as described by the htc-dev website.
I want to make a backup of my Stock Recovery, before I flash a custom one.
I tried to use this Guide: http://forum.xda-developers.com/showthread.php?t=2265618 to achieve that.
In step 7/8 it states ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)") that I should be able to boot a recovery without flashing it. But it also says that it might not work with higher hboots.
It seems that it wont work with my Hboot 1.56
Click to expand...
Click to collapse
You can only use the "fastboot boot recovery.img" command on hboot 1.44. So if you absolutely want to backup the stock recovery using this method you'll need s-off in order to downgrade your hboot so you can boot a custom recovery without flashing it to dump the stock one, not very convenient... Stock recovery can be extracted from the ota update zip file of the same version your phone is running, this is the method used by everyone if their stock recovery.img is not already available to download here on xda.
Now my actual question: Is there any way to make a backup of the 100% Stock Recovery?
Click to expand...
Click to collapse
Yes but not convenient at all like said above, I already did it once, just because the ota update zip file was encrypted and so it was impossible to extract the recovery directly from the ota so I had to pull it directly from the phone: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
And please dont give me a link where i can download one, i would like to create a backup myself
Click to expand...
Click to collapse
Can't give you any link to download your recovery anyway since we don't know what firmware version your phone is running.
alray said:
You can only use the "fastboot boot recovery.img" command on hboot 1.44. So if you absolutely want to backup the stock recovery using this method you'll need s-off in order to downgrade your hboot so you can boot a custom recovery without flashing it to dump the stock one, not very convenient... Stock recovery can be extracted from the ota update zip file of the same version your phone is running, this is the method used by everyone if their stock recovery.img is not already available to download here on xda.
Yes but not convenient at all like said above, I already did it once, just because the ota update zip file was encrypted and so it was impossible to extract the recovery directly from the ota so I had to pull it directly from the phone: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
Can't give you any link to download your recovery anyway since we don't know what firmware version your phone is running.
Click to expand...
Click to collapse
Thank you for your quick answer
It doesn't have to be this way, I just want to create my own backup of Stock Rom and Stock Recovery. If their is a way to extract it from an ota update, I would gladly use this method. Do you know a good guide, that explains how to do that? And could I do that with the current version of Android running on the Phone? Update sounds like I would have to update it first?
hahamuntz said:
Thank you for your quick answer
It doesn't have to be this way, I just want to create my own backup of Stock Rom and Stock Recovery. If their is a way to extract it from an ota update, I would gladly use this method. Do you know a good guide, that explains how to do that? And could I do that with the current version of Android running on the Phone? Update sounds like I would have to update it first?
Click to expand...
Click to collapse
To extract the stock recovery from an update update, simply open the zip file, inside you'll find another zip file named "firmware.zip" open that one and extract the recovery.img file.
what is your firmware version? "fastboot getvar version-main"
alray said:
To extract the stock recovery from an update update, simply open the zip file, inside you'll find another zip file named "firmware.zip" open that one and extract the recovery.img file.
what is your firmware version? "fastboot getvar version-main"
Click to expand...
Click to collapse
Im running 4.19.401.11
How do I get the ota.zip file? Is there a way to extract that from my Phone?
hahamuntz said:
Im running 4.19.401.11
How do I get the ota.zip file? Is there a way to extract that from my Phone?
Click to expand...
Click to collapse
You can get the ota zip file when downloading an update and selecting "install later". Once the download is completed, connect your phone to your computer and copy the ota zip file from your download folder to your computer. Once the update is installed, the ota zip file is deleted form the phone so you can't extract the update from the phone since its already installed.
You can find the ota update file for your version (from 4.19.401.9 to 4.19.401.11) here: https://www.androidfilehost.com/?fid=95747613655045071
Or directly download the 4.19.401.11 stock recovery here: https://www.androidfilehost.com/?fid=95864024717070740 which is the same exact recovery installed on your phone.
alray said:
You can get the ota zip file when downloading an update and selecting "install later". Once the download is completed, connect your phone to your computer and copy the ota zip file from your download folder to your computer. Once the update is installed, the ota zip file is deleted form the phone so you can't extract the update from the phone since its already installed.
Click to expand...
Click to collapse
I think i did it. Thank you very much!
there is the firmware folder with 9 .img files in it seems to be right, altough I can't open the zip folder directly (it says error- Folder invalid), but it worked when I extracted the Folder...
The 9 .img files are about 100 MB, is that right?
And could I apply the same update to my second HTC One M7( running a rooted Stock with Android 5.0.2), to get it back to Stock Rom and Recovery?
What do I have to check to make sure they are compatible?
hahamuntz said:
I think i did it. Thank you very much!
there is the firmware folder with 9 .img files in it seems to be right, altough I can't open the zip folder directly (it says error- Folder invalid), but it worked when I extracted the Folder...
The 9 .img files are about 100 MB, is that right?
Click to expand...
Click to collapse
The stock recovery should be around 12MB not 100MB,
And could I apply the same update to my second HTC One M7( running a rooted Stock with Android 5.0.2), to get it back to Stock Rom and Recovery?
What do I have to check to make sure they are compatible?
Click to expand...
Click to collapse
No, this recovery is only for 4.19.401.11 and that update file is for patching 4.19.401.09 to 4.19.401.11 only.
alray said:
The stock recovery should be around 12MB not 100MB, .
Click to expand...
Click to collapse
Sorry i didn't say that well... All of the .img files in this folder together are about 100 MB.
The Recovery itself is only 12 MB, so it seems fine
alray said:
No, this recovery is only for 4.19.401.11 and that update file is for patching 4.19.401.09 to 4.19.401.11 only.
Click to expand...
Click to collapse
Okay, but if I would install the update and make a Nandroid backup of the updated Rom, would I be able to install that Nandroid backup also on the second Phone?
And would I be able to use the recoverybackup I received out of the OTA.zip to restore the first Phone to StockRecovery if I flashed a custom Recovery after I updated?
hahamuntz said:
Sorry i didn't say that well... All of the .img files in this folder together are about 100 MB.
The Recovery itself is only 12 MB, so it seems fine
Click to expand...
Click to collapse
Yes that seems fine.
Okay, but if I would install the update and make a Nandroid backup of the updated Rom, would I be able to install that Nandroid backup also on the second Phone?
If I understand correctly, you'll update phone #1 then make a nandroid backup
And would I be able to use the recoverybackup I received out of the OTA.zip to restore the first Phone to StockRecovery if I flashed a custom Recovery after I updated?
Click to expand...
Click to collapse
I'm not sure if I should answer this one before knowing the details (fastboot getvar all) of the second phone and knowing what is your goal exactly. That might only brings more confusion and there might be easier solution to restore your phone than creating a backup from device A and restoring it to B...
But yes its possible, you want to make sure your recovery version, software version and firmware version match together. E.G You don't want to restore a 4.19.401.11 software backup on a phone running a different firmware version and the recovery version must also match. So if phone B is 7.19.401.22 firmware you want to restore a 7.19.401.22 software and a 7.19.401.22 stock recovery. If you have updated phone A from 4.19.401.11 to 7.19.401.22 and then make a backup of it, you should be fine restoring that backup on phone B. Any mismatch between version will prevent installation of ota updates and in some case you can have drivers issues.
alray said:
I'm not sure if I should answer this one before knowing the details (fastboot getvar all) of the second phone and knowing what is your goal exactly. That might only brings more confusion and there might be easier solution to restore your phone than creating a backup from device A and restoring it to B...
But yes its possible, you want to make sure your recovery version, software version and firmware version match together. E.G You don't want to restore a 4.19.401.11 software backup on a phone running a different firmware version and the recovery version must also match. So if phone B is 7.19.401.22 firmware you want to restore a 7.19.401.22 software and a 7.19.401.22 stock recovery. If you have updated phone A from 4.19.401.11 to 7.19.401.22 and then make a backup of it, you should be fine restoring that backup on phone B. Any mismatch between version will prevent installation of ota updates and in some case you can have drivers issues.
Click to expand...
Click to collapse
First Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Second Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -
(bootloader) imei: -
(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: 3869mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
What I wanna do is to use the first phone to create my own Backup of ROM and Recovery to get the second phone to the newest Version of stock.
Is this possible with these pair of Phones?
And could you recommend me a good website were I could learn what all these variables mean? an were I could learn more about this topic?
hahamuntz said:
First Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Second Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 3869mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
What I wanna do is to use the first phone to create my own Backup of ROM and Recovery to get the second phone to the newest Version of stock.
Click to expand...
Click to collapse
Well the second phone can simply be updated to the latest version by flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30 which is the latest version.
The first phone can also be updated to the latest version by flashing the 7.19.401.2 firmware first and then doing the same thing, flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30. Simple and easy unlike what you are trying to do
And could you recommend me a good website were I could learn what all these variables mean? an were I could learn more about this topic?
Click to expand...
Click to collapse
Here is the essential:
(bootloader) version-bootloader: This is your bootloader version, sometime called hboot
(bootloader) version-baseband: This is your radio version, radio is the software that controls the reception/transmission. Different carriers/region will requires different radio version because of different infrastructures.
(bootloader) version-main: This is your firmware version, the firmware is the code that make possible the interaction between the software and the hardware.
(bootloader) serialno: Serial number of your phone, don't share this number on the forum
(bootloader) imei: IMEI number is a unique number identifier for GSM networks, for example if your phone is declared lost/stolen or linked to unpaid bills, this number will be added to an international blacklist and you won't be able to use your phone on any carrier worldwide. Don't share this number on the forum.
(bootloader) meid: MEID is the same as IMEI but for CDMA phones, on GSM phone you don't have an MEID (only showing 0)
(bootloader) product: This is your product code, M7_UL means its a M7, U = GSM, L= LTE so its a M7 GSM/LTE
(bootloader) modelid: Model ID (MID) is a little like the product code but more specific to your region. For example, PN0710000 = M7_UL Europe. PN0712000 is also a M7_UL but for North America (all Canadian carriers, USA's AT&T, Google Play Edition and US developer edition)
(bootloader) cidnum: CID is the carrier / region ID
(bootloader) security: Security ON/OFF. Read about s-on/s-off here
alray said:
Well the second phone can simply be updated to the latest version by flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30 which is the latest version.
The first phone can also be updated to the latest version by flashing the 7.19.401.2 firmware first and then doing the same thing, flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30. Simple and easy unlike what you are trying to do
Click to expand...
Click to collapse
How would I know if these are compatible?
I would rather not use some download from the Internet because I afraid that somebody messed it up and I won't get the 100% Stock, maybe even an infected one. (Is this even a rational fear? )
That's why I am trying to create all the necessary resources myself, so I can be sure that they are alright. Also I learn much more if I do it step by step instead of just flashing a Rom from the web.
For example how do I check if a Rom is compatible with my device?
alray said:
(bootloader) serialno: Serial number of your phone, don't share this number on the forum
(bootloader) imei: IMEI number is a unique number identifier for GSM networks, for example if your phone is declared lost/stolen or linked to unpaid bills, this number will be added to an international blacklist and you won't be able to use your phone on any carrier worldwide. Don't share this number on the forum.
Click to expand...
Click to collapse
Is the other stuff save to share?
hahamuntz said:
How would I know if these are compatible?
I would rather not use some download from the Internet because I afraid that somebody messed it up and I won't get the 100% Stock, maybe even an infected one. (Is this even a rational fear? )
Click to expand...
Click to collapse
Not really since the RUU are offical (from HTC) and also they are encrypted with HTC private key .The 7.19.401.22 ruu was uploaded by me as you can see here. :good: So there is nothing to fear. Then the 7.19.401.30 ota update will come directly from HTC's servers so again, nothing to fear.
That's why I am trying to create all the necessary resources myself, so I can be sure that they are alright.
Click to expand...
Click to collapse
No offense, but these ruu are probably more reliable than what you are trying to do + easier to achieve your goal.
Also I learn much more if I do it step by step instead of just flashing a Rom from the web.
Click to expand...
Click to collapse
+1 for learning
For example how do I check if a Rom is compatible with my device?
Click to expand...
Click to collapse
First you have a M7_UL (GSM variant) so make sure you are only flashing M7 GSM stuff (rom, recovery, kernel etc). Also read the rom thread to see if you have all the pre-requisite before flashing a rom, for example, lollipop roms requires at least a 7.xx.xxx.x firmware to work correctly so it would work fine on phone B but not on phone A. Another example: CyanogenMod roms requires at least TWRP recovery 2.7.1.1, using anything below that will not work. Thats why you should always read the first post of the thread from the rom you want to flash before proceeding. If you are unsure after reading, better to ask questions instead of (soft) bricking,
So can I flash the 7.19.401.22 from you directly on phone B? And then update over the official server? Then Phone B is completely stock and with the newest version?
If understood the whole s-off/ s-on that you posted, I only can flash the official RUUs on Phone B with s-on?
I think after that I understood everything for now thank you very much!
Do you have a good source where I can read about this whole topic? I need something like an encyclopedia with explanations, that are not completely basic but easy enough for me to understand
hahamuntz said:
So can I flash the 7.19.401.22 from you directly on phone B? And then update over the official server? Then Phone B is completely stock and with the newest version?
Click to expand...
Click to collapse
Yes you can and btw the ruu is not from me, I have uploaded it but its an official RUU from HTC.
If understood the whole s-off/ s-on that you posted, I only can flash the official RUUs on Phone B with s-on?
Click to expand...
Click to collapse
You can also flash the RUU on Phone A but you will need to update its firmware first since its too old to accept the 7.19.401.2 ruu
Do you have a good source where I can read about this whole topic? I need something like an encyclopedia with explanations, that are not completely basic but easy enough for me to understand
Click to expand...
Click to collapse
About what? flashing RUU?
Btw, you'll find instructions how to flash the ruu here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (see post #1)
I meant to ask if it is correct that I can only Flash official RUUs while on S-On?
I mean something like a collection of Information about all the terms used around flashing and rooting.
At the moment I just google everything I don't understand/know, but I would like to understand it all completely. Is there something like a guide, that doesn't only say " Do this and then do that" but also explains why I should do this and what exactly I am doing.
alray said:
Btw, you'll find instructions how to flash the ruu here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (see post #1)
Click to expand...
Click to collapse
Thanks, can I flash everything from there that has my CID? Or do I have to look out for something else?
And while I am doing this, could I switch from Sense to the Google Play Edition on Phone B?
hahamuntz said:
Thanks, can I flash everything from there that has my CID? Or do I have to look out for something else?
Click to expand...
Click to collapse
As long as the rom you want to flash is for a M7_UL you should be able to flash it, CID is more important when you want to flash a RUU.
And while I am doing this, could I switch from Sense to the Google Play Edition on Phone B?
Click to expand...
Click to collapse
Using a custom GPE rom yes its possible, using a GPE RUU no because the phone is S-ON and flashing the GPE ruu would requires to change the phone CID/MID (s-off needed)
alray said:
As long as the rom you want to flash is for a M7_UL you should be able to flash it, CID is more important when you want to flash a RUU.
Click to expand...
Click to collapse
So could I flash this Rom, although it says its for Gsm or would I lose my ability to use lte?
(http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927)
Is this even the correct Rom if I want the complete stock gpe? And if flash the unrooted version would I be able to root it in a second step (Easier for me to learn the stuff, then just flashing a rooted Rom)
alray said:
Using a custom GPE rom yes its possible, using a GPE RUU no because the phone is S-ON and flashing the GPE ruu would requires to change the phone CID/MID (s-off needed)
Click to expand...
Click to collapse
I think I understood it wrong... I thought the Ruu is a part of a Rom? Used to verify if it is official or not?
Do you know a collection of Information about all the terms used around flashing and rooting.
At the moment I just google everything I don't understand/know, but I would like to understand it all completely. Is there something like a guide, that doesn't only say " Do this and then do that" but also explains why I should do this and what exactly I am doing.