Database Info

Bricked my One S?

So I wanted to root my One S and install CWM.
What I did was use http://forum.xda-developers.com/showthread.php?t=1604677 this tool, everything went fine. I used the TWRP recovery, it booted fine.
Tried to install CWM, found out my Hboot was too low (think it was 1.14.0.02).
Extracted the hboot.img from the CWM zip, installed it:
C:\Users\aSCO\Desktop\blabla\fastboot flash boot boot.img
sending 'boot' (5688 KB)...
OKAY [ 0.890s]
writing 'boot'...
OKAY [ 1.390s]
finished. total time: 2.280s
then fastboot reboot.
Now the ühone won't turn one, LED doesn't shine when connected to charger. From time to time it turns on, show the HTC screen (with text 'this is a developer version etc'), then turns back off.
Any hope there for me? What did I do wrong?
EDIT: I managed to get into fastboot, what's the best way to go on from here? The Hboot version number is still the same, is there another recommended boot.img that I could flash?
EDIT2: Managed to fix this, cannot find an option to delete the thread ...
CAN BE CLOSED.

[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.

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk

[Q] My htc one sv will only go to boot loader

so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me

Check the guide at HTC side if you have done everything correctly, all is written how it should or copy and paste.
Without unlocked bootloader, there is no chance to rescue your phone.
Any information about your phone model and exactly the step it fails is important, too.

this problem has such a friend, and it does not solve constantly locked bootloader ...

Does anyone solved this problem?The same situation of my phone?Please help!

Hi,
i flash 2.8.4.0twrp, then make backup, after that (whit in recovery options) try to make factory reset, and after that my one sv is messed up like hell...
It is not booting...stuck for a while at htc logo, screen goes black, then loads bootloader, I am able to go to twrp (I have fresh backup of complete phone, did it with twrp above), but not able to flash anything...it fails every time, saying that is unable to mount cache...try advance wipe, but it is not able to mount any thing...
Since my phone was S-off, unlocked bootloader, superCID (it is k2ul), hboot2.0, I tryed with fastboot oem relock (to lock bootloader, and flash stock pl80img.zip) but that fails too, ends up with to many links message...and bootloader stays with tampered and unlocked sign...before flashing 2.8.4.0twrp phone was working great, but after factory reset it is not able to mount anything, and running pl80img.zip gives me all so only fail...fail...fail...
So..now i have latest twrp and totaly messed up phone...
How can U help me, anny advice???
THX in advance!

danrock1984 said:
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Click to expand...
Click to collapse
I have the same problem!!
The phone details:
Locked Bootloader
K2_UL XA SHIP S-ON RL
HBOOT 2.00.0000
T-mobile network lock
NO SuperCID
The phone doesn't boot up!
It boot to bootloader fastboot mode always!
The notification led blinks constantly!
When I wanted run the RUU (K2_UL_ICS_EUROPE...etc) the phone doesn't reboot black HTC Screen it goes back to bootloader, and it doesn't working
After I downloaded this:
https://www.androidfilehost.com/?fid=23212708291675772
After I download it rename to PL80IMG.zip and it loading after checking, and goes back to bootloader, no volume up to update option!
After I downloaded OTA_K2_UL_JB_45_S_Voda-Hutch_AU_2.14.862.9-1.17.862.9_release_3136147vue6nb55rwgyw0d.zip
After I extracted the firmware zip from it, edited the android-info.txt CID number to HTC__032 and place it to SD, rename to PL80IMG.zip after I get the same problem!
After these problems are try another method with fastboot!
fastboot flash zip flash firmware zip and I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot flash zip firmware.zip
sending 'zip' (33772 KB)...
OKAY [ 2.668s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.264s
C:\Users\Erkaft\Desktop\Új mappa>
And when i want to erase all with fastboot I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase all
erasing 'all'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: -0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: -0.000s
I also tried bootloader unlock but the last message didn't appear on the phone and it stay locked
Any idea to ressurection this phone?

You need ti unlock your phone,otherwise you can't do anything.

Flashed customer recovery, but it won't boot into it

I recently had to do the RUU recovery method found here: http://forum.xda-developers.com/showthread.php?t=2727831
Which fixed the problem i was having. Now i'm having another problem.
I flash and i get the following from my CMD:
fastboot flash recovery cm-13.0-20151210-NIGHTLY-m8-recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (18436 KB)...
OKAY [ 1.669s]
writing 'recovery'...
OKAY [ 0.982s]
finished. total time: 2.653s
Click to expand...
Click to collapse
But, when i boot into recovery, it gets stuck on "Entering Recovery", and my ADB says "unauthorized"

InuyashaITB said:
I recently had to do the RUU recovery method found here: http://forum.xda-developers.com/showthread.php?t=2727831
Which fixed the problem i was having. Now i'm having another problem.
I flash and i get the following from my CMD:
fastboot flash recovery cm-13.0-20151210-NIGHTLY-m8-recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (18436 KB)...
OKAY [ 1.669s]
writing 'recovery'...
OKAY [ 0.982s]
finished. total time: 2.653s
But, when i boot into recovery, it gets stuck on "Entering Recovery", and my ADB says "unauthorized"
Click to expand...
Click to collapse
I haven't run CM in ages but I don't recall it coming with a recovery. Maybe try using the latest TWRP recovery and flash it in fastboot.
As for the adb "unauthorized" I'm not sure but I didn't think adb works in bootloader. I think it's all fastboot until the Rom boots. Again, definitely not sure about that and I'm away from my pc to go test it out.

cntryby429 said:
I haven't run CM in ages but I don't recall it coming with a recovery. Maybe try using the latest TWRP recovery and flash it in fastboot.
As for the adb "unauthorized" I'm not sure but I didn't think adb works in bootloader. I think it's all fastboot until the Rom boots. Again, definitely not sure about that and I'm away from my pc to go test it out.
Click to expand...
Click to collapse
I was able to get it to work. Turns out, when i went back to early RUU, it also replaced my HBOOT to an earlier version. I updated to 3.19 and it fixed the problem.
NOW i have another problem where my WIFI has stopped working, (altough 4G works now)... So i will try to replace kernel & radios to see if that works.

InuyashaITB said:
I was able to get it to work. Turns out, when i went back to early RUU, it also replaced my HBOOT to an earlier version. I updated to 3.19 and it fixed the problem.
NOW i have another problem where my WIFI has stopped working, (altough 4G works now)... So i will try to replace kernel & radios to see if that works.
Click to expand...
Click to collapse
when you updated to the new hboot, did you flash the last firmware?
this will get you up-to-date with everything.
as for WiFi it could be completely ROM related.

I'm having similar issues. I have had CWM recovery in stalled and have my M8 unlocked, rooted, and S-Off with the Google Play Edition Marshmallow ROM. I made an attempt to flash the latest TWRP using both Flashify as well as Fastboot, but it just sits in "starting recovery" screen even after multiple reboots. I can re flash CWM and it works fine, but I'd really like to get TWRP up and running. Any thoughts on my next step?
I've cleared the cache in Fastboot with no luck. Also, my WiFi won't activate either when booted into Marshmallow. Not sure they are related though.

eliot1171 said:
I'm having similar issues. I have had CWM recovery in stalled and have my M8 unlocked, rooted, and S-Off with the Google Play Edition Marshmallow ROM. I made an attempt to flash the latest TWRP using both Flashify as well as Fastboot, but it just sits in "starting recovery" screen even after multiple reboots. I can re flash CWM and it works fine, but I'd really like to get TWRP up and running. Any thoughts on my next step?
I've cleared the cache in Fastboot with no luck. Also, my WiFi won't activate either when booted into Marshmallow. Not sure they are related though.
Click to expand...
Click to collapse
Yeah, After all the problems, I finally gave up and reverted back to latest stable CM12.1, WIFI is working, 4G working... I'm o.k with that

I bit the bullet as well and installed the 5.0.1 with latest firmware RUU. From there, TWRP installed with no issues.