Hello
After flashing (by mistake) ViperSAGA v1.1.0 update without v1.0.0 my phone didn't boot.
(1)The phone pass the splash HTC screen, turns black, restart and go into recovery.
So i tried to restore my backup (wich ran with RUU official ics) i get no errors but the phone did like previously (1)
i'm "**unlocked**" via HTC dev
HBOOT 2.02.002
I use CWM 5.0.2.0
I already read several post but i didn't find what to do.
I need help to revive my phone in any state (rooted, stock, any android version)
Sorry for bad english
boot.img?
I'm a noob, i don't know what is it or were can i find this...
Edit :
You mean i must try to flash boot.img from my backup ?
fastboot flash boot boot.img
Google it, don't ask me anything - I'm tired of answering the same all over again. Such a basic thing, and every week there's yet another noob that doesn't read.
Lee74 said:
I'm a noob, i don't know what is it or were can i find this...
Click to expand...
Click to collapse
Being 'A Noob' is no excuse for the failure/refusal of you and so many others to follow the Forum Rules - starting with;-
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
Click to expand...
Click to collapse
This is why people start to get fed up - at least a hundred people before you have asked the same question because they also failed to search or read before doing something.
.
GO into your recovery and wipe data, cache, dalvik cache and battery stats for best performance. Now flash ViperSAGA v1.0.0 then once that's installed you can flash v1.1.0 over it.
The reason why it stopped working is because v1.1.0 relies on all the apps and framework in v1.0.0 so it doesn't have many apps and just contains updates etc.
I hope this helped you. If it did, please click the thanks button!
Thanks for all your replies
I tried all you said :
-flash (fastboot) boot.img, reboot
or
-wipe data,cache... flash viperSAGA v1.0.0, flash viperSAGA v1.1.0, reboot
Nothing worked
Lee74 said:
Thanks for all your replies
I tried all you said :
-flash (fastboot) boot.img, reboot
or
-wipe data,cache... flash viperSAGA v1.0.0, flash viperSAGA v1.1.0, reboot
Nothing worked
Click to expand...
Click to collapse
Flashing the boot.img via fastboot should've helped.
Make sure you flashed the correct file, the one that is included in the zip file.
If the problem persists you could try other ROMs (I've been using CM10.1 by Flinny) or run ICS RUU.
Sent from my Desire S using xda app-developers app
I followed this guide http://forum.xda-developers.com/showthread.php?t=1525100 from step 4) and it worked, thanks all
Related
Hi, tried to find the info i need, but coudn't find a situation similuar situation (i think) to mine.
1. I unlocked bootload using htcdev
2. I rooted with super one clikc
3. Installed clockwork rom manager
4. flashed clockwork recovery
5. rebooted in recovery
That's were it goes wrong. I keep getting the mobilephone icon and red warning triangle...
am i overlooking anything here? sorry for probably the dumb question!
ow yeah, goal of this whole thing: install custom rom
That's stock HTC recovery, you can't flash CWM via ROM Manager. Use this tutorial - http://forum.xda-developers.com/showthread.php?t=1484753
You need to setup adb for this. Use this - http://forum.xda-developers.com/showthread.php?t=1272595
shrome99 said:
That's stock HTC recovery, you can't flash CWM via ROM Manager. Use this tutorial - http://forum.xda-developers.com/showthread.php?t=1484753
You need to setup adb for this. Use this - http://forum.xda-developers.com/showthread.php?t=1272595
Click to expand...
Click to collapse
+1
Yup, do what shrome says. You'll be up and running in a couple of seconds.
oke, so that did the trick.
I got in the clockwork recovery. wipe cache/data and flashed the following .zip
- Endymion V3.1
- Endymion V3.1 addons
- Endymion V3.4 update.
Now it's stuck on HTC logo screen? Did i miss out something?
*edit* my bad, i have to flash the boot.img (in endymion 3.4) via fastboot right?
Yup, you have to. Try this
http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
alright, got it booted! thanks for the pointers and guidance! big big thanks
Happy to help Remember, you have to do this every time you flash a ROM
I'm having problems flashing my Desire S with ICS based roms. GB roms work fine, but any ICS rom I flash gets stuck on boot on a lit up black screen. I have tried a variety of roms, flashed both on CWM and 4EXT but the issue persists. Is there some kind of special procedure for ICS roms ?
Did you
1. Wipe all partitions except SD
2. Wipe dalvik + cache
Edit : And the procedures same for flashing ics and gb roms, unless the OP specifically tells you to do otherwise
I did all possible wipes and It's still the same. Any more ideas ?
tomkow4 said:
I did all possible wipes and It's still the same. Any more ideas ?
Click to expand...
Click to collapse
did u u unlock with HTCDEV.com ? if u did just flash the boot.img inside the rom you want if u never then either the rom takes a long time to boot or your not doing the wipe properly
give me some specs of your phone
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
tomkow4 said:
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
Click to expand...
Click to collapse
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Vodka69er said:
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Click to expand...
Click to collapse
This. Exactly. I mean I have a MIUI GB rom so, I guess it's not about flashing a rom but trouble with ICS ones. So I figured that those must have something different about them or have a specific prerequisite. Others have flashed their D S's, so I'm kind of lost.
Can you post what you see on your bootloader
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC - boot
Aug 22 2011, 15:22:13
@op
I know that this is covering old ground, but I've not seen an actual answer
Have you ever used 'fastboot flash boot NAME.IMG' command?
Swyped from my DesireS
http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/ - this is the guide I followed.
On a side note, I did a full wipe of everything I could and still no luck with ICS roms. I think I'll leave it alone.
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
ben_pyett said:
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
Click to expand...
Click to collapse
To answer directly - I don't remeber/don't think so. But honestly didn't care much since my roms ran. Right now I'm on MIUI.
But the remark on the kernel got me thinking - I don't really know how to approach this, should I find some kernel and flash it?
On your pc you need to open the ICS ROM zip file and take out a file called boot.img
After flashing the Rom you must then use the fastboot command from your PC, as you did when you flashed your recovery.
You must then issue the command 'fastboot flash boot boot.img'
see below for the full instructions
HappyEmu said:
If you unzip your ROM's Zip-file (the one you want to flash, you'll find a file called "boot.img". Move it into the same folder as your adb and fastboot executables (Android SDK) and flash it using fastboot.
To be a little more specific:
1. Extract boot.img from ICS rom zip file and move it in the same folder as your fastboot.exe (Android SDK) on your PC
2. Flash the ICS Rom as usual from recovery (don't forget to first perform the full wipe/format including the boot partition)
3. Boot into fastboot mode, connect your phone to your PC and flash boot.img using fastboot
Code:
fastboot flash boot $pathToYourBootIMG\boot.img
4. Reboot
Click to expand...
Click to collapse
Swyped from my DesireS
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
eyahl said:
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
*Bump*
Sent by my fingers to your head.
suku_patel_22 said:
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Click to expand...
Click to collapse
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
tomkow4 said:
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
Click to expand...
Click to collapse
I suspect that you're suffering the problem on other ROMS now as you're wiping the boot partition and therefore have no kernel.
[Q] How long do you wait on boot? you must be patient as first boot can take a while (although not longer than 10minutes).
A video would be a great way of showing the problem...Try to capture everything....
Your bootloader screen....
All the partition wipes
The Rom flash
The fastboot boot.img flash
and then what happens after...
Kind of noobish on my end, but as I was making the video - and did everything according to protocol just as earlier - it worked . I flashed BlackICE 5.5. Christ. Thanks anyway for the patience guys (I assume )
I'm new at all the rooting and stuff, but I managed to root my phone and install the primo-S Rom.
Everything worked, just by following all the links on this forum (thx for that).
But I wanted to install Fallout rom to see the difference between Primo-S and Fallout, but after the installation of Fallout,
I don't have Wifi. At the first setup, the Wifi is on, but keeps on searching for Wifi-connections, and it stays that way.
So I installed Primo-S again, and it worked fine again.
Somebody knows what the cause could be, do other users have this problem too with Fallout Rom?
Sorry to post this here, but I can't report this bug in the Fallout-section, since I don't have 10 posts yet. (maybe I should start spamming )
Did you flash boot from fallout?
Sywepd form my DsereiS
Try downloading fallout again or checking md5 of the .zip, i have this romand everything is fine
Sent from my HTC Desire S using xda app-developers app
Ok, so I tried it again:
I use revolutionary recovery.
First Wipe data/Factory reset
Then Wipe dalvic cache.
Then install the fall-out Rom v4.3.
When the phone reboots, I go through the initial set-up.
Then to 'Settings' - "Wifi", but the status says 'Fault'.
I can't change it to 'ON'.
Like I said before, did you separately flash the fallout boot through fast boot?
Sywepd form my DsereiS
I didn't understand at first what you meant with that.
But I suddenly remembered I did this for the Primo-S Rom also.
So I extracted the boot.img from the zip-file, flashed it with fastboot, and now it seems to work
thx for the help.
BlaRock86 said:
I didn't understand at first what you meant with that.
But I suddenly remembered I did this for the Primo-S Rom also.
So I extracted the boot.img from the zip-file, flashed it with fastboot, and now it seems to work
thx for the help.
Click to expand...
Click to collapse
U used htcdev. U would have to flash boot.img separately everytime.
Sent from my HTC Desire S
We learn each day
Oh well, now I know, I won't make this mistake again.
Hi,
as the title says I cant get jellytime to boot on my DS. I did a full wipe and flashed boot image, since I am HTCdev unlocked and s-on. Do any of you experience the same problem/ is there a solution to this problem?
I would have posted this in the jellytime thread, but i have not met my 10 posts quotum yet.
Thanks :fingers-crossed:
Stupid question, but did you flash the Rom between full wipe and flash boot.img?
eyahl said:
Stupid question, but did you flash the Rom between full wipe and flash boot.img?
Click to expand...
Click to collapse
yes is wiped, then installed the rom and then flashed boot image. also downloaded the rom again, and tried a couple clean installs but no luck. im sure i use the right boot image.
Upgrade your hboot, goodness me. they are tutorials all over the development and general section. I personally lean to revolutionary 7.x
Sent from my HTC Desire S using xda app-developers app
my hboot is 2.00.002, i thought that was good. am i wrong?
did you download from the OP link or a mirror provided in the thread, as I read there was issue with corrupt mirror in thread.
I suggest that you consider re-downloading or check md5sum of your download , could be you corrupt which would explain.
i checked md5sum and others who downloaded from there were able to boot, so i dont think that is the issue
giel123 said:
Hi,
as the title says I cant get jellytime to boot on my DS. I did a full wipe and flashed boot image, since I am HTCdev unlocked and s-on. Do any of you experience the same problem/ is there a solution to this problem?
I would have posted this in the jellytime thread, but i have not met my 10 posts quotum yet.
Thanks :fingers-crossed:
Click to expand...
Click to collapse
That's problem with s-on. Did you reflash boot image in fastboot? fastboot flash boot boot.img (from jellytime.zip you just installed, first install jellytime.zip and than reflash boot.img in fastboot, it works. If you want to restore previous version, you need to reflash boot.img from that version as S-ON phone cannot write boot partition in recovery.)
Try doing full wipe, then flash boot.img and flash the rom last. That should work. Try using boot.img flasher software. It worked for me
Sent from my HTC Desire S using xda premium
giel123 said:
Hi,
as the title says I cant get jellytime to boot on my DS. I did a full wipe and flashed boot image, since I am HTCdev unlocked and s-on. Do any of you experience the same problem/ is there a solution to this problem?
I would have posted this in the jellytime thread, but i have not met my 10 posts quotum yet.
Thanks :fingers-crossed:
Click to expand...
Click to collapse
Or, if you have 4ext touch recovery and choosed the format all ( except sd ) function , that could be the problem. I noticed that, 4ext touch recovery's format all function sometimes didn't work properly! In that case you have to format the partitions individually. It happened to me with cooldroid. I used the format all function and sense kept crashing. When I formatted the partitions individually it worked!
johny.attila said:
Or, if you have 4ext touch recovery and choosed the format all ( except sd ) function , that could be the problem. I noticed that, 4ext touch recovery's format all function sometimes didn't work properly! In that case you have to format the partitions individually. It happened to me with cooldroid. I used the format all function and sense kept crashing. When I formatted the partitions individually it worked!
Click to expand...
Click to collapse
I've personally been using 4ext for over a year and have never experienced the problem you describe, I've probably used the format all (excluding sd) option hundreds of times...
if you genuinely believe there is an issue then report it on the 4ext thread
Sywepd form my DsereiS
It tought it's a common issue because I am not the only one, who experienced this That's the reason why I suggested to wipe individually
johny.attila said:
It tought it's a common issue because I am not the only one, who experienced this That's the reason why I suggested to wipe individually
Click to expand...
Click to collapse
I'm by no means having a go, just pushing the point as max the creator of 4ext would be keen to get any feedback on this issue..if it is one.
Who else has experienced the problem, do you have any thread references urls?
Sywepd form my DsereiS
Hello everyone!
As the title said, I got a bootloop after trying to install Android 4.2.1 Jelly Bean.
How I did it:
1. Installed Android 4.2.1 Jelly Bean and Google apps for CyanogedMod 10.1 to my computer and transfered them to my phone's root.
2. Made a backup of the current version.
3. Installed first the ROM and then Google apps.
4. Rebooted my phone and now I got the bootloop.
I know that I didn't wipe data/cache/dalvik cache, that's probably the problem. I tried to resotre the backup I made but I get an error that says "MD5 mismatch!". I've also tried to wipe data/cache/dalvik cache and then install it again, I still get the same problem. The file isn't corrupted because I downloaded it several times and still same problem. I also tried to install it twice in a row but that doesn't work either. I can get into the bootloader and recovery menu.
Phone info:
HTC Desire S
HBOOT-2.00.0002
S-On
Revolutionary CWM v4.0.1.4
I'm pretty new to this so please give easy steps on what I could do.
Thank you!
As your phone is still s-on, you have to flash the boot.img (from the new rom) in fastboot every time you install a new rom.
teadrinker said:
As your phone is still s-on, you have to flash the boot.img (from the new rom) in fastboot every time you install a new rom.
Click to expand...
Click to collapse
Sorry for the noob question, but how do I do that?
EDIT: I forgot to mention that it bootloops on the CyanogenMod picture, not on the one with the HTC logo.
Google it... It has been mentioned innumerable times on this forum....
Tapatalked from Desire S running Andromadus
ipsvtt deciphers
Znipy said:
Sorry for the noob question, but how do I do that?
EDIT: I forgot to mention that it bootloops on the CyanogenMod picture, not on the one with the HTC logo.
Click to expand...
Click to collapse
dude, this is on the FIRST page of General forum
http://forum.xda-developers.com/showthread.php?t=1525100
And your MD5 mismatch almost certainly means that you created the NanDroid backup, then renamed it or moved it.
Everything works perfect now! Thank you!