Database Info

Have I bricked my Desire S? [SOLVED]

I believe I may have bricked my Desire S also.
I rooted my Desire S through the official HTC method. (I have since relocked)
I then attempted to flash a custom ROM.
The custom ROM (Reaper 2.2) got stuck in (what I believe to be a boot loop) so I attempted to revert to the backup I made - that failed.
I did manage to get CyanogenMod 7 working but with missing functionality
Now I could not get beyond the white HTC screen (or the Black screen with the circle/number pattern on Reaper)
My desire S originally was on Vodafone (Ireland)
Whem I try to load the error is:
SD Checking
Loading...[PG88DIAG.zip]
No image!
Loading...[PG88DIAG.nbh]
No image or wrong image!
Loding...[PG88IMG.zip]
No image!
Loading...[PG88IMG.nbh]
No image or wrong image!
My phone was on 2.3.5 and Sense 3.0
Other details I obtained:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.161.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei:xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
I have spent hours upon hours trawling through forums, posts and guides but nothing has worked.
I have tried RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed.exe and got error [170]:device not detected and I have tried from the command line via fastboot....
I really need help here please.
OR is my Desire S totally bricked beyond repair

If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.

eyahl said:
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
Click to expand...
Click to collapse
this and bootloader need to be ****unlocked**** in order to boot custom rom, and ***re-locked*** when installing RUU

Thanks for the reply's guys.
I managed to get the RUU working this evening but the phone was still ***unlocked***... I got some error (didn't make note of it)
I will re-read both posts when I am not so tired and try the suggestions
Thanks again
(I will post my results)

Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom

GSR-James said:
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
Click to expand...
Click to collapse
Did you read what I wrote?? Do what I said or search forum about that if you need more information. It is definitely necessary, you won't succeed without flashing boot.img separately.
Sent by my fingers to your head.

I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?

GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
Yes, that's what I meant
Sent by my fingers to your head.

GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
YEs that sounds about right, although the full command is
Code:
fastboot flash boot boot.img

Thank you both for the reply's.
I will try this when I sober up in the morning

Now that I am sober I want to thank eyahl, nenad_l and ben_pyett for your input.
I managed to get the rom working last night (drunk and all as I was )
I am now running a MIUI rom
Baseband version: 20.4801.30.0822U_3822.10.08.04_M
I need to ask a couple more questions if I may?
The interface is not what I am used to and don't particularly like it. It reminds me of the UI I had on my old Galaxy I9000. Is this as a result of my kernel version?
Kernel version: [email protected]#1 Thur Oct 6 14:48:57 BST 2011
My understanding of what I have done by flashing the boot.img is that my kernel is that of the rom from where the boot.img was taken and the MIUI rom sits atop - is this correct?
So if I extract a boot.img from a different rom and then flash I will have a different kernel version and subsequently return my UI to (SENSE) that I'm more familiar to?
Sorry for the n00b questions but I am only learning about this at the moment
Thanks guys

No problem, and your understanding is not really correct, the UI is determined by the ROM not the boot image (which is ultimately the kernel), so to get sense back you need to flash a sense ROM like Endy
Every time you flash a new ROM simply flash the associated boot
You shouldn't flash a boot from one ROM under another, it's not mix and match, well that's not completely true.
Swyped form ym Dersie S unsig XAD Permuim

Thanks Ben.
I will look for the 'Endy' rom you suggested.
Ok, so I dl the zip, extract the boot.img, write it from cmd and then flash the rom like normal?
I find it very frustrating to find roms.....almost every time I select a rom to dl I'm redirected to a bad link or to a referral to another referral etc....
If anyone has a source for roms please post it!

Best source for roms is the development section here at desire s xda. Just look through the threads, you will find good quality and stable roms. Endy=endymion ROM
You can look to the index thread, additionally zac made a torrent thread where you can find torrents for the most used roms
Sent by my fingers to your head.

Thanks eyahl
I have dl Endy and will try it now.
I'll have a look where you suggested
Thanks

You must wipe your device (all partitions except sd) prior to each ROM flash
Swyped form ym Dersie S unsig XAD Permuim

Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again

GSR-James said:
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
Click to expand...
Click to collapse
You're welcome
Yes, you can mark the thread solved
Sent by my fingers to your head.

Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!

GSR-James said:
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
Click to expand...
Click to collapse
Go to your first post, click EDIT, then on the edit panel, click on ADVANCED and then modify the topic of your thread by adding [SOLVED] in front of it.
You're done.

Please help!! Stuck in fastboot after flashing a rom

I tried flashing CM10 onto my AT&T HOX and now I'm stuck in the fastboot menu (picture below)
Let me know what information I could supply that could help
C:\Users\temp\Downloads\OneXUnroot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.32.09.01_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.73.502.1
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4127mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s

Shows "relocked" what did you do there? Can you get into recovery.
Sent from my One X using xda premium

lost45 said:
I tried flashing CM10 onto my AT&T HOX and now I'm stuck in the fastboot menu (picture below)
Click to expand...
Click to collapse
Relocked + custom recovery = no boot

subarudroid said:
Shows "relocked" what did you do there? Can you get into recovery.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I was trying to follow some instructions from another website to flash it back to stock and I did a oem relock
And no I can't get into recovery, just the bootloader menu and the fastboot menu.

lost45 said:
I was trying to follow some instructions from another website to flash it back to stock and I did a oem relock
And no I can't get into recovery, just the bootloader menu and the fastboot menu.
Click to expand...
Click to collapse
You have to unlock again.

iElvis said:
You have to unlock again.
Click to expand...
Click to collapse
Could you point me in the right direction on how to do this from fastboot?
Edit: Just realized it has to be in fastboot to unlock the bootloader.
I'll post results after I do this.

lost45 said:
Could you point me in the right direction on how to do this from fastboot?
Click to expand...
Click to collapse
How did you do it the first time? You just flash the same unlock token you used before.

After I reunlock it should I flash the stock recovery?
Then what would my next step be?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

lost45 said:
After I reunlock it should I flash the stock recovery?
Then what would my next step be?
Click to expand...
Click to collapse
What are you trying to do? Flash CM?

iElvis said:
What are you trying to do? Flash CM?
Click to expand...
Click to collapse
At this point I'd like to flash anything that can work. If I can do CM10 that would be great.
Newest Update:
I have TWRP successfully running. How can I copy the .zip onto the sdcard now?

lost45 said:
At this point I'd like to flash anything that can work. If I can do CM10 that would be great.
Click to expand...
Click to collapse
Once you reunlock, you may or may not still have root. Open superuser or SuperSU (whatever you have installed), go into settings, and turn it off and back on again. Then check a root app to see if you're still rooted. If all you did was relock, you should still be rooted.
If that's the case, reboot to recovery and flash away. You have the old hboot so you don't need to worry about flashing boot.imgs.

ok, if you can get back to square 1 (any rom installed, any recovery installed) and get into bootloader and recovery you will be fine. remember when flashing a rom to the One X, you must do "fastboot flash boot boot.img" from terminal before you proceed and flash from twrp (or whatever recovery you use). otherwise it will flash but not boot.
so i recommend:
1. going into your recovery and clearing EVERYTHING (cache, dalvik, data) and then get back into fastboot mode.
2. running the "fastboot flash boot boot.img" from terminal on your PC
3. exiting bootloader and getting into recovery
4. flash the rom/gapps/root zips
if this doesnt work, then let me know. i'll try my best to help you out
EDIT: sorry, just saw that you had the old hboot.... never mind about all those steps :/ i honestly dont know what you should do next, since you dont need to flash the boot.img...

tyessen said:
ok, if you can get back to square 1 (any rom installed, any recovery installed) and get into bootloader and recovery you will be fine. remember when flashing a rom to the One X, you must do "fastboot flash boot boot.img" from terminal before you proceed and flash from twrp (or whatever recovery you use). otherwise it will flash but not boot.
so i recommend:
1. going into your recovery and clearing EVERYTHING (cache, dalvik, data) and then get back into fastboot mode.
2. running the "fastboot flash boot boot.img" from terminal on your PC
3. exiting bootloader and getting into recovery
4. flash the rom/gapps/root zips
if this doesnt work, then let me know. i'll try my best to help you out
EDIT: sorry, just saw that you had the old hboot.... never mind about all those steps :/ i honestly dont know what you should do next, since you dont need to flash the boot.img...
Click to expand...
Click to collapse
I have TWRP working now so I'm going to try to find a good ROM and flash it through recovery.
I'll let you know how it goes
UPDATE: Flashing CM10 with a nightly failed, it would just sit at the start up screen. I flashed the stable CM10 from here: http://get.cm/?device=evita&type=stable which worked!
Now I just need to flash gapps

lost45 said:
I have TWRP working now so I'm going to try to find a good ROM and flash it through recovery.
I'll let you know how it goes
Click to expand...
Click to collapse
ok, hope it works if you get it to work and it runs fine, make a backup in twrp so you always have a safety-blanket if something goes wrong someday

CM10 should boot fine just make sure you wiped everything and flash boot.img in fastboot

CM10 went on smoothly and its all set. Thanks for the help!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

You might want to edit your first post to take out your imei, serial # etc...
Sent from my HTC One XL using xda premium

iElvis said:
Once you reunlock, you may or may not still have root. Open superuser or SuperSU (whatever you have installed), go into settings, and turn it off and back on again. Then check a root app to see if you're still rooted. If all you did was relock, you should still be rooted.
If that's the case, reboot to recovery and flash away. You have the old hboot so you don't need to worry about flashing boot.imgs.
Click to expand...
Click to collapse
I know this is an old thread, but I have the same issue, but when I flash anything it just bootloops still. And my dalvik cache wipe always fails when I try to do that. I dunno why that is.

Read 4 posts up.. Flash boot.IMG first. And wipe everything
Sent from my One X using xda premium

HTC ONE SV Request/Help

Hi,
I have an HTC ONE SV and i tried to flash a stock rom but i haven't any experience with it, and now my device is stucked in boot loading screen.
For what i understand i can install a new stock rom with fastboot because also my recovery mode is corrupted and factory reset as well because when i try to enter it remains in "Loading Recovery Mode boot screen". Could someone help me with a fix and a stock rom for:
K2_UL XC SHIP S-OFF RH
CID - 11111111
HBOOT- 2.19.0000
RADIO - 1.15.49a.00.07
Also i have S-Off as you can see from above and Bootloader Unlocked.
Thanks,
I hope that someone can help me.

What stock Rom did you chose?
Try to flash the RUU
Old.Splatterhand posted the correct link.
Gesendet von meinem HTC One SV mit Tapatalk

Fabian2103 said:
What stock Rom did you chose?
Try to flash the RUU
Click to expand...
Click to collapse
Not so fast, before you tell people to use a RUU, tell them also, how to use. Otherwise people could be lost.
mrrrdude said:
Hi,
I have an HTC ONE SV and i tried to flash a stock rom but i haven't any experience with it, and now my device is stucked in boot loading screen.
For what i understand i can install a new stock rom with fastboot because also my recovery mode is corrupted and factory reset as well because when i try to enter it remains in "Loading Recovery Mode boot screen". Could someone help me with a fix and a stock rom for:
K2_UL XC SHIP S-OFF RH
CID - 11111111
HBOOT- 2.19.0000
RADIO - 1.15.49a.00.07
Also i have S-Off as you can see from above and Bootloader Unlocked.
Thanks,
I hope that someone can help me.
Click to expand...
Click to collapse
I think it could be solved without RUU.
It seems (because of your hboot), you had already the update to Android 4.2.2? Can you tell us which software you were running? Or if you are using an european k2ul? Or any other information could be important.
Please try to use/flash this recovery for flashing a rom:
http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
You have to flash with fastboot. It is made to work also on your hboot.

old.splatterhand said:
Not so fast, before you tell people to use a RUU, tell them also, how to use. Otherwise people could be lost.
I think it could be solved without RUU.
It seems (because of your hboot), you had already the update to Android 4.2.2? Can you tell us which software you were running? Or if you are using an european k2ul? Or any other information could be important.
Please try to use/flash this recovery for flashing a rom:
http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
You have to flash with fastboot. It is made to work also on your hboot.
Click to expand...
Click to collapse
I don't really know if i had the update to Anroid 4.2.2 in Fast Boot Menu it sais OS-3.03.401.1? does that help you? and i think it's an european k2ul. After i flash this recovery image? what do i do next? i mean i want to revert the phone to stock but like i said the Recovery menu dosn't load is there any way to flash the recovery image and then install a stock rom through flasboot commands? i have found this post http://forum.xda-developers.com/showthread.php?t=2277112 and it sais that it's possible but i didn't have the recovery image, now i do but i'm still missing a stock rom that would work with my device.

You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.

old.splatterhand said:
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
Click to expand...
Click to collapse
Thank you, i will try this out and i will let you know if i make any progress

mrrrdude said:
Thank you, i will try this out and i will let you know if i make any progress
Click to expand...
Click to collapse
old.splatterhand said:
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
Click to expand...
Click to collapse
Hi,
The phone now boots into recovery so i'm on the right track thanks to you, but i don't know how to flash the stock rom? what do i need to do? i put the stock on a sd card and plug it in through an external cable and a card reader but i don't seem to find where is the file? Do i need to flash the boot.img from the zip file too? or rename the zip file somehow in the sd card?

You have to flash it from recovery.
First go (in recovery) to "Wipe"-> "Advanced Wipe" and wipe everything but sd card and internal sd card.
Put the rom on your sd card, choose "Install" and navigate to the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip.
Choose it and confirm with"Swipe to flash".
As you are S-off, you usually don't need to flash boot.img afterwards.
When flashing is done, Reboot.
Wait some minutes, first boot takes some time.

old.splatterhand said:
You have to flash it from recovery.
First go (in recovery) to "Wipe"-> "Advanced Wipe" and wipe everything but sd card and internal sd card.
Put the rom on your sd card, choose "Install" and navigate to the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip.
Choose it and confirm with"Swipe to flash".
As you are S-off, you usually don't need to flash boot.img afterwards.
When flashing is done, Reboot.
Wait some minutes, first boot takes some time.
Click to expand...
Click to collapse
It fails to wipe with this error: E:Unable to mount internal storage. do i need to place the sd card inside the phone?

Hmmm, strange. Yes, put your sd card into your phone. If the rom is there, you can't find it, if its not in the phone.
Go on and try to flash.

old.splatterhand said:
Hmmm, strange. Yes, put your sd card into your phone. If the rom is there, you can't find it, if its not in the phone.
Go on and try to flash.
Click to expand...
Click to collapse
I found my rom on the sd card but after a few seconds the installing fails because of the same error "unable to mount internal storage" is there a way to flash this rom through fastboot?

No.
Seems, something got corrupted on your device.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)

old.splatterhand said:
No.
Seems, something got corrupted on your device.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.19.0000
version-baseband: 1.15.40a.00.07
version-cpld: None
version-microp: None
version-main:
version-misc: XC SHIP S-OFF
meid:
product: k2_ul
platform: HBOOT-8930
modelid: PL8010000
cidnum: 11111111
battery-status: good
battery-voltage: 3909mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0049fc265e
hbootpreupdate: 11
gencheckpt: 0

Ok, i see what i wanted to see.
Because the rom will not flash, you should really try to flash the RUU.
To do that, you need to downgrade your hboot.
Please read and follow this guide, to downgrade hboot and flash the RUU afterwards.

old.splatterhand said:
Ok, i see what i wanted to see.
Because the rom will not flash, you should really try to flash the RUU.
To do that, you need to downgrade your hboot.
Please read and follow this guide, to downgrade hboot and flash the RUU afterwards.
Click to expand...
Click to collapse
Do i really need to change the supercid to downgrade the hboot as mentioned in the tutorials? because i can't do that because my device is only recognize in fastboot. when i hit the command adb devices my serial number is not shown. but in fastboot device is. or if i use command like su in adb i get an error message like this "error: device not found"

mrrrdude said:
Do i really need to change the supercid to downgrade the hboot as mentioned in the tutorials?
Click to expand...
Click to collapse
Supercid is fine, no need to change it.

old.splatterhand said:
Supercid is fine, no need to change it.
Click to expand...
Click to collapse
It WORKED LIKE A CHARM! THANK YOU! you are a real life saver! I could not have done it without you, thanks allot!

mrrrdude said:
It WORKED LIKE A CHARM! THANK YOU! you are a real life saver! I could not have done it without you, thanks allot!
Click to expand...
Click to collapse
Nice, so have fun with your new born device :laugh:

old.splatterhand said:
Nice, so have fun with your new born device :laugh:
Click to expand...
Click to collapse
Thank you, i will definitly

[Q] Q: Soft Brick Sprint HTC One M7 (nightmare)

Hello Community,
Let me begin by apologizing if I am in the wrong forum channel. I am new to the site kind of. I mostly sift through answers.
In this case I have not found anyone with my problem cause the wouldn't make the rookie mistake of forgetting to take a backup BEFORE flashing junk on their fancy phones.
Resources: I have latest TWRP, can access it and bootloader
Problem: :crying:
I have an HTC One M7 from Sprint. Currently all user data has been formatted (cause I am genius). I am able to lock and unlock bootloader. My phone is in S-ON (another dumb mistake I know). The device is recognized in fastboot but not in ABD and I cant figure out why not. superuser was deleted by the wipe. :crying:
Solutions Tried but Failed:
I have download the RUU for my phone (or at least I think *651.10 and *651.7) and tried to run the setup.exe in admin mode while my phone was locked in fastboot... This resulted in an Error:155
I have tried flashing the same RUU from cmd prompt... this resulted in remote 12: signature error (still dont know what that means)
I have tried achieving S-OFF but alas I cant get my device to be recognized by ABD, I dont have an OS for internet/radio signal
I am starting to think I may have just effed everything up.
fastboot getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA
imei: 99*
meid: 99*
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4237mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
PLEASE HELP

nbranch1311 said:
Hello Community,
Let me begin by apologizing if I am in the wrong forum channel. I am new to the site kind of. I mostly sift through answers.
In this case I have not found anyone with my problem cause the wouldn't make the rookie mistake of forgetting to take a backup BEFORE flashing junk on their fancy phones.
Resources: I have latest TWRP, can access it and bootloader
Problem: :crying:
I have an HTC One M7 from Sprint. Currently all user data has been formatted (cause I am genius). I am able to lock and unlock bootloader. My phone is in S-ON (another dumb mistake I know). The device is recognized in fastboot but not in ABD and I cant figure out why not. superuser was deleted by the wipe. :crying:
Solutions Tried but Failed:
I have download the RUU for my phone (or at least I think *651.10 and *651.7) and tried to run the setup.exe in admin mode while my phone was locked in fastboot... This resulted in an Error:155
I have tried flashing the same RUU from cmd prompt... this resulted in remote 12: signature error (still dont know what that means)
I have tried achieving S-OFF but alas I cant get my device to be recognized by ABD, I dont have an OS for internet/radio signal
I am starting to think I may have just effed everything up.
fastboot getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA
imei: 99*
meid: 99*
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4237mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
PLEASE HELP
Click to expand...
Click to collapse
As long as you're S-ON you may only flash a RUU thats the same version or newer as installed on your phone. The RUUs you tried are older than the installed firmware. A backup that yu can restore via recovery should work.
Have you been on Android 4.3? This is the latest available RUU -> http://dl3.htc.com/application/RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2_Radio_1.00.20.0913_3_NV_SPCS_4.38_003_release_335355_signed_2.exe

no backup
LS.xD said:
As long as you're S-ON you may only flash a RUU thats the same version or newer as installed on your phone. The RUUs you tried are older than the installed firmware. A backup that yu can restore via recovery should work.
Click to expand...
Click to collapse
Thank you for responding so quickly. I do not have a backup like I said. I dont know what version of RUU to get cause none of them work. If you know of the right RUU that would be AWESOME (HTC One M7 Sprint) so then I can up-date that in to my solutions tried.
Again thank you for helping.

nbranch1311 said:
Thank you for responding so quickly. I do not have a backup like I said. I dont know what version of RUU to get cause none of them work. If you know of the right RUU that would be AWESOME (HTC One M7 Sprint) so then I can up-date that in to my solutions tried.
Again thank you for helping.
Click to expand...
Click to collapse
Have yu been on Android 4.3 before? Have you checked the RUU i posted? That the latest available. BTW you'll have to flash stock recovery before you run the RUU!

LS.xD said:
Have yu been on Android 4.3 before? Have you checked the RUU i posted? That the latest available. BTW you'll have to flash stock recovery before you run the RUU!
Click to expand...
Click to collapse
No I have not gone to Android 4.3 site. I will check it now. Also sorry I saw your RUU right after I replied. As for flashing the stock recovery I assume I can find the file for that Android 4.3? orrr is it already in TWRP.

nbranch1311 said:
No I have not gone to Android 4.3 site. I will check it now. Also sorry I saw your RUU right after I replied. As for flashing the stock recovery I assume I can find the file for that Android 4.3? orrr is it already in TWRP.
Click to expand...
Click to collapse
The RUU contains ALL you need. Flash stock recovery via fastboot. Then relock bootloader. Then run the RUU while phone is connected in fastboot mode. It will delete al changes and set ALL phone files to stock. TWRP will be gone, root, erros, your data...

LS.xD said:
The RUU contains ALL you need. Flash stock recovery via fastboot. Then relock bootloader. Then run the RUU while phone is connected in fastboot mode. It will delete al changes and set ALL phone files to stock. TWRP will be gone, root, erros, your data...
Click to expand...
Click to collapse
I can't seem to find the stock recovery. I am sucking at the internet

nbranch1311 said:
I can't seem to find the stock recovery. I am sucking at the internet
Click to expand...
Click to collapse
Its contained in the RUU. When you open the RUU you have to go to windows temp directory. There are two folders created by the ruu. One folder conatins a rom.zip. Open it with winrar to extract the recovery.img.

LS.xD said:
Its contained in the RUU. When you open the RUU you have to go to windows temp directory. There are two folders created by the ruu. One folder conatins a rom.zip. Open it with winrar to extract the recovery.img.
Click to expand...
Click to collapse
I searched the RUU you sent me but its an exe. All it does is start up. I hate to be a pain but could you please send me the latest image I need. Starting to freak out cause I think I am doing all this right and its still not working. I dont know.

Received my pm?
Sent from my beloved HTC One S using (most time buggy) Tapatalk

nbranch1311 said:
I searched the RUU you sent me but its an exe. All it does is start up. I hate to be a pain but could you please send me the latest image I need. Starting to freak out cause I think I am doing all this right and its still not working. I dont know.
Click to expand...
Click to collapse
I think you gave me a virus... This deleted pretty every local folder on my machine... Thank you?

nbranch1311 said:
I think you gave me a virus... This deleted pretty every local folder on my machine... Thank you?
Click to expand...
Click to collapse
Are you kidding me?
I posted link to the RUU for your phone lol. Thats not a virus...
If you check the link again --> ITS FROM OFFICIAL HTC.COM!!!

LS.xD said:
Are you kidding me?
I posted link to the RUU for your phone lol. Thats not a virus...
If you check the link again --> ITS FROM OFFICIAL HTC.COM!!!
Click to expand...
Click to collapse
Look man I am just tell you what I see. Literally every folder in my library has been delete. I will send a screen shot.
As soon as I tried to unhide temp folder it freaked out and I cant even find me as a user... freaking out. worried about my phone now my comp is pretty much empty. LOL its like having a brand new computer but i have all my apps

nbranch1311 said:
Look man I am just tell you what I see. Literally every folder in my library has been delete. I will send a screen shot.
As soon as I tried to unhide temp folder it freaked out and I cant even find me as a user... freaking out. worried about my phone now my comp is pretty much empty. LOL its like having a brand new computer but i have all my apps
Click to expand...
Click to collapse
I really have no clue what you did with your machine BUT i'm pretty SURE that offficial HTC software from official HTC.COM website won't contain any harmfull software, malware, viruses and so on!!! So just think about it before you start blaming me, while i'm trying to help you.
BTW
I'm downloading the file on my own now, just to be REALLY SURE its fine.
Also i can extract the recovery.img and upload it (If you're still interested... )

LS.xD said:
I really have no clue what you did with your machine BUT i'm pretty SURE that offficial HTC software from official HTC.COM website won't contain any harmfull software, malware, viruses and so on!!! So just think about it before you start blaming me, while i'm trying to help you.
BTW
I'm downloading the file on my own now, just to be REALLY SURE its fine.
Also i can extract the recovery.img and upload it (If you're still interested... )
Click to expand...
Click to collapse
I am interested but I dont know what I would do with them at the moment. literally every file i had personally is gone. I open the option to show all folders and all my folders are empty from the ones I can open. I lost everything. I dont know what happened. All I did was try to unhide hidden folders to see the temp folder

nbranch1311 said:
I am interested but I dont know what I would do with them at the moment. literally every file i had personally is gone. I open the option to show all folders and all my folders are empty from the ones I can open. I lost everything. I dont know what happened. All I did was try to unhide hidden folders to see the temp folder
Click to expand...
Click to collapse
You probably have manually changed or deleted files. I never suggested to do so! You can easily open temp by typing %temp% ! The files are just accessable while the RUU is opened.
I'm opening RUU now to check it for viruses...

nbranch1311 said:
I am interested but I dont know what I would do with them at the moment. literally every file i had personally is gone. I open the option to show all folders and all my folders are empty from the ones I can open. I lost everything. I dont know what happened. All I did was try to unhide hidden folders to see the temp folder
Click to expand...
Click to collapse
Ok...so lol lets say I fixed it and gave you a giant freaken apology for claiming you gave me a virus...I wont go into what dumb-a thing I did I will just say I have my folders and files.
Sooo about that img file.
Dude seriously I feel like bunk and wish I could do something to make it up

LS.xD said:
You probably have manually changed or deleted files. I never suggested to do so! You can easily open temp by typing %temp% ! The files are just accessable while the RUU is opened.
I'm opening RUU now to check it for viruses...
Click to expand...
Click to collapse
If you figure this phone bullcrap out I will donate. I just need my phone back. So I need what ever needs to be done to get this back to stock so I can remake mistakes on it

nbranch1311 said:
If you figure this phone bullcrap out I will donate. I just need my phone back. So I need what ever needs to be done to get this back to stock so I can remake mistakes on it
Click to expand...
Click to collapse
I have checked the RUU. Its locked to extract recovery. I'm just downloading the decrypted version. Just have some patientce. I'll post link as soon as i can
EDIT:
Here is the right firmware (It conatins e.g. recovery.img) --> LINK
And I just minded that THIS is the latest RUU.
Please download both files. Just calm down, your phone will be fine again soon
Installation:
1. connect your phone in fastboot mode
2. flash the "recovery.img" contained in the "firmware.zip" via fastboot (Fastboot flash recovery recovery.img)
3. Reboot bootloader (Fastboot reboot-bootloader)
4. Re-lock bootloader (Fastboot oem lock)
5. Reboot bootloader (Fastboot reboot-bootloader)
6. Run the RUU while phone is still connected
7. Thats all. If you proceed in the described way, your phone will be and fully working again

LS.xD said:
I have checked the RUU. Its locked to extract recovery. I'm just downloading the decrypted version. Just have some patientce. I'll post link as soon as i can
EDIT:
Here is the right firmware (It conatins e.g. recovery.img) --> LINK
And I just minded that THIS is the latest RUU.
Please download both files. Just calm down, your phone will be fine again soon
Click to expand...
Click to collapse
Does this matter
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s

Bootloop - unable to get to recovery - maybe no OS?

Folks, 7 rooted devices over last 7 years, and I have usually been able to find a solution without having to start a new thread... however, this time... I better get an expert opinion.
Essentially, here are the facts... I was flashing a rom yesterday on my wife's m8, and the wifi would not work. I thought about it, and then figured it likely was that I had not updated to latest TWRP prior to flashing. So I restored an old backup, I think the one I made right after rooting, which was 1.5 yrs ago, maybe more. That flashed fine, except after many tries via many methods, I could not get TWRP updated, and in fiddling around, I clicked update software, which downloaded the Verizon kitkat update, and started installing it... that was a mistake, finger too fast notwithstanding... I did not need to do it at all, since I was going to flash something new anyway right after updating recovery. Anyway phone appeared to be stuck, I powered it off (Vol up + Power) and went into bootloader (Vol down while it powered up) to go back into recovery and start over. However, the phone went into a boot loop and has since given me much grief over the past few hours.
Output from getvar all is below. It appears to be missing the OS - which kind of makes sense, if I interrupted it midway through something. The phone neither boots, and refuses to enter recovery - even after flashing recovery using fastboot as well as the Hasoon All in One tool. I also cleared cache. I suspect the recovery is loading, but is hidden behind the boot loop screen (is that possible? not sure, just a guess) because the phone has haptic feedback where the TWRP buttons would be - FWIW.
What should my next steps be? Please advise...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: dottat was here
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: ###
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s

First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.

cntryby429 said:
First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.
Click to expand...
Click to collapse
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'

montropistic said:
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'
Click to expand...
Click to collapse
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk

dottat said:
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.

montropistic said:
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.
Click to expand...
Click to collapse
could be a bad download of the RUU

andybones said:
could be a bad download of the RUU
Click to expand...
Click to collapse
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?

montropistic said:
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?
Click to expand...
Click to collapse
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103

andybones said:
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?

montropistic said:
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?
Click to expand...
Click to collapse
Either way works the same - which one your more comfortable with.

andybones said:
Either way works the same - which one your more comfortable with.
Click to expand...
Click to collapse
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...

montropistic said:
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...
Click to expand...
Click to collapse
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk

dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK - Yeah - it is running very nice right now, Clean Rom loaded fine, and all systems seem ok. However, per your advice, I will run the RUU again. FWIW, I had grabbed the version with the patch.

dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK, so I finally got around to this. I ran the RUU again, and got a fail on Userdata, and finally the same message at the end, partition update failed - power to reboot.
I let the phone boot, and then ran the RUU again, by straightaway going back into bootloader. This time, no fails, everything went through as per spec.
Thanks for insisting on re RUU. Seems like something was off, and iterating over it cured it finally. You rock, dottat.