Loop on boot screen - HTC Desire S

Hello, I got a brand new HTC Desire S (Android 2.3.5, Sense 3.0, HBOOT 2.00.0002)
I wanted to root my phone, but even with all the tutorials here it was immune to it. I decided to install Reaper v.3.0 ROM on it. After hard times I did it... But I would like to come back to my original ROM. I have problems with it, because I found one prerooted ROM here, but when I install it and run, it loops on the boot screen. Can't do anything with it.
Could anybody help me with it?
I am a complete noob with it...

Sllipp said:
Hello, I got a brand new HTC Desire S (Android 2.3.5, Sense 3.0, HBOOT 2.00.0002)
I wanted to root my phone, but even with all the tutorials here it was immune to it. I decided to install Reaper v.3.0 ROM on it. After hard times I did it... But I would like to come back to my original ROM. I have problems with it, because I found one prerooted ROM here, but when I install it and run, it loops on the boot screen. Can't do anything with it.
Could anybody help me with it?
I am a complete noob with it...
Click to expand...
Click to collapse
Did you flash the boot.img separately from fastboot after flashing the ROM? If not, then you need to do that. Do a google search for fastboot flash boot boot.img

enigmaamit said:
Did you flash the boot.img separately from fastboot after flashing the ROM? If not, then you need to do that. Do a google search for fastboot flash boot boot.img
Click to expand...
Click to collapse
How many times have se said this...

Sllipp said:
Hello, I got a brand new HTC Desire S (Android 2.3.5, Sense 3.0, HBOOT 2.00.0002)
I wanted to root my phone, but even with all the tutorials here it was immune to it. I decided to install Reaper v.3.0 ROM on it. After hard times I did it... But I would like to come back to my original ROM. I have problems with it, because I found one prerooted ROM here, but when I install it and run, it loops on the boot screen. Can't do anything with it.
Could anybody help me with it?
I am a complete noob with it...
Click to expand...
Click to collapse
OK Here is how to do it..
From Reaper ROM zip file locate boot.img file
now reboot your phone into fastboot
then from command prompt run "fastboot flash boot boot.img"
reboot your phone and then it should work fine.
After that follow the guide here to revert to stock
http://forum.xda-developers.com/showthread.php?t=1604255

Sorry guys, i think I wrote it unclearly
I mean Reaper works great. Just I downloaded the ROM from here:
http://forum.xda-developers.com/private.php?do=showpm&pmid=7191875
and that one loops. I did what you have said about that boot.img with all the ROMs. Doesn't work on that second ROM ;/
OKAY, THE PROBLEM IS OVER I FOUND SOMEWHERE AN ORIGINAL ROM WHICH I INSTALLED. EVERYTHING WORKS FINE!
THANKS EVERYBODY FOR HELP!

Related

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

Can't boot any custom rom

Hey, first time posting something on this forum but to all devs reading this thanks alot for everything you do!
And Thanks to anyone who can help me!
Now my problem is as following,
My stock rom is RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
I followed this guide to unlock the bootloader and get root http://forum.xda-developers.com/showthread.php?t=1583427
I used this recovery "Official CWM of koush (HTC One S)" (both toutch and regular has been tested)
Then i downloaded MIUI at first and flashed that(full wipe), it installed fine so i rebooted.
Once i got passed the htc boot screen everything went black, no boot animation.
After that i tested some more Roms, ParanoidAndroid and AOKP Milestone 6.
The exact same thing happend with and exeption for AOKP where the toch keys turned on.
I also noticed it showed up as a removable device in windows from time to time when plugged in (dont if that helps).
After that i restored my one s to stock and then did all the steps again but that yeilded the same results.
I have no idea what the problem is and im hoping its something that has an easy fix and im just to dumb to see it.
If you need any more info just ask, and again thanks for any help!
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Daikar said:
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Click to expand...
Click to collapse
just use twrp and problem solved.
CWM IMO sucks in comparison. Not to mention the level of support with TWRP is so far and above ANYTHING you will get with CWM.

[Q] Limited to one rom?

Heyy peeps,
Couple of weeks ago I unlocked my HTC Desire S. Thanks to this thread (http://forum.xda-developers.com/showthread.php?t=1525100) i succeeded and had the Reaper V4.0 rom installed.
I tried to experiment with other roms like PACman. Unfortunatly, every rom I try ends up with the same old HTC boot screen loop.
That's kinda the problem, so any help would be appreciated!
Read step 4 again.
??'boot.img'??
You're right, didn't change the boot image. So I did that now with the Fallout V5 and PACman roms. It worked this time and the rom booted spotless. But after a while I tried to reboot, now again I'm stuck a boot screen with HTC logo.
That's because instead of flashing boot.img to boot partition, you've actually booted the phone with it, but without flashing.
The correct form is:
fastboot flash boot boot.img
You did:
fastboot boot boot.img
Now tell me something: how does it happen that people can't read guides properly? EVERYTHING is documented, why do people still manage to mess things up?
Thanks mate.
hitmoky said:
Thanks mate.
Click to expand...
Click to collapse
You're welcome. Next time, please try to follow the guides exactly - copy-pasting pays off in this case.

[Q] Boot loops after flashing ANY rom

I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309
impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.
You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4
Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")
My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date

[Q] Desire S Boot Failure/2.00.0002/S-ON/ Recovery BootLoop

So, I recently got an HTC Desire S with H-Boot version 2.00.0002 and thus I could not use Revolutionary Tool to root it. The alternative to HTCDev unlock would be to use RUUs to downgrade the H-Boot but I could not figure out which RUU to select in the list at shipped-roms. Thus I HTC Dev unlocked it thinking that the only problem would be having to flash the boot.img of the rom I install separately.
But when I flashed Cyanogen Mod 10 and flashed the file, the rom worked. I had to restart it but i found that no matter what rom i install, the phone always boots to the recovery! I tried it with multiple roms includind the Xperia rom, and roms based on CM. Then I tried the Virtuous rom with the same result. Then I tried the Saga3d rom and it rebooted sucessfully!!!
Thinking the problem was solved, I flashed the CM 10 JB rom I wanted again but it once again booted to recovery when I rebooted it. Seems like the only way I can make them reeboot is to flash the boot.img file again and again! A thread suggested flashing 4ext recovery but the same thing happened. I even tried to reflash the Saga3d rom but it didn't reboot this time!!!
So after careful but failed research, i created this question. Can anyone help me? I think a new RUU with an earlier (0.9*) H-Boot would help but I don't know how to pick one!!! I'll post some pics and hope anyone will suggest me an RUU or other solution.
THANKS IN ADVANCE.
(P.S I'm using a custom rom right now (reaper) cuz I don't know how to find the stock)
Anyone?
Hi,
Stock rom could be found on http://www.androidruu.com/index.php?developer=Saga
Hope it helps
P.
pfloc said:
Hi,
Stock rom could be found on ....
Hope it helps
P.
Click to expand...
Click to collapse
Hi,
Thanks for the response but the problem is I don't know which one of these RUUs to select. I can't seem to find where to look for what are their supported cidnums, or build number, or software number. Thats why I hoped a pro would help me select one. My cidnum is HTC_001.
Thanks again. :good:

Categories

Resources