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.
Related
I tried installing ElementalX kernel on my HTC One M7 AT&T. I flashed the kernel with TWRP and now when I try to boot my phone up it freezes at the loading screen with red text at the bottom saying "This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may load to legal action." I've tried hard resetting it, messing around in the bootloader, etc. I have not found a solution, maybe one of you can.
Thanks
StolenStatus said:
I tried installing ElementalX kernel on my HTC One M7 AT&T. I flashed the kernel with TWRP and now when I try to boot my phone up it freezes at the loading screen with red text at the bottom saying "This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may load to legal action." I've tried hard resetting it, messing around in the bootloader, etc. I have not found a solution, maybe one of you can.
Thanks
Click to expand...
Click to collapse
How much did you over lock and/or undervolt in Aroma for ElementalX? That could be your issue. I would reflash Elemental, choose more conservative values, wipe Dalvik and cache after install, then try booting again
dgtiii said:
How much did you over lock and/or undervolt in Aroma for ElementalX? That could be your issue. I would reflash Elemental, choose more conservative values, wipe Dalvik and cache after install, then try booting again
Click to expand...
Click to collapse
I did not go too far fetched with the overclocking and undervolting, and I cant reflash it for i deleted the zip off my phone hoping for the best. My computer is not even recognizing the phone as a storage device so I cannot access it to put it back on.
StolenStatus said:
I did not go too far fetched with the overclocking and undervolting, and I cant reflash it for i deleted the zip off my phone hoping for the best. My computer is not even recognizing the phone as a storage device so I cannot access it to put it back on.
Click to expand...
Click to collapse
You can get into recovery though, right? Just reflash your rom and that will reinstall the stock kernel
dgtiii said:
You can get into recovery though, right? Just reflash your rom and that will reinstall the stock kernel
Click to expand...
Click to collapse
Could you please give me instructions to do that?
StolenStatus said:
Could you please give me instructions to do that?
Click to expand...
Click to collapse
What rom are you using, or are you still on stock?
---------- Post added at 12:02 PM ---------- Previous post was at 11:55 AM ----------
If you're on a custom rom, boot to recovery, and reflash the rom, without a full wipe, just flash it over what you have.
If you are on the stock rom, things are a little more complicated. You have to ADB push the kernel file (redownload Elemental) to your SD card. Follow this guide http://forum.xda-developers.com/showthread.php?t=2325853
Your computer should see the phone in ADB mode after you install the ADB drivers. It's all in that guide I linked.
StolenStatus said:
I cant reflash it for i deleted the zip off my phone hoping for the best.
Click to expand...
Click to collapse
I'm sure you realize this now, but that is never a good idea. It's good practice to keep all files for your current configuration on your phone should you ever need to reflash. It doesn't hurt to keep an alternate rom/kernel either.
If you don't know what you are doing then don't do it.
Help needed
Hi all,
Help needed. Am stuck in HTC white beats audio screen. Phone restarted after I udpated some Xposed installer files..
Steps already done so far
> Tried installing Xposed disabler recovery...by going into TWRP and then installing it..----It gave error in flashing
> No recovery made before..so no luck..
> Able to sideload file in TWRP but not able to find the right ROM for my device as I have S-ON.
> Tried resetting to factory --- Didn't worked
I have attached logcat file too..
My device details are as follows ...please help guys...
M7_U PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.707.4
eMMC-boot 2048MB
(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.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35PW904368
(bootloader) imei: 354435054280904
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4007mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(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: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !
Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.
hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom
another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(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: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
C:\Documents and Settings\fresh\Desktop\one\data>
Deleted
garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this
garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.
Deleted
when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.
sorry didnt read your reply, well it didnt initialise so no s off anyway
garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us
im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option
right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now
guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me
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
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
My major screwups:
No nandroid backup.
No s-off
I have Sprint
Current State:
I can get to fastboot, recovery and adb works fine. But no matter which recovery/rom combination I try, I get the same end result. My phone will boot to the "HTC One" screen, then go the green HTC logo/white background screen then reboot. Sometimes it stays active long enough to begin the "Welcome to Android" stuff (pick your language, wifi connection, etc...), but not nearly long enough to get through all the screens.
What I've tried so far:
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
ROMS: ARHD 31.6 and 62.0 (I know this doesn't work with Sprint), Viper 6.1 and some "stock" rom I found somewhere (filename One_4.19.401.11_odexed.zip).
I don't remember exactly the order, but I know I did TWRP 2.6.3.4 and ARHD 62.0 first. Then did Viper 6.1, then ARHD 31.6. Since then, I've tried every combination of recovery and ROM that I can think of.
Here's getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4205mV
(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.040s
I'm willing to try anything at this point. So suggestions are welcome. You're also welcome to berate me for the above mentioned screwups, but it won't be very helpful.
TIA
Goto_End said:
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
TIA
Click to expand...
Click to collapse
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: http://techerrata.com/browse/twrp2/m7wls
(make sure to check MD5 on the download)
nkk71 said:
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: (can't post links yet)
(make sure to check MD5 on the download)
Click to expand...
Click to collapse
Downloaded the 2.6.3.0 from the link you provided (checked md5), flashed recovery. Did an adb push to get the Viper ROM (also checked the md5) back to /sdcard and flashed the ROM. Same results as before.
Additional info:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
The screen will timeout on the green HTC logo screen. If I hit Power to bring it back to life, I have to "pull to unlock" and either the logo screen is still there or it's made it to "Welcome to Android".
I actually got to the Welcome screen this time. Picked the language, wifi network and started with my Google login before it rebooted.
Maybe an incompatible ROM issue? If so, I'm out of ideas as to what to try next.
I've downloaded what I believe to be the RUU for this model phone, but since I can't see the phone in Windows, I haven't even tried the RUU.
Goto_End said:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
...before it rebooted.
Click to expand...
Click to collapse
That's usually caused by the modem not initializing properly, and you could have some corrupt partitions due to using an m7_u/ul and it's time for ruu i guess.
Better head over to the HTC One Sprint forum: http://forum.xda-developers.com/sprint-htc-one should be plenty of help there.
Most of us here are on m7_u/ul so can offer only limited assistance... could be as simple flashing a radio for Sprint... but like I said, I'm not too familiar with Sprint unbrick.
Sorry & Good Luck
There's an awesome Rescue Tutorial over in the Sprint HTC One forum for people like me who flashed a GSM ROM on a CDMA phone. I can't post links yet, or I'd link to it just for posterity.
In essence, the GSM ROMs screw up the partition table. The fix was really easy. Most of the time was spend downloading the correct ROM and waiting for the adb push.
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