Hi -- I can't find anything else here at all about this.
Over the course of about 3 hours today I've been trying to get my Nexus 7 (2013) to run multiple roms using this tool:
http://forum.xda-developers.com/showthread.php?t=2457063
I'm going to try to give you as much information as I can.
This is a Nexus 7 2013, Wifi, 16GB
pics: http://imgur.com/a/mSonj
Just incase you missed any of that,
Nexus 7 2013 FLO
Cyanogen Mod 10.2 9/21/13 Nightly Build
TWRP v2.6.3.0
Anyway, here's my problem.
I'm trying to get this tablet to run Cyanogen Mod 10.2 and Ubuntu Desktop 13.04 Raring.
I started off by flashing the custom TWRP recovery, which worked perfectly.
I wiped the cache and dalvik just to be safe.
Rebooted into my Cyanogen Mod which still worked.
I then used the custom TWRP recovery to flash the multirom.zip in that thread.
I wiped the cache and dalvik once again, rebooted, and it worked.
Cyanogen was then my internal with absolutely no problems.
I used TWRP recovery to add the Ubuntu Rom which still posed no problems, the internal booted well but obviously I needed a Kexec patch Kernal to actually boot the Ubuntu image.
Once I flashed the custom Kernal though, the internal would not boot, getting stuck on a black screen.
The Ubuntu rom would attempt to start but get stuck on the Google logo.
Please excuse my complete noobiness, this is literally my first post here and I've only had this tablet for approximately a month or so.
Is anyone having a similar or the same problem, and is there any solution? Thank you so much.
If you've actually read to this point I love you lol
It's related to the patched kernel (I guess), it won't boot my CM10.2 rom, too. It's also mentioned in the CM10.2 thread that ROMs from 09/25 won't boot with the included kernel. You can use the 1.6 beta ElementalX kernel which has the needed patches included, (didn't tested it), wait for an updated (patched) CM kernel, or use a stock based rom as primary rom, the patched stock kernel boots fine. You only have to flash back your working kernel, make backup in TWRP, install any stock based rom, (Full-Wipe), flash patched stock kernel, add rom (Backup), choose your backup. As far as I know, any other system as Android isn't available(working?) ATM, that's the reason you can't boot Ubuntu.
Edit:
ElementalX 1.6 Beta working fine
Gesendet von meinem Nexus 4 mit Tapatalk 4
I'm really sorry I can't be of help, but where did you get the Ubuntu download?
Regardless of your kernel's problems :
Ubuntu will not work on your tablet. It does not have yet the requiered drivers, and I didn't see any team working on it.
Ubuntu touch has some experiments for the Flo version, but nothing that works, and nothing that can be released now, I think.
For a GNU/linux distro ROM, you'll have to wait or buy another device.
iPWNtehNOOB said:
I'm really sorry I can't be of help, but where did you get the Ubuntu download?
Click to expand...
Click to collapse
It's just the raring preinstall image, google it.
For everyone else, thank you all for giving me simple answers.
I'm going to try that kernal later.
I would thank you if I had any idea how
I guess you won`t see the thanks button before you will reach at leat 10 posts.
xPoseid0n said:
It's just the raring preinstall image, google it.
For everyone else, thank you all for giving me simple answers.
I'm going to try that kernal later.
I would thank you if I had any idea how
Click to expand...
Click to collapse
Isn't that only for the old Nexus?
Related
Hi everyone,
I wasn't used to consider myself a too-much-noob anymore, but now I've plenty of doubts.
So, here's my problem: I've decided to give the latest ParanoidAndroid release a try and my maguro was "oem locked". Then, I've run the command "fastboot oem unlock" and copied all files I needed (PA rom, GlaDos v2.2 and latest GApps) into my /sdcard folder (usual job). I've rebooted into recovery (latest touch CWM), formatted /system, /data, /cache (usual full wipe), searched for the files and flashed them.
When it was time to reboot, the phone got stuck at the first screen (black, with the white "Google" and the white opened padlock). In other words, the bootanimation didn't even start.
Then, I've re-downloaded the stuff, double-checked all Md5 sums, re-copied everything in the sdcard but the result didn't change.
I've tried to re-flash the stock unrooted rom, then repeating the steps without formatting /system. I've also tried to not flash the kernel. No way the rom could even boot.
Now I'm seriously wondering what's wrong with what I've done . For completeness, my bootloader version is LC03 and the radio is XXLJ1 (same as the fully stock android bundle that can be found here)
I've also checked (maybe too much quickly, I may admit) the threads for PA and GlaDos, but I haven't seen anyone complaining about the same problem...
Could you guys please help me?
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
- Based on stock Android kernel Jelly Bean 4.1.1 JRO03C
Click to expand...
Click to collapse
Pirateghost said:
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
Click to expand...
Click to collapse
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Endriu90 said:
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Click to expand...
Click to collapse
i have been looking forward to a new GladOS...thanks for the link
in recovery, all you have to do is factory reset then flash the rom. thats it
EDIT:
which version of PA 3.0 are you trying to install
Pirateghost said:
which version of PA 3.0 are you trying to install
Click to expand...
Click to collapse
I've tried with all releases which can be found here
Flash Kernel too
Hi,
When the new PA version was uploaded (20 Feb), this was the warning posted by the developer:
WARNING
As I didn't have so much time, I couldn't make it booting with default kernel (Need to update prebuilt kernel). So if you're gonna use it BE SURE YOU FLASH A CUSTOM 4.2.2 KERNEL!
Click to expand...
Click to collapse
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Hope this helps.
Regards,
Neeraj
neerajvd said:
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Click to expand...
Click to collapse
Thank you guys, I've solved (I've tried just with the factory reset as said by pirateghost, but I was used to format /system, /data and /cache when it was time to flash roms like AOKP and everything used to work properly) (I was used to do the same with the Nexus S).
Now I'm running the 15feb release with the stock android kernel (which comes with the stock 4.2.2 factory bundle) and everything just works as expected.
Anyway, I still can't get the reason why GlaDOS shouldn't work with the 20feb release. I mean, it's a custom kernel and it should work as well as AK or franco kernels, shouldn't it? If I'm wrong, could you briefly tell me why? (sorry, I won't move to other kernels, as I personally love GlaDOS and it provides my GNex with the optimal equilibrium performances/battery life)
EDIT:
alongside the 15feb release, I've tried to flash GlaDOS (just factory-resetting before flashing), but nothing boots. Restored the backup, now I'm still running PA with the stock kernel
So, i recently jumped into the custom ROM scenario and everything related to unlocking+rooting. Within the last 3-4 days, i installed cm 10.1, and then found cm 11 and upgraded. (Thanks to Mustaavalkosta) There are certain questions that i have in mind:
1. So, when i installed cm 10.1, all apps got synced and were installed to my phone automatically as i installed gapps, i made backup with clockwork recovery. Then the next day i clean installed cm 11, neither did my apps were synced with this other gapps for 4.4.2 and the second issue i had belonged to recovery. I accidentally locked my phone by using screen security pin and i couldn't unlock it. In a state of panic i thought of using Clockwork restore to 10.1 from 11. After restoring and rebooting, first came the boot screen, and then all i had was a non-responsive black screen . Why so?
2. Comparing 10.1 and 11, 10.1 was really fast and smooth and everything was working. In 11, i had to install google camera etc, but the issue here is that its really slow. WHY IS THAT SO?
3. What are the best running ROMs right now, preferably JB and KITKAT based.
Thanks .
taz911 said:
So, i recently jumped into the custom ROM scenario and everything related to unlocking+rooting. Within the last 3-4 days, i installed cm 10.1, and then found cm 11 and upgraded. (Thanks to Mustaavalkosta) There are certain questions that i have in mind:
1. So, when i installed cm 10.1, all apps got synced and were installed to my phone automatically as i installed gapps, i made backup with clockwork recovery. Then the next day i clean installed cm 11, neither did my apps were synced with this other gapps for 4.4.2 and the second issue i had belonged to recovery. I accidentally locked my phone by using screen security pin and i couldn't unlock it. In a state of panic i thought of using Clockwork restore to 10.1 from 11. After restoring and rebooting, first came the boot screen, and then all i had was a non-responsive black screen . Why so?
2. Comparing 10.1 and 11, 10.1 was really fast and smooth and everything was working. In 11, i had to install google camera etc, but the issue here is that its really slow. WHY IS THAT SO?
3. What are the best running ROMs right now, preferably JB and KITKAT based.
Thanks .
Click to expand...
Click to collapse
Number 3 is strictly against XDA rules find one that you like
Sent from my Sensation XL using Tapatalk
I meant to say, which one suites you best.
Sorry for that though. If someone would like to answer the rest of two please
1. What the state of your phone bootloader?, still s-on or already s-off?
If still s-on.. did you not forget to flashing the boot.img too after restoring that rom?
2. Not sure about this.. maybe you try asking it in the rom thread it self..
3. Just try it your self what the rom that is suitable with you.. because the best think from someone is not mean always might be the best for you too..
Sent from my Desire HD using Tapatalk
Its on S-on, so i have to flash the image after recovery too?
taz911 said:
Its on S-on, so i have to flash the image after recovery too?
Click to expand...
Click to collapse
yes..you must flashing boot.img too that extracted from the rom.zip (the same rom that you had already restoring from backup)
As the title says:
Got a problem when flashing UBER 2 GHz on Carbon ROM. everything goes fine, then when the phone enters lock screen, phone.apk crashes. haven't installed google apps yet, and also use April 4 build of Carbon ROM. Any problems or AM I JUST LOOKING AT A COMPATIBILITY ERROR?
P.S.
Looked through the UBER Kernel Main Thread. Says you need TWRP 2.6.1.0 . I use TWRP 2.7.0.0. Is there anything wrong?
Thanks!
baloushot said:
As the title says:
Got a problem when flashing UBER 2 GHz on Carbon ROM. everything goes fine, then when the phone enters lock screen, phone.apk crashes. haven't installed google apps yet, and also use April 4 build of Carbon ROM. Any problems or AM I JUST LOOKING AT A COMPATIBILITY ERROR?
P.S.
Looked through the UBER Kernel Main Thread. Says you need TWRP 2.6.1.0 . I use TWRP 2.7.0.0. Is there anything wrong?
Thanks!
Click to expand...
Click to collapse
Pretty sure your issue is either you need GAPPS (all roms need GAPPS... unless they have it built in... if the install instrucitons say install gapps, install gapps. I am fairly confident that phone.apk is part of gapps.) OR UBER isn't compatible with Carbon.
Also, are you using the proper UBER for a KK ROM?
baloushot said:
As the title says:
Got a problem when flashing UBER 2 GHz on Carbon ROM. everything goes fine, then when the phone enters lock screen, phone.apk crashes. haven't installed google apps yet, and also use April 4 build of Carbon ROM. Any problems or AM I JUST LOOKING AT A COMPATIBILITY ERROR?
P.S.
Looked through the UBER Kernel Main Thread. Says you need TWRP 2.6.1.0 . I use TWRP 2.7.0.0. Is there anything wrong?
Thanks!
Click to expand...
Click to collapse
I was having the exact same problem, I've tried running it with uber many times so guessing it's an incompatibility. Uber's experimental Sabermod kernel is working okay with carbon though.
EDIT: Forgot to add that I did install gapps, and I'm also using TWRP 2.7.0.0.
Hi Everyone
I have just grabbed the Paranoid .zip for Nexus 9 (Flounder) flashed it via twrp but it stuck in bootloop for about 10 mins. I have restarted the device but still no luck. Any suggestions?.
Thanks
vampire_8_7 said:
Hi Everyone
I have just grabbed the Paranoid .zip for Nexus 9 (Flounder) flashed it via twrp but it stuck in bootloop for about 10 mins. I have restarted the device but still no luck. Any suggestions?.
Thanks
Click to expand...
Click to collapse
You figure it out? I had the same issue.
Marky__Mark said:
You figure it out? I had the same issue.
Click to expand...
Click to collapse
I think I did can't really remember mate, I think it was the kernal I had a custom one and caused the bootloop. Flashed the stock boot image and it did work afterwards. Honesty I ditched it after 2 days running dirty unicorns now, in my opinion it's the best custom rom out there for now, I even flashed it to my N6 running perfectly fine check it out and make sure u don't have xposed install you can have some issues, just check it out and read the thread you'll be fine ????????
vampire_8_7 said:
I think I did can't really remember mate, I think it was the kernal I had a custom one and caused the bootloop. Flashed the stock boot image and it did work afterwards. Honesty I ditched it after 2 days running dirty unicorns now, in my opinion it's the best custom rom out there for now, I even flashed it to my N6 running perfectly fine check it out and make sure u don't have xposed install you can have some issues, just check it out and read the thread you'll be fine ????????
Click to expand...
Click to collapse
Im running PA with xposed and elementalx and its smooth as silk. My issue, I think, is my device was unencrypted and its been so long that I havent used a custom kernel that i forgot about it. I flashed the new AOSPA without elementalx to test out the stock kernel and i think it tried to encrypt. When it took too long for the first boot, i manually rebooted the device and that borked the data so i had to do a factory reset and lose all my data. Pain in the ass, but im diggin this rom.
So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.
Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!
First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs
Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]