I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...
Related
I previously had a different rom installed just fine (Modaco). I wanted to install Cyanogenmod, so I followed instructions, wipe, install rom and gapps, reboot. It was stuck on the cyanogenmod animation forever. I also tried a different rom (4.2.1 Linario) and same problem.
I was forced to go back to stock. Went back to factory stock, rooted once again, installed CWM, and tried installing rom again and it just wont go past the boot animation.
Ive attached a logcat, hopefully someone could tell me what the problem is.
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
VegasIdaho said:
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
v.konvict said:
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
Click to expand...
Click to collapse
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
VegasIdaho said:
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
Click to expand...
Click to collapse
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Choristav said:
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Click to expand...
Click to collapse
Thanks for your reply. After reading the response from v.konvict above, I thought that CM12 would be caf, but it isn't. I've got several more ROMs working now by using different bootstacks, but it is trial and error with some of the ROMs.
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.
I got bored today and decided to pull out the old N7, 2012 version. I update recovery to TWRP 2.8.7.0, installed CM 12.1, realized this tablet crawls with any version of Android other than shipped version, so I went and got CM 10 and GApps for JB, wiped and flashed them back on. I didn't see any errors when flashing them, but when rebooting after, it just boot loops. I see the Google logo with the unlocked icon at bottom, then reboot and back to Google/unlocked again. So I wipe and reflash cm12.1 and it's GApps and all boots and works fine, other than being slow. I'm assuming the recovery is the problem as I've run into something similar before on another device, but in that case, the recovery was too old and needed updated, but it makes sense that a recovery could be too new as well.
Am I correct that the recovery is the problem? If so, what should I run for CM 10 to flash and work?
Try cwm recovery
iwjosi said:
Try cwm recovery
Click to expand...
Click to collapse
I don't' know if it was using CWM or that I also tried CM 10.2 at the same time, but it's working now. On CyanogenMod's own page, there was no MD5 for CM10, but there was for CM10.2, so it's possible my copy of CM10 was a bad download. Either way, it's working now, so thank you good sir, or madam, or person on no specific gender.
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?