I have literally spent more than 24 hours traversing the depths of internet hell looking for a fix for my phone. So what happened was I was flashing a rom and when it asked what carrier I was on I foolishly picked sprint. After that it has been a hell of bootloops. I couldn't even get into recovery. It showed me the TWRP screen startup for half a second and then proceeded to bootloop. Eventually I got a version of clockwork mod to work ( I used a ton of cmd commands to get to this point) but I am still without real progress.I was able to sideload viper but in the middle of installation it stopped and bootlooped again. At least I have a recovery now. I would be really, really grateful for any help.
The rom I messed up with was insert coin btw
i picked sprint foolishly because the rom I flashed before that somehow erased my phone radio. I wish I knew better. Figured I'll just use twrp to fix whatever happens. That didnt go too well.
Can anyone tell me where to go from here? Also depending on what I do the recovery bootloops as well
Ultimakaiser said:
I have literally spent more than 24 hours traversing the depths of internet hell looking for a fix for my phone. So what happened was I was flashing a rom and when it asked what carrier I was on I foolishly picked sprint. After that it has been a hell of bootloops. I couldn't even get into recovery. It showed me the TWRP screen startup for half a second and then proceeded to bootloop. Eventually I got a version of clockwork mod to work ( I used a ton of cmd commands to get to this point) but I am still without real progress.I was able to sideload viper but in the middle of installation it stopped and bootlooped again. At least I have a recovery now. I would be really, really grateful for any help.
The rom I messed up with was insert coin btw
i picked sprint foolishly because the rom I flashed before that somehow erased my phone radio. I wish I knew better. Figured I'll just use twrp to fix whatever happens. That didnt go too well.
Can anyone tell me where to go from here? Also depending on what I do the recovery bootloops as well
Click to expand...
Click to collapse
If you have a GSM phone and you flashed a Sprint or Verizon ROM/Radio that is the reason for bootloops. You will need to run a RUU or nandroid to reset your phone. Please post a fastboot getvar all removing the imei and serialno.
majmoz said:
If you have a GSM phone and you flashed a Sprint or Verizon ROM/Radio that is the reason for bootloops. You will need to run a RUU or nandroid to reset your phone. Please post a fastboot getvar all removing the imei and serialno.
Click to expand...
Click to collapse
thanks for the reply. this is the info you requested
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.22.599.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0b0efc32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.154s
Ultimakaiser said:
thanks for the reply. this is the info you requested
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.22.599.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0b0efc32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.154s
Click to expand...
Click to collapse
I could not find a RUU or nandroid for your phone. If you made a nandroid prior to trying insert coin or the previous custom rom now would be the time to use it. I also could not find a firmware.zip for your phone. One other thought, you might try to flash insert coin but select a GSM phone like T-Mobile, International or AT&T. It might put things back into the correct order.
This is a long shot, but if you could get S-OFF via firewater then you could flash a different RUU by changing your CID & MID.
majmoz said:
I could not find a RUU or nandroid for your phone. If you made a nandroid prior to trying insert coin or the previous custom rom now would be the time to use it. I also could not find a firmware.zip for your phone. One other thought, you might try to flash insert coin but select a GSM phone like T-Mobile, International or AT&T. It might put things back into the correct order.
This is a long shot, but if you could get S-OFF via firewater then you could flash a different RUU by changing your CID & MID.
Click to expand...
Click to collapse
Is it possible to flash a twrp backup from my laptop to my device? I was able to wipe the device which stopped the bootloops. I can also flash any other recovery and have them work properly now. But where do I go from here? I can't. get firewater because apparently you need a working internet connection on the device itself.:crying:
Yes. You can adb push your twrp nandroid backup to the phone. You just need to figure out the exact path
Ultimakaiser said:
Is it possible to flash a twrp backup from my laptop to my device? I was able to wipe the device which stopped the bootloops. I can also flash any other recovery and have them work properly now. But where do I go from here? I can't. get firewater because apparently you need a working internet connection on the device itself.:crying:
Click to expand...
Click to collapse
Here is the method to sideload backup to your phone from the computer.
majmoz said:
Here is the method to sideload backup to your phone from the computer.
Click to expand...
Click to collapse
Ok so after alot of trial and error and whatnot my phone is back and running great. I was able to flash an old twrp to my device so I would have an os again. Then I flashed android revolution which has been working well since wednesday morning. What a journey. I'm inspired to help others here now. Gonna lurk and see if what I learnt can help anyone. There is no RUU for my version btw. Lucky I had that recovery lying around.:victory:
Thanks for all the help guys
Related
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Use otg cable +USB mouse to control the phone
sent from my mobile device
update
I have my otg cable and im able to use the usb mouse with it but I am unable to check for the at&t software update... i click on it and it puls up for a second and then goes away... any ideas?
Idea
I read somewhere that I can flash firmware with s-on as long as i re-lock the bootloader and the mid and cid match on the firmware that i flash to it... this would be done in the ruu flash boot? does that sound right and would this allow me to either get the ota update or flash the correct ruu OR would it possible get my adb functionality back to my bootloader so i can s-off and flash a stock ruu?
medicsizzle said:
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Click to expand...
Click to collapse
You need to flash your touch drivers.
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
SaHiLzZ said:
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I can try but I am stuck in S-on would this be an issue? and I can flash from cwm and twrp would a stock nandroid help?
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
SaHiLzZ said:
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
Click to expand...
Click to collapse
You are the BEST! Thank you so much.. I have been racking my head trying to get this fixed... I am up and running again! My process
1. I had my phone unlocked bootloader, s-on, and twrp recovery
2. booted into trwp, and adb pushed the Guru stock installer
3. installed the zip, selecting to wipe data, no super user, and then I put the stock recovery and radios on
4. rebooted into bootloader and locked my bootloader
5. rebooted phone
6. ran the RUU that you provided me. (Thanks again)
7. phone booted up 100% working!!!!
8. Gave credit where credit was due!
I've got a HTC One with Wind Mobile in Canada, and I've got Cyanogenmod installed on it.
Today, I got an unlock code from Wind so I can move my phone to Telus. Everything seemed fine, until I got a Telus sim card (and had my number transferred), installed it, and tried inputting the unlock code. It told me that the code was rejected.
Through my limited research abilities, I figured out that SIM unlock doesn't seem to work from non-Sense based roms. But there's also no RUU that I could find for my phone (at least, not for Wind).
So, what I'd like to do is install some sort of Sense rom, so I can go in, unlock the phone, and then reinstall the same rom I currently have (I've created an update.zip with Titanium Backup that will bring my phone back to Cyanogenmod as I have it set up right now).
The only missing piece is how I can get back to some sort of stock/sense rom. Can anyone advise me what to do? I've seen a few links to nandroid restores (of some sort... I'm not completely up to date on how that works), but the links I've tried are dead.
Thanks in advance!
simon.andrews said:
I've got a HTC One with Wind Mobile in Canada, and I've got Cyanogenmod installed on it.
Today, I got an unlock code from Wind so I can move my phone to Telus. Everything seemed fine, until I got a Telus sim card (and had my number transferred), installed it, and tried inputting the unlock code. It told me that the code was rejected.
Through my limited research abilities, I figured out that SIM unlock doesn't seem to work from non-Sense based roms. But there's also no RUU that I could find for my phone (at least, not for Wind).
So, what I'd like to do is install some sort of Sense rom, so I can go in, unlock the phone, and then reinstall the same rom I currently have (I've created an update.zip with Titanium Backup that will bring my phone back to Cyanogenmod as I have it set up right now).
The only missing piece is how I can get back to some sort of stock/sense rom. Can anyone advise me what to do? I've seen a few links to nandroid restores (of some sort... I'm not completely up to date on how that works), but the links I've tried are dead.
Thanks in advance!
Click to expand...
Click to collapse
You'll need to post the output of ''fastboot getvar all'' (minus IMEI and SERIALNO) before. Not sure if a ''close to stock'' rom will do, maybe you'll need to be completely stock. I don't remember excatly, I think @nkk71 already posted the prerequisites to sim-unlock, maybe a month ago in another thread, can't find it.
alray said:
You'll need to post the output of ''fastboot getvar all'' (minus IMEI and SERIALNO) before. Not sure if a ''close to stock'' rom will do, maybe you'll need to be completely stock. I don't remember excatly, I think @nkk71 already posted the prerequisites to sim-unlock, maybe a month ago in another thread, can't find it.
Click to expand...
Click to collapse
Here's what I've got:
Code:
C:\<clipped>\platform-tools>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.1500.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <clipped>
(bootloader) imei: <clipped>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GLOBA001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s
simon.andrews said:
Here's what I've got:
Code:
C:\<clipped>\platform-tools>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.1500.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <clipped>
(bootloader) imei: <clipped>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GLOBA001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s
Click to expand...
Click to collapse
AFAIK there is no ruu for .1500 sw version (WIND) neither CWM or TWRP nandroid backup or guru reset rom. Have you made any nandroid backup of your phone before flashing Cyanogen? If yes restore it and try the unlock code again. If you don't have a backup then maybe you coul try a sense based rom like arhd
Ok I have found the post of nkk71 regarding sim-unlock prerequisites:
nkk71 said:
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.
Click to expand...
Click to collapse
alray said:
AFAIK there is no ruu for .1500 sw version (WIND) neither CWM or TWRP nandroid backup or guru reset rom. Have you made any nandroid backup of your phone before flashing Cyanogen? If yes restore it and try the unlock code again. If you don't have a backup then maybe you coul try a sense based rom like arhd
Ok I have found the post of nkk71 regarding sim-unlock prerequisites:
Click to expand...
Click to collapse
Thanks!
I solved it by installing arhd, like you suggested. Booted it up, got prompted for the unlock code, entered it, then rebooted into recovery to reinstall CM. Worked perfectly.
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
(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: FA34KS903491
(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: 4331mV
(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
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
joshmccormick20 said:
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
Click to expand...
Click to collapse
This will get you fixed up try the latest RUU first if it fails go the long route
Any questions post them here
BD619 said:
This will get you fixed up try the latest RUU first if it fails go the long route
Any questions post them here
Click to expand...
Click to collapse
Thank you, i'll give it a shot
joshmccormick20 said:
Thank you, i'll give it a shot
Click to expand...
Click to collapse
Good luck...I'll be around if you have questions.
BD619 said:
Good luck...I'll be around if you have questions.
Click to expand...
Click to collapse
Ok, i downloaded the RUU and it went about half way through then i got ERROR 155 and it says i need to get the correct version of RUU....:crying:
joshmccormick20 said:
Ok, i downloaded the RUU and it went about half way through then i got ERROR 155 and it says i need to get the correct version of RUU....:crying:
Click to expand...
Click to collapse
4.06.651.2? If so you could try some things like different USB Port(USB 2 work best),different cable,different PC...but you may have already updated beyond that meaning you will have to go the long route
BD619 said:
4.06.651.2? If so you could try some things like different USB Port(USB 2 work best),different cable,different PC...but you may have already updated beyond that meaning you will have to go the long route
Click to expand...
Click to collapse
What do you consider the "long route"?
joshmccormick20 said:
What do you consider the "long route"?
Click to expand...
Click to collapse
Follow the steps in the guide
Do it yourself rather then the RUU doing it...same outcome other then you will have a stock rooted rom rather then a factory rom.
BD619 said:
Follow the steps in the guide
Do it yourself rather then the RUU doing it...same outcome other then you will have a stock rooted rom rather then a factory rom.
Click to expand...
Click to collapse
I was afraid you'd say that. Here's my other problem. I can only get ADB to work using Philz touch recovery. And when i try to push the Zip file or anything like that i get some kind of error which doesnt let it complete. I'm sure you've been through this with other people hundreds of times so forgive me. I get a "failed to write data protocol <no status>"
joshmccormick20 said:
I was afraid you'd say that. Here's my other problem. I can only get ADB to work using Philz touch recovery. And when i try to push the Zip file or anything like that i get some kind of error which doesnt let it complete. I'm sure you've been through this with other people hundreds of times so forgive me. I get a "failed to write data protocol <no status>"
Click to expand...
Click to collapse
Did you re-lock your bootloader?
BD619 said:
Did you re-lock your bootloader?
Click to expand...
Click to collapse
I relocked it and then unlocked it again, tried both ways...i'm about to throw it away.
joshmccormick20 said:
I relocked it and then unlocked it again, tried both ways...i'm about to throw it away.
Click to expand...
Click to collapse
Since you are s-on it needs to be locked/re-locked for the ruu or to flash the firmware.
Add me on hangouts the email addy is in my rescue thread.
BD619 said:
Since you are s-on it needs to be locked/re-locked for the ruu or to flash the firmware.
Add me on hangouts the email addy is in my rescue thread.
Click to expand...
Click to collapse
I'm not sure about the hangouts thing, but I did just relock the bootloader again and ran the RUU you told me to and it got almost all of the way done and i got ERROR 152 image update error
joshmccormick20 said:
I'm not sure about the hangouts thing, but I did just relock the bootloader again and ran the RUU you told me to and it got almost all of the way done and i got ERROR 152 image update error
Click to expand...
Click to collapse
You can add a hangout extension to your chrome browser or use google+
https://chrome.google.com/webstore/search/hangout extension?utm_source=chrome-ntp-icon
BD619 said:
You can add a hangout extension to your chrome browser or use google+
https://chrome.google.com/webstore/search/hangout extension?utm_source=chrome-ntp-icon
Click to expand...
Click to collapse
[email protected] i downloaded it
joshmccormick20 said:
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
(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: FA34KS903491
(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: 4331mV
(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
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
Click to expand...
Click to collapse
My wife got some kind of corrupt file or virus on her phone and I ended up having to wipe EVERYTHING, OS, SDCARD, only thing on phone was bootloader and old version of TWRP, heres how I fixed it and it worked great.... Download the latest TWRP and flash it via fastboot, make sure you have the latest SDK tools on your computer, sideload the rom of your choice, there are instructions on the TWRP website, you should be good to go....
Hi
I have received a Htc One M7 , but I do not know how to find the compatible firmware/rom for it as it has already been flashed. It is now identified as M7wls (so it could be the Sprint variant) and runs a soulteam rom , which after reading some threads is a Chinese team. The main reason for changing is the poor battery life and the Chinese characters that appear in some system application. I could not find any modeln running a similar firmware/rom and I would like to avoid bricking it.
The backcase has the model no. PN07140. The fastboot screen says
***UNLOCKED***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.57.0000
RADIO-2.03.30.0109
OpenDSP-v26.120.274.0202
OS-5.11.661.8
Software info:
Android version 4.4.2
HTC Sense version 6.0
Software number 5.11.661.8
....
Kernel 3.4.19-xiaoxiang8002-soul1.0
[email protected]#2
SMP PREEMPT
Baseband
2.03.30.0109 (4SNN5GO)
Build number
5.11.661.8 CL334166 release-key
Thanks
i.imgur.com/4MBWZxr.png
i.imgur.com/vffkT1R.png
i.imgur.com/2ELm7QW.jpg
I'm not an expert at this sort of thing, but it looks like someone took a Sprint m7 and ran SuperCID on it so they could install any ROM (judging by CID-11111111). My guess is that you can change the CID back to Sprint's (maybe you don't have to) and run the Sprint RUU to reset it. But, like I said, I'm not an expert in SuperCID stuff. Maybe someone else with more experience can chime in ( @Sloth : Heeey yooou guyyyzz).
coal686 said:
I'm not an expert at this sort of thing, but it looks like someone took a Sprint m7 and ran SuperCID on it so they could install any ROM (judging by CID-11111111). My guess is that you can change the CID back to Sprint's (maybe you don't have to) and run the Sprint RUU to reset it. But, like I said, I'm not an expert in SuperCID stuff. Maybe someone else with more experience can chime in ( @Sloth : Heeey yooou guyyyzz).
Click to expand...
Click to collapse
Thanks for the reply. Would this mean that I can flash directly the latest Venom rom? Or as I am on KitKat only the rom based on kitkat?
Can you open a cmd window and type
fastboot getvar all
Do this while booted to fastbootusb
Hi, I have the same issue as paul_ro21, but I have flashed new firmware and am now stuck in bootloop. I have also managed to unlock the device.
Getvar all info below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3791mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help greatly appreciated - I have tried Sprint RUU updates without success and don't seem to be able to change the CID on the phone.
My guess is you flashed the firmware for another M7 variant...I say this because I don't recognize the baseband.
Sloth said:
My guess is you flashed the firmware for another M7 variant...I say this because I don't recognize the baseband.
Click to expand...
Click to collapse
Hi Sloth,
THANK GOD I CAME ACROSS THIS!!
So im in exactly the same boat as these guys, but i have flashed full firmware from below, and im stuck in bootloop:
http://forum.xda-developers.com/showthread.php?t=2795856
I did that coz Santod's Nusense7 which i wanted to flash required latest radios, hboot, firmware, as it said:
http://forum.xda-developers.com/spr...t/rom-nusenseven-sense-7-0-v1-00-973-t3056647
I tried flashing the rom anyway but still stuck in bootloop (actually it boots straight into recovery now (twrp 2.7.1.2).
I know ive done something bad, dont know how bad but obviously the phone isnt bricked (thank God)! i need a way to bring my phone back to life even if it means having to live with the Chinese stuff on the phone as it came.
PLEASE SOMEBODY HELP OUT!! ANYONE??!
If its useful info, i also made a full twrp backup before this but saved it on my pc and not in my phone, i wondered if i could restore with fastboot at all and how..??
Oh, just in case... this is what fastboot getvar returns on my phone
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4064mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
@Mr HaRR
Running the 6.23.651.6 RUU should get you fixed up.
Also if I remember correctly you have to flash the boot.img when flashing Nusense7.
Thanks sloth, im gonna give that a try and revert!
aaaaaaaaaaaaahhhhhhhhhhhh!!!!!!!!! thats me shouting for joy! so it worked and my phone is up and booting! sweet!
i hate to be a pain but i dont wanna ruin anything so im gonna ask a few more questions.. WHAT DO I NEEED TO DO to flash another rom? i thought id just flash twrp via fastboot and flash maybe nusense 7... BUT! i get the "failed <remote: nt allowed>" error. obviously i cant log in to google play to download twrp its all back to the horizon setup etc.. so i pretty much still cant use the phone! im in africa, i need to install a rom that can work internationally!
PLEASE PLEASE PLEASE HELP! i assume status of newbie coz its been years since i had to do anything like this....
Mr HaRR said:
aaaaaaaaaaaaahhhhhhhhhhhh!!!!!!!!! thats me shouting for joy! so it worked and my phone is up and booting! sweet!
i hate to be a pain but i dont wanna ruin anything so im gonna ask a few more questions.. WHAT DO I NEEED TO DO to flash another rom? i thought id just flash twrp via fastboot and flash maybe nusense 7... BUT! i get the "failed <remote: nt allowed>" error. obviously i cant log in to google play to download twrp its all back to the horizon setup etc.. so i pretty much still cant use the phone! im in africa, i need to install a rom that can work internationally!
PLEASE PLEASE PLEASE HELP! i assume status of newbie coz its been years since i had to do anything like this....
Click to expand...
Click to collapse
I'm guessing you are getting the "remote not allowed" error while flashing twrp? If so is the bootloader unlocked? Did you put the twrp.img in the correct folder?
Sloth said:
I'm guessing you are getting the "remote not allowed" error while flashing twrp? If so is the bootloader unlocked? Did you put the twrp.img in the correct folder?
Click to expand...
Click to collapse
Yes, i get the error when attempting to flash twrp. the boot loader is unlocked (or at least it still says it is). Still S-OFF. twrp.img in the correct folder (where i flashed it, and other things from previously).
I just read somewhere that this error could be due to "having stock boot/hboot".. not sure how true or what can be done about it if true...
or perhaps would installing on of the RUUs below (you pointed to in the Q&A section) help at least enable me use the phone on networks here, download twrp and try flashing a more recent rom?
http://forum.xda-developers.com/showthread.php?t=2469782
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
kayohbe said:
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
Click to expand...
Click to collapse
Please, post the output of "fastboot getvar all" (don't post your imei and serialno).
Sent from my HTC One using XDA Labs
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
I recognize this is my own mistake as a result of being short sighted and not careful enough with my actions. Also, i'm willing to take any amount of time necessary to learn whatever skills may be required to resolve this issue (how to utilize certain tools properly, specific programming languages etc.)
kayohbe said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Click to expand...
Click to collapse
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
alray said:
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
Click to expand...
Click to collapse
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
kayohbe said:
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
Click to expand...
Click to collapse
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
alray said:
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
kayohbe said:
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
Click to expand...
Click to collapse
No its to late, try the RUU.
Seems good [:=
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
kayohbe said:
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
Click to expand...
Click to collapse
no problem. Update your phone to the latest version before unlocking and rooting. The latest one is .52
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
kayohbe said:
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
Click to expand...
Click to collapse
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
alray said:
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
Click to expand...
Click to collapse
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
kayohbe said:
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
Click to expand...
Click to collapse
I played the game for 2-3 days at launch and it was easy to spoof a fake gps location to cheat. To do that I also had to hide the fact the I was using "mock location" from the developer options using an Xposed module or the game would detect it. I guess its also really easy to hide the fact the you are using a custom rom/root from pokémon go using the same method... Not tried but im sure it can be done.
I assume it was easy prior to the current update - they've cracked down on 'spoof players' about a week or so ago
Help for HTC - M7
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(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: 3952mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
1191 said:
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(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: 3952mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
Click to expand...
Click to collapse
Yes you've download the right file.
Instructions how to flash: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(see post #1)