[ROM][11][flox][OFFICIAL] crDroid 7.17 Google Nexus 7 2013 repartitioned

Search This thread

bestiatester

Senior Member
Mar 29, 2013
78
124
BE3pE0l.png

Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned


crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today


Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.

Pre-installation:


Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/LineageOS/android_kernel_google_msm
Device: https://github.com/LineageOS/android_device_asus_flox

Download:

ROM


Known issues:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.

Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
 
Last edited:

Mr.Conkel

Senior Member
Oct 10, 2020
211
60
London
Nexus 7 (2013)
OnePlus 5T
BE3pE0l.png

Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned


crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today


Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn

Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.

Pre-installation:


Sources:
ROM: https://github.com/crdroidandroid

Download:

ROM


Known issues:
Battery is shown as charging at 0 mA.
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.

Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
OH MY GAWD I'M IN LOVE😍 everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
 
Last edited:

Mr.Conkel

Senior Member
Oct 10, 2020
211
60
London
Nexus 7 (2013)
OnePlus 5T
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.

So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.

After flashing this through recovery follow these steps..

Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
 

GeekyTanuj

Senior Member
Oct 21, 2015
146
31
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.

So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.

After flashing this through recovery follow these steps..

Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Thanks for this guide! Really helped me get things going smoothly! Love this ROM.
 
  • Like
Reactions: Mr.Conkel

jojo33680

Member
Oct 17, 2013
34
13
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
 

Udonitron

Senior Member
Apr 15, 2010
639
28
Victoria
I am running an old 7.0 Resurrection ROM on my N7.
TWRP is installed & bootloader unlocked so I suspect I would just need to repartition & install?

No clue why ADBgives me these errors in powershell.

fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
 

jamescable

Senior Member
For those who have partition with a different method like me that is NOT flox so they can flash other ROMs, replace this in the ROM zip. All I did was remove assert get prop that checks to make sure your tablet is the right one for the ROM. It won't flash if you're not using flox repartition so I changed it to allow it to flash. I have 1.6gb of system space and am able to flash this ROM, opengapps pico, magisk and custom kernel with no issues running a non flox repartition.

 

bestiatester

Senior Member
Mar 29, 2013
78
124
Hi!

In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.

Can anybody please confirm that this is happening also for you?

And if you know why it is failing or even better, how to fix it... that would be great :)

Thanks in advance.
 

Davidtre07

Member
Jul 26, 2013
6
1
Hi!

In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.

Can anybody please confirm that this is happening also for you?

And if you know why it is failing or even better, how to fix it... that would be great :)

Thanks in advance.
I confirm I have the same problem
 

Davidtre07

Member
Jul 26, 2013
6
1
Hello all,
I follow the guides and the installation went smoothly, thanks for the really good job you've done.
I'm new in the crDroid world so sorry if the question seems stupid: As the power button of the Nexus 7 is not easy to access, how can I activate the double tap to wakeup ?
Some years ago the tablet was installed with aicp, and the DT2W was working. So I'm a little bit disappointed if it is not working now.
Thanks.
 

bestiatester

Senior Member
Mar 29, 2013
78
124
I'm testing a patch for the charge current to be shown ok, seems to work, if all the tests are ok I'll ship it in with the next release.
 

Davidtre07

Member
Jul 26, 2013
6
1

Davidtre07

Member
Jul 26, 2013
6
1
In Magisk I see the module is looking in /sys/ for "doubletap*" or "dt2w*" or "wake_gesture".
If it found one of the files then activate it (echo 1 in the file)

But still, you have to have the right kernel !
 
Thanks very much, this Rom is so smooth and running great. The only thing I've noticed is that the icon size and text is very small when using the tablet in landscape mode but fine in portrait mode. Any changes I make to the icon size from the settings apply in portrait but when switched to landscape stay as really small, is there any setting I have missed to enlarge them?
 

safran64

New member
Dec 1, 2013
3
0
Thank you for the great work! (y)

Just for feedback: I can confirm the camera issue, too, though it doesn't bother me.
Another small thing I noticed: during the initial setup my device was called Pixel 6 Pro (first I thought, I chose the wrong image) but in the settings it says correctly "Nexus 7".
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    BE3pE0l.png

    Code:
    *** Disclaimer
    I am not responsible for any damage you made to your device
    You have been warned


    crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today


    Features:
    https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

    Flashing Instructions:
    Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.

    Pre-installation:


    Sources:
    ROM: https://github.com/crdroidandroid
    Kernel: https://github.com/LineageOS/android_kernel_google_msm
    Device: https://github.com/LineageOS/android_device_asus_flox

    Download:

    ROM


    Known issues:
    When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.

    Visit official website @ crDroid.net
    crDroid Community Telegram
    crDroid Updates Channel
    Donate to help our team pay server costs
    2
    Just a note:
    This ROM doesn't work with followmsi's ElementalX Kernel
    Magisk works fine
    Actually it does, or at least it should. Chances are your using the Twrp Flox build provided by Ud4 which means there aren't any custom kernels for flox or at least not using this codename.

    Long story short flash CrDroid with the flox twrp, then flash the official twrp to change device codename and flash elementalx kernel see if it boots. If it does replace the twrp flox and backup your boot partition so this way after updating or dirty flashing you don't have to change twrp to get elementalx back. I did this on a previous flox build of los so it should be much of the same here.

    Elemental X works perfectly however you need to flash in this order. Twrp (flox build) > Lineage official > Twrp Official build from website > Kernel of your choosing elemental X in this case > Twrp (flox build) this way you don't have any issues with updates.

    The reason this works as far as ik are pretty simple when using flox TWRP the device isn't considered as flo and therefore aren't any kernels for flox but if you use the official twrp to change back to flo the kernel will pass. Then switch recoveries again to assure no issues with updates in the future. Good luck!!
    See this post if I wasn't clear enough here. Cheers!
    2
    Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
    Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.

    So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.

    After flashing this through recovery follow these steps..

    Initial Setup:
    - Complete the setup wizard actions as you prefer
    - Open the app drawer and long-press on Play Store to choose the App Info button
    - Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
    - Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
    - Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
    - Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
    - Choose Google device registration and enable the Register device switch, then go back
    - Choose Cloud Messaging and enable the Receive push notifications switch, then go back
    - SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
    - Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
    - This is important: Reboot now before you add a Google account or do anything else to the Play Store app
    - After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
    - Now get app info for Play Store, clear cache (yes, again), then launch the app
    - Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
    - Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
    - That should be everything!
    Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
    2
    Hi,
    I need dt2w but i can't activate it, does thé kernel support it?
    Can you Hello me please?
    Thanks you
    you need to use the Exkernel to enable dt2w. Here's the latest one: Link.
    2
    There goes 7.13 with the current fix