I have serious problem in flashing these 3 ROMs. I have done everything right but I am still stuck in bootanimation... I have JB hboot but that is no problem because I correctly changed parameters in updater-script but without success. And tried to flash boot.img several ways:
- manually via command: fastboot flash boot boot.img
- via Desire X All in one Kit
- via Boot IMG Installer
but nothing helped me, still stucked at bootanimation...
Is there any general way how to fix that for all of these AOSP ROMs? If not I would like to successfully flash at least CM 9. Does anybody think that the main problem might be in JB hboot? Please help me...
melendi said:
I have serious problem in flashing these 3 ROMs. I have done everything right but I am still stuck in bootanimation... I have JB hboot but that is no problem because I correctly changed parameters in updater-script but without success. And tried to flash boot.img several ways:
- manually via command: fastboot flash boot boot.img
- via Desire X All in one Kit
- via Boot IMG Installer
but nothing helped me, still stucked at bootanimation...
Is there any general way how to fix that for all of these AOSP ROMs? If not I would like to successfully flash at least CM 9. Does anybody think that the main problem might be in JB hboot? Please help me...
Click to expand...
Click to collapse
See post 5 in Shadow ROM, did you do like that?
xpirt
Yep, updater-script is modified for my JB hboot as by ShadowCodeGaming guide... and now there is no problem in flashing! I do not understand! I did it several times and now it works! But I have different question and I do not want to make a different thread for that, maybe it is a silly question... As I have JB hboot now I have problems with backing up any of the ROM... Can it be because I use TWRP recovery made for ICS with my JB hboot? Can it be unstable???
melendi said:
Yep, updater-script is modified for my JB hboot as by ShadowCodeGaming guide... and now there is no problem in flashing! I do not understand! I did it several times and now it works! But I have different question and I do not want to make a different thread for that, maybe it is a silly question... As I have JB hboot now I have problems with backing up any of the ROM... Can it be because I use TWRP recovery made for ICS with my JB hboot? Can it be unstable???
Click to expand...
Click to collapse
Yes. You have to use JB recovery to backup and later restore.
what happened is something like this:
ICS hboot
1.boot
2.system
3.data
4.cache
5.emmc
JB hboot
1.boot
2.data
3.cache
4.system
5.emmc
So the positions of system, data, cache are changed. The ICS recovery will see the second partition as system when infact it is data.
IF, and i say IF, u backup using ICS recovery, and restore also using it, it will blindly restore the contents from where it read it so it will work. so technically, you can back up using TWRP, but later, restore also using same TWRP.
I hope you got my point.
Regards
Yasir
P.S The layout i wrote above is just for example and not the real one.
Hi Guys I'm on the same problem but I'm on ics hboot 1.24 s-on but the cm9 based roms just won't boot up.. it stucks on boot animation. Just tried different kernel but nothing works... Can anyone help?
Sent from my HTC Desire X using xda app-developers app
yesman89 said:
Hi Guys I'm on the same problem but I'm on ics hboot 1.24 s-on but the cm9 based roms just won't boot up.. it stucks on boot animation. Just tried different kernel but nothing works... Can anyone help?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
The first time you tried it you had stock boot.img? Which recovery are you using?
No, I tested it with the boot.IMG from the zip file and with nexus kernel v3. I use team win recovery.
Sent from my HTC Desire X using xda app-developers app
yesman89 said:
No, I tested it with the boot.IMG from the zip file and with nexus kernel v3. I use team win recovery.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
You have to flash boot.img inside zip and use JB recovery if you have JB hboot
xpirt
Hi. Im on ICS hboot (1.24) and I used boot.img form zip file, but it won't boot up. (Waited 2h but nothing happend.) So I installed boot.img from neXus PRIME but this also don't worked for me.
Sent from my HTC Desire X using xda app-developers app
Now i get it. I just cleaned up my SD card and then it worked.
Sent from my HTC Desire X using xda app-developers app
Related
So, I rooted my phone last night and ever since I've been stuck in bootloop. I loaded one rom and it was in bootloop all night until the phone died. I charged the phone up, wiped it and tried another, stuck in bootloop for hours with nothing working. Now, the bigger problem is, I - being an idiot - forgot to do a nandroid backup so there is nothing to restore too, yet when I set it to factory settings it's once again stuck in bootloop.
All my phone now displays is the green HTC logo on the white background, until the phone battery dies.
So... how screwed am I?
EDIT: CDMA, S-on, 1.50, I used HTC dev to root it.
Did you root with HTC dev. You need to flash the boot.IMG using fastboot.
Sent from my HTC Desire S using XDA
MSK01 said:
So, I rooted my phone last night and ever since I've been stuck in bootloop. I loaded one rom and it was in bootloop all night until the phone died. I charged the phone up, wiped it and tried another, stuck in bootloop for hours with nothing working. Now, the bigger problem is, I - being an idiot - forgot to do a nandroid backup so there is nothing to restore too, yet when I set it to factory settings it's once again stuck in bootloop.
All my phone now displays is the green HTC logo on the white background, until the phone battery dies.
So... how screwed am I?
Click to expand...
Click to collapse
We need more info dude.
CMDA or GSM?
what rom did you try to install?
hboot 1.50 or 1.40?
S-On or S-OFF
The more info the more we can help you.
iTzLOLtrain said:
We need more info dude.
CMDA or GSM?
what rom did you try to install?
hboot 1.50 or 1.40?
S-On or S-OFF
The more info the more we can help you.
Click to expand...
Click to collapse
CDMA, S-on, 1.50, I used HTC dev to root it. CM 9 Nightly.
Do what I said. Boot your phone into the boot loader. Select fastboot. Stick the boot.IMG from the Rom you used into the folder on the pc that you used with htcdev.
Connect your device.
Open up command prompt. Navigate to the folder in command prompt where you put the boot.IMG
Type fastboot flash boot boot.IMG
If it works it will say so restart your phone and enjoy.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
Do what I said. Boot your phone into the boot loader. Select fastboot. Stick the boot.IMG from the Rom you used into the folder on the pc that you used with htcdev.
Connect your device.
Open up command prompt. Navigate to the folder in command prompt where you put the boot.IMG
Type fastboot flash boot boot.IMG
If it works it will say so restart your phone and enjoy.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
If you hadn't said anything I probably would have been running around in circles for the rest of the day. I just did and I'm waiting for it to restart right now. Hopefully it works.
Hopefully it will work. If you flash anymore roms you have to do the same flash boot.img using fastboot since you unlocked with HTC dev.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
Hopefully it will work. If you flash anymore roms you have to do the same flash boot.img using fastboot since you unlocked with HTC dev.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Meaning I can just nandroid backup this rom? Or do I have to reflash it then flash the new ones over it?
If you want to flash a new rom do a nandroid backup first and then wipe everything. But everytime you flash a new Rom you have to flash the boot.IMG seperatley that was supplied with the Rom if that makes sense. This also applied when doing a recovery.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
If you want to flash a new rom do a nandroid backup first and then wipe everything. But everytime you flash a new Rom you have to flash the boot.IMG seperatley that was supplied with the Rom if that makes sense. This also applied when doing a recovery.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Unless the boot.IMG is automatically with each rom that does not make sense. However, if that means (which I pretty sure it does, I just need that extra clear clarification) that a new boot.IMG is supposed to be supplied with every single new ROM then that would explain why my phone is still in bootloop. No changes since last time I was on, about an hour ago I took the battery out and restarted it.
So it's still in bootloop whenever I try anything.
Help as well...
Stuck in the same problem. Hboot 1.50, S-on, and I'm trying to load Evergreen's CM7 port. I'm also using CWM 4.x (can't remember number, just the non touch version). Whenever I try to start my phone all I get is the white HTC screen with the little vibrate, then the black screen, and then the HTC screen once again and so on. I've tried flashing the boot from the file and then flashing the ROM with and without the boot.img in the .zip file. Help me. Please.
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
If that last reply was meant me, I've already tried that. Doesn't change anything at all.
Ah ok you mentioned you flashed the boot.img first that's all
Also try formatting your sd card or use a spare one and format that and then flashing the Rom and boot.IMG. I had to do that with my desire s.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
That worked. Holy ****, that worked! Thank you so much!!
Spazz Monk3y said:
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
doesnt work for me :<
Unlocked HBOOT 1.53.0007
rooted with superuser
S-ON
Revolionary CWM v4.0.1.4 (also tried to flash 4EXT but it doesnt work!!:/ )
ROM: cm-9-DevilToast-0.7.5-shooteru.zip
any tips?
sabbath88 said:
doesnt work for me :<
Unlocked HBOOT 1.53.0007
rooted with superuser
S-ON
Revolionary CWM v4.0.1.4 (also tried to flash 4EXT but it doesnt work!!:/ )
ROM: cm-9-DevilToast-0.7.5-shooteru.zip
any tips?
Click to expand...
Click to collapse
Get s-off using the wire trick.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Hi guys,
I'm getting a little problem installing the cyanogenmod 9 on my device, so I founded that I have to "fastboot flash boot boot.img" when i flash cyano. I know how to do that, but I want to ask you: I kept s-on to prevent damages on my smartphone, are there any serious risks flashing boot that way?
Thanks,
Ruben.
As long as you flash the right one, i dont think so but i am not sure. I s offed few weeks back, i can recommenf it
sent from my almighty forbidden viper evo3d
as long as you flash an evo 3d(cdma OR gsm) boot.img you shouldnt have a problem. At the most the phone will bootloop which can be corrected by flashing the correct boot.img from bootloader
EM|NEM said:
as long as you flash an evo 3d(cdma OR gsm) boot.img you shouldnt have a problem. At the most the phone will bootloop which can be corrected by flashing the correct boot.img from bootloader
Click to expand...
Click to collapse
Flashing a cdma boot.img on a gsm and vice versa can brick your phone if i'm correct.. That's why some flashable kernels have shooter and shooteru files.
As I've read, shooteru is the GSM version isn't it? By the way, I'm SURE the boot is correct, because I take it directly from the ROM I'm going to flash, that is exactly for my device
Ruben92 said:
As I've read, shooteru is the GSM version isn't it? By the way, I'm SURE the boot is correct, because I take it directly from the ROM I'm going to flash, that is exactly for my device
Click to expand...
Click to collapse
Shooteru i gsm yes, if you take the boot.img from the rom it shouldn´t hurt.. since flashing the rom itself is doing the same. It's just a kernel.
I'm doing it, let's see if it works
that why i included the OR its either cdma or gsm. different devices as far as the kernel is concerned
Uff, the ROM keeps rebooting infinite times! Now I'm trying to reflash the rom and boot.img...
First do a full wipe, install rom and then flash kernel
sent from my almighty forbidden viper evo3d
I did this before n i got wifi error so i flash back to custom kernel to get back my wifi. Is there any way to fix wifi error after flashing stock boot.img?
Sent from my HTC EVO 3D X515m using xda premium
klect said:
First do a full wipe, install rom and then flash kernel
sent from my almighty forbidden viper evo3d
Click to expand...
Click to collapse
Done... Something like, uh, 5 times... Didn't worked...
What is your hboot? If its 1.53 the rom wont boot. This hboot is known to have issues with CM. I would suggest you try out some other ics rom for now.
You should get s-off and downgrade your hboot if you want agrabrens CM
Sent from my Evo 3D GSM
---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------
KayKram said:
I did this before n i got wifi error so i flash back to custom kernel to get back my wifi. Is there any way to fix wifi error after flashing stock boot.img?
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
Wifi not working in stock kernel means that the stock kernel isnt compatible with the rom you are trying to run. You could look for a kernel with the most stockish setting. I think anryl, coolexe and "the other one" all can be set up to behave mostly like the stock htc kernel. Just have to tweak it right
Sent from my Evo 3D GSM using Tapatalk 2
I just want to point out to the op that anything you flash on your phone has the potential to damage your phone and worst case scenario: bricking your phone. Just make sure you research and do a lot of reading. But I'm pretty sure you already knew that.
klect said:
First do a full wipe, install rom and then flash kernel
sent from my almighty forbidden viper evo3d
Click to expand...
Click to collapse
hi...im a newcomer...never root any phone before...my phone also still S-OFF...im also want to use CM9 but im also having bootloop...erm...I have some question to ask someone that can help me here...
1. what do you means by FULL WIPE...? hope you can list because im confuse...
2. after im done with FULL WIPE...what should i do first...? either install rom from SD or 'Fastboot flash boot boot.img'....?
Hope you guys can help me...n sorry for my broken english...THANKS
S off or s on? Your phone comes s on, with s off you dont.need fastboot flash. Full wipe in.recovery > wipe all user data + dalvik and cache.
First flash the rom, then flash.kernel
sent from my almighty forbidden viper evo3d
full wipe, install rom, then flash boot.img,
Assuming you have a custom recovery installed, you will have an option to do a full-wipe.. It wipes a few partitions on your device and I believe cache from your phone... It does not wipe your personal data on the sd (other than apps installed on phone) card so don't worry about that. He meant install the rom first then fastboot flash boot boot.img in fastboot.
.
affiqaznan8 said:
hi...im a newcomer...never root any phone before...my phone also still S-OFF...im also want to use CM9 but im also having bootloop...erm...I have some question to ask someone that can help me here...
1. what do you means by FULL WIPE...? hope you can list because im confuse...
2. after im done with FULL WIPE...what should i do first...? either install rom from SD or 'Fastboot flash boot boot.img'....?
Hope you guys can help me...n sorry for my broken english...THANKS
Click to expand...
Click to collapse
Ruben92 said:
Hi guys,
I'm getting a little problem installing the cyanogenmod 9 on my device, so I founded that I have to "fastboot flash boot boot.img" when i flash cyano.
Click to expand...
Click to collapse
If you are using fastboot to flash the boot.img, why not just start your recovery with fastboot using the following command:
fastboot boot recovery.img (where "recovery.img" is the name of the recovery file you flashed)
That will put your recovery in a mode where it can flash boot.img as part of the ROM or kernel zip and then you won't have to extract it to flash it separately. You also need to disable SmartFlash (S-ON) in the tools menu if you are using 4EXT recovery when using the fastboot method.
ramjet73
Please don't flame me for asking, but i couldn't find instructions anywhere. I know if your s-on and want to flash aosp roms you need to flash the boot img via fast boot. I just cant seem to do it right and end up in the splash screen indefinitely. Any help is appreciated. Thanks in advance.
This thread helped me resolve the same issue.
http://forum.xda-developers.com/showthread.php?t=1937949
Do you flash the rom first and then the fastboot boot.img, or the other way around?
mito8485 said:
Do you flash the rom first and then the fastboot boot.img, or the other way around?
Click to expand...
Click to collapse
I flashed the boot.img after I installed the rom. I'm not sure if that was the correct way, but it worked for me.
A very simple solution is to download Flash Image GUI, and use it to flash the kernel of the Rom while your phone is still booted and functional. You can do this by opening the app and locating the Rom file, then hit yes to install it to the partition. After extracted, boot into recovery, do your wipes, and flash the AOSP rom. This saves the need for a computer.
Another thing to try is to boot into recovery, flash the rom, let it boot to the boot animation, hard reboot into recovery, and reflash. (This works with Sense roms, but I haven't tried it with AOSP roms yet)
P.S.: I am S-On also
When I was s-on I would flash the rom then boot straight to bootloader, fastboot. USB and flash the boot img. This method always worked for me
Sent from my EVO using xda premium
Thanks for the help. I found that flashing the boot.IMG first then the ROM works good for me. But I will try the GUI app
Sent from my EVO using xda premium
The GUI application works as advertised but it's handy to be used to using fastboot also. Never know when your gonna need it
Sent from my EVO using xda premium
corcgaigh said:
The GUI application works as advertised but it's handy to be used to using fastboot also. Never know when your gonna need it
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I'll keep that in mind. I will educate myself about that method.
______________________________
HTC Evo 4G LTE
One question so when flashing a boot.img I pull it from Rom and fastboot flash. My question is when I do recover flash after do I leave boot image in original zipped Rom folder and recovery flash, or is it not supposed to be in it at all, being I already flashed boot.img via fastboot?
jander54111 said:
One question so when flashing a boot.img I pull it from Rom and fastboot flash. My question is when I do recover flash after do I leave boot image in original zipped Rom folder and recovery flash, or is it not supposed to be in it at all, being I already flashed boot.img via fastboot?
Click to expand...
Click to collapse
Just keep it in the zip
So everyone I have done goes through but lockscreen has no touch functions. I can't get past it any suggestions?
Sent from my EVO using xda app-developers app
Are you s-off?
What rom are you using?
Are you doing a clean install?
jander54111 said:
So everyone I have done goes through but lockscreen has no touch functions. I can't get past it any suggestions?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You are probably on the latest firmware and flashed a 3.15 rom, my guess, you need then to flash a 3.16 sense rom, aosp and 3. 15 roms touch screen doesn't work with the newest firmware, if you are s-off you can downgrade it, if you are s-on I suggest you to go to the original development thread and get s-off using baby racoon if your hboot is 2.09... Good luck
Sent from my EVO using xda app-developers app
Hi,
I flashed the MIUI rom 2 days ago using clockwork mod, but I decided to remove it due to it hanging when I received phone calls.
I tried flashing a new rom and wiped and formatted the data/system/dalvik locations but the old rom is still there and very unresponsive (it appears parts of it uninstalled).
CWM is giving me a cache unmountable error so i cannot delete the cache, flashed a new boot and rom, still no joy.
Any help would be appretiated.
- Crypto
Do you have the right recovery for your hboot installed? If you use hboot 1.24 or lower, you need a recovery for ICS. If you use hboot 1.25, you need a JB recovery.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Deleted.
See dansou's post.
xpirt
dansou901 said:
Do you have the right recovery for your hboot installed? If you use hboot 1.24 or lower, you need a recovery for ICS. If you use hboot 1.25, you need a JB recovery.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks yeah the recovery version was the problem, dont know why clockwork didnt work, flashed PHILZ recovery from the Windroid toolkit and it works fine now,
though it wont stay rooted, is that a desire x issue?