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..
Related
So, I'm in a bad spot with my Nexus S 4g. I had CWR installed on it and flashed a new rom yesterday to try it out, I had been running Deck's rom. I don't remember what the name of the rom was I flashed yesterday, but I didn't care for it so I was going to flash MIUI this morning. When i went to boot into recovery it brought me to the fastboot screen and said no boot or recovery img. From there I rebooted back to the rom I have loaded and tried to search around on the interwebs a little. I went into ROM Manager and tried to reflash the recovery, but that didn't work as upon reboot it did the same thing in returning to fastboot everytime. I did some more searching and I found info on an app called flash image that's in the app store that will flash kernels and recovery's. So I dl'd it and tried to reflash clockwork recovery from there. It gave me an error about not enough free space on the device. I went back to ROM Manager and set it to erase the current recovery before it flashed the new one in hopes that it would resolve the issue. So I reflashed the recovery again and went to boot to recovery. Now I can't get past the bootloader/fastboot screen at all. It won't boot to android, it won't boot to recovery. My pc won't recognize the phone to allow me to install the drivers for adb...I'm at a loss.
Any help would be greatly appreciated as I have no idea what to do next.
Thanks in advance...
Did you try to flash recovery through the computer from the cmd window, Because ROM manager doesn't flash recovery properly sometimes.
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?
Question on rooting.(Not bricked lol),so about a week ago I got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before rezipping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
WhatTheAndroid? said:
So about a week ago I rooted my phone,got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before recapping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
Click to expand...
Click to collapse
I know it happened for me -- Sometimes it wont enter recovery for me even in the bootloader and I have to Power+Vol Down to get it back into the bootloader. But it makes sense this would be a normal process because if you flash the boot.img without any OS files to load after it will just boot-loop.
Once I get back into bootloader and can get back into recovery and flash the ROM everything goes well after -- although I'm not sure if you would classify this as the "norm" but it certainly happens for me
WhatTheAndroid? said:
Question on rooting.(Not bricked lol),so about a week ago I got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before rezipping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
Click to expand...
Click to collapse
I didn't have a bootloop. Mine just sat on the first htc bootscreen and did nothing. I had to do a simlated battery pull to get it to shut off. Generally I flash the rom in recovery then reboot to fastboot and flash the boot.img. This way you don't have to worry about the bootloop or simulated battery pull.
your just supposed to extract the boot.img not the whole rom. you should never be rezipping anything. if you are on windows i hope your using a real archive utility like 7-zip or winrar. just open the zip and drag the boot.img out which extracts it. flash the boot.img in fastboot then flash the rom in recovery.
getting into recovery from bootloader can be a problem at times but i haven't had this problem once since changing over to twrp 2.3.1.0.
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.
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Observer000 said:
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Click to expand...
Click to collapse
I think, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Kungfu73 said:
I think, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Alright, I check bootloader state, it says bootloader unlock done means it's unlocked.
I am going to flash twrp 3.0.2 and will update you soon!
Kungfu73 said:
I think, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Observer000 said:
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Click to expand...
Click to collapse
Did TWRP 3.0.2 ultimately work with this?
If worked, I am also curious to know how much space is left there for apps in device memory, since the ROM seems to be Marshmallow based.