Database Info

Messing around with Fastboot (Stuck at HTC Screen(boot-looping))

Heya guys
Another numpty here that has messed up his phone
Well here is what i did, i unlocked my BootLoader using HTC Dev then i decided to have a go at getting a custom rom installed, this is where my plan went wrong.
I used the fastboot method, cut a long story short i flashed over my recovery .img and now the phone wont boot.
then tried to boot recovery and im stuck in an endless booting loop.
I feel pretty dumb, i was a little out of my depth
Any way here is some information:
(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.13.61.3
(bootloader) serialno: SH18MTJ02051
(bootloader) imei: 3589#########
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4072mV
(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
Looking at the fast boot commands im pretty sure i havent completely wrecked it but what do i know , i have a very pretty paper weight at the moment lol.

Could you write the contents of your bootloader screen
See this http://forum.xda-developers.com/showthread.php?t=1525100 thread
Swyped from my Desire S using XDA Premium

Working ... For now
So I turn the device on this morning and pop up it loads, i dont reayy want to turn it off again now :S , is there a way that i can back up the current rom image eventhough im S-ON ?

Target51 said:
So I turn the device on this morning and pop up it loads, i dont reayy want to turn it off again now :S , is there a way that i can back up the current rom image eventhough im S-ON ?
Click to expand...
Click to collapse
If your recovery installation messed up download 4EXT Recovery Updater via your phone browser (there is a link at 4ext.net), install it and let it flash the recovery for you.

How complicated writing "fastboot flash recovery recovery.img" could possibly become?
Download and flash the recovery you want. If you need direct path for downloading recoveries - http://download.clockworkmod.com/recoveries/
Make sure you choose the correct one (HTC Saga).

[Q] Stock ROM for HBoot v1.13

Hello all, I was trying to S-off my phone in order to be able to flash hboot of version 2.15(i guess the most supporting). But stumbled upon a problem - I need a live Android, ie ROM running to S-off. But all I have is fastboot and TWRP 2.3.0(some later won't boot too)
I now don't have any ROM at all, all ROMs I tried won't boot on my hboot. Actually that's the reason I'm trying to upgrade my HBoot. It seems to be a vicious circle, unless I find a ROM which will run on my config
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT23XW411592
(bootloader) imei: 359901041873577
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4180mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As you can see I gained SuperCID already, did it in recovery as a prerequisite for Facepalm S-Off

Solved
OK, I can confirm that RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
contains boot.img and system.img files which boot on hboot v1.13
In order to flash that system.img I needed to copy it in recovery to /sdcard,
Code:
mount -o loop
it and manually copy the contents to /system, because flashing with fastboot failed:
Code:
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.006s
After rebooting stock will come up

[Q] Phone will not boot into recovery/ bootloops

This morning when I woke up my phone began to bootloop without anything but me turning on the screen. At first it would happen every few minutes but it has progressed to happening whenever it isnt in bootloader.
So far I have tried flashing a new rom, but then the phone began to bootloop in the middle of recovery, which is something Ive never had to deal with before. From there I figured the problem is further down and I tried to flash a new recovery to no success. now to where I am,
I can flash a recovery, but when entering it it takes me back to bootloader. The odd thing is, if I let it boot normally, after a few boot loops, the phone will boot rom with safemode to a half broken rom that will bootloop after a minute. I tried flashing stock boot and recovery but that didnt work either. Finally ive been flashing new firmware and boot imgs with it making no difference. What else can i try?
tl;dr recovery wont boot, stuck in bootloader, wat do?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43FSF01988
(bootloader) imei: 990004996433284
(bootloader) imei2: Not Support
(bootloader) meid: 99000499643328
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.019s

Sukhol said:
This morning when I woke up my phone began to bootloop without anything but me turning on the screen. At first it would happen every few minutes but it has progressed to happening whenever it isnt in bootloader.
So far I have tried flashing a new rom, but then the phone began to bootloop in the middle of recovery, which is something Ive never had to deal with before. From there I figured the problem is further down and I tried to flash a new recovery to no success. now to where I am,
I can flash a recovery, but when entering it it takes me back to bootloader. The odd thing is, if I let it boot normally, after a few boot loops, the phone will boot rom with safemode to a half broken rom that will bootloop after a minute. I tried flashing stock boot and recovery but that didnt work either. Finally ive been flashing new firmware and boot imgs with it making no difference. What else can i try?
tl;dr recovery wont boot, stuck in bootloader, wat do?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43FSF01988
(bootloader) imei: 990004996433284
(bootloader) imei2: Not Support
(bootloader) meid: 99000499643328
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.019s
Click to expand...
Click to collapse
When your phone boots up and before it reboots... Does it appear to get network signal at all?
Have you tried one of my ruu yet?

dottat said:
When your phone boots up and before it reboots... Does it appear to get network signal at all?
Have you tried one of my ruu yet?
Click to expand...
Click to collapse
Thanks for the quick reply
Yes, it seemed to have connected to the network, in the few seconds i have, i went to settings and it was.
i tried the files from http://forum.xda-developers.com/showthread.php?t=2723159 if that matters,
I tried to use your auto ex for the ruu but it would not work ill try it manually in a little bit
UPDATE: Flashing the RUU seems to have solved my problem, i could boot into recovery and there werent any bootloops. Thanks for the suggestion, I was running out of ideas

Rare bird: Stock Tmobile ROM 3.14.531.19

Hi all.
I have a completely stock never-been-modified HTC One S that has started freezing on boot.
No, I never tried to root it, unlock the bootloader, or any other stuff.
I would like to get my data off it, but because I never rooted it, I can't extract said data using ADB (unless you know a trick that I don't).
My options seem to have come down to flashing something to get it to boot... ROM, kernel, radio, what do you think?
- I can get into Fastboot, Bootloader, Recovery, etc.
- I can ADB to the phone while it is boot-stuck (so probably not the kernel?).
I want to get my info off of it and if I can make it boot all the way in, that's an added bonus.
To that end, have you ever seen a 3.14.531.19 ROM that wasn't wrapped up in an RUU? I was willing to try RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2 but it says that it'll wipe all my info.
Here's my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.531.19
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW404294
(bootloader) imei: 359902041072822
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3920mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
What say you?

If your phone is bootloader locked, S-ON with original recovery, you're out of luck... The complete boot sequence is secured and if you try to unlock, all data will be wiped off.
The only first step to get to your data would be to root without unlocking the phone, but I can't see how to do that if you can't start the OS.
One thing you can try is to get to the HTC recovery and wipe cache (I think this is possible).

Thanks for the reply.
I have already wiped the cache (forgot to mention that in the OP, sorry) and it didn't make a difference.
It sounds like what I was expecting to hear: My data are beyond recovery... Which is a bummer.
Anyone else have anything to add?
Some miracle cure, maybe?
I'm going to hold off on my attempt to unlock the bootloader another few days in case someone has a suggestion to offer.

A final bump in the hope that someone might have a solution.
Thanks!

HTC ONE MINI, NO OS, no ADB, Bootloader Unlocked, TWRP and fastboot works...

Hello,
I will try to explain what happened, although I am not sure... I tried to root my phone so I can do a data recovery as I lost all data... at this stage phone still rooted fine, no contacts, no sms, no nothing... it looked like a factory reset.
1. I used htcdev to unlock bootloader
2. I flashed recovery-clockwork-touch-6.0.3.6-m4.img to try and load the superuser.zip to root my phone... I tried several zips, but none of them rooted it... I had to use adb through: cmd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>, at this stage phone still booted normally and no problems... so I used adb push to install zips to root it... none of them worked...
3. I realized that it might be the clockwork recovery that is the problem, so I decided to change the recovery to TWRP... and this when something went wrong as the phone wouldn't reboot into normal mode anymore, only bootloader... I though giving it a factory reset would solve the issue, so I did... nothing happened...
4. I managed to flash twrp-2.8.7.0-m4.img recovery and discovered that there is no OS and basically apart from the bootloader theres nothing else on the phone...
I understand that I need to do a RUU flash, however I cannot find the one I need. I followed this thread, however I cannot seem to find the RUU that I need
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
I also tried fastboot flash zip sense6_firmware.zip, it cannot do it... gives me a fail error...
and now I am stuck as adb doesnt work to push files from either the unlock folder, nor the htc sync one or C:\Program Files (x86)\Android\android-sdk\platform-tools>
This is my first root attempt (maybe I shouldn't do one and won't in the future ) as you can see, but maybe I am just missing something very obvious and easy...
I'd like to get the original soft back on the phone but even if its still stored on it, I don't know how to get to it and make it work...
Phone details
astboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.28.40e.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
If you can, please help me!

I have exact same problem! please help

Alpha1BA said:
I have exact same problem! please help
Click to expand...
Click to collapse
hello, what version are you running?

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.28.40e.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4317mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Alpha1BA said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.28.40e.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4317mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Looks like we have the same version... Honestly, I spent so much time on trying to S-off it and fix it, I think I'll just give up... I found a UK based service that does it for £20... not sure it's worth the time and effort to fix it ourselves... if you're UK based, msg me and I'll give you the details if you're interested!

Hi there, if you unlock the boot loader you will wipe all data from your phone. You confirmed that with the swipe to agree unlock. Recover your data might be difficult but you can give it a try even from Recovery itself.
The easiest way to get your phone back to work is the appropriate RUU for it, but with unlocked boot loader and TWRP booted you can try to put the ROM via USB on the Phone. Flash it via TWRP and since you where S-ON you need to flash the boot.img for your chosen ROM manually the same way you did it for recovery (fastboot flash boot boot.img). If your boot.img does not do well with your ROM you will get into a boot loop. hope this helps.