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.
Related
This is a pure stock compilation of AOSP from Google Source. Only difference is it's compiled with Linaro 4.7. For some reason the build version says 4.2.2.2.2.2.2. I was using this build to test some APK ports I've been working on and figured I'd throw it up here for anyone who might want to go completely bone stock or have a stock back up. As usual the normal disclaimer applies, I am not responsible for anything you do EVER! :laugh:
1. Factory reset
2. Wipe cache/Dalvik
3. Install ROM - http://d-h.st/XZ4
4. Install Gapps - http://goo.im/gapps/gapps-jb-20130301-signed.zip
5. Reboot
6. Enjoy!
Still no tester?
Sent from my Galaxy Nexus using Tapatalk 2
You can test if you want. Most people don't want to run plain ol AOSP. I just put it up here in case people wanted a bone stock backup. I've tested it and it works just fine. :highfive:
Thanks for stopping by!
I tried it. Lost root. Also would not boot into TWRP and would only boot into stock recovery. Restoring Nandroid as I type.
jaizero said:
You can test if you want. Most people don't want to run plain ol AOSP. I just put it up here in case people wanted a bone stock backup. I've tested it and it works just fine. :highfive:
Thanks for stopping by!
Click to expand...
Click to collapse
puothy said:
I tried it. Lost root. Also would not boot into TWRP and would only boot into stock recovery. Restoring Nandroid as I type.
Click to expand...
Click to collapse
This is completely stock with no root. I did not advertise that it was rooted. I have reinstalled this ROM several times and have never lost my recovery. Then, installed my TWRP recovery to PA 3.50+ and AK SKL256 with no issues. This ROM does not alter your recovery in any way.
Also, this ROM is for Verizon Galaxy Nexus only... Toro
jaizero said:
This is completely stock with no root. I did not advertise that it was rooted. I have reinstalled this ROM several times and have never lost my recovery. Then, installed my TWRP recovery to PA 3.50+ and AK SKL256 with no issues. This ROM does not alter your recovery in any way.
Also, this ROM is for Verizon Galaxy Nexus only... Toro
Click to expand...
Click to collapse
I have a Toro GNex. The TWRP thing was odd and was just making all aware. GNex is happy again, but would only allow me to boot into stock recovery and had never experienced that before. My phone is a refurb since the charging port crapped out original one a few weeks back. While this phone has been fine, it's a refurb.
puothy said:
I have a Toro GNex. The TWRP thing was odd and was just making all aware. GNex is happy again, but would only allow me to boot into stock recovery and had never experienced that before. My phone is a refurb since the charging port crapped out original one a few weeks back. While this phone has been fine, it's a refurb.
Click to expand...
Click to collapse
Glad all is well. :highfive:
Very interested in trying this. Actually been waiting for a good ol' AOSP toro rom built with Linaro. Will keep my eye on this. Currently a Shiny Rom (located on Rootzwiki).
Any chance we could get mods for quick settings / clearing of recents?
You are awesome for giving this a try though, I've yet to see any other pure AOSP Linaro roms!
PS.
Does this include all Toro / VZW proprietaries and binaries?
dmillerzx said:
Very interested in trying this. Actually been waiting for a good ol' AOSP toro rom built with Linaro. Will keep my eye on this. Currently a Shiny Rom (located on Rootzwiki).
Any chance we could get mods for quick settings / clearing of recents?
You are awesome for giving this a try though, I've yet to see any other pure AOSP Linaro roms!
PS.
Does this include all Toro / VZW proprietaries and binaries?
Click to expand...
Click to collapse
This ROM includes all binaries as found here - https://developers.google.com/android/nexus/drivers#torojdq39
For some reason, my phone doesn't boot after updating my current rom or wiping and installing a new one.
After the install, the boot animation is displayed for about 1-2 seconds. It then reboots and gets stuck during the boot animation. I've let it sit for an hour, so I know I'm not just being impatient.
Funny thing is that I'm able to restore my nandroid without issue. I'm currently running CM 12.1. I've tried dirty flashing a newer version of 12.1, clean installing a newer version of 12.1 and also clean installing various other roms. The latest I tried was the newest android revolution HD. I'm running the latest TWRP (2.8.7.0).
Can anyone think of why this might be happening? Any troubleshooting tips are welcome.
Thanks.
Got it working with Viper One.
MaxGame said:
Got it working with Viper One.
Click to expand...
Click to collapse
I was gonna suggest.
I've been hooked on this game called Kill Shot Bravo its plays fairly good on my phone.
Ive tried numerous attempts to play it on SM-T520 pro 10.1 with a clean install of CM 12.1 nightly and/or resurrection final. Every time it crashes at the game logo of HotHead.
I wanted to try it on a old 4.4 rom but can't find one that works..
I cannot get Grave Ds 4.4 to boot and I've tried using both kernals.
Can someone give me a suggestion possibly to another rom to try or verify if the game is working for them?
Thank you
OffTheChainz said:
I've been hooked on this game called Kill Shot Bravo its plays fairly good on my phone.
Ive tried numerous attempts to play it on SM-T520 pro 10.1 with a clean install of CM 12.1 nightly and/or resurrection final. Every time it crashes at the game logo of HotHead.
I wanted to try it on a old 4.4 rom but can't find one that works..
I cannot get Grave Ds 4.4 to boot and I've tried using both kernals.
Can someone give me a suggestion possibly to another rom to try or verify if the game is working for them?
Thank you
Click to expand...
Click to collapse
Same thing for me. I have the sm-t520 running latest cm12.1 and the game crashes on the logo.
If you want to try out Grave rom, just flash the rom and then before you try to reboot, just flash the stock kernel for the sm-t520. So in another word flash rom, flash stock kernel, reboot system and let it sit 5 minutes. This is what I did for Grave rom to work on my tab, every other kernel didn't work on my sm-t520.
@coco1476
So in the end KSB does run on Grave 3.0?
Bychance seen that stock kernal you used ? I tried 2 different ones.
And did you go Grave via TWRP from CM
Or did you Odin stock and goto grave?
OffTheChainz said:
Bychance seen that stock kernal you used ? I tried 2 different ones.
And did you go Grave via TWRP from CM
Or did you Odin stock and goto grave?
Click to expand...
Click to collapse
I used this stock kernel from GraveD thread https://www.androidfilehost.com/?fid=95784891001617139
I odin stock before flashing GraveD, rooted with chainfire, installed twrp recovery. Booted in twrp recovery, flashed GaveD rom, flashed stock kernel and rebooted system and everything was running perfect.
---------- Post added at 10:34 AM ---------- Previous post was at 10:31 AM ----------
OffTheChainz said:
@coco1476
So in the end KSB does run on Grave 3.0?
Click to expand...
Click to collapse
Sorry I tried the game on cm12.1 only, i am not sure if it would play on GraveD rom but I would say it would play since GraveD was close to stock without bloat and some tweaks to it.
@coco1476
Appreciate your info! Thank you!
OffTheChainz said:
@coco1476
Appreciate your info! Thank you!
Click to expand...
Click to collapse
Glad to help. I have spent days on my tab a couple of months ago trying to get GraveD rom to work and the only way to get it to boot correctly was with stock kernel. Last week I flashed cm12.1 to give it a run because I was getting tired of a stock look but I might go back to GraveD for better battery
Roger…
Sadly I can't Odin back to Stock for a couple weeks out on business. Heard previously coming from cm to Grave didn't work well just trying to do it through TWRP had to start from scratch.
I really like Ressurection 12.1 final was smooth and fast. Battery life seemed good when in airplane mode w/ screen 50 to 75%… multiple hours of movies on a airplane without a charge.
Ive been playing KSB on my Note 3 with beansrom 2 and its flaky.
I put KSB on a Note 2 with CM12.1 and it runs beautiful.
Just wished it would work on my T520…
Its always something lol ?
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far
I am using TWRP 3.1.1 on my redmi 1s and was using AOSP Extended Rom v4.4 .I thought of trying the phone encryption option but the device went into bootloop. Now only MIUI rom is working and all other ROMs' flashes result into bootloop. Recovery is fine. Is encryption the problem.
First, flashing custom roms requires firmware: get it at https://forum.xda-developers.com/showpost.php?p=73812026&postcount=2
2nd some roms has problems within zip files causing some bootloops or error while flashing
for example AOSP EXTENDED ROM, there is a work around for that get it here: https://forum.xda-developers.com/showpost.php?p=72648733&postcount=223
EmanzzKie said:
First, flashing custom roms requires firmware: get it at https://forum.xda-developers.com/showpost.php?p=73812026&postcount=2
2nd some roms has problems within zip files causing some bootloops or error while flashing
for example AOSP EXTENDED ROM, there is a work around for that get it here: https://forum.xda-developers.com/showpost.php?p=72648733&postcount=223
Click to expand...
Click to collapse
But I had previously flashed several ROMs without any problem they worked fine(even AOSP Ext).The glitch came after trying to encrypt my phone after which it went into bootloops. Strangely MIUI roms are working fine and recovery also looks good. could anyone please suggest what is the problem.I really hate MIUI.
pkrajpur said:
But I had previously flashed several ROMs without any problem they worked fine(even AOSP Ext).The glitch came after trying to encrypt my phone after which it went into bootloops. Strangely MIUI roms are working fine and recovery also looks good. could anyone please suggest what is the problem.I really hate MIUI.
Click to expand...
Click to collapse
remove encryption on your phone, can u do that?
EmanzzKie said:
remove encryption on your phone, can u do that?
Click to expand...
Click to collapse
Disabling Encryption is not an option ROM is already damaged.