Related
[Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free
Here is the Stock Flashable N910VVRU1ANJ5 Rooted, Odex, Knox Free. Built from the original factory image
This is for the DE Phone!!!
I will build a Safe Strap version as soon as you retail guys get root with Safe Strap!!!
I need some testers for my new Rom. Please PM me if you are interested.
Requirments are TWRP Recovery
Features:
Odex
Rooted
Init.d support
Knox Free
Native WiFi Hotspot
Removed Verizon OTA updater
Removed How To Nonsense from Verizon.
Read/Write to external storage
ROM Zips
Verizon Note 4 NJ5 V1.0 ported for the DE Phone-Download: NJ5 V1.0 Odex Note 4
Verizon Note 4 NJ5 V1.1 ported for the DE Phone-Download: NJ5 V1.1 Odex Note 4
Verizon Note 4 NJ5 V1.2 ported for the DE Phone-Download: NJ5 V1.2 Odex Note 4
Code:
[B][U]V1.1 - Full Wipe[/U][/B]
-Various Bug Fixes
Code:
[B][U]V1.2 - Full Wipe[/U][/B]
-App fixes
-Gear VR working
-This version should be BUG Free let me know!!
Installation Instructions:
1: DO A NANDROID
2: Download the ROM and copy it to your external SD card.
3: Do a complete wipe by checking Dalvik Cache, Data, Cache, Internal Storage and System from TWRP.
4: Install the ROM via TWRP.
5: Reboot and Enjoy
6. You will get a few fc's on boot. You need to update Google Services as soon as possible.
I also would set Play Store so it does not auto update apps.
It will take a few hours for the phone to index and settle down.
Please be patient when the phone reboots. It will sit on the boot animation for as long as 5 min.
PLEASE DON'T FORGET TO HIT THANKS!! THIS TOOK MANY HOURS TO PUT TOGETHER!!!!
If any other Dev's want to use this as a base, please feel free to do so with proper credit!! No need to ask me!!
Just in Case
uhhh isnt there another thread for this rom already ?
solidunit said:
uhhh isnt there another thread for this rom already ?
Click to expand...
Click to collapse
Uhhh This is NJ5 based ... other Rom is NI1
odex
How about bloat free odex version?
or a list of apps and supporting files removed from your original release?
Hey I have a problem here. I'm coming from your very first ROM to this one. It was running great smooth as butter until now. I tried flashing this new ROM but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy almost like it has a virus. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately... Anyone help please?
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Hey I have a problem here. I'm coming from your very first ROM to this one. It was running great smooth as butter until now. I tried flashing this new ROM but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy almost like it has a virus. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately... Anyone help please?
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Go here download the StockRestore tar, flash that in odin and you should be good to go. Then you can flash this rom if you like. You shouldn't have to wipe anything but if you run into errors just do a factory reset. FYI the stock restore is pretty much the same as this rom without knox removed, SU will ask if you want to disable it or you can freeze/remove it with TB so technically there is really no reason to flash this after the odin restore.
solidunit said:
uhhh isnt there another thread for this rom already ?
Click to expand...
Click to collapse
One is deodexed and one is odexed.
ifly4vamerica said:
Uhhh This is NJ5 based ... other Rom is NI2
Click to expand...
Click to collapse
The other ROMs are actually NI1.
Is there an ad block zip I can flash? I'm so sick of ads
EMSPilot,
Is there a way you can update this rom with a StageFright fix?
how to flash thise rom ,icant flashe recovery on ni1 can you tellme??
Back to KitKat
EMSpilot said:
[Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free
Here is the Stock Flashable N910VVRU1ANJ5 Rooted, Odex, Knox Free. Built from the original factory image
This is for the DE Phone!!!
I will build a Safe Strap version as soon as you retail guys get root with Safe Strap!!!
I need some testers for my new Rom. Please PM me if you are interested.
Requirments are TWRP Recovery
Features:
Odex
Rooted
Init.d support
Knox Free
Native WiFi Hotspot
Removed Verizon OTA updater
Removed How To Nonsense from Verizon.
Read/Write to external storage
ROM Zips
Verizon Note 4 NJ5 V1.0 ported for the DE Phone-Download: NJ5 V1.0 Odex Note 4
Verizon Note 4 NJ5 V1.1 ported for the DE Phone-Download: NJ5 V1.1 Odex Note 4
Verizon Note 4 NJ5 V1.2 ported for the DE Phone-Download: NJ5 V1.2 Odex Note 4
Code:
[B][U]V1.1 - Full Wipe[/U][/B]
-Various Bug Fixes
Code:
[B][U]V1.2 - Full Wipe[/U][/B]
-App fixes
-Gear VR working
-This version should be BUG Free let me know!!
Installation Instructions:
1: DO A NANDROID
2: Download the ROM and copy it to your external SD card.
3: Do a complete wipe by checking Dalvik Cache, Data, Cache, Internal Storage and System from TWRP.
4: Install the ROM via TWRP.
5: Reboot and Enjoy
6. You will get a few fc's on boot. You need to update Google Services as soon as possible.
I also would set Play Store so it does not auto update apps.
It will take a few hours for the phone to index and settle down.
Please be patient when the phone reboots. It will sit on the boot animation for as long as 5 min.
PLEASE DON'T FORGET TO HIT THANKS!! THIS TOOK MANY HOURS TO PUT TOGETHER!!!!
If any other Dev's want to use this as a base, please feel free to do so with proper credit!! No need to ask me!!
Click to expand...
Click to collapse
Is this the way, on my newly unlocked, rooted DE, US Verizon note 4, running 5.1.1 android, to get back to Kitkat? I loved the speed, and battery life for two days, in the original Kitkat. Unfortunately, I lost the ability to go back with OTA updates .
Had to rub my eyes to make sure I was seeing a new rom for 4.4.4!!!!! YeeeeHaaaa!
Thank you so much.
On Definitive ROM now, but will try this when i get home.
What kernel would you recommend?
thanks again!
Can't seem to figure out how to install this, with my newly unlocked, rooted DE, Verizon Note 4. I would love to go back to original Kit Kat!
evolovernow said:
Can't seem to figure out how to install this, with my newly unlocked, rooted DE, Verizon Note 4. I would love to go back to original Kit Kat!
Click to expand...
Click to collapse
I've got to echo this question/statement. I've been going around in circles for about two months on and off trying various methods and combinations of kernels and roms and firmwares in order to downgrade. I've unlocked the bootloader about 4 times now in my quest and every time eventually have ended with the "software update failed" screen forcing me to re-partition and flash MM again. A few random places on the internet seem to infer that it's nigh impossible to get back to kitkat. If that's the case then so be it, but why?
I've searched and searched and experimented and experimented some more but can't seem to find a way past 5.1.1. Heck I can't even seem to get to OAF flashed successfully (one website instructs being at 5.0.1 before being able to dgrade to kitkat). Any help would be appreciated. I've thought about starting a thread but with the derision this kind of question gets (even though I've tried quite a bit on my own), this seems like a better place to post for now.
Cheers!
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Introduction
I am very proud to bring you HDX Nexus Safestrap ROM. This is for both the Kindle Fire HDX 7" and 8.9" WIFI only variants and brings full AOSP functionality which are using Safestrap. You must be running stock firmware .3.2.4 - 3.2.8
Click to expand...
Click to collapse
Features
- Full Jelly Bean 4.2.2 AOSP functionality
Click to expand...
Click to collapse
Bug Reports
- Please use the Bugs section on this thread, it will make it a lot easier to to keep track.
Click to expand...
Click to collapse
Fresh Installation
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
- Then flash any addons
- If coming from any other ROM then do a factory reset.
- Reboot and enjoy.
Click to expand...
Click to collapse
Upgrading From Previous Version
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
- Wipe Dalvik Cache and Cache
- Then flash any addons
- Reboot and enjoy.
Click to expand...
Click to collapse
Changelog
- x -> v1.0.1
Code:
- Initial Release.
- Branched from mainline HDX Nexus ROM v2.0.5
Click to expand...
Click to collapse
Downloads
- Safestrap Apollo Nexus ROM
- Safestrap Thor Nexus ROM
- Gapps 1.2
Click to expand...
Click to collapse
Add-Ons
- Dolby Digital v1.2
Click to expand...
Click to collapse
FAQ
TBD
Source Code
- Kernel Source: Kindle HDX stock kernel, build number 1314.3.2.4
Finally
- Thank you to everyone for your ongoing support and to everyone that made a Donation.
Click to expand...
Click to collapse
XDA:DevDB Information
HDX Nexus Safestrap, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: .3.2.4 - 3.2.8
Based On: AOSP JDQ39
Version Information
Status: Stable
Current Stable Version: 1.0.1
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2016-02-10
Reserved
Reserved
Update
Hello All,
Files are now up
Ggow much appreciated that safetrap version is coming back!
Just to clarify that this rom will work with devices that got upgraded to 4.5.2 and then downgraded by ACS to 3.2.7/8 and rooted with safetrap working.
Here are some questions that I'm sure people will be curious about:
- I'm currently on 2.0.2 and root checker says root is enabled, but couldn't find the supersu app. How does it work? Do i need to flash supersu?
- Can you install xposed with modules on this version? For example to mod notifications bar, status bar, power menu, etc.
- can I safely upgrade from the older 2.0.2 to this version?
- what about addons like the dolby digital? I assume its safe to flash too?
- current build.prop ids the device as Nexus HDX and tgere are a lot of apps on play store that are not compatible with the device, but they work just fine installed from another market (say 1mobile). Can we do something about it?
Sorry for so many questions, but i tried reading most stuff from the other thread but for some reason search in thread is disabled (no idea why).
Cheerz!
Awesome, thanks!!!
johim said:
Ggow much appreciated that safetrap version is coming back!
Just to clarify that this rom will work with devices that got upgraded to 4.5.2 and then downgraded by ACS to 3.2.7/8 and rooted with safetrap working.
Correct, yes.
Here are some questions that I'm sure people will be curious about:
- I'm currently on 2.0.2 and root checker says root is enabled, but couldn't find the supersu app. How does it work? Do i need to flash supersu?
The ROM is pre-rooted with the su binary and a daemon. SuperSU is a root manager so its up to you if want that functionality.
- Can you install xposed with modules on this version? For example to mod notifications bar, status bar, power menu, etc.
Yes you can.
- can I safely upgrade from the older 2.0.2 to this version?
Yes
- what about addons like the dolby digital? I assume its safe to flash too?
Yes
- current build.prop ids the device as Nexus HDX and tgere are a lot of apps on play store that are not compatible with the device, but they work just fine installed from another market (say 1mobile). Can we do something about it?
No matter how I modify the build.prop, google play store ends up not playing nice. So no not at the moment. Market helper used to work for this problem but seems to but patched now on googles servers.
Sorry for so many questions, but i tried reading most stuff from the other thread but for some reason search in thread is disabled (no idea why).
Cheerz!
Click to expand...
Click to collapse
See my responses above. I'll add some information to the FAQ when possible.
Sent from my Nexus 6 using Tapatalk
OK, I updated and flashed all gapps and addons. Everything works!
Then I tried installing Xposed Framework, and on reboot the result was black screen after rom bootup (right after android animation). Waited like 2-3 minutes, but nothing. Then had to force reboot it via power button. After reboot everything works again with Xposed installed. No idea what happened. Any guidelines on where I can check logs probably.
havent tried any module yet, but it would be nice if we keep a list of compatible and safe modules.
Question: can any of the xposed modules trip eFuse or break stock kernel (as rom is running on top of it) or safetrap makes it safe so any changes to system would be just to the slot rom?
johim said:
OK, I updated and flashed all gapps and addons. Everything works!
Then I tried installing Xposed Framework, and on reboot the result was black screen after rom bootup (right after android animation). Waited like 2-3 minutes, but nothing. Then had to force reboot it via power button. After reboot everything works again with Xposed installed. No idea what happened. Any guidelines on where I can check logs probably.
havent tried any module yet, but it would be nice if we keep a list of compatible and safe modules.
Question: can any of the xposed modules trip eFuse or break stock kernel (as rom is running on top of it) or safetrap makes it safe so any changes to system would be just to the slot rom?
Click to expand...
Click to collapse
Use this verison of Xposed found here.
Try Gravitybox (JB).
I don't know if any of the modules can trigger the efuse. You are correct, in theory Safestrap makes it so that any changes should only occur in that slot.
So far this ROM has been excellent. Great job and thanks a lot!
I have the problem, that there is no Play Store and I can't install downloaded applications. I downloaded applications through the browser and when I try to execute them I get the error "can't open file". So I can literally install no app. I tried to install ES File Explorer and gapps pico.
Anyone else who had this problem or knows how to solve it or has some ideas?
faulix said:
I have the problem, that there is no Play Store and I can't install downloaded applications. I downloaded applications through the browser and when I try to execute them I get the error "can't open file". So I can literally install no app. I tried to install ES File Explorer and gapps pico.
Anyone else who had this problem or knows how to solve it or has some ideas?
Click to expand...
Click to collapse
Did you flash gapps?
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
Click to expand...
Click to collapse
Is this the only iteration of the ROM for 3.2.8?
jeryll said:
Did you flash gapps?
Click to expand...
Click to collapse
That's quite embarrassing, I forgot it and now everything works perfectly, thanks.
In case anyone else has the same problem, flash the gapps stuff in safestrap
Thank you for still supporting those of us stuck with safestrap only... lol
ggow said:
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Hi GGow, I'm a complete noob to the scene, have searched around the forums. Finally got Safestrap 3.75 and SuperSU working on my Amazon Kindle Fire HDX that was downgraded to 13.3.2.8 by ACS from 4.5.2. Utilized the TowelRoot method to get rooted.
I want to make sure the installation procedure for this ROM, since I've never done one. Currently I utilized SafeStrap 3.75 and backed up my stock 13.3.2.8 ROM on the device.
The process to install this ROM would be -
1. Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
2. Flash hdx-nexus-gapps-v1.2.zip
3. Then flash any addons
4. If coming from any other ROM then do a factory reset.
5. Reboot and enjoy.
My only issue is that do I flash all of these roms like the safestrap-thor-nexus-rom.zip onto seperate slots? Or keep re-flashing the same slot? I apologize for my noobness, but I'm really new to Android Dev and rooting.
Click to expand...
Click to collapse
All same slot.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Just queue them all up to flash all in one shot.
camerajunkie said:
ggow said:
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Hi GGow, I'm a complete noob to the scene, have searched around the forums. Finally got Safestrap 3.75 and SuperSU working on my Amazon Kindle Fire HDX that was downgraded to 13.3.2.8 by ACS from 4.5.2. Utilized the TowelRoot method to get rooted.
I want to make sure the installation procedure for this ROM, since I've never done one. Currently I utilized SafeStrap 3.75 and backed up my stock 13.3.2.8 ROM on the device.
The process to install this ROM would be -
1. Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
2. Flash hdx-nexus-gapps-v1.2.zip
3. Then flash any addons
4. If coming from any other ROM then do a factory reset.
5. Reboot and enjoy.
My only issue is that do I flash all of these roms like the safestrap-thor-nexus-rom.zip onto seperate slots? Or keep re-flashing the same slot? I apologize for my noobness, but I'm really new to Android Dev and rooting.
Click to expand...
Click to collapse
To add to what @gqukyo said:
1. If you intend for HDX Nexus ROM to be your main ROM and because you are on 13.3.2.8 I would make sure you take a backup of your current stock ROM.
2. Restore the backup to slot 1 . Ensure slot 1 then boots correctly
3. You can then switch back to your stock slot and follow the instructions above.
4. Otherwise if you want stock to be your main ROM then just follow the instructions as they are above after creating a new ROM slot.
Click to expand...
Click to collapse
ggow said:
camerajunkie said:
To add to what @gqukyo said:
1. If you intend for HDX Nexus ROM to be your main ROM and because you are on 13.3.2.8 I would make sure you take a backup of your current stock ROM.
2. Restore the backup to slot 1 . Ensure slot 1 then boots correctly
3. You can then switch back to your stock slot and follow the instructions above.
4. Otherwise if you want stock to be your main ROM then just follow the instructions as they are above after creating a new ROM slot.
Click to expand...
Click to collapse
Ha! I didn't even think to use the "stock rom" for any custom roms... I don't suppose it really matters does it? I did create the max 16gb for my rom slot though I did hear about people having issues installing games when it complained device didn't have enough space... if it does matter then I'd rather use the stock slot since there doesn't seem to be any other roms to try anyways.
Click to expand...
Click to collapse
I don't think he ment to replace your stock slot with custom rom.
I was wondering why would i restore stock backup to slot 1? Is this just to verify if backup works? Can i later remove it from slot 1.
It would take too much space to have a stock and slot 1 as stock and then slot 2 for nexus.
Fyi you can safely install Xposed 2.7 experimental and then activate gravitybox, and other aosp modules.
Sent from my Nexus HDX 7 using XDA Free mobile app
Hello All,
A few months ago I got a Nexus 6 as a replacement for a Moto 2014. I love Nexus devices and used to flash roms back in the day and now I am a little lost. I followed some instructions when I first got the device on how to set up Root using WUGFresh Root Tool Kit: http://www.wugfresh.com/nrt/ I also installed TWRP recovery. I can't remember how I actually got here because I did it a while back. I rooted and set up a custom recovery.
I am on 5.1.1 at the moment.
Kernel Version: 3.10.40-gc16a3c6
[email protected] #1
Tue Jul 28 17:58:25 UTC 2015
Build Number:
LMY48W
Im on AT&T
I can't remember how I actually got here because I did it a while back. I rooted and set up a custom recovery (I think) and I basically started from scratch and had to reinstall everything. I want to update to Marshmallow and I have a few questions.
1.) If I do update it to the Marshmallow 6.0.1 will I lose all my data and installed programs?
2.) Where can I get the closest to stock Marshmallow 6.0.1 or 6.0 for the Nexus 6?
3.) Whats the best way to install it?
4.) If I get an OTA should I install it? What will happen if I do?
Sorry for all the NEWB questions. I got so lost in all the documentation, references, XDA developers, multiple versions of custom recoveries I can't figure out what I did anymore and I can't figure out what to do!
TLDR: I have a Nexus 6 on 5.11 LMY48W, phone is rooted, I have TWRP, how can I get step by step instructions to install the best and most up to date Marshmallow for Nexus 6?
First and foremost: Please, don't use rootkits and toolkits, the Marshmallow updates come fast, toolkit developers will always be a step behind. Not to mention, that if something goes sideways (and wirh Marshmallow it probably will), you won't have the knowledge to fix it.
So:
4) You're rooted, you won't get an OTA
1) Since you won't get an OTA, you must flash by hand, and you should always do a clean install when doing a version upgrade
3) Now you can decide if you do a full factory setup, with flashall, or you can choose to learn how to flash images one by one, then if you don't flash userdata, and you do the factory reset from a custom recovery, you'll have all your files intact. But the stock recovery deletes everything when doing factory reset.
https://developers.google.com/android/nexus/images?hl=en#instructions
2) https://developers.google.com/android/nexus/images?hl=en#shamu
Scroll down to the most recent one: 6.0.1 (MMB29K)
istperson said:
First and foremost: Please, don't use rootkits and toolkits, the Marshmallow updates come fast, toolkit developers will always be a step behind. Not to mention, that if something goes sideways (and wirh Marshmallow it probably will), you won't have the knowledge to fix it.
So:
4) You're rooted, you won't get an OTA
1) Since you won't get an OTA, you must flash by hand, and you should always do a clean install when doing a version upgrade
3) Now you can decide if you do a full factory setup, with flashall, or you can choose to learn how to flash images one by one, then if you don't flash userdata, and you do the factory reset from a custom recovery, you'll have all your files intact. But the stock recovery deletes everything when doing factory reset.
https://developers.google.com/android/nexus/images?hl=en#instructions
2) https://developers.google.com/android/nexus/images?hl=en#shamu
Scroll down to the most recent one: 6.0.1 (MMB29K)
Click to expand...
Click to collapse
Thanks. Since I am using the Nexus 6 do you recommend that I set it back to factory settings to get the OTA updates? If so what is a good link for instructions to do that? Thanks!
As long as you are going from stock to stock, you can skip the factory reset - I've done that all this time, and have never had an issue. Just flash using fastboot (don't use flash-all), and skip the step to flash userdata.
shibed said:
Thanks. Since I am using the Nexus 6 do you recommend that I set it back to factory settings to get the OTA updates? If so what is a good link for instructions to do that? Thanks!
Click to expand...
Click to collapse
Nevermind I saw your link. I should have read that a little closer. Thanks! I will try the factory image.
istperson said:
First and foremost: Please, don't use rootkits and toolkits, the Marshmallow updates come fast, toolkit developers will always be a step behind. Not to mention, that if something goes sideways (and wirh Marshmallow it probably will), you won't have the knowledge to fix it.
So:
4) You're rooted, you won't get an OTA
1) Since you won't get an OTA, you must flash by hand, and you should always do a clean install when doing a version upgrade
3) Now you can decide if you do a full factory setup, with flashall, or you can choose to learn how to flash images one by one, then if you don't flash userdata, and you do the factory reset from a custom recovery, you'll have all your files intact. But the stock recovery deletes everything when doing factory reset.
https://developers.google.com/android/nexus/images?hl=en#instructions
2) https://developers.google.com/android/nexus/images?hl=en#shamu
Scroll down to the most recent one: 6.0.1 (MMB29K)
Click to expand...
Click to collapse
Dude! Just as an FYI I want to thank you and let you know I was able to successfully sort out my issues using your guidance.
shibed said:
Dude! Just as an FYI I want to thank you and let you know I was able to successfully sort out my issues using your guidance.
Click to expand...
Click to collapse
I'm glad I could help.
Hi all after trying hundreds of different roms on my old nexus. I think i have found the best way to boost the speed. I'm using xenonhd 5.1.1 with parrot mod and M-kernels. ??
Trying it out right now and it seems snappy. But I am using f2fs version of Xenonhd without the M kernel.
Give the xenonhd please...
Links please
GrandLuLu said:
Give the xenonhd please...
Click to expand...
Click to collapse
Sab3elbromba said:
Links please
Click to expand...
Click to collapse
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
"Lightning fast" and "Nexus 7 2012" are not normally used in the same sentence.
Maybe I'll have to give this a try. I've kept mine on stock KitKat, and it's dog slow.
Are you using SuperSU as recommended by ParrotMod, or does it work with Magisk? Thanks.
Edit: To answer my own question, it seems to work fine with Magisk.
so, you have to downgrade the bootloader to use this?
beside that, in the xenonhd thread someone said .. after u install some apps you'll get the same slow down like on every other rom
https://forum.xda-developers.com/showpost.php?p=69949425&postcount=1817
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The latest version update-XenonHD-09-13-15 is not available anymore. If anyone that has the files could share.
I was also pointed to try this rom: https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514
And this one, but again no working links https://forum.xda-developers.com/showthread.php?t=2784244
I will buy today a Nexus 7 3G 2012 very cheap, so I will try some roms on it.
skinniezinho said:
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
Click to expand...
Click to collapse
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
jbaumert said:
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
Click to expand...
Click to collapse
Thanks. The device comes with 4.2.2 should I flash first 5.1.1 (in order to update radios and stuff) and then root=>recovery=>rom? Or should I just root it in 4.2.2?
If anyone have the older files that I pointed I would appreciate, I will test them and leave my feedback.
I would download the last "official" update from Google for your device (Tilapia I'm assuming), and manually flash the radio and bootloader with fastboot. (Granted, you could install the entire update, but why bother if you're going to put on a custom ROM anyways) Then, unlock the bootloader (if not already done) install TWRP recovery and flash away.
Anyone tested this ROM yet (with a bunch of apps installed to see if slows down or not) ?
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The download links are dead. :crying:
Jaguar10301 said:
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Click to expand...
Click to collapse
Root it and load RootBooster and choose the last option..
andynroid said:
Root it and load RootBooster and choose the last option..
Click to expand...
Click to collapse
I have a 2012 Nexus 7 running Resurrection Remix M (Android 6.0.1), and I can say that RootBooster *does* help. My N7 was *very* laggy and slow to respond when tapping on anything. I chose "Basic Mode -- Speed", re-booted and it's a LOT faster now. Time will tell if it lasts.
I've had MultiROM and TWRP on this tablet for quite awhile, so I also have RR-N installed as a secondary ROM. I'm going to try RootBooster on that ROM also.
I have a Nexus 7 2012 wifi model and need it strictly for Chromecast audio to control Pandora and Spotify.
What's the best rom for that?
Don't care for anything else really...
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
spocko said:
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
Click to expand...
Click to collapse
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Strormrage said:
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Click to expand...
Click to collapse
What was it in your case?
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs
Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,
Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.
Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.