Hoping someone here might be able to help as nothing on the HTC website did.
My phone updated yesterday to Lollipop 5.0 (through EE in the UK)...well it it had a go, but failed. I'm left with just an exclamation mark of helpfulness. I've tried all of the basic recovery options but it just restarts a few times and goes back to said exclamation mark.
The error is..
DEVICE_CW_Install: Can't mount /cwprop
Then stuff about failing to mount the SD card (that it doesn't have).
Are there any tools that might help me sort this out? I don't particularly want to install something none standard on it but if that's all I can do to get it working, it would be ok.
Jxt. said:
is your bootloader is unlocked and are you on complete stock.
Click to expand...
Click to collapse
It's totally stock.
alfev said:
It's totally stock.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number.
however if it is totally stock and the bootloader is locked, then id suggest you send it back under warranty.
Thanks for replying and trying to help. It's out of warranty this is just a last ditch attempt before getting a new one really. I have zero knowledge in this area but have installed the sdk and run that command...
(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: sssh
(bootloader) imei: ssshh
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3778mV
(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
all: Done!
finished. total time: 0.088s
Seanie280672 said:
post your fastboot getvar all please without imei and serial number.
however if it is totally stock and the bootloader is locked, then id suggest you send it back under warranty.
Click to expand...
Click to collapse
Is it possible to unlock it, is there anything I can do with it, or is it a paper weight now?
alfev said:
Is it possible to unlock it, is there anything I can do with it, or is it a paper weight now?
Click to expand...
Click to collapse
If it's still under warranty, better send it back to service center since it is an OTA failure, not your fault.
eyeyousee said:
If it's still under warranty, better send it back to service center since it is an OTA failure, not your fault.
Click to expand...
Click to collapse
I would do but as I say, it's out of warranty so just making the best of it.
I'm downloading this at the moment RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
No idea if that's a good idea but I can't be any worse off than I am at the moment.
alfev said:
I would do but as I say, it's out of warranty so just making the best of it.
I'm downloading this at the moment RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
No idea if that's a good idea but I can't be any worse off than I am at the moment.
Click to expand...
Click to collapse
If that RUU fails, the best thing to do is to unlock your bootloader, you can find the unlocking instructions here search for it. Then install custom recovery, and then install custom rom.
Just post the results of your RUU setup.
eyeyousee said:
If that RUU fails, the best thing to do is to unlock your bootloader, you can find the unlocking instructions here search for it. Then install custom recovery, and then install custom rom.
Just post the results of your RUU setup.
Click to expand...
Click to collapse
The RUU update got to 1/5 checking header then crashed with "htc_fastboot.exe has stopped working." Then Error 171: USB connection error. Not sure if their is a problem with a driver or something.
alfev said:
The RUU update got to 1/5 checking header then crashed with "htc_fastboot.exe has stopped working." Then Error 171: USB connection error. Not sure if their is a problem with a driver or something.
Click to expand...
Click to collapse
171 is a USB error, means therres a problem with your drivers, sorry been a bit busy today, car problems, but that RUU is wrong for your phone anyway, that's a 401 RUU (4.19.401.2), you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Seanie280672 said:
171 is a USB error, means therres a problem with your drivers, sorry been a bit busy today, car problems, but that RUU is wrong for your phone anyway, that's a 401 RUU (4.19.401.2), you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Click to expand...
Click to collapse
I've sorted of veered off the RUU route and unlocked the phone. I've installed twrp... I'm winging it completely. Trying to get a ROM on it now... or something.
alfev said:
I've sorted of veered off the RUU route and unlocked the phone. I've installed twrp... I'm winging it completely. Trying to get a ROM on it now... or something.
Click to expand...
Click to collapse
you will have problems with Lollipop based roms, so use this one which matches your firmware: https://www.androidfilehost.com/?fid=95897840722644627
your best bet if you want it full stock is to get s-off using sunshine once you get a rom on it and convert it to a 401 WWE phone, which gets one of the fastest updates, sunshine however will cost you $25 via paypal.
I'm not familiar with M7 software numbers but, yes maximusHD custom roms are good to begin with.
Seanie280672 said:
you will have problems with Lollipop based roms, so use this one which matches your firmware: https://www.androidfilehost.com/?fid=95897840722644627
your best bet if you want it full stock is to get s-off using sunshine once you get a rom on it and convert it to a 401 WWE phone, which gets one of the fastest updates, sunshine however will cost you $25 via paypal.
Click to expand...
Click to collapse
Thanks,I will probably have a go at putting different rom's on at some point and was wondering what people thought the best option is for the M7.
I managed to get sorted using Guru_Reset_M7_2.24.401.8.zip. I had some problems uploading it to begin with, I think the usb issue stopped the ruu and abd working but not fastboot. I have a working phone now, which seems like a bonus after thinking the phone was maybe a goner. It's been a massive learning curve having known absolutely nothing about any of this stuff on Monday, I know how to put different rom's on now which is handy to know. The phone is still unlocked at the moment, I don't know what the cons of that are. Would this rom maybe update if I locked it again?
alfev said:
Thanks,I will probably have a go at putting different rom's on at some point and was wondering what people thought the best option is for the M7.
I managed to get sorted using Guru_Reset_M7_2.24.401.8.zip. I had some problems uploading it to begin with, I think the usb issue stopped the ruu and abd working but not fastboot. I have a working phone now, which seems like a bonus after thinking the phone was maybe a goner. It's been a massive learning curve having known absolutely nothing about any of this stuff on Monday, I know how to put different rom's on now which is handy to know. The phone is still unlocked at the moment, I don't know what the cons of that are. Would this rom maybe update if I locked it again?
Click to expand...
Click to collapse
no, don't try and update either, you'll stand a high chance of seriously bricking your phone, it will try and install 401 firmware which isn't for your phone, hence 2.24.401.8 like I said before, your firmware is 61. orange / EE.
the numbers work like this, 2.24.401.8 ( the 2 is android version) the 24 is part of the build number, the 401 is carrier / region (401 is WWE world wide English) yours is 61 orange / EE and you can only use these files same or above the one your currently on as your phone is s-on, and the last number 8 is build number, or alternatively you can flash any custom rom you like upto KitKat as your firmware on your phone is currently 6.xx.61.x
you are stuck with custom rom's only up to KitKat, the one I linked earlier is Maximus HD 50.0 which is as close to stock Kitkat as you will get for now, but still a custom rom. Lollipop rom's will play up as your on firmware 6xxxxxxx unless you s-off and convert your phone or unless you can get hold of the 7.xx.61.x firmware and manually upgrade your firmware, you need to have, or find someone who has the 7.xx.61.x OTA and grab the firmware.zip out of it and flash that in fastbootRUU mode.
I think I've been pretty lucky to get the thing up and running really could've gone badly but I didn't think I had anything to lose. With all of the different firmware and rom version that I wasn't aware of it sounds like there was actually a lot I could've lost with my wing it aproach.
This oldish Android version I'm on now seems to use a lot of battery, presumably connected to the additional "HTC Pocket Radiator" feature which it also turns on sporadically. It's not a big problem but I think I'll have a bash with the MaximusHD you suggested. Question though, Googling for a bit more info on MaximusHD 5.0 it appears to be Lollipop, am I right? If so, just to confirm, you're saying that I could have problems with Lollipop because of my firmware but this version of it should work ok with my current firmware? From googling I found a description of the rom that said "Firmware 7.15.401.1 is recommended to install". Sorry, just making sure because my luck is likely to run out soon.
EDIT
Also, if I do need to S-OFF, you mention Sunshine and you mention $25, this is a 3 year old phone with a slight crack in the screen so I'm not going to throw any money at it but I found Squabbi's tool kit which uses Revone for S-OFF, would this be no good?
Seanie280672 said:
(..)you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Click to expand...
Click to collapse
There is a 6.16.61.8 signed RUU available but unfortunately, its only available at ir-file.com and you need a paid account to download from that website.
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Seanie280672 said:
no, don't try and update either, you'll stand a high chance of seriously bricking your phone, it will try and install 401 firmware which isn't for your phone, hence 2.24.401.8 like I said before, your firmware is 61. orange / EE.
Click to expand...
Click to collapse
Right the update will not work but there is no chance of bricking here, the ota install process will only stop before flashing anything since the Orange CID and .61 Firmware of the phone doesn't match the WWE CID and .401 base of the OTA
alfev said:
EDIT
Also, if I do need to S-OFF, you mention Sunshine and you mention $25, this is a 3 year old phone with a slight crack in the screen so I'm not going to throw any money at it but I found Squabbi's tool kit which uses Revone for S-OFF, would this be no good?
Click to expand...
Click to collapse
No, Revone is only for hboot 1.44 pre-June 2013 version. For hboot 1.57 and above, Sunshine is the only way.
alray said:
There is a 6.16.61.8 signed RUU available but unfortunately, its only available at ir-file.com and you need a paid account to download from that website.
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Right the update will not work but there is no chance of bricking here, the ota install process will only stop before flashing anything since the Orange CID and .61 Firmware of the phone doesn't match the WWE CID and .401 base of the OTA
No, Revone is only for hboot 1.44 pre-June 2013 version. For hboot 1.57 and above, Sunshine is the only way.
Click to expand...
Click to collapse
Ok, MaximusHD was mentioned. 50.0 looks to be the latest version and that's the version posted above but that's Lollipop, would 40.0 be the right one for me?
I might be best just leaving it as is. I've successfully upgraded it from a paperweight to a phone, if I twist I might bust and end up back with a shiny paperweight again.
alfev said:
Ok, MaximusHD was mentioned. 50.0 looks to be the latest version and that's the version posted above but that's Lollipop, would 40.0 be the right one for me?
I might be best just leaving it as is. I've successfully upgraded it from a paperweight to a phone, if I twist I might bust and end up back with a shiny paperweight again.
Click to expand...
Click to collapse
sorry my bad, I thought 50 was a KitKat rom as its sense 6, use this one instead which is a KitKat 6xxxx as close to stock rom as possible: https://www.androidfilehost.com/?w=files&flid=22071 (Maximus HD 46.0)
custom rom based on 6.09.401.11
Seanie280672 said:
sorry my bad, I thought 50 was a Ki
Code:
tKat rom as its sense 6, use this one instead which is a KitKat 6xxxx as close to stock rom as possible: [url]https://www.androidfilehost.com/?w=files&flid=22071[/url] (Maximus HD 46.0)
custom rom based on 6.09.401.11
Click to expand...
Click to collapse
Excellent, thanks, I think I'll have a pop at that then.
Related
Decided to rewrite this as the problem is different now, not as bad, but a lot weirder! I can't get my head round whats up
Description of Problem
Right, so simplistically, the phone boots up, and you can use it (sort of) for about 30 seconds, before it reboots. Whilst its on, you can open apps, but there is definite issues with menu's not opening and you cant set a wallpaper, but its almost fully working. Then without any warning it just reboots, and does the same thing again.
I'm just confused at how it can boot up and almost fully work before rebooting. Failing to boot at all or bootlooping at the start animation, I can understand that, but not this.
Video of the Problem
What Caused the Issue
Its been a week or so since it first died, so I cant fully remember exact things that happened (I appreciate this will not be helpful!)
I had converted the phone to a google edition version using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2358781
Changed the MID and CID, flashed the bootloader, recovery and RUU and the whole thing worked great.
Then I got my Xperia Z, so wanted it back to stock to be sold. Problem is I locked the bootloader and went S-ON before flashing the stock bootloader because i'm an idiot! Then obviously it wouldn't boot due to locked bootloader and custom recovery, so I tried to flash stock RUU, failed naturally due to upgraded bootloader, so I unlocked the bootloader again, flashed stock, and now this happens
Things I've Tried
Factory Reset
Flashed Stock Roms (1.28 / 2.17 / 2.24 and google edition) via both flashable zip and CWM backups - flashing in fastboot doesnt work because of signature error
Revone to re S-OFF (On HBOOT 1.54 so get a -6 error)
Maybe some other things?
Does anyone have any ideas? Any help is appreciated at the moment, don't want to wait for S-OFF on 1.54 or a 2.24 RUU as that could mean a brick on my shelf for a while.
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
redbull123 said:
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
dh2311 said:
Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't downgrade when you're s-on.
iElvis said:
You can't downgrade when you're s-on.
Click to expand...
Click to collapse
Thats what I thought, hence why I got a bit concerned earlier. Phones not fixed yet, stuck in a bootloop but my internet is slow for downloading firmwares
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
dh2311 said:
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't - I thought you were s-off since I didn't read in your post that you went back to s-on, that's what I was asking..
Sent from my HTC One using xda premium
iElvis said:
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
Click to expand...
Click to collapse
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
dh2311 said:
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
Click to expand...
Click to collapse
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
iElvis said:
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
Click to expand...
Click to collapse
Genius! Dont know how i didnt think of that. Now i have an accessible SD card, just still bootlooping, itll work with the 1.28 backup and then the RUU will correct everything I've messed up
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
dh2311 said:
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
Click to expand...
Click to collapse
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Edit: n/m, just saw you're s-on. I think the problem is that you've got an incompatible mix of firmwares from trying to convert to GE. You need to get s-off again somehow.
iElvis said:
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Click to expand...
Click to collapse
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
EDIT: same problem! :'(
dh2311 said:
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
Click to expand...
Click to collapse
Are you flashing firmware or just roms?
iElvis said:
Are you flashing firmware or just roms?
Click to expand...
Click to collapse
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
dh2311 said:
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
Click to expand...
Click to collapse
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
iElvis said:
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
Click to expand...
Click to collapse
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
dh2311 said:
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
Click to expand...
Click to collapse
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
iElvis said:
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
Click to expand...
Click to collapse
Thats the solution. Or a 2.24 RUU from HTC could also do it. But revone requires a booting phone, which mine cant do, doesnt work out of recovery unfortunately. and moonshine is only for older versions. Tempted to just put this phone on a shelf and wait for an RUU. Carry on using my Xperia Z
Dont know if this will be of any help for sorting the issue, but this is all the hboot info from getvar all
Code:
(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.17.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed for safety>
(bootloader) imei: <removed for safety>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Definitely cant seem to get this to work, upon booting i get lots of force closes like the messaging app and contacts storage. That a clue for anyone?
Or if anyone knows how to S-Off without a working F/W that would be a help but I doubt it can be done
Hey all,
I received a used T-Mobile HTC One a couple months ago (I am on T-Mobile in Miami). It came unlocked S-ON. I am a GE kind of guy and have yet to use Sense on it once. With all the firmware updates, I am wondering if it is time to upgrade the firmware as I am sure I am probably on old or original firmware. A couple of questions in particular I would like to address (and I have read on this for months but have yet to make the upgrade):
1) Pro's/Cons of T-mobile firmware vs GE firmware?
2) What is the real benefit of S-OFF exactly?
3) If I go the T-Mobile firmware upgrade with S-ON, am I going to be less likely to sell the phone on per say, SWAPPA or get less for it because I upgraded S-ON and hence have what I think is referred to as a locked H-Boot?
4) Lastly for the moment, what is the real benefit of the upgraded firwmare as I have yet to see any real change logs of any of these firmware updates?
Thank you in advance for any and all comments you have it is much appreciated!!!
Here are the details from my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
Bump
umrico said:
Bump
Click to expand...
Click to collapse
3) Don't know
1 & 4) In theory updated firmware (and/or matching firmware and ROM version), should provide better stability, performance, battery life and remove any bugs it they existed. you are still on 1.xx so for example, the update to 2.xx introduced new touchscreen drivers which made the screen more responsive.
2) you are able to flash anything you want:
with an unlocked bootloader and S-ON, you can flash ROM, kernel, recovery, even radio
with S-Off (on top of above), you can flash unsigned firmware, and you are able to downgrade, even change CID and MID to any version you like, and make your phone (for example) a US Developer edition, an unbranded International version etc.
also with S-Off, you can remove TAMPERED from bootloader, set your phone LOCKED (otherwise only RELOCKED possible), and go back to 100% "out of the box" if you wish.
T-Mobile is just a GSM variant (so no need to think of it as T-Mob) and you can use pretty much any of the ROMs out there (oh if you use WiFi calling, then you have to check if it's supported in the ROM).
Hope that helps
nkk71 said:
3) Don't know
1 & 4) In theory updated firmware (and/or matching firmware and ROM version), should provide better stability, performance, battery life and remove any bugs it they existed. you are still on 1.xx so for example, the update to 2.xx introduced new touchscreen drivers which made the screen more responsive.
2) you are able to flash anything you want:
with an unlocked bootloader and S-ON, you can flash ROM, kernel, recovery, even radio
with S-Off (on top of above), you can flash unsigned firmware, and you are able to downgrade, even change CID and MID to any version you like, and make your phone (for example) a US Developer edition, an unbranded International version etc.
also with S-Off, you can remove TAMPERED from bootloader, set your phone LOCKED (otherwise only RELOCKED possible), and go back to 100% "out of the box" if you wish.
T-Mobile is just a GSM variant (so no need to think of it as T-Mob) and you can use pretty much any of the ROMs out there (oh if you use WiFi calling, then you have to check if it's supported in the ROM).
Hope that helps
Click to expand...
Click to collapse
Thank you very much!
nkk71 said:
3) Don't know
1 & 4) In theory updated firmware (and/or matching firmware and ROM version), should provide better stability, performance, battery life and remove any bugs it they existed. you are still on 1.xx so for example, the update to 2.xx introduced new touchscreen drivers which made the screen more responsive.
2) you are able to flash anything you want:
with an unlocked bootloader and S-ON, you can flash ROM, kernel, recovery, even radio
with S-Off (on top of above), you can flash unsigned firmware, and you are able to downgrade, even change CID and MID to any version you like, and make your phone (for example) a US Developer edition, an unbranded International version etc.
also with S-Off, you can remove TAMPERED from bootloader, set your phone LOCKED (otherwise only RELOCKED possible), and go back to 100% "out of the box" if you wish.
T-Mobile is just a GSM variant (so no need to think of it as T-Mob) and you can use pretty much any of the ROMs out there (oh if you use WiFi calling, then you have to check if it's supported in the ROM).
Hope that helps
Click to expand...
Click to collapse
Thanks again. I decided to S-Off and super cid since I was at it. Upgraded firmware to 3.62.401.1. Can't say I notice the difference but I'm sure the latest and greatest from where I was and soff is a great thing. Thanks again!!!
umrico said:
Thanks again. I decided to S-Off and super cid since I was at it. Upgraded firmware to 3.62.401.1. Can't say I notice the difference but I'm sure the latest and greatest from where I was and soff is a great thing. Thanks again!!!
Click to expand...
Click to collapse
Did you go directly from 1.xx to 3.62? I would recommend flashing 2.24 first and then 3.62, because I'm not sure the 3.62 contains the updated touchscreen drivers, so if you do the 2.24 first, you'll get the updated touchscreen drivers and then go to 3.62.
EDIT: or just check the 3.62 zip, if it contains the file "tp_SYN3202.img", those were the updated drivers in 2.24
nkk71 said:
Did you go directly from 1.xx to 3.62? I would recommend flashing 2.24 first and then 3.62, because I'm not sure the 3.62 contains the updated touchscreen drivers, so if you do the 2.24 first, you'll get the updated touchscreen drivers and then go to 3.62.
EDIT: or just check the 3.62 zip, if it contains the file "tp_SYN3202.img", those were the updated drivers in 2.24
Click to expand...
Click to collapse
I did go directly to 3.62. I *briefly* read and saw a comment that I dont need intermittent firmwares but that was only one comment so I took the chance.
Unfortunately, the zip does NOT have that file...I assume I should push it then? Thank you for your help!!!!
umrico said:
I did go directly to 3.62. I *briefly* read and saw a comment that I dont need intermittent firmwares but that was only one comment so I took the chance.
Unfortunately, the zip does NOT have that file...I assume I should push it then? Thank you for your help!!!!
Click to expand...
Click to collapse
Download 2.24 from here: http://forum.xda-developers.com/showthread.php?t=2365506 and flash it in fastboot RUU mode
and then flash 3.62 again.
nkk71 said:
Download 2.24 from here: http://forum.xda-developers.com/showthread.php?t=2365506 and flash it in fastboot RUU mode
and then flash 3.62 again.
Click to expand...
Click to collapse
Thanks.
I see that Vomer has this file: - Touch panel Driver from firmware 2.24.401.1: http://d-h.st/lL4 but I cannot find anything on the web on how to install it. You have any idea by chance?
umrico said:
Thanks.
I see that Vomer has this file: - Touch panel Driver from firmware 2.24.401.1: http://d-h.st/lL4 but I cannot find anything on the web on how to install it. You have any idea by chance?
Click to expand...
Click to collapse
I would just flash the 2.24 firmware complete and then the 3.62, easiest way in my opinion, won't take more than a minute or two.
nkk71 said:
I would just flash the 2.24 firmware complete and then the 3.62, easiest way in my opinion, won't take more than a minute or two.
Click to expand...
Click to collapse
OK. I did it your way. I have had my fair share of flashing firmware hopefully for the next year as I hold my breath every time doing this with S-OFF. Thanks so much for all of your help!!!!
umrico said:
OK. I did it your way. I have had my fair share of flashing firmware hopefully for the next year as I hold my breath every time doing this with S-OFF. Thanks so much for all of your help!!!!
Click to expand...
Click to collapse
no need to hold your breath, it's quite safe flashing firmware as long as you follow instructions (eg flash zip .... twice), and anyway with S-Off even if you semi-brick, you have a very high chance of unbricking.
i like @vomer's firmware packages cause they have boot.img and recovery.img removed, so no need to reflash the ROM or custom recovery.
nkk71 said:
no need to hold your breath, it's quite safe flashing firmware as long as you follow instructions (eg flash zip .... twice), and anyway with S-Off even if you semi-brick, you have a very high chance of unbricking.
i like @vomer's firmware packages cause they have boot.img and recovery.img removed, so no need to reflash the ROM or custom recovery.
Click to expand...
Click to collapse
Agreed. Thanks again for all of your guidance!
If anyone has some time to spare, I could really use some individual guidance.
I just purchased a used HTC One, it had 4.1.2 on it and would not update so I unlocked it and rooted it.
Now though, I keep getting stuck no matter what I try...
I've been trying to get S Off, I have the 1.44 version of hboot I think it's called, and CWS_001 and PN0712000. I can't get S Off to work, even after updating to 4.2.2, now my wifi will not connect. I keep getting stuck in boot loop, or TWRP will not load. I've tripped the 'tamper' flag and would like to get rid of that.
I'm just not familiar enough with all the instructions to purposefully move from where I'm at to where I want to go. I would like to have 4.4 eventually and be unlocked and rooted with a custom ROM with no HTC overlay.
If there is any chance anyone would be willing to walk me through, I would greatly appreciate it. My S3 is working fine so I'm not desperate, but getting there quickly.
Thank you.
I've spent the last 12 hours going around in circles, my Chrome browser looks like 100 tabs are open across the top with all the pages I've been reading trying to figure this thing out. I feel like an idiot about now. Anyways, thanks to anybody for considering helping ahead of time.
bubsnews said:
If anyone has some time to spare, I could really use some individual guidance.
I just purchased a used HTC One, it had 4.1.2 on it and would not update so I unlocked it and rooted it.
Now though, I keep getting stuck no matter what I try...
I've been trying to get S Off, I have the 1.44 version of hboot I think it's called, and CWS_001 and PN0712000. I can't get S Off to work, even after updating to 4.2.2, now my wifi will not connect. I keep getting stuck in boot loop, or TWRP will not load. I've tripped the 'tamper' flag and would like to get rid of that.
I'm just not familiar enough with all the instructions to purposefully move from where I'm at to where I want to go. I would like to have 4.4 eventually and be unlocked and rooted with a custom ROM with no HTC overlay.
If there is any chance anyone would be willing to walk me through, I would greatly appreciate it. My S3 is working fine so I'm not desperate, but getting there quickly.
Thank you.
I've spent the last 12 hours going around in circles, my Chrome browser looks like 100 tabs are open across the top with all the pages I've been reading trying to figure this thing out. I feel like an idiot about now. Anyways, thanks to anybody for considering helping ahead of time.
Click to expand...
Click to collapse
You have an AT&T HTC one
it's very simple to update it to 4.3 >> Download This
all you need is this one file and read the instruction Here
clsA said:
You have an AT&T HTC one
it's very simple to update it to 4.3 >> Download This
all you need is this one file and read the instruction Here
Click to expand...
Click to collapse
Thank you! So, there is no requirement for root, locked/unlocked, previous/installed ROM etc??? Doesn't care what build of my HTC ONE or anything?
Sounds too good to be true.
Will I still be rooted and unlocked afterwards?
Is this a stock ROM?
Downloading now, thanks for the help.
bubsnews said:
Thank you! So, there is no requirement for root, locked/unlocked, previous/installed ROM etc??? Doesn't care what build of my HTC ONE or anything?
Sounds too good to be true.
Will I still be rooted and unlocked afterwards?
Is this a stock ROM?
Downloading now, thanks for the help.
Click to expand...
Click to collapse
It's not a Rom it's a RUU
It's full factory reset it wipes everything and updates the firmware
sent from my recliner
clsA said:
It's not a Rom it's a RUU
It's full factory reset it wipes everything and updates the firmware
sent from my recliner
Click to expand...
Click to collapse
"Sent from my recliner" Well played Sir...
I see by your signature, you are exactly where I want to be. I too have the CSW_001 version. I was up until 2 this morning messing with it so I'm 'off' for the night but will be up bright and early following your suggestion, thank you for that.
Might I still find you in your recliner should I happen to falter? I'm hoping that after this works, I can put my One in the same condition as yours, S Off etc...
Any further pointers on that score? You know exactly the state my One will be in after I get done with your previous advice.
Thanks again, I really appreciate your assistance.
Yeah I'll be here
sent from my recliner
clsA said:
Yeah I'll be here
Click to expand...
Click to collapse
Because ViperOne 5.0 is so new it's going to take a couple of steps for you to get to where I am.
I'm going to use @nkk71 SuperGuide from here http://forum.xda-developers.com/showthread.php?t=2541082.
Lets see If I can get this in the right order
First lets get all the files together before you start
Download
the RUU.exe
TWRP 2.6.3.3 >> http://techerrata.com/browse/twrp2/m7
Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
Get Both rumrunner and firewater to get S-Off: http://firewater-soff.com/ and http://rumrunner.us/
I Recommend having ARHD 31.6 for Getting s-off >> http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/Android_Revolution_HD-One_31.6.zip
and finally download your ViperOne 5.0 Rom
I'm going to alter the steps somewhat from the above guide because of what you have already done to the phone.
as I understand it your already on 4.2.2 from 4.1.2 is this correct?
here's the steps using the above files
Run the 3.17.502.3 RUU for AT&T (don't bother setting up the phone much your going to loose everything in the next step)
Unlock the bootloader again @ HTCDEV.com
Reboot to bootloader (fastboot USB)- Flash the 2.6.3.3 TWRP Recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Boot into Recovery and flash ARHD 31.6 (again use minimal setup your not going to be here long)
Get S-off (rumrunner should work fine / or just go with firewater your choice)
next is the Guru reset to remove the Tampered flag ... don't lock the bootloader.
and last step is flash ViperOne 5.0 and Enjoy your new phone
Note: I typed most of this from memory and if I missed any important steps Please feel free to correct me @nkk71 :good:
clsA said:
Note: I typed most of this from memory and if I missed any important steps Please feel free to correct me @nkk71 :good:
Click to expand...
Click to collapse
Sounds good to me :good: :good: :laugh:
(there's also a ruu.zip just in case)
Good luck OP :fingers-crossed:
clsA said:
Because ViperOne 5.0 is so new it's going to take a couple of steps for you to get to where I am.
I'm going to use @nkk71 SuperGuide from here http://forum.xda-developers.com/showthread.php?t=2541082.
Lets see If I can get this in the right order
First lets get all the files together before you start
Download
the RUU.exe
TWRP 2.6.3.3 >> http://techerrata.com/browse/twrp2/m7
Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
Get Both rumrunner and firewater to get S-Off: http://firewater-soff.com/ and http://rumrunner.us/
I Recommend having ARHD 31.6 for Getting s-off >> http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/Android_Revolution_HD-One_31.6.zip
and finally download your ViperOne 5.0 Rom
I'm going to alter the steps somewhat from the above guide because of what you have already done to the phone.
as I understand it your already on 4.2.2 from 4.1.2 is this correct?
here's the steps using the above files
Run the 3.17.502.3 RUU for AT&T (don't bother setting up the phone much your going to loose everything in the next step)
Unlock the bootloader again @ HTCDEV.com
Reboot to bootloader (fastboot USB)- Flash the 2.6.3.3 TWRP Recovery
Boot into Recovery and flash ARHD 31.6 (again use minimal setup your not going to be here long)
Get S-off (rumrunner should work fine / or just go with firewater your choice)
next is the Guru reset to remove the Tampered flag ... don't lock the bootloader.
and last step is flash ViperOne 5.0 and Enjoy your new phone
Note: I typed most of this from memory and if I missed any important steps Please feel free to correct me @nkk71 :good:
Click to expand...
Click to collapse
Wow, this is great! Just what I need, step by step by step. Like when the golfer hits something up there a couple of inches and the announcer proclaims, "Even I could make that putt." Thank you.
Now, I'm going to give you an opportunity to look your instructions over again while I'm downloading the V1 5.0 ROM (or, another RUU?) (What's the difference btw?) and the ARHD 31.6 file (I'm on lowly 12mb connection so going to take me 40 minutes) before I get started. I already had the other files.
I'm following your instructions blindly so if you've missed something, I'm hosed (I don't want to be hosed, tyvm).
Is that enough?
bubsnews said:
Wow, this is great! Just what I need, step by step by step. Like when the golfer hits something up there a couple of inches and the announcer proclaims, "Even I could make that putt." Thank you.
Now, I'm going to give you an opportunity to look your instructions over again while I'm downloading the V1 5.0 ROM (or, another RUU?) (What's the difference btw?) and the ARHD 31.6 file (I'm on lowly 12mb connection so going to take me 40 minutes) before I get started. I already had the other files.
I'm following your instructions blindly so if you've missed something, I'm hosed (I don't want to be hosed, tyvm).
Here are the particulars, phone state as of right now...
4.2.2
HTC Sense 5.0
CID CWS_001
MID PN0712000
Software MaximusHD 11.0.0
HTK SDK API 5.34
Kernel
3.4.10-g28df0d6
[email protected] #1
SMP PREEMPT
Baseband 4A.17.3250.20_10.441150.04L
Build 2.24.401.8 CL235216 release-keys
Browser WebKit/534.30
Is that enough?
Click to expand...
Click to collapse
Yeah the instruction are fine
run the RUU and get your bootloader unlocked and twrp installed while your downloading ARHD and viperOne
clsA said:
Yeah the instruction are fine
run the RUU and get your bootloader unlocked and twrp installed while your downloading ARHD and viperOne
Click to expand...
Click to collapse
Snag #1, ERROR [155]: UNKNOWN ERROR
Please get the correct TOM Update Utility and try again.
bubsnews said:
Snag #1, ERROR [155]: UNKNOWN ERROR
Please get the correct TOM Update Utility and try again.
Click to expand...
Click to collapse
post your results for fastboot getvar all ( - SerialNo and IEMI )
clsA said:
post your results for fastboot getvar all ( - SerialNo and IEMI )
Click to expand...
Click to collapse
Well, not sure what to do though, the error claims my phone should be in one of two states, either rebooted (no) or black screen with HTC logo and 4 exclamation marks in the corners of the screen (no either). I have the HTC logo but no exclamation points.
The options given by the program are EXIT if phone has rebooted or NEXT to start recovery process.
Not sure which I should choose...
bubsnews said:
Well, not sure what to do though, the error claims my phone should be in one of two states, either rebooted (no) or black screen with HTC logo and 4 exclamation marks in the corners of the screen (no either). I have the HTC logo but no exclamation points.
The options given by the program are EXIT if phone has rebooted or NEXT to start recovery process.
Not sure which I should choose...
Click to expand...
Click to collapse
Error 155 usually means your using the wrong RUU
which means you phone is not CID CWS_001
MID PN0712000. not sure how you got that info
Just exit the update utility
then post your "fastboot getvar all" ( excluding SerialNo and IEMI )
clsA said:
Error 155 usually means your using the wrong RUU
which means you phone is not CID CWS_001
MID PN0712000. not sure how you got that info
Click to expand...
Click to collapse
I can't remember exactly but I did run something and that was returned, I wrote it down.
I use Chrome (I've heard others having problems with Chrome and large file downloads) so I'm downloading that RUU again using IE.
I'm going to hit NEXT to start recovery process.
Will getvar once done, if I can...
I'm positive about the CWS_001 etc...
bubsnews said:
I can't remember exactly but I did run something and that was returned, I wrote it down.
I use Chrome (I've heard others having problems with Chrome and large file downloads) so I'm downloading that RUU again using IE.
I'm going to hit NEXT to start recovery process.
Will getvar once done, if I can...
I'm positive about the CWS_001 etc...
Click to expand...
Click to collapse
Stop !!
if your going to download again we need to change the file
post your getvar so we can continue
bubsnews said:
I can't remember exactly but I did run something and that was returned, I wrote it down.
I use Chrome (I've heard others having problems with Chrome and large file downloads) so I'm downloading that RUU again using IE.
I'm going to hit NEXT to start recovery process.
Will getvar once done, if I can...
I'm positive about the CWS_001 etc...
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.20
version-cpld: None
version-microp: None
version-main: 1.26.502.15
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4311mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
bubsnews said:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.20
version-cpld: None
version-microp: None
version-main: 1.26.502.15
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4311mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
Click to expand...
Click to collapse
ok 2 things did you MD5 check the the RUU.exe ?
and did you hard reboot the phone after the RUU failed
it looks like it's still in RUU mode (last line in your getvar)
clsA said:
ok 2 things did you MD5 check the the RUU.exe ?
and did you hard reboot the phone after the RUU failed
it looks like it's still in RUU mode (last line in your getvar)
Click to expand...
Click to collapse
I did not check MD5 (I know I've done that before but not very familiar, instructions?) (I am downloading that file again with IE, almost done).
I did not reboot the phone, only exited the program as instructed and ran getvar.
I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot 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: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(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.035s
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646
twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old
BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.
twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.
BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.
bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.
BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6
BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?
BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery
Hi Guys,
Bought an m7 cheap on ebay. I don't know anything about the history, except to say it's been fiddled with...
It powers up but it won't boot up; it hangs on the HTC logo.
Bootloader's unlocked, it's been rooted... S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ** edited out **
(bootloader) imei: ** edited out **
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm thinking I should try and take it back to stock, but I don't know where I should go from here and I'm worried I might screw it up.
Any help would be greatly appreciated
Thanks in advance!
Go to RUU mode and flash an RUU. There's a lot of threads explaining how to go to back to stock on this forum. If it still doesn't work, it might be an internal issue like the motherboard.
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Thanks
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
mdb said:
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Click to expand...
Click to collapse
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
mdb said:
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
Click to expand...
Click to collapse
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
alray said:
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
Click to expand...
Click to collapse
Thanks so much for this... I've been learning more all day (traditionally an iOS guy)...
Am I right in thinking I would need to sideload a custom rom through twrp and then install it? If so, I'm having an issue getting my laptop to talk to the phone - "adb devices" is pretty flakey to say the least, sometimes it works sometimes it doesn't... I've read various things about Windows 8 and that adb works best on Windows 7, can you please confirm I'm on the right track here. I'd like to put the Viper rom on it.
Thanks again
In order to flash custom recovery you need to be booted to bootloader menu, and use fastboot commands. If you flash TWRP 2.8.6.0 or later, there's no need to sideload a ROM because newer TWRP recoveries have MTP option, so you use that. Try to go to bootloader, connect your phone to your laptop or PC, and issue a command fastboot devices. If it shows your phone, you're good to go
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
mdb said:
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
Click to expand...
Click to collapse
flash the 7.19.401.2 firmware and then the 7.19.401.2 RUU. If you still have imei problem after that, its most likely an hardware defect.
relock your bootloader if not already locked or re-locked:
Code:
fastboot oem lock
Code:
fastboot orm rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastbppt flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot
*** use htc_fastboot.exe for flashing the ruu (linked below). Save all files in the same folder where you already have fastboot.exe and adb.exe on your computer.
M7_UL_Firmware_7.19.401.2.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot.exe
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
To flash a ruu on a s-on phone there are many prerequisites:
The RUU must match your MID: 7.19.401.2 is for PN0710000
The RUU must match your CID: You have superCID so its not a problem.
The RUU must be the same version or an upgrade from your actual version, we don't know your actual version because of your blank versio-main but you have 1.57 hboot which suggest a 6.xx.xxx.x version. So 7.19.401.2 should be an upgrade.
The bootloader must be locked or re-locked.
There is no risk trying it, the worst that can happen is that the phone won't accept the ruu and nothing will be flashed.
mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
Super CID + your MID. WWE firmware should work just fine. Right @alray?
donkeykong1 said:
Super CID + your MID. WWE firmware should work just fine. Right @alray?
Click to expand...
Click to collapse
:good:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
mdb said:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
Click to expand...
Click to collapse
Try to bend your sim tray just a little bit. Maybe your sim card is not reaching the contacts inside the phone. Or put a piece of paper under the sim and see what happens
Thanks donkeykong1, I've tried but it's not working... The fact the IMEI / IMEI SV and baseband are unknown though... they're not sim related...
It does show the baseband and IMEI in fastboot getvar all though?...
There were a lot of people with that same issue, and their phones worked fine, so I doubt it has anything to do with your sim. Your sim works in another phone?
Yeah, the sim's fine. @alray said it's likely a hardware issue if the firmware / rom didn't repair the IMEI issue, and the other threads I've looked at with the same issue are all saying the motherboard's faulty.
Although I am baffled as to why it is showing the IMEI / baseband in the bootloader, in fastboot etc. but not once the phone has booted up?...
I read on another thread (http://forum.xda-developers.com/showthread.php?t=2253514) that maybe flashing a kernal and/or radio might solve it?
Just wondering whether I should try flashing an official HTC rom? I've been in touch with the guy I got it off and he said it was originally on Orange, UK:
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 6
One M7 / Orange / UK / CRC / 3.4.10 / v5.0.2 / 539.0 MB / 7.19.61.10
Was also thinking of...
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 1
One M7 / HTC / EU / MR 3 / 3.4.10 / v5.0.2 / 486.0 MB / 7.19.401.22
If I did that would I need to update the firmware first like you advised originally @alray?
If I know I can revive the IMEI etc. I'll be happy to go ahead and pay to S-OFF
Thanks in advance
You need a kernel to match your firmware. If you're on 7.19.401.2, then you need 7.19.401.2 kernel. I can give you boot.img, but I don't have the whole zip, with modules. Then again, if your phone boots fine, maybe boot.img will help. I'd [email protected] to confirm my thoughts though. He's much more into this than I am