Hi,
I have a Sprint HTC One M7 running stock rom and S-Off(bought it new, thats what i thought then, it is S-off so refurbished maybe). I wanted to upgrade it to sense 6 rom. I did the following procedure:
1. Unlocked bootloader through HTCDev – Success,
2. Based on my readings, flashed recoveries (twrp, philz, cwm) through fastboot – The phone hangs at entering recovery. Hence unable to root.
3. Wasn’t able to get adb working with the rom on. Was always showing HTC one in device manager .Tried various drivers but didn’t work.
Despite this, was able to boot into rom and use as normal. So tried doing the same procedure yesterday. Viola, the Rom is not booting anymore. It stays stuck at the splash screen. I have not wiped anything other than cache so I am sure the rom is still there. I have tried the following steps,
1. Tried installing stock recovery to factory reset – Get a red triangle with ! mark above a phone symbol and stays there. Goes no further.
2. Tried several other recoveries(sprint ones) – When I check adb devices, it detects the phone and says it’s in recovery. Nothing on the phone.
3. Tried going back to stock by flashing RUU(after relocking bootloader) – Error 120 battery below 30% is the message I get. I am sure the battery is above 90% and I it is charging. While charging I noticed the LED at the top changed from Red to Green which I assume means battery is above 90%.
Right now the only thing I am able to access is fastboot. I think when I reboot, it is trying to boot into recovery by default even without me selecting recovery. It is showing recovery after every boot in adb but nothing on the phone. I don’t know where I went wrong in all this.
Can anybody suggest what I can do to bring my HTC back to life. Don’t need sense 6 after all these hassles, just want it working.
Getvar posted below.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.04.651.2
(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: 4257mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
OK. Looks like i did this "fastboot flash boot recovery.img". I know its a stupid mistake but need help recovering. Will i be able to boot into the rom if i flash kernel? If yes, can anybody link me to kernel for 3.04.651.2?
Still have the other problem of not being able to boot into recovery despite flashing it in the correct partition.
killmastern3 said:
OK. Looks like i did this "fastboot flash boot recovery.img". I know its a stupid mistake but need help recovering. Will i be able to boot into the rom if i flash kernel? If yes, can anybody link me to kernel for 3.04.651.2?
Still have the other problem of not being able to boot into recovery despite flashing it in the correct partition.
Click to expand...
Click to collapse
You are also in the wrong section. If you flashed anything from this section that's why you can't boot. You need to be in the sprint htc one section
Sent from my HTCONE using Tapatalk
thicklizard said:
You are also in the wrong section. If you flashed anything from this section that's why you can't boot. You need to be in the sprint htc one section
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Apologies. Will take the query to the correct section. I did flash sprint specific recovery though. Request mods to please close this thread.
killmastern3 said:
Apologies. Will take the query to the correct section. I did flash sprint specific recovery though. Request mods to please close this thread.
Click to expand...
Click to collapse
I just wanted to make sure you flashed sprint specific files. A ruu will get you fixed up there is a thread in the sprint section with a link to the ruu and a how to
Sent from my HTCONE using Tapatalk
thicklizard said:
I just wanted to make sure you flashed sprint specific files. A ruu will get you fixed up there is a thread in the sprint section with a link to the ruu and a how to
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Tried flashing RUU. Get error 120 - low battery. Can i just get the specific kernal and flash it through fastboot?
Related
Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point. Thankyou for reading
SaadQamer said:
Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point. Thankyou for reading
Click to expand...
Click to collapse
Can you still boot in bootloader?
if you can, you can flash a custom recovery (TWRP or CWM) again so you can install a custom rom.
it would be best if you can do fastboot getvar all and post the result here so everyone can have a clearer view on what RUU you need. will definitely help to help you properly.
Are you able to get into fastboot? If you can get into fastboot, you'll be able to flash a custom recovery, and then from there on you can either mount USB storage or use adb sideload to flash a rom onto your phone.
Thyankyou for responding
thanks for responding, if bootloader is the menu with fastboot and factory reset and those options then yes i can boot into that because my phone is off right now and i can hold vol. down and power to go into that. not sure how i can flash a custom rom though or even a recovery any help with that would be greatly appreciated as well. the phone is currently blinking with an orange light leaving me to assume the battery is deal so i cant even turn it on at the moment but i will post the getvar command when it does thankyou so much, by the way the phone is an htc one rogers just for clarification.
getvar
when i typed in fastboot getvar all i got this
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34GW901697
(bootloader) imei: 354439053152296
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(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.064s
again any help with these will be greatly appreciated
Solved thanks to @alray
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: (not sure if you need this)
(bootloader) imei: (not showing this to you)
(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: 4262mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
CorcoranM96 said:
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
Click to expand...
Click to collapse
the ruu failed because you need s-off to use them with hboot 1.55 (require hboot downgrade to 1.44 which require s-off)
so now your best option is tu install a guru reset. Use this file
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
video tutorial here
so now your best option is tu install a guru reset.
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
Thanks @alray for the reply! I'm trying that now, I'll let you know how I get on!
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
CorcoranM96 said:
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
Click to expand...
Click to collapse
Move the .zip file to your fastboot/adb folder. boot your phone in recovery. then:
Code:
adb push name_of_file.zip /sdcard/
then in recovery select ''install'' and slect the zip you pushed
no need to use otg cable
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
CorcoranM96 said:
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
Click to expand...
Click to collapse
what recovery are you using? You are doing adb command in recovery right?
Solved!
alray said:
what recovery are you using? You are doing adb command in recovery right?
Click to expand...
Click to collapse
Fixed it, I just changed computer... My phone works perfectly and is returned to stock! :good:
Thanks a million @alray!
hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)
progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
My major screwups:
No nandroid backup.
No s-off
I have Sprint
Current State:
I can get to fastboot, recovery and adb works fine. But no matter which recovery/rom combination I try, I get the same end result. My phone will boot to the "HTC One" screen, then go the green HTC logo/white background screen then reboot. Sometimes it stays active long enough to begin the "Welcome to Android" stuff (pick your language, wifi connection, etc...), but not nearly long enough to get through all the screens.
What I've tried so far:
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
ROMS: ARHD 31.6 and 62.0 (I know this doesn't work with Sprint), Viper 6.1 and some "stock" rom I found somewhere (filename One_4.19.401.11_odexed.zip).
I don't remember exactly the order, but I know I did TWRP 2.6.3.4 and ARHD 62.0 first. Then did Viper 6.1, then ARHD 31.6. Since then, I've tried every combination of recovery and ROM that I can think of.
Here's getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4205mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I'm willing to try anything at this point. So suggestions are welcome. You're also welcome to berate me for the above mentioned screwups, but it won't be very helpful.
TIA
Goto_End said:
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
TIA
Click to expand...
Click to collapse
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: http://techerrata.com/browse/twrp2/m7wls
(make sure to check MD5 on the download)
nkk71 said:
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: (can't post links yet)
(make sure to check MD5 on the download)
Click to expand...
Click to collapse
Downloaded the 2.6.3.0 from the link you provided (checked md5), flashed recovery. Did an adb push to get the Viper ROM (also checked the md5) back to /sdcard and flashed the ROM. Same results as before.
Additional info:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
The screen will timeout on the green HTC logo screen. If I hit Power to bring it back to life, I have to "pull to unlock" and either the logo screen is still there or it's made it to "Welcome to Android".
I actually got to the Welcome screen this time. Picked the language, wifi network and started with my Google login before it rebooted.
Maybe an incompatible ROM issue? If so, I'm out of ideas as to what to try next.
I've downloaded what I believe to be the RUU for this model phone, but since I can't see the phone in Windows, I haven't even tried the RUU.
Goto_End said:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
...before it rebooted.
Click to expand...
Click to collapse
That's usually caused by the modem not initializing properly, and you could have some corrupt partitions due to using an m7_u/ul and it's time for ruu i guess.
Better head over to the HTC One Sprint forum: http://forum.xda-developers.com/sprint-htc-one should be plenty of help there.
Most of us here are on m7_u/ul so can offer only limited assistance... could be as simple flashing a radio for Sprint... but like I said, I'm not too familiar with Sprint unbrick.
Sorry & Good Luck
There's an awesome Rescue Tutorial over in the Sprint HTC One forum for people like me who flashed a GSM ROM on a CDMA phone. I can't post links yet, or I'd link to it just for posterity.
In essence, the GSM ROMs screw up the partition table. The fix was really easy. Most of the time was spend downloading the correct ROM and waiting for the adb push.
Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(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.7
(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: 4296mV
(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
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(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.7
(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: 4296mV
(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
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.