Ok so I flashed the cm10 rom today and used CMD to add the boot.img for cm10 but now I want to go back to Viperrom. I flashed the original boot.img using cmd again but I got stuck in a boot loop (kind of) what I mean by that is that if I flash cm10 from the recovery It works fine but I can't flash any other rom without triggering the bootloop so how do I fix this? I can still access both the bootloader and the recovery and I don't want to go back to stock, just to ics roms. Thank you!
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
frdd said:
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
Click to expand...
Click to collapse
Thanks, so do you have to flash the img of every rom you want to use?
Related
Hello everybody.
i have a problem....with my freshly unlocked S.
I first started off with the aio and unlocked my OneS and flashed twrp afterwards.
Then I flashed my first ROM (Liquid), did a full wipe and did a reboot...but it hangs in the boot animation.
With another ROM i got the same result...so iswitched the to clockword mod recovery i flashed again....same result.
Can someone give me a hint what could be wrong????
K-Nose said:
Hello everybody.
i have a problem....with my freshly unlocked S.
I first started off with the aio and unlocked my OneS and flashed twrp afterwards.
Then I flashed my first ROM (Liquid), did a full wipe and did a reboot...but it hangs in the boot animation.
With another ROM i got the same result...so iswitched the to clockword mod recovery i flashed again....same result.
Can someone give me a hint what could be wrong????
Click to expand...
Click to collapse
Usually TWRP will flash the boot.img for you. I have heard situation where it doesn't.
Just extract the boot.img from the ROM file and use fastboot.
Code:
fastboot flash boot boot.img
baseballfanz said:
Usually TWRP will flash the boot.img for you. I have heard situation where it doesn't.
Just extract the boot.img from the ROM file and use fastboot.
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
That did the Trick! THANK YOU VERY MUCH!
Hello guys I just rooted my phone I flashed cwm recovery 5.0.2.0 I tried to flash a rom but after doing a full wipe and flashing the rom and rebooting it the phone didn't boot into the rom it booted into cwm and I have tried different roms and none of them worked same thing happend again and again the rom does not boot the phone boots into cwm HELPPPP PLEASEEEE !!!!!!!
tugonu said:
Hello guys I just rooted my phone I flashed cwm recovery 5.0.2.0 I tried to flash a rom but after doing a full wipe and flashing the rom and rebooting it the phone didn't boot into the rom it booted into cwm and I have tried different roms and none of them worked same thing happend again and again the rom does not boot the phone boots into cwm HELPPPP PLEASEEEE !!!!!!!
Click to expand...
Click to collapse
How you root your phone? Revolutionary or HTCDev?
by using htc dev then I flashed cwm then super user
tugonu said:
by using htc dev then I flashed cwm then super user
Click to expand...
Click to collapse
You need to flash boot.img everytime that you flash a new rom.
1. Extract boot.img from the ROM you want.
2. boot into recovery, select fast boot
3. In command line type: fastboot flash boot boot.img [press enter] (in folder where you installed fastboot)
thats it!
should we flash the rom afterwards
tugonu said:
should we flash the rom afterwards
Click to expand...
Click to collapse
flash the rom and then do what i say
where are boot images located in the roms - couldnt find them
Which rom are you trying? Normally there is in root of zip
Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks
You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.
Ok so today i tried to flash the JellyBam ROM 6.3.0. I read in the comments that first i had to go into bootloader mode and flash the boot.img that was in the ROM .zip when i did that it said it successfully flashed the boot.img but then when i tried to reboot it just got stuck in a bootloop. I was able to eventually get back to twrp with the fastboot boot recovery.img command but when i try to flash my old ROM (ViperXL) the Aroma installer comes up but with a weird blue gradient over it. And when it finishes it just goes right back to bootlooping. How do i fix this!? please help! thanks in advance.
All you did was flash the boot.img.
You have to flash the actual ROM also.
i forgot to mention that i did flash the rom when i was able to get back to recovery but i still got the bootloop
Sounds like a rom/kernel conflict. You flashed a cm kernel, and you can't run a sense rom (Viper) over that.
so what should i do then?
Factory reset and flash the apporpiate combo..
i just want to ask how can i flash this rom on my device . im running hboot 2.02.002 and htc dev unlock .
and im using a sony panel
i do this steps . wipe dalvik and cache
flash the rom
go to bootloader . flash the boot.img via fastboot
then reboot .
but after doing it . it is rebooting and force close . what should i do
it says , unfortunately . system ui has stopped then it got to the boot . pelase help me
What recovery are you using?
Format all partitions except sd, flash rom through recovery, flash gapps through recovery then flash boot.img with adb whilst phone in fastboot. If your stuck at any point click the link in my sig, post 2 contains a link to how to install 4ext and custom rom with clear instructions that you could copy and paste into cmd
He who sleeps on the floor will not fall off the bed.
- Robert Gronock.
jugg1es said:
What recovery are you using?
Format all partitions except sd, flash rom through recovery, flash gapps through recovery then flash boot.img with adb whilst phone in fastboot. If your stuck at any point click the link in my sig, post 2 contains a link to how to install 4ext and custom rom with clear instructions that you could copy and paste into cmd
He who sleeps on the floor will not fall off the bed.
- Robert Gronock.
Click to expand...
Click to collapse
im using 4ext recovery . so these are the steps
reboot to recovery
format all partitions except sd
flash rom then flash gapps
then reboot to bootloader .
then flash the boot.img via fastboot flash boot boot.img
then reboot normally .
is this ryt ? is my hboot is okay ? or should i change it ?
2easy4you said:
im using 4ext recovery . so these are the steps
reboot to recovery
format all partitions except sd
flash rom then flash gapps
then reboot to bootloader .
then flash the boot.img via fastboot flash boot boot.img
then reboot normally .
is this ryt ? is my hboot is okay ? or should i change it ?
Click to expand...
Click to collapse
That's it, hboot is fine, if your flashing a newer version of the same rom you can get away with just formatting cache and dalvic, you'll still need to flash the boot.img though.
He who sleeps on the floor will not fall off the bed.
- Robert Gronock.
jugg1es said:
That's it, hboot is fine, if your flashing a newer version of the same rom you can get away with just formatting cache and dalvic, you'll still need to flash the boot.img though.
He who sleeps on the floor will not fall off the bed.
- Robert Gronock.
Click to expand...
Click to collapse
thanks . already hitted the thanks button too . im using aosp build 9 by flinny's now . btw i just want to ask what is the stable JB rom now ? sorry for my bad english .