Database Develop

Can't boot into recovery

I just unlocked the bootloader and flash recovery but can't boot into it, any ideas

mikevillarroel said:
I just unlocked the bootloader and flash recovery but can't boot into it, any ideas
Click to expand...
Click to collapse
I know it's a stupid question but are you rooted

you don't need to be rooted to boot into recovery, try to type
Code:
fastboot erase cache
and reboot again into recovery

matt95 said:
you don't need to be rooted to boot into recovery, try to type
Code:
fastboot erase cache
and reboot again into recovery
Click to expand...
Click to collapse
will try that and report back, thanks!

Yeah I experienced this yesterday - after flashing a rom. Now, I am afraid to flash another ROM. Very weird problem.
So, I booted into bootloader, connect to your PC... make sure the it can recognize your phone. At first, my PC would not recognize it. If you have HTC sync and drivers installed, i would uninstall both and only install the drivers. Once it recognizes, I unplug and restart the phone. It works form.

mikevillarroel said:
will try that and report back, thanks!
Click to expand...
Click to collapse
nope, after clean cache, tryed but it just shows the picture posted screen for like 5 0r 6 seconds and then reboot to rom

then simply reflash the recovery

matt95 said:
then simply reflash the recovery
Click to expand...
Click to collapse
done that couple of times, nothing(twrp and cw)

type
Code:
fastboot getvar all
and paste here

matt95 said:
type
Code:
fastboot getvar all
and paste here
Click to expand...
Click to collapse
Code:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.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: 4150mV
(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.047s

when you flash the recovery do you get this too?
Code:
FAILED (status read failed (Too many links))

matt95 said:
when you flash the recovery do you get this too?
Code:
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
no when i flash it everything goes well, the when i try to go into jus get this and after a wile it reboots
BTW, I've tried One_M7_All-In-One_Kit_v1.2 tool and adb

i think the problem is that you've flashed the international One recovery while you own a Sprint HTC One right? m7_wls says this...
---------- Post added at 10:10 PM ---------- Previous post was at 10:09 PM ----------
you should follow this guide
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
next time be carefull with these things, cause a wrong recovery can mess up your partitions and potentialy brick your device....

matt95 said:
i think the problem is that you've flashed the international One recovery while you own a Sprint HTC One right? m7_wls says this...
---------- Post added at 10:10 PM ---------- Previous post was at 10:09 PM ----------
you should follow this guide
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
next time be carefull with these things, cause a wrong recovery can mess up your partitions and potentialy brick your device....
Click to expand...
Click to collapse
OMG international recovery? I did even kn0ow theremore than one TWRP for the M7. lets see how it goes!

mikevillarroel said:
OMG international recovery? I did even kn0ow theremore than one TWRP for the M7. lets see how it goes!
Click to expand...
Click to collapse
you need a recovery compatible with the sprint htc one, and you actually installed a recovery made for the international htc one

matt95 said:
you need a recovery compatible with the sprint htc one, and you actually installed a recovery made for the international htc one
Click to expand...
Click to collapse
thanks for all your help, need to wait for some files to transfer and then will flash the other recovery.

ok i'm waiting for your report

matt95 said:
ok i'm waiting for your report
Click to expand...
Click to collapse
yeah man that was it. sorry for my ignorance, after all this years dealing with all this I still need to learn! thanks again!

glad to help now stay on that forum cause the roms of the international htc one wont' work on yours

I am having the same problem as op. My exception is that i have an M7 with virgin mobile canada. Tried everything from flashing with tool-kits to fastboot. Different .img's from all 3 recoverys and different versions. Even fastboot erase cache. Nothing works.
For a split second after i reboot into recovery i see the spash screen with the red dev writing then it reboots into android. I have tried it on both a win 7 and win 8 machine as well.

[Q] Conversion to GPE led to eternal boot loop. Fix?

Hi! I tried to convert my M7 to a GPE with OTAs, but this did not succeed. After that I tried to simply revert it back to stock, this also failed and I am now at a state where the phone boots up, as usual, to the homescreen, but turns off after 3 seconds only to repeat the process. I believe this to be a sort of boot loop.
I have tried pretty much everything I could think of. I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh", but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail). However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either. Tried to simply do a factory reset through the bootloader, nope.
My current state is S-ON, Bootloader Unlocked and the only way to interact with the phone is fastboot, because I can't access ADB in order to S-OFF...
So my first question is whether there is a way to S-OFF through fastboo? Since every thread and site I read requires ADB, which I cannot access.
If not.. What to do ?
Thanks in advance!

Sari95 said:
I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
Click to expand...
Click to collapse
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
Click to expand...
Click to collapse
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either.
Click to expand...
Click to collapse
How? define "did not do anything either" any error message?
Tried to simply do a factory reset through the bootloader, nope.
Click to expand...
Click to collapse
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
My current state is S-ON
Click to expand...
Click to collapse
You must be S-OFF to convert to GPE !!
Bootloader Unlocked and the only way to interact with the phone is fastboot because I can't access ADB in order to S-OFF...
Click to expand...
Click to collapse
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
So my first question is whether there is a way to S-OFF through fastboo?
Click to expand...
Click to collapse
No
If not.. What to do ?
Click to expand...
Click to collapse
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone

alray said:
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
How? define "did not do anything either" any error message?
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
You must be S-OFF to convert to GPE !!
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
No
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone
Click to expand...
Click to collapse
Thanks for answering! I am now stuck at the first step :l I believe I've found the correct stock RUU for my device, HTC One M7 bought in Norway, but when I try to download it from htc1guru.com, it downloads a little bit and stops. I am not able to download the full .zip file in order to flash it. I have tested to see if it has anything to do with my internet connection to do, but it doesn't have anything to do with it.
I am now downloading Android Revolution for M7, hoping that it will work....
Do you know if this issue with htc1guru.com is common or not?
Btw, I think it is best if I explain to you the whole process:
1. I downloaded a google play Edition RUU.zip that I could flash to convert the device into GPE.
2. Unlocked and S-OFF'd the device, then I flashed the RUU.zip. After these steps, I had a GPE device. However, the RUU I downloaded was Kitkat 4.4, which I thought would automatically update to 4.4.3. This did not happen.
3. I read more and understood that my CID and modelid had to be changed to CID: GOOGL001 and modelid: PN0712000, and so I did. I did not take note of my original CID, of course, so I don't know what that was :/
4. After having changed those settings, I once again tried to update it with OTA, as one would do with a GPE device, without any luck.
5. Reading on, it became clear that the device had to have stock recovery, which I downloaded and flashed. Once again, no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Hope this helps to clarify my situation

Sari95 said:
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Click to expand...
Click to collapse
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?

alray said:
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?
Click to expand...
Click to collapse
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.

Sari95 said:
no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
Click to expand...
Click to collapse
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
Sari95 said:
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.
Click to expand...
Click to collapse
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)

alray said:
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)
Click to expand...
Click to collapse
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either

Sari95 said:
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either
Click to expand...
Click to collapse
please post a picture when you got the FAILED error when attempting to flash arhd

alray said:
please post a picture when you got the FAILED error when attempting to flash arhd
Click to expand...
Click to collapse
ok.. so I tried flashing it now, there's a different error.

Sari95 said:
ok.. so I tried flashing it now, there's a different error.
Click to expand...
Click to collapse
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3

alray said:
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3
Click to expand...
Click to collapse
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
I just flashed ARHD, but when the Aroma installer finishes and I reboot the system this happens:
1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above
Any idea what this means?

Sari95 said:
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
Click to expand...
Click to collapse
why? do you have the active cmd line overflow error?

alray said:
why? do you have the active cmd line overflow error?
Click to expand...
Click to collapse
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.

Sari95 said:
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.
Click to expand...
Click to collapse
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery

alray said:
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery
Click to expand...
Click to collapse
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"

Sari95 said:
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"
Click to expand...
Click to collapse
have you wiped when you have flashed arhd?
and have you checked md5 value of the rom before flashing it?

alray said:
have you wiped when you have flashed arhd?
Click to expand...
Click to collapse
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG

Sari95 said:
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG
Click to expand...
Click to collapse
what version of arhd?

alray said:
what version of arhd?
Click to expand...
Click to collapse
The latest I believe:
"Android_Revolution_HD-One_71.1"

Sari95 said:
The latest I believe:
"Android_Revolution_HD-One_71.1"
Click to expand...
Click to collapse
have you checked md5 just in case?

[HELP] Soft Brick M7wls

Okay, so yesterday I came into an HTC One that was on Sprint. I have an AT&T micro sim so naturally I went to work to root, s-off, etc. so I could Simunlock it. I did it all and then started to install a custom rom. Android 4.4.2 Kitkat. got stuck in a bootloop, went to wipe cache and accidentally wiped the whole system and everything pretty much.
I think something is wrong with the partitions. Maybe some corrupted data along the line with all my..mess ups.
I should've researched more before I delve into this and I'm getting a lot of knowledge out of this but it's not enough.
It would be highly appreciated if someone could help me out. I've read countless threads, tried to redo the RUU or something. Nothing to avail and I can't sideload because my adb won't work in cmd for some reason.
here's a lil info from the getvarall command from the All in One Kit exe:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 1.00.20.1108
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: edit
imei: edit
meid: edit
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
If you need more info, just ask. I'll do all I can, but I'm pretty novice with this. *sigh*

OneLyfe said:
Okay, so yesterday I came into an HTC One that was on Sprint. I have an AT&T micro sim so naturally I went to work to root, s-off, etc. so I could Simunlock it. I did it all and then started to install a custom rom. Android 4.4.2 Kitkat. got stuck in a bootloop, went to wipe cache and accidentally wiped the whole system and everything pretty much.
I think something is wrong with the partitions. Maybe some corrupted data along the line with all my..mess ups.
I should've researched more before I delve into this and I'm getting a lot of knowledge out of this but it's not enough.
It would be highly appreciated if someone could help me out. I've read countless threads, tried to redo the RUU or something. Nothing to avail and I can't sideload because my adb won't work in cmd for some reason.
here's a lil info from the getvarall command from the All in One Kit exe:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 1.00.20.1108
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: REMOVE
imei: REMOVE
meid:
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
If you need more info, just ask. I'll do all I can, but I'm pretty novice with this. *sigh*
Click to expand...
Click to collapse
First, please remove your IMEI and Serialno from your first post!
Follow the steps in this post, including the prerequisites.

OneLyfe said:
Okay, so yesterday I came into an HTC One that was on Sprint. I have an AT&T micro sim so naturally I went to work to root, s-off, etc. so I could Simunlock it. I did it all and then started to install a custom rom. Android 4.4.2 Kitkat. got stuck in a bootloop, went to wipe cache and accidentally wiped the whole system and everything pretty much.
I think something is wrong with the partitions. Maybe some corrupted data along the line with all my..mess ups.
I should've researched more before I delve into this and I'm getting a lot of knowledge out of this but it's not enough.
It would be highly appreciated if someone could help me out. I've read countless threads, tried to redo the RUU or something. Nothing to avail and I can't sideload because my adb won't work in cmd for some reason.
here's a lil info from the getvarall command from the All in One Kit exe:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 1.00.20.1108
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid:
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
If you need more info, just ask. I'll do all I can, but I'm pretty novice with this. *sigh*
Click to expand...
Click to collapse
dont post IMEI, MEID and SERIALNO
if you have used a toolkit from this forum, you probably have flashed an incompatible recovery and rom for a gsm variant (yours is cdma-sprint)
you'll have to flash a sprint (m7wls) recovery, format everything and then push and install a sprint rom
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
majmoz said:
First, please remove your IMEI and Serialno from your first post!
Follow the steps in this post, including the prerequisites.
Click to expand...
Click to collapse
thanks for sharing this guide:good:, but this is for the M7_U and UL. OP can use the guide but must make sure to flash a M7WLS recovery, not that one linked in the guide.
+
he will need to wipe + format data from recovery. flashing the wrong recovery probably screwed is data partition.

alray said:
dont post IMEI, MEID and SERIALNO
if you have used a toolkit from this forum, you probably have flashed an incompatible recovery and rom for a gsm variant (yours is cdma-sprint)
you'll have to flash a sprint (m7wls) recovery, format everything and then push and install a sprint rom
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
thanks for sharing this guide:good:, but this is for the M7_U and UL. OP can use the guide but must make sure to flash a M7WLS recovery, not that one linked in the guide.
+
he will need to wipe + format data from recovery. flashing the wrong recovery probably screwed is data partition.
Click to expand...
Click to collapse
I have TWRP 2.6.3.0 and as far as I know it's for M7wls. It won't let me mount cache or anything anymore. When I'm attempting to use adb the device won't show up on the list and I can't find it at all so I can't push roms over even with minimal adb and fastboot.
Is there something I'm missing?
I just miss having an OS so much.. lool

OneLyfe said:
I have TWRP 2.6.3.0 and as far as I know it's for M7wls. It won't let me mount cache or anything anymore. When I'm attempting to use adb the device won't show up on the list and I can't find it at all so I can't push roms over even with minimal adb and fastboot.
Is there something I'm missing?
I just miss having an OS so much.. lool
Click to expand...
Click to collapse
just to be sure flash this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
check md5 is good: b940a8e63bf1992b7a16546915c6bc7c
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp and check if you have adb connection:
Code:
adb devices
if not, re-install the drivers correctly (refer to the guide)
if ok then, push a WLS rom:
wipe everything + format data then:
Code:
adb push rom.zip /sdcard/
and install the rom

alray said:
just to be sure flash this one:
check md5 is good: b940a8e63bf1992b7a16546915c6bc7c
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp and check if you have adb connection:
Code:
adb devices
if not, re-install the drivers correctly (refer to the guide)
if ok then, push a WLS rom:
wipe everything + format data then:
Code:
adb push rom.zip /sdcard/
and install the rom
Click to expand...
Click to collapse
I can't get ADB to work for the life of me. I tried uninstalling HTC Sync, reinstalled drivers, then tried to install drivers in device manager.
Don't i have to have an OTG USB for adb to even work in cmd..?

OneLyfe said:
I can't get ADB to work for the life of me. I tried uninstalling HTC Sync, reinstalled drivers, then tried to install drivers in device manager.
Don't i have to have an OTG USB for adb to even work in cmd..?
Click to expand...
Click to collapse
Did fastboot work and did you install twrp 2.6.3.0 successfully? If yes, did you boot into recovery before checking ADB Devices? If no, then try booting into recovery and follow the steps @alray laid out for you. And no, you don't need a OTG cable to use adb commands you just need the USB cable attached to your computer and phone.

If you are stuck with a wiped system partition, then there is no android there for ADB to talk to. From the Bootloader, you need to use fastboot commands to flash a new recovery first. Are you in the bootloader? Do you have fastboot connectivity in the bootloader? Flashing a proper recovery suited to m7wls should fix your partitions and get you on the way to a successful rom flash.

1262
dougeedug said:
If you are stuck with a wiped system partition, then there is no android there for ADB to talk to. From the Bootloader, you need to use fastboot commands to flash a new recovery first. Are you in the bootloader? Do you have fastboot connectivity in the bootloader? Flashing a proper recovery suited to m7wls should fix your partitions and get you on the way to a successful rom flash.
Click to expand...
Click to collapse
Yes I wiped the system partition somehow in all of this. I have TWRP 2.6.3.0, I've tried from the recovery main menu like it says. Nothing.
adb devices comes up with no list.
adb usb says it cannot find it.
and fastboot works with recovery images, but it won't load a zip.
sooo it's probably my drivers or..?
cause adb is the only thing I need working to fix all of this, I believe. -__-

[SOLVED] Can anyone help me fix my htc one m7?

I recently acquired an htc one m7. i decided it would be cool to root it and put a custom rom ( i have had experience in this i have done it on my s3 my galaxy tab 2.0 and a galaxy express) so i unlocked my bootloader, flashed a custom rom and rooted my device and i decided (stupidly) to erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching. i tried to gain s-off but with every solution i need to be booted up but i dont have an os so i cannot. i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors. i tried fastboot flashing it but it wont verify it. i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either. i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit. this did not work. ive tried different recovery (but not different versions of these recoveries) everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.

sethdrak3 said:
(...)erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching.
Click to expand...
Click to collapse
This is the most common situation here, no worries, it can be fixed easily.
i tried to gain s-off
Click to expand...
Click to collapse
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
but with every solution i need to be booted up but i dont have an os so i cannot.
Click to expand...
Click to collapse
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors.
Click to expand...
Click to collapse
What is the error exactly? What is your TWRP recovery version? What rom exactly?
i tried fastboot flashing it but it wont verify it.
Click to expand...
Click to collapse
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either.
Click to expand...
Click to collapse
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit.
Click to expand...
Click to collapse
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
Click to expand...
Click to collapse
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?

alray said:
This is the most common situation here, no worries, it can be fixed easily.
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
i thought i heard somewhere you needed s off to flash roms
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
What is the error exactly? What is your TWRP recovery version? What rom exactly?
my twrp is v2.6.0.1 and im trying to flash cm12
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i understand this now i was trying ever possibility and how do you get to RUU mode?
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
(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: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35XW916185
(bootloader) imei: 354439055703575
(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: 3664mV
(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!
finished. total time: 0.040s
output from command "fastboot getvar all"
@alray
thank you for all your help. btw the toolkit is very useful for small things like writing new recoveries it makes it easier plus sometimes its less problematic
Click to expand...
Click to collapse

sethdrak3 said:
i thought i heard somewhere you needed s off to flash roms
Click to expand...
Click to collapse
No, you only need an unlocked bootloader + custom recovery installed.
my twrp is v2.6.0.1 and im trying to flash cm12
Click to expand...
Click to collapse
TWRP 2.6.0.1 is really outdated. Latest official version is 2.8.6.0 or (2.8.6.4 unofficial) and since 2014-05-01 you need at least twrp 2.7.0.8 to flash Cyanogenmod
i understand this now i was trying ever possibility and how do you get to RUU mode?
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
but it won't help flashing roms, only for signed RUU and Signed firmware same or newer version that match your CID, MID and base version( x.xx.502.x) so 3.17.502.3 or above
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
If you want to flash CM12, update your recovery.
You might want to read this, this and this
TWRP can be downloaded from here and here

thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.

sethdrak3 said:
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
Click to expand...
Click to collapse
you're welcome, that's one example why we are not suggesting to use any toolkits.
can you edit your title to "[SOLVED] Can anyone help me fix my htc one m7?" (go to your first post, click "edit" then click "go advanced" change your title and click "save changes) thanks

HELP !! HTC ONE M7 Bricked, with Recovery

hello guys, i got htc one m7, today, i rooted the phone and installed the twrp recovery, then rebooted to system and was working fine until i installed the modified rom "NuSenSeven", it successfully installed the rom but when i restarted the phone it stuck on boot animation and then rebooted and entered the recovery, i tried to wipe cache, data, factory reset, reboot, it still didn't worked, i installed the rom again with the different settings, and it still isn't working and unfortunately when i connect phone to computer, it cannot be detected. i have 2 laptops and it was working on both of them before it got stuck. Can anyone help me to fix it?
Thanks in advance.

TAT1SHA said:
hello guys, i got htc one m7, today, i rooted the phone and installed the twrp recovery, then rebooted to system and was working fine until i installed the modified rom "NuSenSeven", it successfully installed the rom but when i restarted the phone it stuck on boot animation and then rebooted and entered the recovery, i tried to wipe cache, data, factory reset, reboot, it still didn't worked, i installed the rom again with the different settings, and it still isn't working and unfortunately when i connect phone to computer, it cannot be detected. i have 2 laptops and it was working on both of them before it got stuck. Can anyone help me to fix it?
Thanks in advance.
Click to expand...
Click to collapse
What recovery version do you have?

donkeykong1 said:
What recovery version do you have?
Click to expand...
Click to collapse
I used the one from all in-one toolkit, i have no idea what version it is. also i tried to connect otb but it doesnt lets me use the otg neither. I wish it had a sd-card slot, it would escalate it easily.

TAT1SHA said:
I used the one from all in-one toolkit, i have no idea what version it is. also i tried to connect otb but it doesnt lets me use the otg neither. I wish it had a sd-card slot, it would escalate it easily.
Click to expand...
Click to collapse
Go into recovery and at the top of the screen is version number

donkeykong1 said:
Go into recovery and at the top of the screen is version number
Click to expand...
Click to collapse
TWRP v2.7.1.0a

TAT1SHA said:
TWRP v2.7.1.0a
Click to expand...
Click to collapse
I think your recovery is old. Find a newer version for your phone and flash it via recovery. You are on T-mobile, right?

Almost like something happens.
With HTC PN07200 (searching the model is a HTC ONE M7). I wanted to put a different rom.
The equipe was with the Bootloader "Locked", "S-Off" and "1111 user" (by what I read is superuser).
With the tools unlock "One_All-In-One_Kit_v3.1" or other downloadable for this model ...
Since fastboot command console and unlockcode .... I got to the "Unlocked" STEP 1 OK !!!
As recovery was already the "TWRP 2.5.0.0" try putting seven different ROMs without success.
Android_Revolution_HD-One_84.0.zip
Android_Revolution_HD-One_92.0_4a9d05.zip
Guru_Reset_M7_3.22.1540.1.zip
HTC_One_-_MaximusHD_53.0.0.zip
NuSenSeveN-LP-m7-gsm_v4.02_050715.zip
One_M7_7.15.401.1_stock_system_dump.zip
Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
The installation within TWRP is done without problems, you do not give error messages. But when asked reboot was presented with all of the 3 problem I describe them ...
or catch, white screen with HTC logo with a small and short vibration, black screen 3 seconds and again the white screen with HTC logo with a small and short vibration (bootloop)
or white screen with HTC logo with a small and short vibration and screen goes black.
or log in directly and fast recovery.
I tried without success to achieve other recovery programs from loading them into recovery Fastboot (fastboot flash recovery /// xxx.img fastboot erase cache)
TWRP 2.5.0.0.img
TWRP 2.7.0.0.img
TWRP 2.8.7.0.img
OpenRecovery-TWRP-2.5.0.0-m7wls.img
OpenRecovery-TWRP-2.7.0.0-m7.img
This team does not have external SD card, so did everything from internal memory, and also tried to OTG cable pendrive, without success.

donkeykong1 said:
I think your recovery is old. Find a newer version for your phone and flash it via recovery. You are on T-mobile, right?
Click to expand...
Click to collapse
I cant connect the phone to pc, its undetectable on all 3 laptops i got, i downloaded and installed about 3 different HTC drivers but it still isn't detected, i have bootloader unlocked and cid 1111, and S-off just in case if you might need to know that too

slash22toly said:
Almost like something happens.
With HTC PN07200 (searching the model is a HTC ONE M7)
Click to expand...
Click to collapse
PN0720000 is a Sprint CDMA HTC One.
I wanted to put a different rom.
Click to expand...
Click to collapse
So you need to use roms that are compatible with the Sprint HTC One (CDMA)
The equipe was with the Bootloader "Locked", "S-Off" and "1111 user" (by what I read is superuser).
Click to expand...
Click to collapse
11111111 is SuperCID not SuperUser, these are 2 different things. SuperCID allows the phone to bypass the CID check when flashing a RUU that was not made for your phone. Pretty useless for the Sprint M7 imo since you can only flash Sprint RUU because others ruu are not compatible with Sprint HTC one but anyway its ok to have superCID, you can keep it like that.
With the tools unlock "One_All-In-One_Kit_v3.1" or other downloadable for this model ...
Since fastboot command console and unlockcode .... I got to the "Unlocked" STEP 1 OK !!!
Click to expand...
Click to collapse
You might to use adb and fastboot directly from a command window using the latest android sdk tools. These toolkits are not up-to-date and not ideal when having issues. The other major issue with this toolkit is that its for the GSM M7 not for the Sprint variant.
As recovery was already the "TWRP 2.5.0.0" try putting seven different ROMs without success.
Android_Revolution_HD-One_84.0.zip ---> Its a rom for GSM htc one M7 (M7_UL or M7_U). You have a sprint M7 (M7WLS)
Android_Revolution_HD-One_92.0_4a9d05.zip ---> Its a rom for GSM htc one M7 (M7_UL or M7_U). You have a sprint M7 (M7WLS)
Guru_Reset_M7_3.22.1540.1.zip ---> Its a rom for GSM htc one M7 Developer edition PN0712000 not PN0720000
HTC_One_-_MaximusHD_53.0.0.zip ---> For GSM
NuSenSeveN-LP-m7-gsm_v4.02_050715.zip ---> For GSM
One_M7_7.15.401.1_stock_system_dump.zip ---> For GSM
Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip ---> Its an RUU for Sprint HTC one. RUU are not flashed using custom recovery, its flashed using fastboot.
Click to expand...
Click to collapse
The installation within TWRP is done without problems, you do not give error messages. But when asked reboot was presented with all of the 3 problem I describe them ...
or catch, white screen with HTC logo with a small and short vibration, black screen 3 seconds and again the white screen with HTC logo with a small and short vibration (bootloop)
or white screen with HTC logo with a small and short vibration and screen goes black.
or log in directly and fast recovery.
Click to expand...
Click to collapse
All these errors are caused by flashing a GSM rom on a CDMA phone.
I tried without success to achieve other recovery programs from loading them into recovery Fastboot (fastboot flash recovery /// xxx.img fastboot erase cache)
TWRP 2.5.0.0.img
TWRP 2.7.0.0.img
TWRP 2.8.7.0.img
OpenRecovery-TWRP-2.5.0.0-m7wls.img
OpenRecovery-TWRP-2.7.0.0-m7.img
Click to expand...
Click to collapse
You can only flash recoveries that are compatible with Sprint HTC One M7, in that above list, only that one ending with "m7wls.img" should work. To flash a recovery you have to use:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Better to post the output of "fastboot getvar all" so we can know everything about your phone, stop the confusion and direct you to a rom/recovery and instructions that will work with your phone. When posting the output of "fastboot getvar all", censor your IMEI, MEID and SERIALNO, you don't want to post these values on the forums. Other values will help determining what you can flash and how.

alray said:
PN0720000 is a Sprint CDMA HTC One.
So you need to use roms that are compatible with the Sprint HTC One (CDMA)
Click to expand...
Click to collapse
This little detail much explains my problem. Thanks
alray said:
Better to post the output of "fastboot getvar all" so we can know everything about your phone, stop the confusion and direct you to a rom/recovery and instructions that will work with your phone. When posting the output of "fastboot getvar all", censor your IMEI, MEID and SERIALNO, you don't want to post these values on the forums. Other values will help determining what you can flash and how.
Click to expand...
Click to collapse
Here is the data...
Code:
E:\ROMs\HTC One m7\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4056mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
alray said:
You might to use adb and fastboot directly from a command window using the latest android sdk tools. These toolkits are not up-to-date and not ideal when having issues. The other major issue with this toolkit is that its for the GSM M7 not for the Sprint variant.
Click to expand...
Click to collapse
In the directory, I use a command console, and write fastboot... etc.
Code:
Directorio de E:\ROMs\HTC One m7\One_All-In-One_Kit_v3.1\HTC\Data
09/10/2015 10:13 <DIR> .
09/10/2015 10:13 <DIR> ..
19/08/2012 01:00 846.848 aapt.exe
19/08/2012 01:00 191.488 adb.exe
19/08/2012 01:00 96.256 AdbWinApi.dll
19/08/2012 01:00 60.928 AdbWinUsbApi.dll
20/05/2013 04:03 1.151.546 APKBIT.exe
20/11/2010 22:23 345.088 cmd.exe
05/10/2015 17:19 1.345 Data - Acceso directo.lnk
19/08/2012 01:00 140.800 fastboot.exe
01/04/2012 00:53 186 mainver_fix.bat
19/02/2012 01:24 656.708 misctool
19/02/2012 08:41 4.526 misctool.c
07/10/2015 14:50 1.288.121.395 One.zip
28/07/2013 13:43 <DIR> Recoveries
07/10/2015 14:40 1.204.676.279 Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
28/07/2013 13:42 <DIR> SU
06/10/2015 10:48 1.360.737 Superuser.zip
14 archivos 2.497.654.130 bytes
4 dirs 60.303.917.056 bytes libres
alray said:
You can only flash recoveries that are compatible with Sprint HTC One M7, in that above list, only that one ending with "m7wls.img" should work. To flash a recovery you have to use:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ok. i will use that
alray said:
Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip ---> Its an RUU for Sprint HTC one. RUU are not flashed using custom recovery, its flashed using fastboot.
Click to expand...
Click to collapse
So, I don´t need to use a twpr to flash the phone?. but from fastboot, how can i flash a .ZIP file? I thought i needed a .IMG
------------------------------------------------------------------------------------
I just installed ok the OpenRecovery-TWRP-2.5.0.0-m7wls.img. it´s running ok
I unzipped file Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip ....
Code:
adb.exe
AdbWinApi.dll
android-info.txt
ARUGlobal.dll
ARUWizard.exe
ARUWizard.ini
ARUWizard_ARA.lng
ARUWizard_BrPt.lng
ARUWizard_Cze.lng
ARUWizard_Dan.lng
ARUWizard_Dut.lng
ARUWizard_Eng.lng
ARUWizard_EuPt.lng
ARUWizard_EuSpa.lng
ARUWizard_FIN.lng
ARUWizard_Fra.lng
ARUWizard_Ger.lng
ARUWizard_Grk.lng
ARUWizard_Ita.lng
ARUWizard_Jap.lng
ARUWizard_Nor.lng
ARUWizard_Pol.lng
ARUWizard_Rus.lng
ARUWizard_SC.lng
ARUWizard_Svk.lng
ARUWizard_TC.lng
ARUWizard_Thai.lng
ARUWizard_TRK.lng
default.pal
DIFxData.ini
DMData00.DAT
DMData01.DAT
DMData02.DAT
DMData03.DAT
DMData04.DAT
DMData05.DAT
DMData06.DAT
DMData07.DAT
DMData08.DAT
DMData09.DAT
DOL_RECOVERY02_01.bmp
FontData.ini
htc_fastboot.exe
isrt.dll
MonitorConsole.exe
PHONE.bmp
ReadMe_ARA.doc
ReadMe_BrPt.doc
ReadMe_Cze.doc
ReadMe_Dan.doc
ReadMe_Dut.doc
ReadMe_Eng.doc
ReadMe_EuPt.doc
ReadMe_EuSpa.doc
ReadMe_FIN.doc
ReadMe_Fra.doc
ReadMe_Ger.doc
ReadMe_Grk.doc
ReadMe_Ita.doc
ReadMe_Jap.doc
ReadMe_Nor.doc
ReadMe_Pol.doc
ReadMe_Rus.doc
ReadMe_SC.doc
ReadMe_Svk.doc
ReadMe_TC.doc
ReadMe_Thai.doc
ReadMe_TRK.doc
rom.zip
setup.inx
StringTable_0x0409.ips
UPD_RECOVERY00_01.bmp
UPD_RECOVERY01_01.bmp
UPD_RECOVERY02_01.bmp
UPD_RECOVERY03_01.bmp
UPD_RECOVERY04_01.bmp
_isres_0x0409.dll
I ran the file "ARUWizard.exe" and ...
HTC Android Phone ROM Update Utility 2.0.5.2013, some steps ok,
Verify that you want to apdate the ROM version from 4.06.651.9 to 3.04.651.2, ok
Some steps before, the ERROR [155]: UNKNOWN ERROR (the rom update cannot update. Please get the correct ROM update utility).

slash22toly said:
Code:
E:\ROMs\HTC One m7\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4056mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
So, I don´t need to use a twpr to flash the phone?. but from fastboot, how can i flash a .ZIP file? I thought i needed a .IMG
Click to expand...
Click to collapse
If you flash a rom, you must flash it using twrp and make sure your twrp is for M7WLS variant and that the rom is also for that variant. If flashing a RUU, you must flash it using fastboot. Yes the ruu are zip files, all the required .img files are packed inside of it, you just need to flash the entire zip file. You can only flash ruu for sprint so*the ones that match with the sprint CID MID and version number x.xx.651.x <----- important since your phone is s-off. Make sure you are flashing the right files because with s-off, you can brick your phone easily if flashing a file that is not for your variant. Better to ask if you are unsure.
Code:
fastboot oem rebootRUU
fastboot flash zip your_ruu_name.zip
fastboot flash zip your_ruu_name.zip
fastboot reboot
That ruu is a downgrade btw but it should flash fine since your phone is s-off.

Im not shure the ruu files. I think it will be better, if i flash a custom ROM whith twpr. I only need to find a ROM for sprint m7wls.
What ROM do you recomend?

slash22toly said:
Im not shure the ruu files. I think it will be better, if i flash a custom ROM whith twpr. I only need to find a ROM for sprint m7wls.
What ROM do you recomend?
Click to expand...
Click to collapse
you can find Sprint HTC One M7 rom there: http://forum.xda-developers.com/sprint-htc-one/development
Make sure your phone have all the requirements before flashing a rom. Some roms like the Lollipop ones, requires to be on the latest firmware to be used, so if its the case you won't be able to flash those one, you'll probably be limited to kitkat roms.

alray said:
you can find Sprint HTC One M7 rom there: http://forum.xda-developers.com/sprint-htc-one/development
Click to expand...
Click to collapse
Well, my solution...
I Install in my PC the HTC One M7 driver MTP
By Fastboot, I install a TWPJ (twrp-2.8.7.0-m7.img)
Wipe ALL and format.
Install the last Cyanogenmod (CM11) custom ROM (https://download.cyanogenmod.org/get/jenkins/90464/cm-11-20141112-SNAPSHOT-M12-m7spr.zip)
Install a Gapps for 4.4 (ARM-4.4-Pico) (OpenGapp)
Install the Argentina Radio (Link)
It Run OK!!!!!!!!
---------- Post added at 03:20 PM ---------- Previous post was at 02:48 PM ----------
Well, my solution...
I Install in my PC the HTC One M7 driver MTP
By Fastboot, I install a TWPJ 2.8.7
Wipe ALL and format.
Install the last Cyanogenmod (CM11) custom ROM (download.cyanogenmod.org/get/jenkins/90464/cm-11-20141112-SNAPSHOT-M12-m7spr.zip)
Install a Gapps for 4.4 (ARM-4.4-Pico) (opengapps.org)
Install the Argentina Radio (androidfilehost.com/?fid=23159073880933335)
It Run OK!!!!!!!!