I know it has been asked before, and I have searched the threads. reverting to stock is not a problem.
nexus 7 grouper when installing a custom rom (liquid smooth v2.9 specifically) I get stuck on the liquid boot image.
I have successfully installed v2.7 and am able to revert back to stock or custom.
after a data format, factory reset, and wiping all caches, installing the zip file from abd sideload, or directly from the device the new rom that has flashed will not get past the boot image. am I doing something wrong, or could I do something differently so that the new v2.9 boots up correctly?
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
thank you.
aircooledbusses said:
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
Click to expand...
Click to collapse
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
ameinild said:
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
Click to expand...
Click to collapse
I will keep trying. getting liquid to run on the fascinate was curious as well, but after a few flashes it took. I'll keep trying on the nexus.
Update: yes, persistence is the key. thanks
What I did was from v2.8 a factory reset, wipe cache and dalvik and flash from sideload
as expected it boot looped. manually booted into fastboot and flashed v2.9 again with only a cache and dalvik wipe.
this time it booted and I flashed gapps.
at the reboot I set up the rom to my liking and it seems to boot normally now.
aircooledbusses said:
at the reboot I set up the rom to my liking and it seems to boot normally now.
Click to expand...
Click to collapse
Yes, after it boots through the first time, I've only seen it boot normal from that point on.
Related
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.
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 :/
ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
wasa67 said:
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
Click to expand...
Click to collapse
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
blusydays said:
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
Click to expand...
Click to collapse
I did all that before, and it still didn't work.
I think your problems are related to flashing the recovery, did you try to revert back the the old one ?