Database Info

[Q] Desire S boots into recovery mode automatically!!

hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.

long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.

It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor

yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech

batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?

batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?

I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.

eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?

[Q] Bricked after trying to flash CM10

Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.

First for the One XL it is suggested you use TWRP and not CWM
You can get it here from their website .
It tells you how to fastboot flash it.
If you did an OTA to 2.20 or your device came with 2.20 you probably need to flash the boot.img /kernel
So in your CM10 zip, extract the boot image.
and use fastboot to flash the boot img with the command
fastboot flash boot boot.img
and that should help you out.
I also suggest reflashing the rom with TWRP just in case. Hope this helps.

Can adb see the phone?

FrustratedAndConfused said:
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
Click to expand...
Click to collapse
This is the one xl correct, not the international on x?

If you can get anything on your screen, your phone isn't hard-bricked.
First, which phone do you have? ClockworkMod Touch Recovery does not work on the AT&T One X (One XL). If you tried flashing a ROM through it, it's not going to work and it's probably not booting up because the ROM is corrupted.
I would start with flashing a new recovery in adb. Use TWRP, because even the basic CWM is not supported for this phone and can cause issues.

Can you get into recovery? If so is the SD card mountable?
First time I flashed i had a similar issue where the SD couldn't mount. I ended up having to run the factory RUU after relocking the bootloader & then start again. I waited for a later nightly to come out. Also seems to go better if you flash a different rom first like viper.

NismoR31 said:
Can you get into recovery? If so is the SD card mountable?
Click to expand...
Click to collapse
Doesn't matter. He flashed the wrong recovery (not for our phone). There is not Touch CWM for our version.

i should really refresh pages before replying

BRICKED any fix?

so my stupid head downloads a s3 rom for my s4 hard and flashes it...
now its bricked but i can still get into recovery..
is this the end:[

No, wipe everything and reflash the right one. You should use TWRP so...
Depending on your bootloader version don't forget to 'fastboot flash boot boot.img' within fastboot mode. Remember: **** happens...

rootrider said:
No, wipe everything and reflash the right one. You should use TWRP so...
Depending on your bootloader version don't forget to 'fastboot flash boot boot.img' within fastboot mode. Remember: **** happens...
Click to expand...
Click to collapse
hopefully this works :[
i tried stock ruu but it says error the whole time.
im using twrp so ill try flashing a diff rom..

bstylz911 said:
hopefully this works :[
i tried stock ruu but it says error the whole time.
im using twrp so ill try flashing a diff rom..
Click to expand...
Click to collapse
For stock ruu you need to be on stock recovery, your device relocked. You can always do that after you've tried it the easy way. :good:

i completly forgot about the relocking...thank you so much

half brick htc one s s4
Hi, so after upgrading to MIUI.us_ville_v4_2.11.16_Eng_Deo_ZipA_Signed_linds6630 for some reason my htc one s s4 storage usb sotrage stopped working and now even wifi wont work, I've tried wiping installing many times and it didn't help.
So I went and flashed stock recovery and locked bootloader I got the ruu file and now it wont flash as I get signature error so went to check mainver and there is a problem it's all blank. I've tried to use mainver error fix from all in one toolkit ver3.3.1 and no luck as system can't mount sd. when on custom recovery windows couldn't recognize file system so i only had an option to format the storage, I didn't want to do that as miumi starts and I was affraid that this operation will wipe some data and I loose phone completely. So what can I do next, can you help me please?

[Q] Screen stuck when try to reboot

Hi,
Im trying to root my HTC ONE S. I followed all the steps that suggested in the forums, but when I reboot the phone in the final step, it got stuck in the 'HTC quietly brilliant' screen. I left it there for 20 min or so, it didn't change. I am able to go to the recovery mode but I don't know what to do. I did a factory reset attempting to go back to the original software but it didn't work either. Any ideas what can I do? Im in real trouble if Im not able to use my phone anymore.
Thanks in advance,
Angel

100315595 said:
Hi,
Im trying to root my HTC ONE S. I followed all the steps that suggested in the forums, but when I reboot the phone in the final step, it got stuck in the 'HTC quietly brilliant' screen. I left it there for 20 min or so, it didn't change. I am able to go to the recovery mode but I don't know what to do. I did a factory reset attempting to go back to the original software but it didn't work either. Any ideas what can I do? Im in real trouble if Im not able to use my phone anymore.
Thanks in advance,
Angel
Click to expand...
Click to collapse
Well if you are installing a custom ROM then there is no need to root before hand, you just need a custom recovery installed. The custom ROM will have root access enabled.
If you are asking how to just be rooted on a stock rom, then I would just google how to do it like you would. But I assume you install custom recovery, download a supersu.zip and install via recovery.

tivofool said:
Well if you are installing a custom ROM then there is no need to root before hand, you just need a custom recovery installed. The custom ROM will have root access enabled.
If you are asking how to just be rooted on a stock rom, then I would just google how to do it like you would. But I assume you install custom recovery, download a supersu.zip and install via recovery.
Click to expand...
Click to collapse
Hi, thank you for the reply
Well, I have no access to the sd card, it says it's not mounted. I can't copy any files to the phone, therefore I can't reinstall it from the phone. Sorry for my ignorance, but I don't know what to do next.
Thanks,
Angel

100315595 said:
Hi, thank you for the reply
Well, I have no access to the sd card, it says it's not mounted. I can't copy any files to the phone, therefore I can't reinstall it from the phone. Sorry for my ignorance, but I don't know what to do next.
Thanks,
Angel
Click to expand...
Click to collapse
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img

tivofool said:
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
Hi,
I tried to do what you told me, but now I can´t even go into the recovery mode. I can only access the bootloader; anytime I select recovery mode it shows this (image below), after a few minutes it reboots and stays with the white screen ´HTE quietly brilliant´. I can´t copy any files either because the computer doesn´t read the sd card. Any ideas?
Thank you for your time.
Angel
Click to expand...
Click to collapse

100315595 said:
tivofool said:
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
Hi,
I tried to do what you told me, but now I can´t even go into the recovery mode. I can only access the bootloader; anytime I select recovery mode it shows this (image below), after a few minutes it reboots and stays with the white screen ´HTE quietly brilliant´. I can´t copy any files either because the computer doesn´t read the sd card. Any ideas?
Thank you for your time.
Angel
Click to expand...
Click to collapse
That is good, that is the stock recovery, basically saying you don't have access to it.
But you don't need to go into recovery, it is there just to fix the issue when you enter the bootloader and pick "clear storage"
So get back to the bootloader and clear storage. Then you will need to flash the recovery of your choice, CWM or TWRP. You should now be able to access usb storage. (unless you are using the special TWRP in the Maximus thread meant for hboot 2.16, then it just doesn't work)
Click to expand...
Click to collapse

Yes, it worked. Thank you.
But, which ROM should I install now? I tried with the SU, but the screen was stuck again. Do I need the phone in S-off mode? how do I do that? I saw that many ROM's need this.
Thank you again for your help, very appreciated
Angel

100315595 said:
Yes, it worked. Thank you.
But, which ROM should I install now? I tried with the SU, but the screen was stuck again. Do I need the phone in S-off mode? how do I do that? I saw that many ROM's need this.
Thank you again for your help, very appreciated
Angel
Click to expand...
Click to collapse
You are welcome.
You only need S-Off if the rom says 2.16 HBoot required.
So there are a lot of different ones to try. As long as your Hboot is 2.15, if not then you need to upgrade your firmware to that. You see your HBoot in the bootloader screen.
So ya, most of the roms are ok with S-on, you just have to remember to:
fastboot flash boot boot.img
So on your pc download the rom, unzip it you will see the boot.img move that to fastboot folder and fastboot flash it.
Then you can move the ROM.zip to your phone and install via recovery.
Don't forget to wipe caches before rebooting. (when installing, if that particular rom opens up Aroma installer and one of the options is to wipe, do that but don't wipe again when back to recovery)
The sense based roms are generally more stable and like stock.
The CyanogenMod may have a few little bugs.
Just browse around and see which one you like.

It all worked out pretty well.
I'm trying with the MagioRom, seems to be very stable!
Thank you for your help, you literally saved my HTC!
:good:

[Q] help with tampered, locked, ruu, s off etc

I have a one sv which:
is k2 ul
normally boots only to HTC screen (no quietly brilliant) and stays there till the end of times
shows tampered locked, which i now changed unlocked status (htcdev)
s-on
has twrp recovery on, but swipes fail mostly
flashing roms in twrp recovery show success but result is still HTC logo without being quietly brilliant
can not be ruu-ed beucause the ruus i find are i think older than required
hboot 2.21, radio 1.18 version
s-off fails because tho fastboot recognizes phone, adb doesnt in fastboot mode and in bootloader pc thinks it is not attached (tried xp, 7, 8.1 and many different drivers)
i am not sure if usb debugging was on before the phone crashed
so i can't put an older ruu because of s-on, i can't get s-off because rumrunner and moonshine can't work without adb, and basically that is it.
does anyone PLEASE have any idea what to do?
and yes, the warranty is over and the phone has gone to the warranty twice with bootloop before.

After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?

old.splatterhand said:
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
Click to expand...
Click to collapse
yes i did.
twrp 2.6.3.2
now i have made such progress that twrp tells me it cannot mount int sd and when booting, phone stays on the htc logo for some seconds and then switches off. i believe i have actually made it worse (didnt think that could happen).
EDIT: so i formatted the storage like this http://forum.xda-developers.com/showthread.php?t=2576897 and it BOOTED
EDIT2: the phone now kind of works IF it boots. half of booting times it just switches off, the other half it switches off and then reboots and works. i think something is still kind of not good but i dont have the b***s atm to poke it more.
thank you all for your potential help.

What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced

old.splatterhand said:
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
Click to expand...
Click to collapse
it was this one http://forum.xda-developers.com/showthread.php?t=2512742 which is, as i understand, your work, thank you very much, donations will happen when im a tincy bit richer
and i will wipe some time later when im at home and courageous enough.

You can also try to restore this TWRP backup.

great news! today the phone restarted itself and froze on the logo. i tried to start twrp but it froze on that logo too. tried to do a factory reset, which removed the "tampered" sign until next reboot but that was about it.
now i can't reflash twrp or anything at all, with the error remote: image update error. oh please save me again.

Does not sound good.
You can boot into bootloader? Is it locked or unlocked? Did you reflash the recovery to check if you can boot into it?

looks bad indeed.
i can boot into bootloader, which is unlocked. and please specify what do you mean by reflashing the recovery (pardon my stupid brain)

When in bootloader, connect your phone to fastboot and try to flash recovery again.
If you can't get into recovery, i don't know, if there is much i can do for you

fastboot basically tells me to go f* myself with the error "remote: image update error" what ever I try to flash. right now Im trying to find a way to reflash twrp from ext sd. not doing so great

Well, about your country flag i suggest you speak (or you can at least read) russian language.
Go to 4pda.ru and look for the posts of "MikG". He has made zip files, similar to RUU. They are flashed from bootloader/Ruu mode. Maybe they can bring your phone back to life.
I can't tell you how to use this files, because i don't speak russian.

I'll try, thanks.
edit: and it just refuses to cooperate. it kind of does something in bootloader, but still doesnt boot past htc logo or if i try recovery, it stays on teamwin logo. i dont know if im doing something wrong or what... maybe i'll wait for the 4.2.2 hboot 2.21 radio 1.18 ruu then because i really dont know what else i could do.