Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Happyhog11 said:
Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Click to expand...
Click to collapse
first of all post your fastboot getvar all of the phone that says this is a test device please, remove imei and serial number before posting please, sounds s-off to me, and that's a good thing.
Happyhog11 said:
Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Click to expand...
Click to collapse
Ok there's a few reasons why you may not be receiving OTA updates on the first device.
The second device (test device) Sounds like it's s-off that's not something you want to fix there are many benefits to having the device s-off. As for transferring backups between devices that should be fine as long as their both of the same model id. To be sure of all this can you please post the output of
Code:
fastboot getvar all
For both devices :good:
Hi Guys
So here is the code for the old phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3814mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As for the new phone, surprisingly out of the blue today it notified me it needed a update to fix the audio so i let it start downloading but my internet is awfully slow so i cant turn it off for another 4 hours. After the update is finished i will post the fastboot stuff asap
Have to look into this s-off thing some more. I have no idea what it means but it sounds interesting
Thanks Again
Joel
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Happyhog11 said:
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Click to expand...
Click to collapse
first of all, remove imei and serial numbers from your outputs in your 2 posts, these are 2 numbers you want to keep to yourself, the s-off phone is the better one and easier to work with, leave it s-off, don't ever go s-on, you will regret it, you can follow this very simple step by step guide to get this phone receiving updates again, all the way upto lollipop: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 you will need to unlock the bootloader first though to do this.
Happyhog11 said:
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Click to expand...
Click to collapse
Well I was first thinking maybe it was AT&T and AT&T phones only get OTA's when connected to the AT&T network but that's not the case here.
Are both devices running a the same stock rom. As they are identical you could just make a nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data. Could you maybe post a screen shot of the Settings>About>Software information screen from each of the devices?
It's not that it cant "get" the ota updates its more that it wont install.
Also I'm in Aus, as for the first phone it was bought outright through a retailer and i have no idea for the second phone(eBay guy didn't leave any history about the phone.)
I have just put cmw on the new phone so now i can do the guide posted by Seanie280672.
Will post the screenshots in a sec.
Will need your help with making a backup of just the boot and system partitions......don't know how to do that.
Joel
Okay This is the "old phone" screenshot:
https://drive.google.com/file/d/0B5yAH_RjUp-KQmU2bkJfUVlINXc/view?usp=sharing
Okay here is the screenshot for the new phone
https://drive.google.com/file/d/0B5yAH_RjUp-KcmRIUjZIOVN2TU0/view?usp=sharing
Also sorry Google drive was the quickest way to get pictures online from my laptop at the moment.
Only difference is the software number the old phone is x.x.x.7 not x.x.x.12 which im guessing is the update to fix audio.
Not sure if it is relevant but i have the file "OTA_M7_UL_K443_SENSE60_MR_Optus_AU_6.11.980.12-6.11.980.7_release_407474r14kwjhfpdkw8z4t" Thats the update file that the old phone downloaded to fix audio which would make it identical to the new phone, but alas it dose not install.
So i guess the "nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data" is still the best solution?
Thanks again i know i say that alot but could not have done this without your help!
Joel
Wait....i was of the belief that cmw was the reason i couldnt install ota's. Is that correct? If so what if i just put the original stock recovery back on the old phone(link http://forum.xda-developers.com/showthread.php?t=2158151) then let the update install and then put cmw back on..... i dont know if it will work but its another method, maybe i have this all back the front lol
Happyhog11 said:
Okay here is the screenshot for the new phone
https://drive.google.com/file/d/0B5yAH_RjUp-KcmRIUjZIOVN2TU0/view?usp=sharing
Also sorry Google drive was the quickest way to get pictures online from my laptop at the moment.
Only difference is the software number the old phone is x.x.x.7 not x.x.x.12 which im guessing is the update to fix audio.
Not sure if it is relevant but i have the file "OTA_M7_UL_K443_SENSE60_MR_Optus_AU_6.11.980.12-6.11.980.7_release_407474r14kwjhfpdkw8z4t" Thats the update file that the old phone downloaded to fix audio which would make it identical to the new phone, but alas it dose not install.
So i guess the "nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data" is still the best solution?
Thanks again i know i say that alot but could not have done this without your help!
Joel
Click to expand...
Click to collapse
Ok this may get a little complicated but I'll try to make it as clear as possible
You can use the system and Boot nandroid from the s-off device to update the Rom on the s-on device. Then make a full nandroid backup of the s-on device of System, boot and data. (so now you have a nandroid of the updated Rom with all your apps and settings) now backup the internal storage of the s-on device to your pc.
Now you can extract the firmware.zip from the OTA file and manually flash the firmware to the s-on device to update the firmware. This will require you to relock the bootloader and when you unlock the bootloader the device will be wiped (that's the reason we backup the internal storage to the pc) so you can Unlock the bootloader again restore the internal storage with your pc backup then Flash twrp and restore the nandroid and heypresto the s-on device is fully updated with Rom and Firmware. If you need further instruction on how the flash the firmware from the OTA just let me know
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
Happyhog11 said:
Wait....i was of the belief that cmw was the reason i couldnt install ota's. Is that correct? If so what if i just put the original stock recovery back on the old phone(link http://forum.xda-developers.com/showthread.php?t=2158151) then let the update install and then put cmw back on..... i dont know if it will work but its another method, maybe i have this all back the front lol
Click to expand...
Click to collapse
Yes that's correct if you flash the stock recovery you should be able to install the ota. Although if the stock Rom is modified in some way the OTA may fail to install.
Danny201281 said:
Ok this may get a little complicated but I'll try to make it as clear as possible
You can use the system and Boot nandroid from the s-off device to update the Rom on the s-on device. Then make a full nandroid backup of the s-on device of System, boot and data. (so now you have a nandroid of the updated Rom with all your apps and settings) now backup the internal storage of the s-on device to your pc.
Now you can extract the firmware.zip from the OTA file and manually flash the firmware to the s-on device to update the firmware. This will require you to relock the bootloader and when you unlock the bootloader the device will be wiped (that's the reason we backup the internal storage to the pc) so you can Unlock the bootloader again restore the internal storage with your pc backup then Flash twrp and restore the nandroid and heypresto the s-on device is fully updated with Rom and Firmware. If you need further instruction on how the flash the firmware from the OTA just let me know
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
Yes that's correct if you flash the stock recovery you should be able to install the ota. Although if the stock Rom is modified in some way the OTA may fail to install.
Click to expand...
Click to collapse
Okay your method sounds like a fun experience, as long as your sure my data is safe . Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Happyhog11 said:
Okay your method sounds like a fun experience, as long as your sure my data is safe [emoji14]. Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Click to expand...
Click to collapse
Yeah my instruction kinda assumes you are using TWRP recovery [emoji14] no one uses CWM on HTC one anymore. TWRP if a far better recovery for best results use TWRP 2.6.3.3 other newer versions all have some bugs of some sort. 2.6.3.3 is bug free and stable :good:
Happyhog11 said:
Okay your method sounds like a fun experience, as long as your sure my data is safe . Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Click to expand...
Click to collapse
Edit: this is possible with cmw or do i need to swap to twrp? Also as for the firmware is that just the zip called "firmware.zip" inside the ota zip? what do you do with the images inside? Shame on htc for putting a zip in a zip its just plain bad practice lol
Happyhog11 said:
Edit: this is possible with cmw or do i need to swap to twrp? Also as for the firmware is that just the zip called "firmware.zip" inside the ota zip? what do you do with the images inside? Shame on htc for putting a zip in a zip its just plain bad practice lol
Click to expand...
Click to collapse
Ok this is what I was afraid of when I said it might get complicated.
So first unfortunately I'm really not sure what CWM is and is not capable of these days I have not used it for about 4 years lol, since my galaxy ace days. Either way I would definitely recommend switching to twrp for your HTC one. Although you will need to make new nandroids if you do as TWRP is not compatible with CWM backups as far as I'm aware. TWRP allows you to backup and restore partitions separately.
You are correct about the firmware.zip inside the OTA file just extract the firmware.zip from the OTA and then you can flash the firmware.zip with fastboot. You must be sure you update the Rom before the firmware though or the phone won't boot after flashing the firmware. This is not an unrecoverable situation but will further complicate matters.
To manually update the firmware put the firmware.zip in your fastboot folder.
Boot the phone to the bootloader connected with fastboot usb. In the command window type.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Your device will reboot to the bootloader and should now be ***RELOCKED***
Code:
fastboot oem rebootRUU
**--- Case sensative ---^^^
Your device should boot to a black screen with a Silver HTC logo. This is RUU mode. We can now flash the firmware. In the command window type
Code:
fastboot flash zip firmware.zip
The first flash will be short, and will appear to fail. Thats normal its just a pre update preparing the hboot for the firmware. The phone screen will go black then return to RUU mode. So now we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal. As long as the command window has finished its output its done. Reboot to the bootloader.
Code:
fastboot reboot-bootloader
Just for the record if the device was s-off like the other one there is never any need to relock the bootloader as s-off allows flashing while unlocked.
Okay super quick question. I'm trying to flash twrp onto one of the phones but how do i use adb/fastboot with multiple devices plugged in? cant figure it out.....the other device is being backed up.
Happyhog11 said:
Okay super quick question. I'm trying to flash twrp onto one of the phones but how do i use adb/fastboot with multiple devices plugged in? cant figure it out.....the other device is being backed up.
Click to expand...
Click to collapse
Fastboot should only see the device that's in the bootloader.
E.g if one device is booted to Android or Recovery (this will be the device your backing up) only adb should see this device.
So you can flash twrp to the other device while in the bootloader with fastboot
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
So just so I'm sure we are on the same page I'm going to:
1. System/Boot Nandroid from s-off device
2. System/Boot/Data Nandroid from s-on device
3. Backup files from s-on device to pc
4. Follow your steps flash firmware updates.
5. Copy Files back to phone
6. flash twrp back onto device
7. Restore The nandroid from step 2
8. Heypresto my s-onn phone now has the latest firmware and all my data just as before?
Hope i've got that right makes sense really
Okay so I've flashed twrp onto both phones, backup of the s-off is complete, backup of the s-off is ongoing.
This...i have to say is uber cool. Having two identical phones is going to be super fun when it comes to custom roms and backups and stuff like that, if one phone dies ill just apply the back to the other...super cool stuff
Related
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.708.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Oops
(bootloader) imei: nothing to see here
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-14eb688c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks for taking the time to read this, any pointers would be very much appreciated
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
kelvov said:
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
Thanks for taking the time to read this, any pointers would be very much appreciated
Click to expand...
Click to collapse
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
hp79 said:
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:...
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
Click to expand...
Click to collapse
Thanks for the info, will have to try it tomorrow after buying a cable
alray said:
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
Click to expand...
Click to collapse
Unfortunately no, I wrongly assumed a simple backup would have sufficed in the event anything went wrong. Never again. Oops, that for the heads up on that
You should be able to push ARHD 31.6 and be ok
sent from my mobile device
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
BlockABoots said:
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
Click to expand...
Click to collapse
if you have made no changes to the OS just install the stock recovery for your os version.
Stock recovery's
if your using custom roms you need to RUU back to stock then take the update
find your RUU here >> http://www.androidruu.com/index.php?developer=M7
use fastboot getvar all to find your phones information
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3************
(bootloader) imei: 354***************
(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: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
BlockABoots said:
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3**********
(bootloader) imei: 354**************
(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: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
Click to expand...
Click to collapse
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
clsA said:
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
Click to expand...
Click to collapse
Thanks for the pointer.
So these are the steps i need to do:
1. Download 'recovery 2.24.401.8.img'
2. Rename 'recovery 2.24.401.8.img' to 'recovery.img'
3. Place 'recovery.img' in my adb/fastboot folder (C:\Adb)
4. Open Command Prompt and navigate to your adb folder
5. Type 'adb reboot bootloader' to get into fastboot on the HTC ONE
6. And then flash the recovery img by typing 'fastboot flash recovery recovery.img'
Is the above all correct?
Yep that's it
Sent from my HTC One using Tapatalk
uarbie
clsA said:
Yep that's it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
BlockABoots said:
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
Click to expand...
Click to collapse
ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
BlockABoots said:
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
Click to expand...
Click to collapse
ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
ipfreelytech said:
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
Click to expand...
Click to collapse
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
BlockABoots said:
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Click to expand...
Click to collapse
ipfreelytech said:
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
Click to expand...
Click to collapse
It should of already been unlocked, as it was rooted and had TWRP install previously
So theres no way for me to get this stuff back then, pictures, messages, contacts etc?
Um, there's some missing information here.
Short answer, if you in fact "unlocked" the phone recently, you wiped all personal data and there is absolutely no way to go back.
There are other ways data can get erased however.
As you pointed out, the phone was likely unlocked previously. Not sure how it would have become relocked forcing you to unlock again, which you don't seem to remember doing anyway.
Also you didn't originally say you lost your pictures. Did you or didn't you? Losing texts and contacts is normal when flashing a ROM. There are backup apps for texts and most people keep their contacts in the cloud do you normally just resync and you're done.
But pictures is something else. Sounds like someone did a factory reset and/or formatted the entire /data partition in recovery.
Normally most recoveries know that when you "format" data, you are really just selectively erasing everything in /data *except* /data/media. You don't usually do an actual format. The stock recovery does not make this distinction, and even custom recoveries often have an advanced features that lets you truly format all of /data. So you might have nuked your pictures in recovery somehow, no unlocking necessary.
You need to go into more detail.
But if you are saying your pictures are gone, they're probably totally gone.
One last possibility, the version-main you posted suggests you may have been using android 4.2 originally.
But I suppose it's possible the original ROM you were using was actually 4.1. Maybe your stuff was at the top level of /data/media and never got moved to /data/media/0
This surprised quite a few people during the transition from Android 4.1 to 4.2
So *if* you didn't unlock *and* didn't totally format everything *and* your old ROM was 4.1, well.. get a file browser and have a look around. Maybe you got lucky.
Sent from my HTC One using xda app-developers app
Well before i flashed the recovery image bootloader had 'Tampered' and 'unlocked' listed at the top of the sceeen, just like it does now so im not really sure what happened. But as soon as i flashed the 'recovery 2.24.401.8.img' back onto my phone and then downloaded the 4.4.2 system update and installed it, when the phone restarted again it was like it was back to factory default in that i had to go through the whole setup screens!, so not sure whats happened.
But on closer inspection even though i have downloaded and installed system update 4.4.2, if i go in settings>about>Software information> it says im on Android version 4.3 and software number 3.62.401.1, isnt this wrong as ive updated to 4.4.2???
You have two separate issues here. You lost your data and you're not running 4.4.2
Apparently you're not worried about your data.
To get 4.4.2 you either need to a) get to a place that is so "stock" that OTA's will take you the rest of the way or b) manually flash a 4.4.2 ROM. The b) option usually requires S-OFF and a suitably recent recovery compatible with KitKat.
If you are already S-OFF of course b) is way simpler. But you're not. In fact you have HBOOT 1.56 which can make S-OFF less certain. If you can get S-OFF that's the way I would go. I personally never screw around chasing OTA's.
You may be in an awkward place right now.
Time for someone with more patience than me to get involved I guess.
Sent from my HTC One using xda app-developers app
No please don't get me wrong I am certainly worried about my lost data, especially the pictures, but from what you said I there's no real way to recover them, is that correct or is there a way at all?
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
NxNW said:
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sadly there is nothing in /data/media there are 3 folder, 0, legacy. obb and a file .htc_layout_version none hold any of my old photos . I have even tried the program, Wondershare Dr.Fone and that doesnt find any of my old photos either...so i guess there lost for ever, bugger.
I guess i need to get this phone back to stock and then try the update and see if it takes this time?, so ill need to remove the root, TWRP recovery and SuperSU?
Last night I got a notification for a System Update to version 6.12.161.5.
Has anyone tried this yet? And any problems found?
With the last two updates over the last 3-4 months I have had major problems:
1. When VodaFone forced the Rich Communication Suite / Service upon us; abysmal battery performance and terrible instability problem with phone frequently crashing on incoming calls and texts - which I 'solved' by Disabling RCS.
2. When VodaFone pushed the next update that greyed out the box to Disable RCS (they appeared to fix the instability and battery drain problem, but now I don't even have the option to disable RCS).
After lots of self-help and web searching I now have a stable phone with decent battery life again, and given those past painful experiences I am somewhat reluctant to blindly update.
Has anyone tried this Update yet, and can you comment after a few days of usage, particuarly on stability and battery usage?
Thanks
David
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Pilch2k said:
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Click to expand...
Click to collapse
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
daveingram said:
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
Click to expand...
Click to collapse
To be honest i've not noticed any issues yet, or any changes!
needed Ota file 6.12.161.8
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Seymour2002 said:
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Click to expand...
Click to collapse
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Flash firmware from OTA...
alray said:
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Click to expand...
Click to collapse
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823; but probably I'm wrong...
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Seymour2002 said:
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823;
Click to expand...
Click to collapse
Dont know what you are referring to.
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Click to expand...
Click to collapse
Unfortunately, there is not much files for that CID.
I don't understand what you want to attempt with an OTA file. Firmware included in OTA are not complete, it only contain files to be updated in an incremental way. If you manually flash a firmware from an OTA updates and you do it over the wrong version (currently installed on your phone) this could end with a bricked phone (hardbrick)
Flashing the entire OTA zip file will not help either. OTA files are patches that must be installed over a working rom and proper rom version. It also must be flashed using the "software update" option within the OS (unless the phone is s-off)
what you should do imo, is to start over fresh, flash twrp recovery 2.6.3.3 and flash a "close to stock" rom
Flash firmware from OTA...
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37WW904203
(bootloader) imei: 357864057367987
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Seymour2002 said:
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(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: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Click to expand...
Click to collapse
how did you manage s-on + locked bootloader + no recovery ?
was this phone converted to DE or GPE at one time ?
Flash firmware from OTA...
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Seymour2002 said:
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Click to expand...
Click to collapse
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ?
followed by fastboot reboot-bootloader ?
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Flash firmware from OTA...
clsA said:
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ? Yes, several times...
followed by fastboot reboot-bootloader ? Yes....
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Click to expand...
Click to collapse
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Seymour2002 said:
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Click to expand...
Click to collapse
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Flash firmware from OTA...
clsA said:
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Click to expand...
Click to collapse
Once I select recovery from the bootloader menu and I press power button the phone reboots the bootloader...
SOLVED! Unbrikked THC ONE M/!!!!!
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Seymour2002 said:
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
Glad you got your phone revived :good:
since a phone is S-On there's no risk to flash a wrong firmware
Click to expand...
Click to collapse
The risk is there, if you flash a firmware patch (ota firmware) over the wrong version (i.e 5.xx.xxx.x over 3.xx.xxx.x), this could brick. Happened many times that's why its mentioned in some threads. There is no risk flashing the same version like you did
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(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: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(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: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.
I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.
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.