Database Info

[Q] Desire S problems after flashing RUU

Hi Guys.
Before i start i want to mention that i searched everywhere and basically all these technical guide's and terms makes me even more confused and i don't really know what to do with this problem i have.
Ok here we go, last night i S-Off and Rooted my cousin's HTC Desire S with (revolutionary-0.4pre4 and Superuser-3.0.7-efghi-signed).
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
So far so good, this all worked fine. No problems.
After that i installed the "RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed"
It was successfully flashed but here is where the problems started, after this i got the famous "stuck on white background with green HTC Logo"
Now to make things worse, i cannot access SD Card from the phone and it will not recognize my phone anymore from my PC (with ADB drivers installed).
The only thing that does work and recognize my phone is the "Fastboot USB" mode on my phone along with the "
ROM Upgrade Utility (RUU) - Aruwizard.exe"
I got a tons of errors and problems.
1. HBOOT gives
SD Checking...
Loading... [PG88DIAG.zip]
No image!
Loading... [PG88DIAG.nbh]
No image or wrong image!
Loading... [PG88IMG.zip]
2. in Recovery menu the following problems occur
E:Can't open /cache/recovery/command
Wipe data/factory reset gives
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Apply update from sdcard gives
-Invalid Operation-
Also i seem to have lost a few options in recovery after the RUU like "install zip from sd card" etc
My question is : Is there anything that can fix this or did the RUU bricked it completely?

I believe before flashing you were supposed to do a downgrade HBOOT using ENG HBOOT
Atleast thats what i did!

Revolutionary hboot has protection to prevent it from being overwritten, the way to change the hboot is to write it through recovery, but you also need to flash a recovery option (if none is available), through fastboot.
Basically, check if CWM or EXT4 are installed, if yes flash hboot through recovery (see the last 10 pages of the ENG HBOOT thread), if no, flash recovery through fastboot (see google), once recovery is installed, flash hboot, then proceed with RUU.

I tried this as well
http://forum.xda-developers.com/showthread.php?t=958968
But no luck either
fastboot oem rebootRUU (Gives grey HTC Logo on my phone)
C:\android>fastboot flash zip HTC_DESIRE_S_2.3.5-2.10.401.4.zip
sending 'zip' (337560 KB)...
OKAY [ 55.123s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 65.056s
Click to expand...
Click to collapse
Most other commands just give a "(bootloader) [ERR] Command error !!!" so i just ended it with "fastboot reboot"
So my guess is that is must have something to do with that HBOOT thing yes.
"adb devices" will not find any devices at all.
C:\android>fastboot flash hboot hboot.img
< waiting for device >
sending 'hboot' (1024 KB)...
OKAY [ 0.196s]
writing 'hboot'...
(bootloader) image update is bypassed! (cannot roll back hboot version)
OKAY [ 0.026s]
finished. total time: 0.222s
Click to expand...
Click to collapse
I don't know if i can put the other eng hboot back

"Fastboot devices" still gives me a serial number in cmd prompt so that still works.
Where can i find a recovery.img for the Desire S?
I found a whole list here but i don't know which one to pick?
download.clockworkmod.com/recoveries
i tried "recovery-clockwork-2.5.0.7-desirec.img"
C:\android>fastboot flash recovery recovery-clockwork-2.5.0.7-desirec.img
sending 'recovery' (2766 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 1.261s]
finished. total time: 1.727s
Click to expand...
Click to collapse
Problem now is, when i select "Recovery" from the hboot menu.. it gets stuck also at the White background / green HTC Logo screen. so now my recovery part is broken also?

Its all working now, i used the wrong recovery image at first.
I got clockwork recovery to work and from there i could do the HBOOT ENG and a pre-rooted RUU
xAutobot and Zeekiz, thanks for your help. Much appreciated!

wut?
Trackah123 said:
Its all working now, i used the wrong recovery image at first.
I got clockwork recovery to work and from there i could do the HBOOT ENG and a pre-rooted RUU
xAutobot and Zeekiz, thanks for your help. Much appreciated!
Click to expand...
Click to collapse
i have exactly the same problem but i do not understand what you did to fix it...
do i need a program for my pc? what recovery did you use? just a simple explanation of what you did because im worried i cant get my phone to work again and im not necessarily a tecnitian... please

I can't remember anymore tbh its been a long time since i did this.
But it had something to do with the right recovery file for your phone i think.
at the clockworkmod rom manager website you can download it.

tehpwnrer said:
i have exactly the same problem but i do not understand what you did to fix it...
do i need a program for my pc? what recovery did you use? just a simple explanation of what you did because im worried i cant get my phone to work again and im not necessarily a tecnitian... please
Click to expand...
Click to collapse
What you need is, first:
- change the revolutionary hboot for an engineering hboot to allow RUU to overwrite it.
--> https://www.box.com/s/8a14444cd1dc4c91f077
This file contains both original and overalpharevx .img (6.98.2000) you should use this one first. You could use fastboot, android flasher or the PG88IMG.zip (the easy way) included to do that.
when it's done you can safely run the RUU and go back to stock (s-on)
or
you can flash 4ext or clockworkmod using fastboot and enjoy your custom rom.
--> https://www.box.com/s/70a0d0608bf3f90b9a3a

Cant install new recovery

Hi, ive been trying to S-off and root my HTC sensation using this guide
http://forum.xda-developers.com/showthread.php?t=1870233
ive managed to get up to step 2, but unable to flash a new recovery using instructions in this guide and also whilst trying kgs utility…. Im pulling my hair out tbh been at it for hours…
so basically, I unlocked my phone, then have got s-off..but now cant get new recovery to get rooting.
when I use the utility in theafore mentioned guide. It either cant find device or just hangs. When I use the kgs utility, it looks promising until I get the message the system cannot find the bacth label specified - dl_4ext_found
any ideas?

try this
boot your device into bootloader
connect your device into pc via usb(it should say fastboot usb)
now in your pc place the recovery.img in the folder where you have adb and fastboot files
open a command window in that folder and do this command
fastboot flash recovery recovery.img

hi rzr86, thanks for the help. tried what you said, but it tells me remote not allowed. any ideas?
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (6348 KB)...
OKAY [ 1.619s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.936s
c:\android>

gdallas said:
hi rzr86, thanks for the help. tried what you said, but it tells me remote not allowed. any ideas?
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (6348 KB)...
OKAY [ 1.619s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.936s
c:\android>
Click to expand...
Click to collapse
hmm ok,
do you have htc drivers installed?
also check if you are using 2.0 usb ports
enable also usb debugging mode
edit:i just inform you also that the recovery can be renamed as recovery.img
i mean when you perform the command do it like this
fastboot flash recovery <the name of recovery>

rzr86 said:
hmm ok,
do you have htc drivers installed?
also check if you are using 2.0 usb ports
enable also usb debugging mode
edit:i just inform you also that the recovery can be renamed as recovery.img
i mean when you perform the command do it like this
fastboot flash recovery <the name of recovery>
Click to expand...
Click to collapse
hi, i noticed that even though I now have S-off, my phone went back to "locked" status. So i tried uinllocking it again, and currently it is now. I flashed the recoevry again as per your instruiction, and seems to have worked!! but not really sure, how would i tell? is there a simmilar way to root it too as when i use the kgs utitly is now goes into a boot loop when i attempt to root.
thanks

gdallas said:
hi, i noticed that even though I now have S-off, my phone went back to "locked" status. So i tried uinllocking it again, and currently it is now. I flashed the recoevry again as per your instruiction, and seems to have worked!! but not really sure, how would i tell? is there a simmilar way to root it too as when i use the kgs utitly is now goes into a boot loop when i attempt to root.
thanks
Click to expand...
Click to collapse
that's why you couldn't perform the command
if i remember well after S-OFF an unlocked bootloader goes again locked
but there was no need to unlock it again
you could use an eng hboot(juopunutbear) which is unlocked
nevermind
flash this zip from recovery now
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
it will give you root

hi and thanks..
So i should capy this to my SD card, then what? sorry for the noob questions.

gdallas said:
hi and thanks..
So i should capy this to my SD card, then what? sorry for the noob questions.
Click to expand...
Click to collapse
Hi,
Yes.
Copy to the root of your sd card.
Flash like a ROM.

malybru said:
Hi,
Yes.
Copy to the root of your sd card.
Flash like a ROM.
Click to expand...
Click to collapse
thanks gents

hmm, i think i must be doing this wrong guys. it thought I flashed the recoevery ok, but then when i hit powerdown on the recovery option, it goes to an HTC logo for a while, then i see my vodafone logo etc and then have a clean install of the orginal rom i guess.
Where am i going wrong?
Many thanks

hey man u just saved my life lol
rzr86 said:
try this
boot your device into bootloader
connect your device into pc via usb(it should say fastboot usb)
now in your pc place the recovery.img in the folder where you have adb and fastboot files
open a command window in that folder and do this command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My htc sensation was just rebooting couldnt get into recovery, i had clockwordmod recovery, i thought i lost my phone, i searched on xda and saw ur post, and i fixed my phone thnx to you,
So just wanted to say thank you very much.

AT&T One X bricked downgrading bootloader, im fully S-OFF Help!!!

So i dont know what happend, i succesfully make my hox S-OFF, use the phone and everything was working fine, then a try to downgrade my bootloader with Jet but everything went wrong from there, the process didnt finish, i try to relocked my bootloader to install the 2.20 RUU thinking it would fix it but know the RUU procesos finishes with a 131 error because my cid is diferent, this is what i have:
******tampered*****
******relocked******
jewel pvt ship s-off rl
cid-spcs_001
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1.0.45.0622
emmc-boot
I can put fastboot commands but its shows FAILED (remote: not allowed), i cant go into recovery, also on jet i cant go into QHSUSB_DLOAD anymore.

You really didn't need to downgrade being you were s-off.............
Sent from my HTC One X using Tapatalk 2

Did you try this command to unbrick?: sudo ./jet -u
Edit: hmm just noticed your cid changed to stock. Sorry idk where to go from there
Sent from my HTC One X using xda premium

Yes i did try the ./jet -u command but i cant get in to QHSUSB_DLOAD anymore that is the stock cid for the one x ? if thats the case maybe i can run de 1.85 RUU?

pikul said:
i cant get in to QHSUSB_DLOAD anymore
Click to expand...
Click to collapse
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.

No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium

redpoint73 said:
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
Click to expand...
Click to collapse
I guess i could run the ./jet -u command and press those keys, its that what you mean?
panda_mode said:
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ooooooooo :good: at least i can get into bootloader and put fastboot commands, i guess thats something

pikul said:
I guess i could run the ./jet -u command and press those keys, its that what you mean?
Click to expand...
Click to collapse
I've actually never used JET, and not quite sure how it works.
But power and vol + will put the phone in QHSUSB_DLOAD in most situations (nothing to do with JET), if that is all you are trying to do. Similar to how power and vol - boots into bootloader. Just curious if it would still worked in your "bricked" condition.

Are you able to get into fastboot? If so just use stock RUU to get back to stock,

thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?

pikul said:
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/HTC_One_X
Try this thread. I think there is a way to use the stock recovery and the cid you used to unlock it. May give you some ideas.
AT&T HTC OneX
Andriod 4.1.1
ViperXL

i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader

pikul said:
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
Click to expand...
Click to collapse
Have you tried to get a new identifier token and unlock the phone to get TWRP again?
http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/
AT&T HTC OneX
Android 4.1.1
ViperXL

is it posible to get it in bootloader mode? cause thats all i can access :/
Everytime i try to flash a file in fastboot it shows FAILED (remote: not allowed)

pikul said:
is it posible to get it in bootloader mode? cause thats all i can access :/
Click to expand...
Click to collapse
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.

mirGantrophy said:
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
Click to expand...
Click to collapse
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s

pikul said:
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
Click to expand...
Click to collapse
If you have the RUU.zip, do this then:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip rom.zip
see if that works..

This is what i get:
C:\Programas\Fastboot>fastboot flash zip rom.zip
sending 'zip' (576544 KB)...
OKAY [ 24.368s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 26.975s

this sucks, i have to go to work and i dont have another cellphone :/

pikul said:
this sucks, i have to go to work and i dont have another cellphone :/
Click to expand...
Click to collapse
You can try to find the cidnum for the htc onexl and see if you can trick it by editing android-info.txt file to match cid num.
Example:
edited android-info file
modelid: PG3213000
cidnum: KT___901
cidnum: HTC__004(this edited file only)
mainver: 2.32.1010.1
hbootpreupdate:13
boot again into fastboot
AT&T HTC OneXL
Android 4.1.1
ViperXL

[Q] HTC One S can't pass the HTC logo

Hello
a few days ago I used "HTC ONE S AIO KIT" to install Jelly bean 4.2.2 on my HTC ONE S
I successfully installed the jelly bean and everything was fine
during the process, I created a backup from my phone in the ClockworkMod
today, I booted to ClockworkMod recovery > backup and restore > restore > and selected the backup file I created
the phone restarted and got stuck on the HTC ONE logo
I did everything I could in the past 2 hours, searching everywhere
even tried this command "fastboot flash boot "C:\...\boot.img"" but nothing worked - after doing this, the ClockworkMod gave me an error that said "can't mount /sdcard"
appreciate any help

Ok , I just updated to latest version of clockwork and still can not fix "can't mount sdcard" error
I have been doing this for 6 hrs now
can someone please help me ?

dnotoco some
jimlee2 said:
Ok , I just updated to latest version of clockwork and still can not fix "can't mount sdcard" error
I have been doing this for 6 hrs now
can someone please help me ?
Click to expand...
Click to collapse
install ruu original and unlok again is the most easiest for you

ZALACAYN2 said:
install ruu original and unlok again is the most easiest for you
Click to expand...
Click to collapse
thanks for the reply
I can't find the RUU for Fido/Rogers HTC ONE S
I searched for factory every where, I made a backup before but now I can't access the SD card to see if it it still there or not

jimlee2 said:
thanks for the reply
I can't find the RUU for Fido/Rogers HTC ONE S
I searched for factory every where, I made a backup before but now I can't access the SD card to see if it it still there or not
Click to expand...
Click to collapse
Well that is a pickle. Not having a RUU to fall back on.
Good news is you can still fastboot in bootloader.
So you can try different roms until one works. So at least you have a phone that works.
Push a rom to your phone
http://forum.xda-developers.com/showthread.php?t=1667929&highlight=adb+push
Flash a boot.img
http://forum.xda-developers.com/showthread.php?t=1752270&highlight=fastboot
fixing sd card mounting
http://forum.xda-developers.com/showthread.php?t=1630459

tivofool said:
Well that is a pickle. Not having a RUU to fall back on.
Good news is you can still fastboot in bootloader.
So you can try different roms until one works. So at least you have a phone that works.
Push a rom to your phone
http://forum.xda-developers.com/showthread.php?t=1667929&highlight=adb+push
Flash a boot.img
http://forum.xda-developers.com/showthread.php?t=1752270&highlight=fastboot
fixing sd card mounting
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
I followed all these steps but I am not able to get it fixed
is it possible to help me via google talk or something? thanks

I get this error now when I try to flash a recovery
Code:
C:\Fastboot>fastboot flash recovery op
enrecovery-twrp-2.4.1.0-ville.img
sending 'recovery' (7820 KB)... OKAY [ 1.426s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.251s
I searched the forum and tried different methods to fix it but still no luck
I am going crazy over this problem

jimlee2 said:
I get this error now when I try to flash a recovery
Code:
C:\Fastboot>fastboot flash recovery op
enrecovery-twrp-2.4.1.0-ville.img
sending 'recovery' (7820 KB)... OKAY [ 1.426s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.251s
I searched the forum and tried different methods to fix it but still no luck
I am going crazy over this problem
Click to expand...
Click to collapse
Where did you download that recovery from?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Where did you download that recovery from?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
from the original twrp site

Ok. Are you flashing the boot. img from the extracted rom zip that you are installing. I never used the c:/ blah blah. I always put the boot.img file in the same folder as adb and fastboot then with the phone in fastboot usb type fastboot flash boot boot.img in the command prompt on the computer. It sounds like you might have a bad recovery. Have you tried to flash a new recovery?
Sent from my HTC One using xda app-developers app

[Q] bricked? not sure

Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?

Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?

Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app

Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?

Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app

installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.

any suggestions on trying something else?

waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk

unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?

waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk

Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?

waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there

Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.

abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.

What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.

abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?

waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6

abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s

Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.