I bought a sprint htc one m7 couple of days ago and brought it to india.. it has
-stock 4.3 rom
-hboot 1.55
-bootloader unlocked
-s-off acheived using firewater
i was trying to sim unlock the phone... but after flashing this http://forum.xda-developers.com/showthread.php?t=2586704 ruu... its struck on htc logo.. all help appreciated... im a bit noob in this subject...
i would like to also share that while flashing ruu the phone got ejected from the system and now i cant access the intenal storage...when i try to do adb sideload it says "device not found"...TWRP recovery also does not shows my internal sd card.. and i hav ordered USB OTG cable to try and flash it from usb drive..is this way safe and will it work?? is there any way to fix this problem??
thanks in advance..
EDIT
i tried USB OTG method but the USB wont mount at all it shows USB-OTG(0MB) and usb-otg mount failed
and the phone goes in fastboot mode when i try to connect it to pc...
please help me out...
thanks in advance:crying:
First, which version of the one did you have like m7wls m7vzw or like which m7? Did you cross flash ruu's??? That could cause lots of issues if you did that.... Only ruu's specifically made for the phone will work, also when trying to ruu, were you running the exe or zip?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
First, which version of the one did you have like m7wls m7vzw or like which m7? Did you cross flash ruu's??? That could cause lots of issues if you did that.... Only ruu's specifically made for the phone will work, also when trying to ruu, were you running the exe or zip?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
i have m7wls... when i connect it to pc and go to twrp recovery it shows up as m7wls with a small yellow exclamatory mark (!) and when i connect it in bootloader it shows up as my htc...
i was flashing it through pc by running .exe file and i got ejected sound on my win 8.1...
since then i have this problem
please help me out..
thanks in advance
praveensk.rcb said:
i have m7wls... when i connect it to pc and go to twrp recovery it shows up as m7wls with a small yellow exclamatory mark (!) and when i connect it in bootloader it shows up as my htc... please help me out..
thanks in advance
Click to expand...
Click to collapse
When you run
Code:
adb devices
while in recovery what does it give you? Also could you post a fastboot, and do
Code:
fastboot getvar all
post all except imie and Serial No, and meid
pball52998 said:
When you run
Code:
adb devices
while in recovery what does it give you? Also could you post a fastboot, and do
Code:
fastboot getvar all
post all except imie and Serial No, and meid
Click to expand...
Click to collapse
while in fastboot when i connect the phone i get a sound notification that phone is plugged and phone shows FASTBOOT USB...
but i cant see anything in windows explorer....
as in twrp recovery i cant see my backup rom it only shows folders like /cache /data /dev /etc /licence etc...
praveensk.rcb said:
while in fastboot when i connect the phone i get a sound notification that phone is plugged and phone shows FASTBOOT USB...
but i cant see anything in windows explorer....
as in twrp recovery i cant see my backup rom it only shows folders like /cache /data /dev /etc /licence etc...
Click to expand...
Click to collapse
You don't find it in windows explorer... Its a command initiated through cmd prompt where your adb and fastboot is..... and actually same for when in twrp, look i will show you mine....
Code:
Preston-Ball:Main files and scripts prestonball$ adb devices
List of devices attached
My Serial No... recovery
Preston-Ball:Main files and scripts prestonball$
That is just in the main menu of TWRP, nothing else....
now lets say you wanna push a ROM.... just do..
Code:
adb push name_of_rom.zip /location/where/you/want/ROM
Then for the fastboot USB... With fastboot getvar all
Code:
Preston-Ball:Main files and scripts prestonball$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: **************
(bootloader) imei: ************
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3904mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.497s
Preston-Ball:Main files and scripts prestonball$
Thats what the fastboot getvar all is...
Bootloader
pball52998 said:
You don't find it in windows explorer... Its a command initiated through cmd prompt where your adb and fastboot is..... and actually same for when in twrp, look i will show you mine....
Code:
Preston-Ball:Main files and scripts prestonball$ adb devices
List of devices attached
My Serial No... recovery
Preston-Ball:Main files and scripts prestonball$
That is just in the main menu of TWRP, nothing else....
now lets say you wanna push a ROM.... just do..
Code:
adb push name_of_rom.zip /location/where/you/want/ROM
Then for the fastboot USB... With fastboot getvar all
Code:
Preston-Ball:Main files and scripts prestonball$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: **************
(bootloader) imei: ************
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3904mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.497s
Preston-Ball:Main files and scripts prestonball$
Thats what the fastboot getvar all is...
Click to expand...
Click to collapse
my bootloader reads
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-OFF RH
CID-SPECS_001
HBOOT-1.44.0000
RADIO-1.00.20.1108
OpenDSP-v32.120.274.0909
eMMC-boot
at first my bootloader version was 1.55 but while flashing ruu it got downgraded but in the middle of the process it got stuck and phone got ejected with no rom at all... i was doing it in my friend's pc which has windows 8.1.. is it safe to do it win 8.1 or shuld i do it in win 7???
can you please share a link on how to repair the phone step by step...(newbie)
thanks in advance
okay i got this
pball52998 said:
You don't find it in windows explorer... Its a command initiated through cmd prompt where your adb and fastboot is..... and actually same for when in twrp, look i will show you mine....
Code:
Preston-Ball:Main files and scripts prestonball$ adb devices
List of devices attached
My Serial No... recovery
Preston-Ball:Main files and scripts prestonball$
That is just in the main menu of TWRP, nothing else....
now lets say you wanna push a ROM.... just do..
Code:
adb push name_of_rom.zip /location/where/you/want/ROM
Then for the fastboot USB... With fastboot getvar all
Code:
Preston-Ball:Main files and scripts prestonball$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: **************
(bootloader) imei: ************
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3904mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.497s
Preston-Ball:Main files and scripts prestonball$
Thats what the fastboot getvar all is...
Click to expand...
Click to collapse
i got this...
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>adb devices
List of devices attached
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>fastboot devices
FA344S900731 fastboot
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA344S900731
(bootloader) imei: 9***********10
(bootloader) meid: 9*********11
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4045mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
now what should i do??? please help
thanks in advance
praveensk.rcb said:
i got this...
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>adb devices
List of devices attached
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>fastboot devices
FA344S900731 fastboot
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA344S900731
(bootloader) imei: 9***********10
(bootloader) meid: 9*********11
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4045mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
now what should i do??? please help
thanks in advance
Click to expand...
Click to collapse
If you are trying to flash a Sprint RUU, use this thread: Bad Boyz RUU. It's the latest RUU, and I've used it myself. I've wiped my internal storage on accident and on purpose and was able to get my phone up and running using this.
Your phone is not showing up using ADB because you currently have no operating system, same for the USB OTG. Make sure you are using the stock cable (or a high quality replacement). Best of luck to you.
praveensk.rcb said:
i got this...
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>adb devices
List of devices attached
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>fastboot devices
FA344S900731 fastboot
C:\Users\Praveen-SK\Desktop\HTC One\adt-bundle-windows-x86_64-20140321\sdk\platf
orm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA344S900731
(bootloader) imei: 9***********10
(bootloader) meid: 9*********11
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4045mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
now what should i do??? please help
thanks in advance
Click to expand...
Click to collapse
Sorry just got to my computer... but Good device is found, all drivers are installed good then.... Okay now time for the RUU... We're going to try a RUU first and see how good it works, okay?
Here is the RUU file.. http://www.androidfilehost.com/?fid=22926241640219526 Download the zip, place it in the folder where your ADB and fastboot is. Once you have it downloaded and in your ADB/fastboot folder,
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen). If not rerun
fastboot oem rebootRUU
now simply reflash the rom.zip
fastboot flash zip Rom.zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically
(Error 155)
You did not re lock your bootloader first
-go relock and flash again
More than likely the first time you flash it, it will not work, it usually takes twice for the RUU to go through.. I did copy this from another forum post. But it worked when I have ruu'ed my phone. Do you just wanna go to stock? Or another ROM, if this doesn't work we can load a ROM... .-.
pball52998 said:
Sorry just got to my computer... but Good device is found, all drivers are installed good then.... Okay now time for the RUU... We're going to try a RUU first and see how good it works, okay?
Here is the RUU file.. http://www.androidfilehost.com/?fid=22926241640219526 Download the zip, place it in the folder where your ADB and fastboot is. Once you have it downloaded and in your ADB/fastboot folder,
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen). If not rerun
fastboot oem rebootRUU
now simply reflash the rom.zip
fastboot flash zip Rom.zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically
(Error 155)
You did not re lock your bootloader first
-go relock and flash again
More than likely the first time you flash it, it will not work, it usually takes twice for the RUU to go through.. I did copy this from another forum post. But it worked when I have ruu'ed my phone. Do you just wanna go to stock? Or another ROM, if this doesn't work we can load a ROM... .-.
Click to expand...
Click to collapse
ok i will try to do that... but can you tell me what has hapened to by phone now??? before the got soft bricked its hboot version was 1.55 but after incomlete flashing of ruu, its hboot version has become 1.44???
praveensk.rcb said:
ok i will try to do that... but can you tell me what has hapened to by phone now??? before the got soft bricked its hboot version was 1.55 but after incomlete flashing of ruu, its hboot version has become 1.44???
Click to expand...
Click to collapse
While it was probably restoring system or something like the emmc, could have went ka plunk.... which if it did and the ruu doesn't work... its a good thing you're s-off..
pball52998 said:
While it was probably restoring system or something like the emmc, could have went ka plunk.... which if it did and the ruu doesn't work... its a good thing you're s-off..
Click to expand...
Click to collapse
will it be safe flash an RUU??? im using windows 8 32-bit and x86 sdk kit... is it ok??
slyest12 said:
If you are trying to flash a Sprint RUU, use this thread: Bad Boyz RUU. It's the latest RUU, and I've used it myself. I've wiped my internal storage on accident and on purpose and was able to get my phone up and running using this.
Your phone is not showing up using ADB because you currently have no operating system, same for the USB OTG. Make sure you are using the stock cable (or a high quality replacement). Best of luck to you.
Click to expand...
Click to collapse
thanks for the info....but i have see many others who have got adb sideload working... and i have got an aftermarket USB OTG cable...are there different RUU's for HTC one like 3.0,1.29.4.0... which one will be suited for my device??
The one that I sent you was for your device, pretty much you would take it, it would return you back to stock. Take a OTA, have the newest radios and unlock again. But if you want a new ROM, you don't even need adb sideload... I've never gotten that crap to work... -,,,,,,,,,- but there's also different RUUs, they all do the same thing pretty much. But if you want to use a ROM. Go into Mount in twrp and what are you options?
Sent form my Rezound running sense 5. S-OFF
pball52998 said:
The one that I sent you was for your device, pretty much you would take it, it would return you back to stock. Take a OTA, have the newest radios and unlock again. But if you want a new ROM, you don't even need adb sideload... I've never gotten that crap to work... -,,,,,,,,,- but there's also different RUUs, they all do the same thing pretty much. But if you want to use a ROM. Go into Mount in twrp and what are you options?
Sent form my Rezound running sense 5. S-OFF
Click to expand...
Click to collapse
i intend to downgrade the phone to 4.1.2 from 4.3 and unlock the phone using sim unlocker app and then upgrade the rom to any newer version like viper rom
praveensk.rcb said:
i intend to downgrade the phone to 4.1.2 from 4.3 and unlock the phone using sim unlocker app and then upgrade the rom to any newer version like viper rom
Click to expand...
Click to collapse
You should be able to do that its just downgrading then upgrading radios.. I would say, take the ruu. Take the latest ota, or unlock and root for that sim unlock, then take a ota, Which I think you would have to then unlock again or flash the radios via recovery since your s-off in the form of a zip. Then take your ROM put it on internal SD card, wipe everything but Internal SD card and all that crap, then flash ROM and correlating GAPPS.
pball52998 said:
You should be able to do that its just downgrading then upgrading radios.. I would say, take the ruu. Take the latest ota, or unlock and root for that sim unlock, then take a ota, Which I think you would have to then unlock again or flash the radios via recovery since your s-off in the form of a zip. Then take your ROM put it on internal SD card, wipe everything but Internal SD card and all that crap, then flash ROM and correlating GAPPS.
Click to expand...
Click to collapse
will it be safe to RUU in windows 8???
Yes, as long as you have proper drivers.
Sent form my Rezound running sense 5. S-OFF
Related
Hey all. A some time ago I rooted my phone, unlocked bootloader, no S-OFF, and installed HD Revolution, 31.6 or something and it worked great for a good two months. But now my phone got jammed, I booted it and it doesn't work. Can't access recovery or start the phone, when I go to bootloader and try to go to recovery, it says entering recovery and boots again. I've tried to install multiple RUU's via fastboot method but it won't work. I always get the message remote: 24 parsing android info file. Tried to relock bootloader and then it gives the error 12 parsing android info file error.
So where to now? Can't get adb to work, tried multiple ways. It could've been the solution to boot to recovery? Can't boot to recovery via fastboot. Any ideas?
Have you tried reflashing recovery via fastboot?
Can you boot to recovery via fastboot with a recovery img file stored on your PC?
shaitan667 said:
Have you tried reflashing recovery via fastboot?
Can you boot to recovery via fastboot with a recovery img file stored on your PC?
Click to expand...
Click to collapse
I've tried reflashing multiple recoveries multiple times, and always did fastboot erase cache. Couldn't boot to recovery via fastboot command also, phone just jammed for 10minutes.
And I just figured out, I can't get adb working because I can't start my phone. Am I correct?
hessusi said:
I've tried reflashing multiple recoveries multiple times, and always did fastboot erase cache. Couldn't boot to recovery via fastboot command also, phone just jammed for 10minutes.
And I just figured out, I can't get adb working because I can't start my phone. Am I correct?
Click to expand...
Click to collapse
N o as long as it switches on you are fine boot into
You need the info in these threads, read carefully before you make any moves
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2265618
L0rdNels0n said:
N o as long as it switches on you are fine boot into
You need the info in these threads, read carefully before you make any moves
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
As said, I can't get adb to work. I think the phone should be started for it to work, but as said, I can't start it. Only available to bootloader etc.
I just want to know why the recovery won't work, I've installed many recoveries many time, everytime it says entering recovery, and then just boots. And boots again for a million times, but what is the reason?
I'm trying to boot the recovery through fastboot, but the phone just freezes. Well I'll wait for 30min and we'll see if it works. I doubt.
Is there any Roms or RUUs I could install straight from fastboot?
So is the problem that I've got hboot 1.55? And I can't downgrade it because I can't use adb. Where to now? Anyone?
According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works. So can anyone help me? I can't use adb at all.Anything to do or should I throw it out of the window?
hessusi said:
According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works. So can anyone help me? I can't use adb at all.Anything to do or should I throw it out of the window?
Click to expand...
Click to collapse
Does anyone have any answers?
What is your fastboot getvar all output ? Remove imei/SN
Have you tried this?
Fastboot flash recovery recover.IMG
Fastboot erase cache
sent from my mobile device
According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works.
Click to expand...
Click to collapse
hessusi said:
Does anyone have any answers?
Click to expand...
Click to collapse
yeah .. if you flashed a cdma recovery on your GSM phone you probably killed the partition structure and it's not easy to fix.
Their are a couple of guys here that can do it, but it's way over my head, ... maybe @nkk71 will help you
hessusi said:
According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works. So can anyone help me? I can't use adb at all.Anything to do or should I throw it out of the window?
Click to expand...
Click to collapse
how about we start with a "fastboot getvar all" (only show us the first two characters of IMEI, MEID, and s/n) and also the link(s) of what you flashed.
nkk71 said:
how about we start with a "fastboot getvar all" (only show us the first two characters of IMEI, MEID, and s/n) and also the link(s) of what you flashed.
Click to expand...
Click to collapse
I installed all CWM recoveries for any HTC One.. verizon at&t, all of them. So I did only more damage huh? Well, let's see if you can help me now. Here's the info you asked: IMEI 35, MEID 00, s/n MB. That's all?
hessusi said:
I installed all CWM recoveries for any HTC One.. verizon at&t, all of them. So I did only more damage huh? Well, let's see if you can help me now. Here's the info you asked: IMEI 35, MEID 00, s/n MB. That's all?
Click to expand...
Click to collapse
no ...like this
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(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: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
C:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.042s
Click to expand...
Click to collapse
(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.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: MBxxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(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!
finished. total time: 0.068s
There you go.
hessusi said:
Hey all. A some time ago I rooted my phone, unlocked bootloader, no S-OFF, and installed HD Revolution, 31.6 or something and it worked great for a good two months. But now my phone got jammed, I booted it and it doesn't work. Can't access recovery or start the phone, when I go to bootloader and try to go to recovery, it says entering recovery and boots again. I've tried to install multiple RUU's via fastboot method but it won't work. I always get the message remote: 24 parsing android info file. Tried to relock bootloader and then it gives the error 12 parsing android info file error.
So where to now? Can't get adb to work, tried multiple ways. It could've been the solution to boot to recovery? Can't boot to recovery via fastboot. Any ideas?
Click to expand...
Click to collapse
I had this issue and is annoying how long it took to me fix. I had to try and get adb to work on several computers and eventually it did, from there I installed everything stock then unlocked the phone and root, install custom recovery and s-off with chosen rom. Now if you install twrp the latest version and sideload a Rom you will be good to go or get a usb otg. I was able to install custom recovery by adb but couldn't do anything else. I was able to sideload using twrp recovery in adb
Sent from my HTC One using XDA Premium 4 mobile app
hessusi said:
(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.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: MBxxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(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!
finished. total time: 0.068s
There you go.
Click to expand...
Click to collapse
Well you know how to flash recovery lets try one more time with the correct one.
Download this >>http://techerrata.com/browse/twrp2/m7ul
put it in your fastboot folder and md5 check it - f428caf36c9c337e2ae417fc10fbe165
if it's ok continue
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
after the last step use volume down to select bootloader then volume down to select recovery (power button to select)
can you get into twrp now ?
clsA said:
Well you know how to flash recovery lets try one more time with the correct one.
Download this >>http://techerrata.com/browse/twrp2/m7ul
put it in your fastboot folder and md5 check it - f428caf36c9c337e2ae417fc10fbe165
if it's ok continue
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
after the last step use volume down to select bootloader then volume down to select recovery (power button to select)
can you get into twrp now ?
Click to expand...
Click to collapse
No, didn't work. Instant power off when I press recovery. Tried again and it just keeps saying entering recovery... Aaaand a bootloop again. So same thing with this one. What's next?
hessusi said:
No, didn't work. Instant power off when I press recovery. Tried again and it just keeps saying entering recovery...
Click to expand...
Click to collapse
well maybe a RUU will rebuild your partitions
lets look, Go here and find the RUU that matches
3.62.401.1
PN0710000
HTC__Y13
http://www.htc1guru.com/downloads
Well after looking it seems without s-off your done
Try and get s-off with rumrunner
clsA said:
well maybe a RUU will rebuild your partitions
lets look, Go here and find the RUU that matches
3.62.401.1
PN0710000
HTC__Y13
http://www.htc1guru.com/downloads
Well after looking it seems without s-off your done
Try and get s-off with rumrunner
Click to expand...
Click to collapse
I thought that adb is unavailable if phone can't be powered on? Atleast I can't get it to work.. And I tried RUU and it was correct but couldn't get it to work.
hessusi said:
I thought that adb is unavailable if phone can't be powered on? Atleast I can't get it to work.. And I tried RUU and it was correct but couldn't get it to work.
Click to expand...
Click to collapse
actually adb works fine ...in recovery or booted phone
clsA said:
actually adb works fine ...in recovery or booted phone
Click to expand...
Click to collapse
I can't access recovery.
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
I did s-off since you're unlocked. Probably the issue. Then I would go into fast boot to either ruu or transfer a rom
I think rumrunner is what works on 1.55 hboot
Sent from my HTC One
krankenator said:
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
Click to expand...
Click to collapse
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
clsA said:
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
Click to expand...
Click to collapse
Not pro, but I hobble by. Results:
(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:
(bootloader) imei:
(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: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
krankenator said:
Not pro, but I hobble by. Results:
(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:
(bootloader) imei:
(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: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
clsA said:
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
Click to expand...
Click to collapse
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
krankenator said:
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
Click to expand...
Click to collapse
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
clsA said:
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
Click to expand...
Click to collapse
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
krankenator said:
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
I don't think that file requires s-off
but yes a locked boot loader is needed
fastboot oem lock
Well, time to try something else.
Any ideas anyone?
krankenator said:
Something didn't work. It only reboot to the bootloader.
Pro-Mac-Jesseesktop jesse$ ./fastboot oem lock
Click to expand...
Click to collapse
FAILED (remote: 12 signature verify fail)
I'll take a guess this means you need s-off
or a windows PC to run the RUU.exe I posted first
Hi all
I have a HTC One (M7). Its has been rooted and was running 4.3. Tried to update to 4.4 and flashed an Android Revolution HD ROM. Not sure if it was the wrong ROM or if I wasn't S-OFF. Now i am stuck on HTC boot screen. When i try to load into recovery it flashes up for a second and then goes back to HTC boot image.
Have tried to flash a new recovery using EZtoolkit - Flashed TWRP - didnt help, still cant get in.
Also used the toolkit to erase the cache but hasnt helped.
Any suggestions??
Output of fastboot getvar all?
SaHiLzZ said:
Output of fastboot getvar all?
Click to expand...
Click to collapse
Sorry mate. Im not the best with this.
How do i find this?
SaHiLzZ said:
Output of fastboot getvar all?
Click to expand...
Click to collapse
C:\Users\Gary\Downloads\EZToolkit%20Advanced%20(M7-M7WLS)\EZToolkit Advanced (M7
-M7WLS)\EZToolkit Advanced (M7-M7WLS)\mBF>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37LW903746
(bootloader) imei: 357864056977711
(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: 4199mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.150s
Think this is what u mean
Garyflem said:
C:\Users\Gary\Downloads\EZToolkit%20Advanced%20(M7-M7WLS)\EZToolkit Advanced (M7
-M7WLS)\EZToolkit Advanced (M7-M7WLS)\mBF>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37LW903746
(bootloader) imei: 357864056977711
(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: 4199mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.150s
Think this is what u mean
Click to expand...
Click to collapse
Download: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m7ul//philz_touch_6.08.9-m7ul.img
Connect your phone to USB.
Go to bootloader >> fastboot mode (fastboot USB) - [power + volume down].
Code:
fastboot flash recovery philz_touch_6.08.9-m7ul.img
Do not turn off USB in phone and turn off your phone.
You go to recovery?
Garyflem said:
C:\Users\Gary\Downloads\EZToolkit%20Advanced%20(M7-M7WLS)\EZToolkit Advanced (M7
-M7WLS)\EZToolkit Advanced (M7-M7WLS)\mBF>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37LW903746
(bootloader) imei: 357864056977711
(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: 4199mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.150s
Think this is what u mean
Click to expand...
Click to collapse
Yup..
Download this: http://www.androidruu.com/getdownlo..._P2_release_324936_signedma8j1sa3e2o09s35.zip
Unzip. Find the firmware.zip in the unzipped content, and flash it like this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
This *SHOULD* get your stock recovery back, you should be able to get back in STOCK recovery. Then, flash custom recovery, and you should be able to get back in TWRP recovery.
Then you will need to ADB push/ ADB Sideload a custom rom to your device, and get going. Stay with 4.3, until your device is booted and you have a chance to S-OFF.
Don't use toolkits.. Get used to using fastboot and adb.. Download fastboot and adb from here.. Read the guide. Once setup, from within the fastboot and adb folder, Shift*key and*right click*on the*folder. open Command window here..
Connect your phone to PC while in bootloader screen.
Make sure fastboot USB is shown on bootloader
Then type..
Fastboot devices. A seemingly random number should be shown.
If it is.. Type fastboot erase cache.
fastboot reboot
PS.. Make sure you are using TWRP 2.6.3.3.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Rename to recovery
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
SaHiLzZ said:
Yup..
Unzip. Find the firmware.zip in the unzipped content, and flash it like this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
This *SHOULD* get your stock recovery back, you should be able to get back in STOCK recovery. Then, flash custom recovery, and you should be able to get back in TWRP recovery.
Then you will need to ADB push/ ADB Sideload a custom rom to your device, and get going. Stay with 4.3, until your device is booted and you have a chance to S-OFF.
Click to expand...
Click to collapse
Ok im downloading the ZIp file now. If flash that could i then flash a stock ROM and return fully to stock and get an OTA update to 4.4?
SaHiLzZ said:
Yup..
Unzip. Find the firmware.zip in the unzipped content, and flash it like this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
This *SHOULD* get your stock recovery back, you should be able to get back in STOCK recovery. Then, flash custom recovery, and you should be able to get back in TWRP recovery.
Then you will need to ADB push/ ADB Sideload a custom rom to your device, and get going. Stay with 4.3, until your device is booted and you have a chance to S-OFF.
Click to expand...
Click to collapse
You are a star mate. RUU flashed and then it loadeded up into TWRP straight away without me even flashing it again.
Just downlaoding a 4.3 ROM now
SaHiLzZ said:
Yup..
Download this: http://www.androidruu.com/getdownlo..._P2_release_324936_signedma8j1sa3e2o09s35.zip
Unzip. Find the firmware.zip in the unzipped content, and flash it like this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
This *SHOULD* get your stock recovery back, you should be able to get back in STOCK recovery. Then, flash custom recovery, and you should be able to get back in TWRP recovery.
Then you will need to ADB push/ ADB Sideload a custom rom to your device, and get going. Stay with 4.3, until your device is booted and you have a chance to S-OFF.
Click to expand...
Click to collapse
I was searching forum for my problem (quite similar to the problem of OP) i have tried all of the mentioned steps but i am unable to write any thing via bootloaders (i.e. recovery, zip, ruu etc) i have also tried to restore my phone via RUU...setup is shutdown the device but do not boot it up again (as it suppose to)... i m uploading the cmd screen shot for your kind perusal, kindly help me out as well please...
Thanks & best regards,
Mortal Eternity said:
I was searching forum for my problem (quite similar to the problem of OP) i have tried all of the mentioned steps but i am unable to write any thing via bootloaders (i.e. recovery, zip, ruu etc) i have also tried to restore my phone via RUU...setup is shutdown the device but do not boot it up again (as it suppose to)... i m uploading the cmd screen shot for your kind perusal, kindly help me out as well please...
Thanks & best regards,
Click to expand...
Click to collapse
The error says sd card failure
SaHiLzZ said:
The error says sd card failure
Click to expand...
Click to collapse
does it mean that it might be a hardware issue and nothing can be done further??
If you came even flash recovery, sounds like it
sent from my mobile device
SaHiLzZ said:
If you came even flash recovery, sounds like it
sent from my mobile device
Click to expand...
Click to collapse
yes i can not even flash recovery... whenever i attempt to do so it gives an error as attached!
seems like some sort of security has been activated but can be a hardware issue as well...
Hello,
This is my first post but I've been reading for months and months everything I could find here on ways to fix my M7. In the meantime I've bought an M8, call me crazy but I'd really like to get my M7 back up and running. I'm stubborn, but now it's time to ask for help
One day, a few months ago, I tried installing a custom splash screen. I kind of thought, well, this might brick it, but I can fix it. I had tested my backup but somewhere along the line it became corrupted and I didn't have a backup of my backup. Since then, I have tried flashing different recoveries (CWM, TWRP, Philz), tried converting to Google Play edition per the instructions I found on these forums, tried various RUU's, both zips and exe's. I edited the android-info.txt file to match what the phone said in "fastboot getvar all", I changed CID's where appropriate to match the RUU's, tried running with the bootloader locked and unlocked and still the closest to life I could bring this thing was stuck on a Google splash screen. It will not boot into recovery, although it seems to install a recovery. It just sits on "entering recovery". Even if I leave it there for a day thinking maybe it's just taking it's time.
So then I tried flashing the original firmware, and a copy of a Nandriod backup for version 3.23.666.1 for Bell, none of which has worked. I am unable to get any results from "adb devices" (it just returns a blank line), so pushing anything via adb won't work either. Adb does indeed work because I am able to access my M8 with adb commands.
I have tried all of this on Windows 7, Ubuntu (a few different version), and a MacBook.
Is there any hope for this phone? Here are the details:
It's unlocked and S-OFF, here are the results of getvar all:
C:\adb\sdk\platform-tools>fastboot 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.666.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.107s
Thanks a bunch for taking the time to read all of this, and any input at all is greatly appreciated.
Take Care,
~PittieInPink
PittieInPink said:
Hello,
This is my first post but I've been reading for months and months everything I could find here on ways to fix my M7. In the meantime I've bought an M8, call me crazy but I'd really like to get my M7 back up and running. I'm stubborn, but now it's time to ask for help
One day, a few months ago, I tried installing a custom splash screen. I kind of thought, well, this might brick it, but I can fix it. I had tested my backup but somewhere along the line it became corrupted and I didn't have a backup of my backup. Since then, I have tried flashing different recoveries (CWM, TWRP, Philz), tried converting to Google Play edition per the instructions I found on these forums, tried various RUU's, both zips and exe's. I edited the android-info.txt file to match what the phone said in "fastboot getvar all", I changed CID's where appropriate to match the RUU's, tried running with the bootloader locked and unlocked and still the closest to life I could bring this thing was stuck on a Google splash screen. It will not boot into recovery, although it seems to install a recovery. It just sits on "entering recovery". Even if I leave it there for a day thinking maybe it's just taking it's time.
So then I tried flashing the original firmware, and a copy of a Nandriod backup for version 3.23.666.1 for Bell, none of which has worked. I am unable to get any results from "adb devices" (it just returns a blank line), so pushing anything via adb won't work either. Adb does indeed work because I am able to access my M8 with adb commands.
I have tried all of this on Windows 7, Ubuntu (a few different version), and a MacBook.
Is there any hope for this phone? Here are the details:
It's unlocked and S-OFF, here are the results of getvar all:
C:\adb\sdk\platform-tools>fastboot 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.666.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.107s
Thanks a bunch for taking the time to read all of this, and any input at all is greatly appreciated.
Take Care,
~PittieInPink
Click to expand...
Click to collapse
What was the error when trying to flash RUUs? it should be very easy to restore your phone with s-off. you could try the dev edition ruu
change cid to BS_US001:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then confirm the cid is correct:
Code:
fastboot oem readcid
then download this ruu.zip and save it to your adb/fastboot folder, rename it to "ruu" (ruu.zip)
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
btw your blank line when typing "adb devices" is normal. Adb doesnt work from the bootloader, only from a custom recovery of from the OS whit usb debug ON.
Good morning and thank you, I'm downloading the RUU you posted and will give it a try following all of your instructions.
I didn't actually get any error messages when flashing the RUU's, for the most part (when I had the correct cid etc) there were no error messages and it actually said successful on both the first and second executions of the flash command. It just wouldn't boot, it would get stuck on either the HTC or Google splash screen, depending which RUU I was trying.
No error logs either. I'm obviously doing something wrong eh? Fingers crossed the above works!
@alray
I followed all of the above steps and got the RUU seemed to flash okay, it said "sucessful" both times. I ran the fastboot reboot command and it's just sitting on the white screen with the green htc logo.
Hey guys, What's up?
First of all, I must mention what happened, I always had an iPhone, and I bought a HTC One (M7) like 2 years ago, and I never thought about rooting it..
One year ago, my friend suggested that he can upgrade it to Lollipop, and he seemed so confident lol, and I think he messed it up, I do have Lollipop on it, but it's SO BUGGY!, The phone gets so HOT easily! keeps crashing! and many many other problems..
So I decided to have the Stock ROM back, and I started reading how, but honestly, it's so difficult since I don't know what he has done to the phone..
The only thing I remember he did: He was coming to this forum and mentioned that this is the best forums for Android devs..
So.. Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first? What I need to have?
And most important, help me find the right files for my phone?
Thanks alot,
Have a nice day
Stock like in GPE or Sense?
IF you have international M7 not verizon, sprint etc.
The most simple method would be just flashing nearly stock tweaked rom through recovery i.e. this one:
Sense: http://forum.xda-developers.com/showthread.php?t=2183023
GPE: http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
Full on back to stock would require using fastboot and RUU images, but you wouldn't gain anything from that.
MahmoudM10 said:
Hey guys, What's up?
First of all, I must mention what happened, I always had an iPhone, and I bought a HTC One (M7) like 2 years ago, and I never thought about rooting it..
One year ago, my friend suggested that he can upgrade it to Lollipop, and he seemed so confident lol, and I think he messed it up, I do have Lollipop on it, but it's SO BUGGY!, The phone gets so HOT easily! keeps crashing! and many many other problems..
So I decided to have the Stock ROM back, and I started reading how, but honestly, it's so difficult since I don't know what he has done to the phone..
The only thing I remember he did: He was coming to this forum and mentioned that this is the best forums for Android devs..
So.. Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first? What I need to have?
And most important, help me find the right files for my phone?
Thanks alot,
Have a nice day
Click to expand...
Click to collapse
We will first need to know the exact info about your phone. You'll need to have adb and fastboot installed on your computer, if you don't have it yet, I would suggest you to download the simplified version (Minimal adb and fastboot). You'll also need to have HTC drivers installed on your computer. Once both are installed, reboot your phone in bootloader mode (hold power and volume down), make sure your phone is in "fastboot usb" (showing a red "fastboot usb" caption, if not select "fastboot" from the bootloader menu), then start a "minimal adb and fastboot" command prompt (start menu --> program --> Minimal adb and fastboot ---> Minimal adb and fastboot.exe). Type "fastboot getvar all" and hit enter. Copy/paste the output here (remove your IMEI, MEID and SerialNo before posting).
Should look like this:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3231.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FAxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
FeelThePoveR said:
Stock like in GPE or Sense?
IF you have international M7 not verizon, sprint etc.
The most simple method would be just flashing nearly stock tweaked rom through recovery i.e. this one:
Sense: http://forum.xda-developers.com/showthread.php?t=2183023
GPE: http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
Full on back to stock would require using fastboot and RUU images, but you wouldn't gain anything from that.
Click to expand...
Click to collapse
Hey FeelThePoveR,
Well, I don't really know what are verizon or sprint... and I don't know how to know..
but I live in Israel, and bought it from a private store, so I guess I have the international M7.. (makes sense? :/ )
Honestly, I want it back to stock so I can do whatever I want with my phone knowing what I'm doing..
I have some experience with adb and fastboot already.. I have ubuntu as well, it's not gonna be hard for me to follow instructions.. my WHOLE problem is.. that I don't know the condition of my phone.. what's wrong with it..
for example.. all the time I thought I have root, I tried to follow instructions few days ago to install something..
and I checked my root via Root Checker app, and it says that I don't have root installed proberly..
So yeah.. I want my phone back to stock.. :/
And yeah it's Sense not GPE..
Any suggestions?
(I'm gonna post in a reply the "getvar" info in few hours..)
Thanks alot for giving me some of your time
Have a nice day..
alray said:
We will first need to know the exact info about your phone. You'll need to have adb and fastboot installed on your computer, if you don't have it yet, I would suggest you to download the simplified version (Minimal adb and fastboot). You'll also need to have HTC drivers installed on your computer. Once both are installed, reboot your phone in bootloader mode (hold power and volume down), make sure your phone is in "fastboot usb" (showing a red "fastboot usb" caption, if not select "fastboot" from the bootloader menu), then start a "minimal adb and fastboot" command prompt (start menu --> program --> Minimal adb and fastboot ---> Minimal adb and fastboot.exe). Type "fastboot getvar all" and hit enter. Copy/paste the output here (remove your IMEI, MEID and SerialNo before posting).
Should look like this:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3231.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.707.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FAxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Hey alray,
I've been trying to get fastboot to work on my Windows for all day now..
and I tried following your instructions and files you mentioned above..
But I still get "< waiting for any device >", it doesn't recognize my phone..
tried downloading Android-SDK and installed google usb drivers as well..
It didn't work..
That's why I didn't post the getvar info yet :/
So I'm thinking about trying to do that on my Ubuntu..
but It's gonna take few hours until I'm on my laptop..
then I'll post the getvar info
For now, I don't know if that helps,
But I do know that my phone is TAMPERED + UNLOCKED + S-OFF
Thanks for your time..
Windows can be weird that way. You just have to manually install the driver.
I think I used that driver pack http://d-h.st/23V .
Unpack it, connect your phone in fastboot mode, go to device manager in the control panel and search for your device, than right click on it and select update drivers, browse my computer and select the folder with drivers.
Voila it should be working now.
Hey..
Here's my getvar info:
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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
NOTE: I didn't hide the meid field.. it's all zeros (is that okay?)
MahmoudM10 said:
Hey..
Here's my getvar info:
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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since your phone is S-OFF you can simply flash the international version on it but before flashing the international RUU, you'll have to change your CID and then update your firmware.
Download these 2 files and save it in your adb/fastboot folder on your computer:
RUU: https://www.androidfilehost.com/?fid=24391638059058554
htc_fastboot.exe (this version is needed to flash the RUU, not the regular fastboot): https://www.androidfilehost.com/?fid=24341993505161791
Change your CID to SuperCID:
Code:
fastboot oem writecid 11111111
fastboot reboot-bootloader
and confirm your cid is now 11111111 (8 times 1) using "fastboot getvar all"
Download the attached firmware.zip file and save it in your adb/fastboot folder on your computer
Then with the phone in bootloader mode:
Code:
fastboot oem rebootRUU
phone will reboot to a black screen with silver HTC logo (RUU mode), you can now flash the firmware:
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
You'll have to do the "fastboot flash zip" command twice, fist time it will fail. Ignore the green progress bar on your phone, it will not reach 100% just confirm in the command window that everything is OK.
Now that you are back in bootloader make sure your hboot is now 1.57 and your version-main is 7.19.401.102. If yes go back in ruu mode and flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.401.151_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458806_signed.zip
fastboot reboot
Make sure to use htc_fastboot to flash the RUU and not the regular fastboot.
NOTE: I didn't hide the meid field.. it's all zeros (is that okay?)[/QUOTE]
Thats fine, only CDMA phones have both an IMEI and MEID numbers (yours is GSM and only have an IMEI number)
alray said:
Since your phone is S-OFF you can simply flash the international version on it but before flashing the international RUU, you'll have to change your CID and then update your firmware.
Download these 2 files and save it in your adb/fastboot folder on your computer:
RUU: https://www.androidfilehost.com/?fid=24391638059058554
htc_fastboot.exe (this version is needed to flash the RUU, not the regular fastboot): https://www.androidfilehost.com/?fid=24341993505161791
Change your CID to SuperCID:
Code:
fastboot oem writecid 11111111
fastboot reboot-bootloader
and confirm your cid is now 11111111 (8 times 1) using "fastboot getvar all"
Download the attached firmware.zip file and save it in your adb/fastboot folder on your computer
Then with the phone in bootloader mode:
Code:
fastboot oem rebootRUU
phone will reboot to a black screen with silver HTC logo (RUU mode), you can now flash the firmware:
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
You'll have to do the "fastboot flash zip" command twice, fist time it will fail. Ignore the green progress bar on your phone, it will not reach 100% just confirm in the command window that everything is OK.
Now that you are back in bootloader make sure your hboot is now 1.57 and your version-main is 7.19.401.102. If yes go back in ruu mode and flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.401.151_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458806_signed.zip
fastboot reboot
Make sure to use htc_fastboot to flash the RUU and not the regular fastboot.
NOTE: I didn't hide the meid field.. it's all zeros (is that okay?)
Click to expand...
Click to collapse
Thats fine, only CDMA phones have both an IMEI and MEID numbers (yours is GSM and only have an IMEI number)[/QUOTE]
Hey alray,
Thanks for the instructions, but I have a question..
The fastboot you mentioned, ends with '.exe', which means it's for Windows, and I couldn't get my Windows to recognize my phone, so I'm using Ubuntu..
How can I get this fastboot for linux?
Thanks alot
MahmoudM10 said:
Hey alray,
Thanks for the instructions, but I have a question..
The fastboot you mentioned, ends with '.exe', which means it's for Windows, and I couldn't get my Windows to recognize my phone, so I'm using Ubuntu..
How can I get this fastboot for linux?
Thanks alot
Click to expand...
Click to collapse
Idk if there is a Linux version but there is a Windows and a MacOS version on htcdev.com
thanks boyy
thanks friends