Hello,
First, sorry for my bad english and knowledge on flash/root.
I flashed Slimbean on my P700, everything worked fine, expect of the modem. I tried other ones, but didn't work.
So I decided to change the ROM and flashed CM10.2 on my L7 which was working fine until battery was empty. After loading my phone, I wanted to start it, but it stayed in a bootloop on the boot animation. I tried everything, wipe/dalvik wipe, flashing slimbean --> still bootloop
Now I thought, maybe CM11 could work, but still the same problem, I formated everything expect of sd, wipe/dalvik wipe, flashed the ROM, Gapps and kernel, but still the bootloop...
Any ideas?
It may take a while on first boot. But if it don't load you could restore a backup of you have one or flash a kdz or use LG update tool to fix your issue. Other than that make sure you have word everything in recovery and format system, data and cache before flashing a rom. Do not flash kernel before first boot unless it's required.
I can add to that to flash ROM only without gapps just to get OS to boot correctly.
I already solved it.
I whiped everything, formatted everything except of external sd and than first only flashed the ROM and rebooted, all worked, than i installed the Gaps, rebooted, and last i flashed the kernel, now it works fine but i will never ever reboot my phone or let battery get empty ^^ no more
thanks for your help
Related
UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/
Hi,
i have a problem flashing the Sentinel 5.0 Rom with the latest Trinity kernel to my rooted Nexus 10 via recovery. I tried twice now and once it booted fine but 30 minutes after restoring my apps with Titanium backup, it stopped at the google font following a reboot.
Then i wiped everything and formatted data in recovery, flashed rom, gapps, kernel and wiped dalvik/cache and fixed the permissions.
This time around it doesn't even boot to the rom, but is stuck on the google font from the beginning.
What am i doing wrong?
Something i noticed is that TWRP tells me my device does not appear to be rooted and if i want to install supersu, not sure if this
is significant.
Thank you
edit: apparently it is not the rom. I tried another rom and another kernel and the same thing is happening.
Anything else to try other than flashing stock recovery and rom?
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
mejorguille said:
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
Click to expand...
Click to collapse
Fixed it... realized I still had recovery active, booted into it with the button combo, wiped, installed cloudy pro, all is good.
Hi guys,
I have the standard note III 9005 and I had always installed CFWs on it.
I wanted to update to newer 6.0.1 Roms (had 6 roms before) but I seem to have a VERY annoying bug:
I tried to install Temaseks rom and resurrection rom but I had huge issues with it. I got bootloops although I got the newest 3.0.2.0 Team Win Recovery Project
I installed rom, GAPPS (correct version of course 6.0.1) , install rom again then delete cache and then it worked on both roms.
So a simple "install rom, GAPPS, then clean cache" didnt work. I tried to install multiple times until I got the installation! YAY! BUUUT!
Here is the fun part:
If I restarted the phone acidentally or on purpose I got stuck in a bootloop. After that the phone was unuseable again so the installation was useless.
Only solution is to completely wipe and reinstall and experiment with the order of installation until it works!
I did install STOCK rom because I was so freaked out and then went with ODIN the complete rooting guide for clean rooting, but still problem exists.
I tried two other roms but the problem was that while flashing the phone restarted automaticly and then TWRP said no installed rom? ???
Huge thanks for helping me!
New info:
I was able to make the rom work. I restarted and got stuck into bootloop!
I could boot normally after deleting dalvik cache!
But after rebooting I got into bootloop. Tried deleting cache again but this time it never booted properly.
How can I avoid by always deleting dalvik whenever I have to restart my phone (if battery dies or purpose)?
PPS: Stock Rom flash works flavlessly. I am waiting in stock rom until I find a proper solution :"(
Suggest you read the roms faqs and Q&A particularly with regard to TWRP .
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
sounds like your system is fcucked currenty. should probably boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
Try booting up after that.
e753 said:
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
Click to expand...
Click to collapse
When flashing these ROMs are you wiping properly (system, data, cache, dalvik cache) first? You should try going back to stock, but you'll need to do more than the previous person who replied has said. First you need to wipe data in TWRP, then you need to flash the full factory images, not just the ones mentioned above. You'll find instructions for that in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
I had that problem today. I traced it down to my wifi. Turning off wifi allowed me to boot with no further issues.
1) Boot loop as soon as I got to work.
2) Dirty flashed the ROM
3) Restored backup from 4 days ago.
4) Wiped system and reflashed ROM and gapps. Same issue.
Finally chased it to the wifi. The instant it connected, bootloop. I ran and app called FXR Wifi fixer. Ill see if it bootloops tomorrow at work. No problems on my home wifi after all of this.
e753 said:
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
Click to expand...
Click to collapse
i wouldn't consider this to be strange really. something was not correct in the system partition probably. pretty standard when flashing different ROMs