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.
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
leandronb said:
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Click to expand...
Click to collapse
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
andyabc said:
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Nigeldg said:
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Click to expand...
Click to collapse
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
12ian34 said:
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
Click to expand...
Click to collapse
I had exactly the same issue you had at first boot, it remained at Google logo forever when i first flashed PA 3.92. This issue came because i was flashing PA 3.02 with Franco nightly 165, franco nightly 165 is for 4.2.2m and if you were in 4.2.2 then you will never know new releases as that one was the last 4.2.2 kernel. I suggest you flash PA 3.92 + gapps from 0802, without Franco, it will boot fine. Also, as explained in big letters in PA download, first step is to download radio and bootloader for the update, i did not have to wipe my memory for the upgrade.
I don't recommend downloading Franco 175 for 4.3, as it has conflicting issues with PA, so use PA with the stock kernel and you should be good meanwhile this gets solved.
12ian34 said:
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Click to expand...
Click to collapse
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
But how do I go about backing it up before I wipe it give that I can only access fastboot and recovery (CWM) ?!?!
OK, I've found a way to do it using
./adb-mac pull /sdcard/0/ sdcardbackup
do I need to backup anything else?
Also, I've downloaded the link you sent me, just to be clear, first, I wipe data, factory reset, then I send the radio and baseband to my phone using adb, then flash them in recovery and then flash PA 3.69, GApps, Franco Kernel r165 then wipe cache, dalvik cache, then reboot, then go about restoring all my data. Is this correct?
Mee too
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
jsmonu said:
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
Click to expand...
Click to collapse
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
molesarecoming said:
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
Click to expand...
Click to collapse
Moles! Help me! I refer you to my first post in this thread, I want to stay on 4.2.2 and PA 3.69 for the moment, and preferably not wipe everything. I accidentally updated to PA 3.92 and then stuck at the PA logo on boot forever. Now I've tried to go back to 3.69 many times and still get stuck at PA logo. currently using adb pull to get all my important stuff off phone.
Is there a shortcut for me, which doesn't involve wiping??
EDIT:
... OK, I just downloaded the 4.3 radio and bootloader, pa 3.94, gapps and sent them to my phone, flashed each one in turn and then wiped caches, reboot. I skipped the wipe, and now my phone is working for the first time in three days - [optimising apps]. Let's see if this works....
Yep, phone works absolutely fine, didn't have to wipe and now have 4.3 and PA 3.94, which wasnt my original intention, but it had to happen sometime! Thanks for all the help people, I think we can consider this one solved
12ian34 said:
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Click to expand...
Click to collapse
Download the nexus 4 toolkit and flash stock rom from it
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem
htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?
Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.
no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)
EDIT: the problem is solved, see my last post
Hey guys,
I'm not new to installing roms, as I did with my SGS 2 before. But I haven't done it for a long time and it's the first time I do it on my SGS 5... with no success at all.
The problem is that, out of all the roms I've tried, none of them boot up entirely without crashes. I've followed the instructions to the letter and I'm not sure what I'm doing wrong.
Here's what I had before starting to fiddle:
SGS 5 G900F, no specific carrier, bought in Europe
stock android/touchwiz 5.0, never rooted or anything
Here are the roms I have tried:
cynaogen 5.1.1 12.1 20150508 for klte + these gapps http://teambliss.x10host.com/BlissStalk/Gapps/ --> stays blocked on the samsung logo forever
BlissPop 5.1.1 v3.3 20150515 for klte + pa_gapps-stock-5.1-20150418-signed or pa_gapps-modular-full-5.1-20150418-signed --> google newstand and another google app are crashing in a loop during the setup, I can't tap any button
PAC 5.1.1 20150503 for klte + pa_gapps-stock-5.1-20150418-signed or pa_gapps-modular-full-5.1-20150418-signed --> the install wizard application itself is crashing in a loop
THe kernels I've tried:
KT-SGS5-LP5.1-AOSP-G900-05.02.2015
boeffla-kernel-2.0-beta8-CM12.1-g900f.recovery
My recovery:
twrp-2.8.6.0-klte (flashed with Odin, it works fine, and I could boot the stock rom without problems with it)
Any idea about the cause of the problem?
Thanks
I guess if you are not new to stuff like this, you have 100% wiped everything before flashing in TWRP recovery, and factory reset / wiped caches after flashing the ROM and Gapps?
*Detection* said:
I guess if you are not new to stuff like this, you have 100% wiped everything before flashing in TWRP recovery, and factory reset / wiped caches after flashing the ROM and Gapps?
Click to expand...
Click to collapse
Yes, before and between installing different roms, I wiped everything: system, cache, dalvik, internal storage
I've also flashed twrp previous version 2.8.5.0, and philz touch recovery. They all work fine, but still can't boot any rom
Strangely, I now works using this version of CM 12.1: http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-1-android-5-1-t3066252
I have no idea why I had all these crashes and boot problems with the other 3 roms.
Cheers
Odd.