[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16] - Thunderbolt Android Development

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

installed last night. already liking it a lot! no problems so far.

I also am enjoying this. No issues to report. I am waiting for some loving for my xoom. Great job guys!

Amazing work as always, love it guys!

Finally decided to give twrp a go after reading so many praises about it. Very nice... Very fast!

Hmmm. Cant believe I'm the only one where Capacitive keys don't light up. Any Ideas? Love the hell out of this Recovery.

this recovery is full of win!

Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?

stevey5036 said:
Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?
Click to expand...
Click to collapse
Has nothing to do with the recovery, been running it since the first day and zero problems

False alarm.. The OTA was pushed to my phone (again) and would reboot the phone to try to install via stock recovery but it obviously wasn't there. Sorry.

I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.
Sent from my rabbit hole using my carrotbolt.

Me likey. Thanks for this!!!!

droid future said:
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.
Sent from my rabbit hole using my carrotbolt.
Click to expand...
Click to collapse
Just shooting in the dark here, but have you tried a different kernel?
USB Mass Storage works for me with TWRP2 & LiquidSmooth 3.2.

What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.
Sent from my ADR6400L using Tapatalk

PeteLopez197 said:
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I used ROM Manager to reflash CWM.
The way TWRP backs up the rom seems to be different than CWM (hooray compression!), so you can't restore a CWM Nandroid directly. At least, not that I've noticed.

So i may have bricked my phone...
Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?

twrp works great for me. its very fast. made a backup of lgb 3.2 in about 2 minutes!

I just flashed this. It worked for me. Did u make sure you renamed the zip and put it root of sdcard. This recovery has potential. I do like using the touch screen instead of my hardware, especially if volume keys are not responsive.
Sent from my ADR6400L using Tapatalk

GatoEnFuego said:
So i may have bricked my phone...
Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?
Click to expand...
Click to collapse
So the twrp IRC chat was extremely helpful in getting my phone working again. Great group of guys! Lesson learned, if you're going to flash a new recovery make sure you have a working ROM installed or else you can get caught in a bind if you pull the battery during the white HTC screen.
And if you do, make sure you lick your terminals...

I really like the concept of this recovery (touchscreen instead of hardware keys), but I feel it still needs some work to become "idiot proof", and needs to be more thorough.
For example, I decided to try restoring a backup of Skyraider Zeus, coming from Gingeritis1.1. After it completed and I rebooted into the system, there were all sorts of "leftovers" from the Gingeritis ROM packed in with Skyraider Zeus.
In other words, the recovery doesn't format the partitions prior to restoring the backup. This could lead to some serious issues for people when restoring backups of one ROM from another without manually formatting everything first.
Sent from my ADR6400L using XDA App

Related

[ROM][2.1] Eclair Strikes Back v2 [2011.06.23]

Since there's been some interest in comparing the 2.2 ROMs with the 2.1, here are some stock eclair nandroid images based on the Cincinnati Bell 2.1 ROM that can be used in OpenRecovery without flashing SBFs. You can use these to switch between 2.1 and other 2.2 ROMs without bothering with RSD Lite/sbf_flash.
Of course gallery key, camera and FM radio work well on these. Although, I've been having market problems (paid apps fail to download). Hopefully that will resolve itself if/when market decides to self-update... In the interim, I recommend using something like Titanium Backup to migrate your paid apps.
Eclair Strikes Back v2 (2011.06.23)
This is a tweaked version of CBW_eclair_STR_U2_04_1E_1.zip with some tricks we've been using in 2.2 (expanded apns-conf.xml, JIT from FrozenEclair, memhack to move dalvik-cache to /cache, egl.cfg hack to disable software rendering).
eclair-strikes-back-v2-beta.zip (the beta is now final )
Changes since v1:
ext-partition support compatible with the stock221-derived ROMs*
Automatic swap support for fjfalcon's fastboot kernel
Automatic support for link2sd (either FAT extra partition or stock221's /sd-ext/link2sd method)
Additional cpu governors (conservative, interactive)
Market upgraded to 2.2.7
*dalvik-cache on /sd-ext is not supported by default on this ROM.
Previous release: Eclair Strikes Back v1
eclair-strikes-back.zip
2011-06-16 Update to fix market on ESB v1 (upgrades market to 2.2.7)
Stock 2.1 (Cincinnati Bell)
This is a rooted version of Cincinnati Bell's STR_U2_04.1E.1 with OpenRecovery support pre-installed.
CBW_eclair_STR_U2_04_1E_1.zip
Hey Mioze do you have the app2ext script that is in the Bluesteel rom? Might try your eclair nands with it and see what i get.
I've finally successfully downloaded and installed a paid app from the market now on Eclair Strikes Back. Market is still old one though... not sure why it's taking so long to update to new one. When I did a factory reset on stock 2.1 soon after I bought the phone the market updated itself pretty quickly IIRC.
Still, this feels so smooth and fast....
EDIT:
And don't seem to be having downloading issues with any apps, be it paid or free anymore. Maybe you'll have to manually replace the market.apk with the new one though, since I'm not sure it's ever going to self-update.
syrenz said:
I've finally successfully downloaded and installed a paid app from the market now on Eclair Strikes Back. Market is still old one though... not sure why it's taking so long to update to new one. When I did a factory reset on stock 2.1 soon after I bought the phone the market updated itself pretty quickly IIRC.
Still, this feels so smooth and fast....
EDIT:
And don't seem to be having downloading issues with any apps, be it paid or free anymore. Maybe you'll have to manually replace the market.apk with the new one though, since I'm not sure it's ever going to self-update.
Click to expand...
Click to collapse
And what about moving applications to the sd? available or will be applied app2sd?. Open recovery will still work? I have some applications that are supported only from 2.2, they can no longer be installed .... of course there will have to sacrifice something.
I at the continuing problems of delay in opening and closing apps, malfunction of the camera, out of trouble and delay an application to load the launcher and would return to around 2.1, but I also like the space for application installation and open recovery.
PS: It's easy to return to 2.1?
download on process
kinda miss the haptic feedback hahaha..
thx a lot Mioze..
I'm pretty sure you can only move apps to SD for 2.2... since I never used it (I never have so many apps installed at once that it's neccesary) I don't mind losing that functionality.
There are a few apps from 2.2 that I like, most notably the new gmail and youtube apps, but those are minor sacrifices for me really.
Open recovery is installed in both those links. I find the camera works much better on 2.1, seems much faster in taking and processing pictures.
In any case, it is indeed very easy to return to 2.1 and then return back to a 2.2 ROM if you don't like it. You take one of those links (I'm using eclair strikes back) and flash it through nandroid just as you would any other ROM that we have here. And you can flash back the same way if you don't like it.
Be advised, there are currently some issues around the android market for some reason (just see the posts above)... I'm thinking we might have to replace the market apk.
Anyways, I personally am loving it.
EDIT:
Oh, you might have to setup the APN's as well.
Tavinsky said:
And what about moving applications to the sd? available or will be applied app2sd?. Open recovery will still work? I have some applications that are supported only from 2.2, they can no longer be installed .... of course there will have to sacrifice something.
I at the continuing problems of delay in opening and closing apps, malfunction of the camera, out of trouble and delay an application to load the launcher and would return to around 2.1, but I also like the space for application installation and open recovery.
PS: It's easy to return to 2.1?
Click to expand...
Click to collapse
I intend to make an updated eclair-strikes-back to add app2ext support and additional governors but I probably won't have time until later in the week. I view link2sd as the eclair equivalent of froyo's native app2sd, though. Link2sd may already work with fat as the second partition, but I haven't tested it yet because of the market problem. The market problem is #1 on my list when I get time.
And yes, these 2.1 ROMs will keep OpenRecovery intact and you can just flash between 2.1 and 2.2 ROMs the same way you would switch between 2.2 ROMs.
Thanks for the work Mioze7Ae! Let's try it, you know, always gives a bit of fear making a mistake, but gradually removes the fear. I do not know that flashing. It's like applying an Update? I apply a copy nandroid?
Tavinsky said:
Thanks for the work Mioze7Ae! Let's try it, you know, always gives a bit of fear making a mistake, but gradually removes the fear. I do not know that flashing. It's like applying an Update? I apply a copy nandroid?
Click to expand...
Click to collapse
I know how you feel. I always used to have fear/apprehension when flashing a ROM. I've done it enough times now that it's all gone by now though.
Anyways:
Download the ROM. Unzip it. Copy and paste the folder (should contain 4 things in it boot.img etc...) into your SD card under OpenRecovery/Nandroid/ (if you've gone to a 2.2 ROM you should see that ROM in the same place where you're putting this). Anyways, launch open recovery and do recovery boot or hold volume up while pressing power on (if your phone is off). If you get an image and nothing happens, you may have to go into open recovery and select install recovery system before doing this - if you have a bunch of weird pictures in your gallery including Darth Maul then you don't have to worry about this. Then navigate - using the volume keys to move up and down and the camera button to select - to Nandroid, select restore, select Eclair strikes back, select restore all. Once that's done, make sure to wipe data/factory reset and then wipe/clear dalvik cache and cache. Then reboot and it should work. (First reboots are long).
You may have to setup your APN's also.
Excellent. Thanks, sounds simple ... downloading ..... then tell how it worked.
syrenz said:
it boot.img etc...) into your SD card under OpenRecovery/Nandroid/ (if you've
Click to expand...
Click to collapse
They actually go in nandroid/openrecovery/, it's the updates.zip that go in OpenRecovery/updates/ so it's easy to remember that wrong. I'm always adb push'ing to them so I only noticed the mistake because I've got the muscle memory from typing them all the time. Gotta love the consistency
hey mioze7ae, using it right now btw, is it possible to change the read_ahead settings to 2048 instead of 128? i can manually replace the file but once reboot, it changes back.
thanks!
Manual market update
I replaced /system/app/Vending.apk with the 2.2.7 com.android.vending.apk found here:
http://forum.xda-developers.com/showthread.php?t=875067
After doing this and rebuilding dalvik-cache I have the new market and I am able to install paid apps! I'll make an update for it tomorrow, I have to crash.
Two things you can get from market before you flash. APN backup/ restore and SD speed Increase. You can backup your APNs and then once you get to the eclairs, restore them. SD Speed Increase will kick up your SD cache to 2048, instead of 128. Both are free.
Woodrube said:
Two things you can get from market before you flash. APN backup/ restore
Click to expand...
Click to collapse
Much appreciated... Didn't know there was such an app and it's a pain to re-enter all that stuff...
syrenz said:
I know how you feel. I always used to have fear/apprehension when flashing a ROM. I've done it enough times now that it's all gone by now though.
Anyways:
Download the ROM. Unzip it. Copy and paste the folder (should contain 4 things in it boot.img etc...) into your SD card under OpenRecovery/Nandroid/ (if you've gone to a 2.2 ROM you should see that ROM in the same place where you're putting this). Anyways, launch open recovery and do recovery boot or hold volume up while pressing power on (if your phone is off). If you get an image and nothing happens, you may have to go into open recovery and select install recovery system before doing this - if you have a bunch of weird pictures in your gallery including Darth Maul then you don't have to worry about this. Then navigate - using the volume keys to move up and down and the camera button to select - to Nandroid, select restore, select Eclair strikes back, select restore all. Once that's done, make sure to wipe data/factory reset and then wipe/clear dalvik cache and cache. Then reboot and it should work. (First reboots are long).
You may have to setup your APN's also.
Click to expand...
Click to collapse
I just want to check; is it completely safe to remove those wierd pics in the gallery?
androidlover123 said:
I just want to check; is it completely safe to remove those wierd pics in the gallery?
Click to expand...
Click to collapse
Yes. But if you have to use open recovery for whatever reason, you'll need them. You can either click install recovery as needed (which creates the pics) and delete them after, or the best thing to do is get an app that just hides the pics from gallery - so they are there when you need them, but don't interfere. I saw an app "Gallery Excluder" or something floating around in the XDA Android Apps section - that would work. Or a gallery like QuickPic let's you hide things as well.
EDIT:
Nevermind, Gallery Excluder hides folders only. There are other apps though, I believe.
Just an update on progress with ESB
I've done some testing and Link2SD already works with the released eclair-strikes-back but currently only when using FAT for the second partition.
To get ext support in, I'm trying to get the darktremor a2sd scripts to work. They look high quality and robust and should handle swap gracefully when booting the custom kernel as well (current status--some rare hung boots with a flaky SD card when using the latest beta scripts, will try the stable release next). There's also a GUI in the market for managing the SD card (currently only Froyo+, I'm inquiring whether the developer can add eclair support).
Mioze7Ae said:
Just an update on progress with ESB
I've done some testing and Link2SD already works with the released eclair-strikes-back but currently only when using FAT for the second partition.
To get ext support in, I'm trying to get the darktremor a2sd scripts to work. They look high quality and robust and should handle swap gracefully when booting the custom kernel as well (current status--some rare hung boots with a flaky SD card when using the latest beta scripts, will try the stable release next). There's also a GUI in the market for managing the SD card (currently only Froyo+, I'm inquiring whether the developer can add eclair support).
Click to expand...
Click to collapse
I am hoping that the ext will come through. If I am using the sd-ext/app folder on the Steelblue ROM, can I leave all my apps in there and flash your eclair with ext support (when ready) or will I have to use Titanium-migrate? I would think that it really wouldn't matter for most of the apps, except FroYo specific ones like Flash 10.3 but not sure.
p.s. Are you going to call your next version "Return of the Eclair"?
MD5 Check failed. Does this have something to do with the fact that I bought my phone in the middle east?

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
This looks interesting
I hope that many of you find this recovery very useful. I spent many days bugging the hell out of dees_troy on getting this up and running(sorry about that dees). But I my opinion the features that this recovery offers is much more than any other than what the A500 currently has. Please check it out and if you like it and would consider donating, please visit team win website. These guys spent a lot of time into this recovery and have good plans for future stuff. Enjoy!
Sent from my Sensation using Tapatalk 2
Can someone please post the flashable zip file for this? I can't install from GooManager, it always abort installation.
Does this recovery support flash from USB?
Sent from my A500 using Tapatalk 2
this recovery don't support flexreaper r11 rom (Picasso).
"Status aborded 7"
Sent from my A500 using Tapatalk 2
Does this recovery support the extendedcommand file?
micky387 said:
this recovery don't support flexreaper r11 rom (Picasso).
"Status aborded 7"
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I was wondering why it didn't install for me. Hope the team will fix this issue.
because build prop is false with flexreaper (i suppose)
who can change recovery (.zip) for flexreaper ??
thanks
Sent from my A500 using Tapatalk 2
micky387 said:
this recovery don't support flexreaper r11 rom (Picasso).
"Status aborded 7"
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Guys Status 7 Aborted errors are usually bad downloads. Please keep trying and it should go through.
i'm downloaded 5 times but same errors
Sent from my A500 using Tapatalk 2
10507 said:
Can someone please post the flashable zip file for this? I can't install from GooManager, it always abort installation.
Does this recovery support flash from USB?
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
This flashable zip has been tested on cwm-based recovery's 1.3.something and 1.7 by the man who's name may not be named.
I see no reason why it won't work on any ROM as recovery is independant of it.
Edit: Ofc only tested on my iconia a500. Just saying.
That's work with your .zip but like micky387, before I tried 5 times with GooManager and the installation didn't work.
elborak said:
Does this recovery support the extendedcommand file?
Click to expand...
Click to collapse
We have ported OpenRecoveryScript over to ClockworkMod Recovery and have submitted the code to CyanogenMod for inclusion so that any app will be able to take advantage of the same scripting support in ClockworkMod Recovery too.
Some may now be wondering why we didn't just use the "extended commands" feature that already exists in ClockworkMod Recovery. Unfortunately, recent builds of ClockworkMod Recovery have been locked down to only work with ROM Manager, so other apps like GooManager are unable to make use of this feature.
Click to expand...
Click to collapse
Some instructions on the OpenRecoveryScript would be much appreciated. Does someone have a link?
Taptalked u see
Reno_kun said:
That's work with your .zip but like micky387, before I tried 5 times with GooManager and the installation didn't work.
Click to expand...
Click to collapse
So it worked, and now you have twrp 2.1.0? On which rom? To be honest, i couldn't get the gooapp to do the work for me, that's why i made this zip (based on thor's zip as template, who's ics rom i am running also)
Taptalked u see
Yes I have twrp 2.1.0 now instead of RA-Iconia 3.16. I use Flexreaper 11.
You made a good job with this zip because it's very easy to install it and thanks to the team win for this recovery !
May have missed it, but in the wipe area, there is no wipe flexrom, some times that needs to be wiped when there are problems.
Also I forgot to look around, but can /data/media be toggled so when you wipe data that data/media can be wiped also?
Sent from my A500 using Tapatalk 2
thanks zatta.
Work fine now with your .zip.
Thank you very much
Best regards
Sent from my A500 using Tapatalk 2
Looks real nice. Just take care of the couple little things mentioned in previous posts and it will be great. (Ability to toggle full data backup and restore/wipe data/media, and ability to format flexrom)
Sent from my A500 using xda premium
BakaNeko59 said:
Looks real nice. Just take care of the couple little things mentioned in previous posts and it will be great. (Ability to toggle full data backup and restore/wipe data/media, and ability to format flexrom)
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Have you tried toggling data/media yourself?
Can someone with twrp already installed try this out for us?
Thanks all
Sent from my NexusHD2 using Tapatalk
BakaNeko59 said:
Looks real nice. Just take care of the couple little things mentioned in previous posts and it will be great. (Ability to toggle full data backup and restore/wipe data/media, and ability to format flexrom)
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Flexrom format we decided that was not really needed. I have been using twrp for almost 2 months now and have not had an issue. If a rom does anything with flexrom which are only stock based roms, they format flexrom during the install process. These are features that can be added with a theme as well. Will talk with team win tomorrow.
Sent from my Sensation using Tapatalk 2

[Tutorial] [OTA 3.0] [Nvidia Shield Tablet] How to debloat and optimize ota 3.0

DISCLAIMER: though this seems safe, there are always risks. Warranty may be void, bugs might crawl out of your shield. I am not responsible for mishaps, bugs, crashes, damage, loss of jobs, girlfriends, and/or if your shield turns into Skynet and begins to destroy the human race!
Firstly, throughout this tutorial I will be shamelessly pointing you toward others threads. Please, give them your thanks. They are masters in their fields and with out them none of this would be happening! Also remember noone gets paid for any of this, they with their skills and I with time do this out love for tech and a desire to help others and see them enjoy their tech as much as we all love ours. That said... Onto the cookies!
*********PLEASE NOTE*********
*********THIS ENTIRE PROCESS CAN BE DONE WITH OUT ANY ACCESS TO A PC!
--BUT--
TO KEEP A LOCKED BOOTLOADER AND AVOID WARRANTY NASTYNESS PLEASE READ
*If you are still on a locked bootloader, and want to easily keep it. Root ota 2.2.1 first, install flashify, and use it to install twrp.
*Rooting ota 3. 0 and using flashify from there will also preserve locked bootloader.
*Rooted ota 2.2.1 or a custom recovery will break nvidias native ota system. You will have need a copy if the FULL OTA from the links provided. They flash easily in twrp. But ONLY THE FULL OTA, NOT THE INCREMENTAL.
******PREREQUISITES (These Are Required)******
*Must be rooted.
If coming from stock, (unrooted, stock recovery, and locked bootloader) Kingroot will root any ota so far.
Install apk, run it, it will most likely reboot your shield, on ota 3 it will freeze, (mine did at around 30% on ota 3, but instead of a reboot, I got a freeze) this is normal. Hold power button until the shield turns off. Boot back up, and run Kingroot again. It should now complete fine, installing Kinguser as root control app. This gives you enough root to run flashify from play store to install the next step. (thanks to China for making kingroot and whoever translated it for us)
Kingroot link: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
*Team Win Recovery Project (twrp) must be installed.
Head over here to @Steel01 thread for multi rom twrp. You will only (at the moment) need his modified twrp build. More instructions there. Don't forget to thank him! (Thanks @Steel01)
@Steel01 multi rom twrp thread: http://forum.xda-developers.com/shield-tablet/development/multirom-v30-unofficial-port-t3025355
*ota 3.0 FULL OTA (thanks to @MidgetMob)
Link: http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
*MEGA may or may NOT work. Mega has issues from time to time. (thanks @Ctrl_Alt_Del for the heads up)
****If MEGA links are not working, here's another source.
Thanks @gavin-phelan for the links.
OTHER Link for full ota: http://forum.xda-developers.com/shield-tablet/general/android-5-1-t3115536
*SuperSU recovery flashable installer. (thanks to @Chainfire)
Link to supersu beta (beta works better for the xposed framework):
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
*Fdroid store for selinux mode changer (needed for viper) and ad away apps! (thanks Fdroid!)
Link: https://f-droid.org
*****OPTIONAL*****
*Xposed super alpha for Android 5.1 (sdk22) (thanks @romracer)
Link: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
You must read that thread a bit. You will need the xposed installer from the main xposed lollipop thread. (thanks @rovo89)
Main xposed thread
Link: http://forum.xda-developers.com/showthread.php?t=3034811
*Gravitybox works on 5.1 now (thanks @C3C076)
Link: http://forum.xda-developers.com/xposed/modules/app-gravitybox-v5-0-0alpha-tweak-box-t3037566
*BusyBox - Busybox is required for viper4android install. Make sure to run and install it BEFORE YOU INSTALL VIPER DRIVER. The apk can be installed, but when you run it. It will try to install the viper driver. Selinux must be set to permissive, and busybox installed first.
It can be found in play store.
*selinuxmodechanger can be found in fdroid repository.
*ViPER4Android audio engine (thanks @zhuhang)
For viper install. Be sure to install fdroid and get selinux mode changer. And change to permissive BEFORE YOU INSTALL VIPER DRIVER. the app is fine but for the driver to install selinux must be set to permissive. After that it's fine to set it back to enforcing.
Link: http://vipersaudio.com/blog/?page_id=48
Forum:
http://forum.xda-developers.com/showthread.php?t=2191223
Someone said cookies? (Procedure)
**tip** titanium backup SUCKS FOR backing up app data. Bugs out the apps sometimes. So for games, manually backup saves and place them back after reinstall. It's helpful to use tibu to backup your apps alone. Then use tibu again to make a recovery flashable zip to reinstall them all at once....
*Firstly you will need a root enabled file browser (I use es file explorer)
*On the internal memory, firstly back up any pics or ANYTHING you want saved from internal memory to the external SD card. (I usually name my backup folders starting with a # to keep them separated from anything that's written to external via an app or the system. Helps to keep track.)
*Next delete it ALL. In es file Explorer just as everything in sdcard0. /android gone, all folders, ax them. I even nuked the hidden folders and all. I wanted a totally clean install. So anything in the /sdcard0 folder can get wiped. As wiping through twrp DOES NOT WIPE THESE FILES. And sometimes can cause oddness on new installs. This can also be achieved through twrp but it takes longer. Keep in mind that everything inside /sdcard is rebuilt on FIRST boot. Hence deleting in twrp. Don't navigate to straight / things go bad if you mess about in those files....
*After everything has been deleted on internal, and the folders your not using for backups on external. Namely the /android folder on external. You should be ready to reboot to recovery....
*Now reboot into twrp. Click wipe, advanced, then check dalvik, system, data, and cache. Wipe
*Now flash the FULL OTA for your model of shield.
*Next click the home button in twrp. Then Mount, then, uncheck the box for system, then, re-check it. (remount system)
*Now click on the Home button again, Advanced, File Manager.....
*Now the fun part...
Navigate to /system/app and delete the following FOLDERS, contents and all, by clicking on each folder one at a time, once clicked, it will show you contents of that folder. At the bottom click select, then delete, swipe to delete. For each of the following folders....
++*NOTICE* Some of these folders contain libs (library files) and i discovered some issues with deleting them. (videos not working, possible connection console mode crashing, etc) These folders are indicated below, and any side effects possible due to its removal. Console mode has been solid so far even without the libs. That doesnt mean that it wont cause any issues later and i just havent seen it yet. So BEWARE o0o0o =D
Adobe reader
Books
Calendar
++**Chrome (I use chrome beta) (CONTAINS LIBS) possible connection to the "great chrome slowdown" These ARE SAFE to remove and removal may cure the slowdown bug. either way, using any browser BUT chrome (i.e. Chrome Beta, Dolphin, Opera etc.) also fixes the "Chrome slug races"
Cloud print
Input methods for Japanese and Korean (unless you need it)
++**Drive (CONTAINS LIBS) i havent noticed any side effects from removing these and SHOULD BE SAFE to delete. also i use es file explorer for drive access
Email (I use inbox)
Evernote
Evernote widget
Exchange2
Gmail (I use inbox or reinstall from store)
++**Hangouts (CONTAINS LIBS) i use hangouts for OUTGOING PHONE CALLS, as such i feel these libs are POSSIBLY NOT SAFE to remove. i havent found any issues so far but BETTER SAFE THAN SORRY on an essential core sytem
Holo spiral
Google tts (optional)
Juswrite (I don't use the stylus or handwriting)
latinIME (aosp keyboard)
++**Maps (CONTAINS LIBS) i havent found any issues but NAVIGATION to me is an essential core system therefore i feel these are POSSIBLY NOT SAFE to remove. again BETTER SAFE THAN SORRY
Music2 (I use gonemad music player or reinstall from store)
Newstand
Nvcameraawesome (it sucked and I use camera51)
Phase beam
Play games
++**Print spooler (CONTAINS LIBS) never use(d) it so i dunno really. SHOULD BE SAFE to remove (feedback welcome)
Street
Stylusmobileoem (like I said I don't even HAVE a stylus (unless someone has an extra they are willing to mail....)
Talkback
Trine 2 (unless you like it)
Twitch (unless you use it, also in play store)
++**Videos (CONTAINS LIBS) I had issues playing embedded videos in play store (app trailers) and some websites. i would recommend DO NOT REMOVE THIS. i ONLY left this here for info only. remove ONLY AT YOUR OWN RISK
Write (again with stylus stuff)
++**Youtube (CONTAINS LIBS) never had any issues removing this. but i feel it could be related to my above mentioned video playback bug. this is OPTIONAL.
*now navigate to /system/priv-app
Delete folder musicfx (needs to be gone or disabled for viper4android audio install)
*now navigate to /system/vendor/app
Delete the folder watercolor (dabbler can be gotten from play store)
*if you feel busy /system/media/audio is where the ring tones are and you can delete the ones you don't use for more space but it's only 3mb....
*FINALLY hit the home button in twrp again.
**DO NOT FORGET** Install superSU beta for root!!!
*REBOOT!!
*After system boots up and gets done optimizing, it's safe to reboot back to twrp and flash the xposed framework.
*You're done! That's it... Wait... What? You want even MORE cookies? Well, OK....
*Keep reading for optional steps for even better results!
***PS... Keep checking our friend's @BitOBSessiOn and @twistedumbrella threads for really great kernels for our ota..
Thanks @BitOBSessiOn
Thanks @twistedumbrella
Links:
Bito: http://forum.xda-developers.com/shi.../tweaked-kernel-nvidia-shield-tablet-t3069776
++++++ ***check out @BitOBSessiOn thread, ota 3.0 source built, optimized kernels for all models released!
NEW UNIFIED BUILDS FOR OTA 3.0 (ONE FILE FOR ALL MODELS)
Twistedumbrella: 2.2.1 ONLY http://forum.xda-developers.com/shi...t/stock-lollipop-kernel-cifs-support-t2967839
And some more post script.
PPS **tips**
*System apps always keep a copy of themselves for when it gets updated, so all those apps (that you just deleted) end up being over 400 mb after they all update once. And they ALL HAVE updates at time of install. So you save there. Just takes a minute to reinstall as user apps from the play store,and save a bunch of space.
***WIFI ISSUES!** If you do NOT HAVE a 5ghz router. Go to wifi settings, advanced, wifi band, switch from auto to 2.4ghz, makes the Web run faster and if it's set to auto I notice a good 40 second delay in wifi connecting. Also make sure the box "wifi always scan" is turned in. Otherwise wifi doesn't auto connect at boot.
*Get folder mount from the play store. It automagically patches android to let apps write to external SD. As well as links folders on external to internal so you can move ANY app to sd card. Profit!
*For a cleaner install. Install fdroid, then ad away. And run ad away before you ever open more than play store for es file Explorer to install fdroid. This way ad away is the first or one of the first apps to open. Blocking ads from that point on. That way if apps have built in ads, they won't even be able to load!
*Also thanks to @djdarkknight96 here's a link for a bad ass themed SwiftKey keyboard
http://forum.xda-developers.com/showthread.php?t=1016053
*To improve system responsiveness, enable developer options (In settings, click about tablet, click build number 7 times.) Then in developer options about midway down, turn "window animation scale" "transition animation scale" and "animator duration scale" from 1.0 to .5 this increases the speed of animations throughout the system/rom
*After installing the gravitybox xposed module, you can turn those 3 animation scales down further to .25 for even faster response.
*Native lcd density for shield tablet is 283.
It comes stock at 320
*Nvidia corporate tegra color scheme. Green is hex (#76b900) rgb (r:118 g:185 b:0), and grey, hex (#5c5c5c) not sure greys rgb. And black.... I looked it up in their corporate and product guidelines pdf.
*You can add apps to console mode by clicking the little + symbol under "android games" and "media apps" in shield hub. They will then be added to the "easier" to navigate shield hub menu.
*In the play store kernel adiutor (yes that's how it's spelled) allows control over the cpu speed and other critical stuff and things. To squeeze alot more juice from your battery, if everything else here is done, I found I could clock the cpu @2ghz (200mhz down from stock) and it's just as fast as true stock. Killer battery savings on top of the improvements already made in ota 3.0
*If you adjust the clock speeds in kernel adiutor... Make sure to reset the minimum to 51 every time and sit and watch to make sure they stuck. They will float around, then settle. But if you exit after altering the max and the minimum is floating high, it will set the minimum to that value.... Found THAT out the hard way......
*The letters that form the word "SHIELD" on the back of our devices.... Are stickers in small indents.... Looks really kewl if taken out. (see post #13 for pics)
+ *POSSIBLE USB ON THE GO (OTG) FIX*
Power off your shield, plug in USB OTG cable with a flash drive in it. Power on the shield. Once booted, pull flash drive and use whatever OTG compatible device you wish (mouse, keyboard, micro missile launcher--thanks ThinkGeek!))
ONE CONDITION! This method BREAKS CHARGING UNTIL NEXT REBOOT! (thanks nvidia!)
Enjoy!
Questions and comments always welcomed and encouraged!
If i forgot something, missed a step, whatever. Let me know!
I'll update/add to this if/when I think of things.
Ideas? Let me know!
CHECK POST #2 FOR UPDATE TIMES.
I'll try to highlight changes until I update again.
Look for the + symbol
Cheers,
Cyris
Mmm cookies just like mom makes!
Just a reminder! ALWAYS CHECK THE MD5 CHECKSUM FOR DOWNLOADED FILES. Md5 checker in play store works great. It can certainly save some headaches!
A SECOND MORE IMPORTANT REMINDER, KEEP A COPY OF YOUR FULL OTA IN THE ROOT OF YOUR EXTERNAL SD CARD. THAT WAY IF THE LIQUID DEFECATION TRULY STRIKES THE AUXILIARY ROTOR. YOU CAN USE NVIDIAS BACKUP STOCK RECOVERY (AT BUGDROID (ANDY ON HIS BACK WITH A RED ! OVER IT) HIT "VOLUME UP" + "POWER") TO WIPE DATA AND FLASH A STOCK FULL OTA AND GET BACK UP AND RUNNING AGAIN. THEN USE KINGROOT, THEN FLASHIFY, THEN TWRP, TO GET ROOT BACK AND CUSTOM RECOVERY....
**UPDATES**
Times are Pacific (my local)
+Initial post 5/25 @ 1300 (apx)
+Updated 5/25 @ 1655
+Updated 5/25 @ 1730
+Updated 5/25 @ 1810 - make sure you check this one for viper audio install
+Updated 5/25 @ 2304 - new full ota links
+Updated 5/26 @ 1030 - @BitOBSessiOn ota 3 kernel release, links posted
+Updated 5/26 @ 1546 - Added usb-otg temporary fix
+Updated 5/27 @ 2200 - Cleanup OP, removed old + symbols
+Updated 6/17 @ 1430 - Added info on folders containing LIBS in the wiping section.
Nice! I will report back once I have redone my tablet.
And please, give me some time. It's the end of a holiday weekend & I have a few things to do before going back to work Tuesday.
Ctrl_Alt_Del said:
Nice! I will report back once I have redone my tablet.
And please, give me some time. It's the end of a holiday weekend & I have a few things to do before going back to work Tuesday.
Click to expand...
Click to collapse
No worries. I created this thread for a laid back easy way to (try) and get the most from our device. Xda was always my go to place to find help and it's a bit different now. Not everyone is a developer, but it shouldn't be hard to get knowledge from those that are. Hell I'm no dev, just like to test stuff, a crack flasher. But at one time I didn't know what root was..... We all were. I know I love it when I show someone my device I spent 100s of hours tweaking just right and the look on their face! At one time that was me. I had to ask questions that probably got a few chuckles. But usually there was someone there to ask. If i can help I figure I SHOULD,
As I said I encourage questions. It may help someone else later on. Cheers!
... Wrong button.....
All is well. And the wipe,install directions from TWRP went flawlessly.
As soon as it booted, I was presented with the Welcome screen, as if it were a brand new device, unlike just updating an older OS. Chose the language, if I had a Google account & signed in...all that cookie dust. Apps from the list I have backed up to the Google servers under my account downloaded & installed automagically.
And best of all....no more "Android is Starting" & no more "optimizing the apps" at cold startup! Big thumbs up there! :good:
By the way, I could not get the full install from the link you provided from another user. It went to Mega & Mega is having transfer issues. It would download about 10 thru 15 % then flash something about a transfer error, then reduce the file transferred back down to 8 or 9 %...then download that again up to around 12 % or so, then back down to 8 %....lather, rinse, repeat...indefinitely! I used this user's link in his post to get the correct ROM: Android 5.1 out now
Just an FYI there.
Ctrl_Alt_Del said:
All is well. And the wipe,install directions from TWRP went flawlessly.
As soon as it booted, I was presented with the Welcome screen, as if it were a brand new device, unlike just updating an older OS. Chose the language, if I had a Google account & signed in...all that cookie dust. Apps from the list I have backed up to the Google servers under my account downloaded & installed automagically.
And best of all....no more "Android is Starting" & no more "optimizing the apps" at cold startup! Big thumbs up there! :good:
By the way, I could not get the full install from the link you provided from another user. It went to Mega & Mega is having transfer issues. It would download about 10 thru 15 % then flash something about a transfer error, then reduce the file transferred back down to 8 or 9 %...then download that again up to around 12 % or so, then back down to 8 %....lather, rinse, repeat...indefinitely! I used this user's link in his post to get the correct ROM: Android 5.1 out now
Just an FYI there.
Click to expand...
Click to collapse
Glad to hear it went well. And thanks for the info on mega. It does that from time to time. Could be alot of people trying to get that file right now. Links updated.
If you go through the xposed install and all. It gets spooky fast....
can you explain about screen density? native 283? how do you know that? table has 320 dpi
Excellent guide and info. Spent all weekend formatting and dealing with "optimizing apps", this fixed it all, great tablet now
GOALAR said:
can you explain about screen density? native 283? how do you know that? table has 320 dpi
Click to expand...
Click to collapse
It's an 8 inch screen. With a resolution of 1920x1200 I'm not sure the math, but it adds up to 283,or there are a few sites that you can go to and enter your the screen info and it will tell you what you density is. Density is how many pixels are in a square inch. Also GSM arena and a few other sites show this data if you Google "shield tablet specs".
Switching from 320 to 283 just makes the screen look sharper. It also can effect what games are listed as compatible in the play store. Example, dead space and dead trigger 2 will not install @ 283. But will run at it. I have dead space myself and it plays fine but I have to side load it or set my density back to 320 in build.prop then install it.
Think of it like running different resolutions on your pc monitor. The monitor will show them just fine, but only 1 is the exact spec from the factory, and look the best.
Thanks For This
Hi, @Pariahnoble. Just wanted to say that this is great, exactly the kind of effort that supports the XDA community.
I am sure that this will be a huge help to a lot of people.
koop1955 said:
Hi, @Pariahnoble. Just wanted to say that this is great, exactly the kind of effort that supports the XDA community.
I am sure that this will be a huge help to a lot of people.
Click to expand...
Click to collapse
Thanks! =D Just hope it does in fact help some folks enjoy their shields a little more. I've been pretty unhappy so far, it was this or a Nexus 9, now I don't regret my decision anymore lol
Pictures of back of shield with letter stickers removed
Updated again
I'm surprised there aren't more comments on this thread. This looks great.
By the way, did I miss something or can this actually be done completely without the use of a computer?
radio five said:
I'm surprised there aren't more comments on this thread. This looks great.
By the way, did I miss something or can this actually be done completely without the use of a computer?
Click to expand...
Click to collapse
Nope didn't miss a beat. This whole process can be done with no pc (I don't have a pc, my shield is my ONLY device.) so I've learned how to do it all locally (on board the shield itself).
This is only just now available, 5/13 kingroot was released that would root the tablet stock off the shelf. And flashify to put on the custom twrp. After that it's good times!
Ps, thanks for the heads up on the no pc thing, I forgot to mention that, OP updated...
That's great news for me since my computer recently took a **** and I'm about to throw my old laptop out the window. (windows vista, won't take adb drivers, runs out of memory using chrome, etc...)
Sent from my SHIELD Tablet using XDA Free mobile app
radio five said:
That's great news for me since my computer recently took a **** and I'm about to throw my old laptop out the window. (windows vista, won't take adb drivers, runs out of memory using chrome, etc...)
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Ouch! I feel your pain. I recently had to try to flash using add (adb but "add" was a great typo) on Windows xp.... Oh yeah... THAT went well.... Then 2 days later kingroot came out.
Just make sure (and I'll add this to the op as well) to keep a copy of the full ota on the ROOT of your external SD card, that way if your shield take a flaming deuce in your hands, you can STILL use nvidia backup recovery. If you have ever seen the "bug droid" (ole Andy on his back and the flaming red ! Over it) hold the "volume up" button and hit power and the nvidia recovery comes up. Let's you flash a STOCK FULL OTA and bam, back in business, just kingroot, flashify, twrp, keep calm, and carry on!
Man, I'm glad you said something! I'm gathering all the files on my external sd card in a folder (downloads/Shield Optimization) and I was getting ready to take the plunge. I'll move everything to the sd card's root before I get started.
I'm also considering backing all of my sd card to a work computer temporarily so I can reformat it. My junk heap of a laptop can't read it but I suspect my shield may have formatted it to a weird..... format.
I just want to have the card ready in the event I want to transfer large files and not wait as long.
Speaking of which, would I be able to format my sd card via my PC with it still in the Shield, connected by a usb cable?
Sorry if I'm getting slightly off topic.
Sent from my SHIELD Tablet using XDA Free mobile app
@radio five
Firstly the only file you really need in the root folder is the ota zip. That's only because I'm pretty sure that's where the stock recovery will look for it, IF everything goes to hell.
Yes about formatting your card or storing files elsewhere during all this. The closer to a fresh card and internal memory the better.
Not sure what if any besides ntfs that the shield would format it to. But ntfs is recommended. And it's so far the only (I think) supported format for cards over 32gb. Also. After you format it to ntfs, quick format is OK, full is better but much slower on Windows, make sure to name it. Any is OK. "Sdcard" works.
In Windows Explorer, click on the volume (Sdcard you just formatted) to select it. Wait a sec. Then click it again. And name it when it highlights.
It fixes SOMETHING, Noone really knows what, but makes the shield recognize SD cards over 32gb
I'm sure there IS a way to format via adb, but I have no idea how...
What topic? >.< lol all questions are encouraged.

[ROM] Evervolv | 7.0.0p1 [AOSP Nougat 7.0.0] [3.4 kernel] [ALPHA] WIFI & 4G

For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is Nougat(Android 7.0.0).
Current version: 7.0.0p1
Current Items not working/Buggy
Updated 10-27-2016
WIFI MODEL
Camera
Wifi cuts out for some.
4g MODEL
Camera
Wifi cuts out for some.
You tell me what you find.
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
[Unoffical TWRP Builds]
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09-06-16.zip Updated to 3.0.2.0
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09-11-16.zip Made a little smaller then previous 9.2mb
**REQUIRES 1312MB System Partition.
This is very easy to do via JCSullins Toolbox
WIFI MODEL TEST BUILDS
http://evervolv.com/get/ev_tenderloin-7.0-testing-2016.10.05.zip Ok this isn't block style install which allows changing the size of system to what you want and use all of it. Its a slower install time but not much slower then before. Also some BT changes that allow me to use my headset. Test out BT and let me know. I'm still testing myself. Another change is root is disabled by default. You will have to go into Evervolv toolbox to enable root.
http://evervolv.com/get/ev_tenderloin-7.0-testing-2016.10.27.zip Behind the scene updates along with fixing BT speakers HOPEFULLY 8)
4g MODEL TEST BUILDS
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.09.07.zip
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.09.17.zip Includes all above
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.10.27.zip Behind the scene updates along with fixing BT speakers HOPEFULLY 8)
These are the gapps im using. http://opengapps.org/?download=true&arch=arm&api=7.0&variant=pico gapps that seem to work the best with Nougat UPDATED 09-06-16
Click to expand...
Click to collapse
****************************************PLEASE READ**************************************************************
F2FS installs. If you want to try out F2FS you will have to wipe your data parition which includes your internal sd card. Some steps if you want to backup your data. PLEASE NOTE DON'T DO THIS IF YOU DON'T KNOW WHAT YOU ARE DOING CAN CAUSE ISSUES OR LOST DATA. IF YOU DON'T DO THIS IT WILL STILL WORK WITH THE CURRENT FORMAT EXT4.
-- Flash the F2FS compatible TWRP Recovery
-- Boot into Recovery
-- Backup > Data
-- Save your internal SD card by transfering to your PC or if you have room your external_sd
-- Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
-- Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
-- Copy the saved SD card content back to your device
-- Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
-- Advanced > Fix Permissions
-- Wipe > Advanced Wipe > Cache & Dalvik Cache
-- Flash the 2-12-15 test build and gapps to ensure you got them
-- Reboot to system
Click to expand...
Click to collapse
[UPGRADE(Dirty Flash)]
I have noticed if you dirty flash on first boot you may experience a little lag or possible reboot. After it settles down no issues. Not sure if its art related on upgrades or what. Its hard to pin point as it only happens once and smooth after that. Recommend after an upgrade let it settle in before playing hard.
Thanks
Click to expand...
Click to collapse
FIrst boot is a little slow but that is due to art. I always recommend a clean install when upgrading but if you feel luck. Backup and try a dirty flash. If you have issues run a clean install and if you still have issues please post with a logcat. You can upload via bugreport in the toolbox under settings. If going from a differnt rom other then evervolv lollipop always clean install. ALWAYS REMEMBER TO BACKUP its important if you don't want to loose anything
Click to expand...
Click to collapse
NOTE: NEED a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
EricBlade --for my second 4g model to start in on this for Marshmallow
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
Biggest thing is need to update system size and use new recovery.
Alot of features have been turned on yet this is ALPHA its not a daily. I released for all to play with and we will grow on this. 8)
TP Toolbox v0.42 Complete Data Reset Guide with Updated Links
NOTICE: THIS THREAD WAS ABANDONED BY THE OP, BUT I WILL KEEP THE LINKS IN THIS POST UPDATED
This guide is for a complete data reset to start from scratch. You should only need to use TP Toolbox to either adjust partition sizes, or start from scratch if any partitions got corrupted or you get errors while adjusting partitions or installing new ROMs.
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
I recommend keeping those files on your PC hard drive so you can always re-use them in the future if needed.
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files from your PC to the "tpinstall" folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the newer 3/24/17 TWRP 3.1.0.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the Wifi model ROM or the 4G model ROM along with some OpenGapps
AlwaysLucky said:
Great work @flintman! Will test out now! Many thanks on your continued attention on the tenderloin!
PS: Your OP says you are working on "Marshmallow(Android 7.0.1)"
Click to expand...
Click to collapse
Missed that one. Remember to upsize your system partition.
Wow.
Thank you flintman for giving our touchpad a treat of fresh nougat.
I increased the system size to 1.5 gb several days ago and waited for your nougat. Now downloading it...
Edit: are we required to use the new twrp recovery in the OP? I have twrp 3.0.2 with an older time stamp.
BIG THANKS @flintman
googlephone said:
Wow.
Thank you flintman for giving our touchpad a treat of fresh nougat.
I increased the system size to 1.5 gb several days ago and waited for your nougat. Now downloading it...
Edit: are we required to use the new twrp recovery in the OP? I have twrp 3.0.2 with an older time stamp.
Click to expand...
Click to collapse
Yes use the one in the op you will get an error (not fatal) on older recoveries.
Sent from my Nexus 6 using XDA-Developers mobile app
flintman said:
Remember to upsize your system partition.
Click to expand...
Click to collapse
I actually enlarged the System partition to 1500mb just to be safe, and am testing the Nano OpenGApps. So far everything works great! I've installed several different apps, and all seem to work just fine with no FCs. I also get to test out the apps I'm developing on the Nougat OS, so that's really nice. I do miss CM theme support and the Evervolv toolbox, but I promise to be very patient; as I know those are out of your hands. :angel: I also flashed AdAway to the system and that is also functioning fine.
EDIT: For those who would like a flashable zip of AdAway to flash it to the System, I attached it to this post.
I dirty flashed over evervolve 6.0.1 and it boots up in about 6 minutes.
It feels much faster than 6.0.1 and the multi window is amazing.
There is no evervolve toolbox tab in setting, so there is no option to change the cpu frequency.
In the OP, it mentioned evervolve toolbox for bug report. Is the toolbox supposed to be absent?
Edit: second question: where do we control root permissions?
googlephone said:
I dirty flashed over evervolve 6.0.1 and it boots up in about 6 minutes.
It feels much faster than 6.0.1 and the multi window is amazing.
There is no evervolve toolbox tab in setting, so there is no option to change the cpu frequency.
In the OP, it mentioned evervolve toolbox for bug report. Is the toolbox supposed to be absent?
Edit: second question: where do we control root permissions?
Click to expand...
Click to collapse
Im surprised a dirty flash worked. As stated above not alot of features have been added but the toolbox access at the moment is only though the launcher you should see toolbox just like any other app. Root permission is controlled though the toolbox as well.
How can we promote this thread to the xda news portal? Flintman deserves a spot there.
Edit: there is no thanks button any more on XDA? I can not find that button.
Edit: now the thanks button shows up. Weird.
AlwaysLucky said:
I actually enlarged the System partition to 1500mb just to be safe, and am testing the Nano OpenGApps. So far everything works great! I've installed several different apps, and all seem to work just fine with no FCs. I also get to test out the apps I'm developing on the Nougat OS, so that's really nice. I do miss CM theme support and the Evervolv toolbox, but I promise to be very patient; as I know those are out of your hands. :angel: I also flashed AdAway to the system and that is also functioning fine.
Click to expand...
Click to collapse
Toolbox is located in the launcher for now. All features will be added back little by little. 8) trying to get a good base and then we move on.
flintman said:
Toolbox is located in the launcher for now.
Click to expand...
Click to collapse
OMG, I'm so blind. Sorry about that. :silly:
@ flintman
how is your general partitionsetup, not just system.
schwatter said:
@ flintman
how is your general partitionsetup, not just system.
Click to expand...
Click to collapse
1312 for system, 1 gig for external and rest in data. I
Sent from my Nexus 6 using XDA-Developers mobile app
flintman said:
1312 for system, 1 gig for external and rest in data. I
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, it looks like my setup. I find in touchpad toolbox the partition "media". So "media is like "external" right?
And about "cm-cache", i think i set it up in the past from 200 to 1000. Is that better? So normally yes because
of more. But i don't know how android handle it. That's why i ask.
Hey gang, using tptb I placed jcs rom and the gapps and used jc twrp recovert. it failed. ant pointers? thanks..
deafasheck said:
Hey gang, using tptb I placed jcs rom and the gapps and used jc twrp recovert. it failed. ant pointers? thanks..
Click to expand...
Click to collapse
If you've switched to f2fs, then that's the reason. TPTB is unfortunately incompatible with it.
Hi didn't switch to f2fs. I downloaded the files and used pc tptb for the installation.. Currently I am trying to get wifi working better. I installed the job new rom and cm 12 going to the WiFi forum. I have just bought a new one that's 16 gig, it has WiFi access but falters..
But on this issue I will try to get it going on the other TouchPad see if it works..
Amazing stuff
Great job as always. Flintman, you have always been the first ou with the new release of Android since i have had a toucpad for the last few years. Congratulations again and thanks for all your work.
And Multi screen works too!

FLOSSbOxIN - A Customized Stock ROM

FLOSSbOxIN - Since 2016, I am a non-foogle person, nor do I have shucksfook, or anything of those stuffs. I was on Telegram and used to run the flossboxin channel, but left the application due to too much of spam and useless stuffs, and moreover, privacy issues tbvh. Now my XMPP channel is named FLOSSbOxIN too. I recently lost my M30, however, I have been for quiet sometime trying to get this M30 debloated to a level where knox also does not trip, nor where one will have to face the unnecessary Samsung bloatware and annoying analytics. Finally, I have made it to that level, after several permutation combinations.
Code:
[B]FLOSSbOxIN M305F Debloated FOSS/FLOSS Stock ROM[/B]
Released: [B]20200925[/B]
Patch Level: September 01, 2020
Build Date: [B]20200926[/B]
Base Version: Android 10
Build #: QP1A.190711.020.M305FDDS6CTI1
Kernel: [I]4.4.177-19407255[/I]
UI Core: [U]One UI 2.0[/U]
Links:
M30 Database -- AFH
DM-Verity -- AFH
FLOSSbOxIN - ROM -- Cloud - Direct Link
Odin V3.14.4 -- AFH
TWRP 3.4.0-0 -- AFH
Magisk Canary -- AFH
Installation Guide (Only For Bootloader UL On Q/10)
Download ROM from the links given.
Boot to recovery (stock/TWRP) (Guide Link)
Code:
adb reboot download
You will have to format data, as the ROM is decrypted, and coming from an encrypted ROM will give issues. For decrypting, do a "format data" in TWRP Recovery and then reboot to recovery and Wipe Dalvik/ART, Cache, System, Data, Hidden, Internal
Copy over ROM OS & DM-Verity file (do not rename DM-Verity file, keep as is)
Flash ROM - Would take around 10 minutes time for it to flash
Go to wipe, and wipe /hidden
Flash DM-Verity file
Reboot - should take around 5-6 minutes
Notes:
I have removed the setup wizard altogether
Post system starts, wait 5-10 minutes, as system tries to integrate system apps, which are newly introduced
Only necessary foogle stuff is kept, including Maps+Location, GSF & Play Services and all other foogle stuffs is removed
Somehow, even after removing the notorious HIYA (so called caller id and spam protection service), it somehow comes back with a valid internet/mobile data connection. If you wish to remove it again, boot to TWRP, mount /system and then delete the hiya service folder and clear dalvik/cache, and reboot
If any app has permission issue, then reinstall as "user" app (install again manually), and reboot sysui. Should work post that, as sometime, few apps are by default not allowed system changes by Samsung framework, and to add each app to framework is a bigggg task, and very irritating too
Still if any app (e.g., AnysoftKeyboard (see git issue), then uninstall as system, and reinstall as user
Ensure minimal apps are made /system, as they can be harmful
Features:
Fully debloated
Fully stock
Smoother, faster and has long battery run
Foogle & Samsung stupidity free
FLOSS apps included:
Aurora Droid, Aurora Store
F-Droid Classic - Classic variant by bubu
F-Droid Privilege (if you ever install F-Droid main app)
Bromite Webview is default
UngoogledChromium is the default browser
FreeOTP+ is your FLOSS 2FA companion
K9 Mail is the default FOSS email
KeePassDX for auto-login and enhanced privacy
Notification Log allows you to view several logs, once usage access is granted, and is fully FLOSS
QKSMS replaces Samsung Messaging app
Power App allows you to reboot to various modes - sysui, recovery, bootloader....
Vinyl is your music buddy
Dual-Mod for audio included
Screen capture (image & video) feature added
Data transmit (Up/Down) in status bar added (thanks Akhil)
Various camera tweaks (FOSS - OpenCamera is not included)
My hosts file is included, which enhances privacy by blocking various trackers and ads - URL
Hosts editor also included
GPS fast locking in closed areas - debug included for it
USB debug revoke option added to Dev mode
initd support added
Shutdown thread log enabled
BUGS
FLOSSbOxIN - You tell me..
Contributors/Credits:
Samsung for the superb bloat filled operating system, which is like a bliss in the irritation module
topjohnwu for Magisk
Akhil99 for TWRP
vdbhb59 for actually spending hours on getting this sorted, and when I do not even have the phone anymore (lol)...
XDA:DevDB Information
FLOSSbOxIN, ROM for the Samsung Galaxy M30
Contributors
vdbhb59, vdbhb59
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: M305FDDS6CTI1, M305FDDUS6CT13
Based On: Stock
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-09-25
Created 2020-09-25
Last Updated 2020-10-17
Snapshots
Snapshots
Reserved 2
Cool FLOSS Rom sar!
Thank you sir. Working on getting a Foogle Based FOSS ROM, so that few stupid apps which are GSF dependent can work out of box.
Google version added, and OFFICIAL tag added..
vdbhb59 said:
DM-Verity -- https://www.androidfilehost.com/?fid=8889791610682882483
Click to expand...
Click to collapse
@faiz5200 here is the link..
Ajayagrawal said:
Hello
Click to expand...
Click to collapse
Okay mate.
Few ways to do it.
1. By installing rooted AP with TWRP already included:->
Install September stock Firmware from my post here: https://forum.xda-developers.com/galaxy-m30/development/rom-t4167497
Use that to flash the September FW. Use ODIN via windows, and use the file: AP ROOTED WITH TWRP RECOVERY. Flash only AP. CP is optional. Follow the steps there. Ensure to flash DMVERITY.
This is one way...
Another way:
2. Flash stock ROM. Connect to wifi/mobile data and setup. Change the time to say 7 days prior to today. Wait 30 minutes and boot to download mode via the following method:: switch off. Press Vol+/- together and connect to laptop/pc via usb. Ensure usb debugging is ON and then perform. Now you are in download mode. Flash TWRP.tar file from AP. All checkboxes should be unticked. Once flashed successfully, press vol- and power button for 7-8 seconds and let go off vol- upon haptic feedback and press vol+ to enter to twrp recovery. You can let go of the buttons once twrp shows up.
Now format data and reboot to twrp again. Mount data and /system and if OS is installed boot to system, else flash a ROM of your choice.
3rd way:
3. Download FLOSSbOxIN (FLOSS/Google variant available). Extract to any desktop folder. Now open 7Zip and make a zip file with all the .img files. Choose .tar (available from 7Zip dropdown as well) and rename the tar file to say rom.tar.
Once done flash this one via AP. Ensure all checkboxes are unchecked. Reboot to TWRP following the steps in method 2 above. Format data, boot to twrp, flash dm-verity and boot to system. You can wipe cache/dalvik and /hidden if you want. Will take around 10 minutes to boot. Dont forget to boot to twrp first and flash dmverity, else you will end in bootloop.
Note: With Samsung, in case you forget to flash DMVerity, and by mistake clicked boot to system, do not worry. Switch off, or reboot to twrp and mount /system and flash. Wipe dalvik and cache, reboot. Done.
vdbhb59 said:
Okay mate.
Few ways to do it.
1. By installing rooted AP with TWRP already included:->
Install September stock Firmware from my post here: https://forum.xda-developers.com/galaxy-m30/development/rom-t4167497
Use that to flash the September FW. Use ODIN via windows, and use the file: AP ROOTED WITH TWRP RECOVERY. Flash only AP. CP is optional. Follow the steps there. Ensure to flash DMVERITY.
This is one way...
Another way:
2. Flash stock ROM. Connect to wifi/mobile data and setup. Change the time to say 7 days prior to today. Wait 30 minutes and boot to download mode via the following method:: switch off. Press Vol+/- together and connect to laptop/pc via usb. Ensure usb debugging is ON and then perform. Now you are in download mode. Flash TWRP.tar file from AP. All checkboxes should be unticked. Once flashed successfully, press vol- and power button for 7-8 seconds and let go off vol- upon haptic feedback and press vol+ to enter to twrp recovery. You can let go of the buttons once twrp shows up.
Now format data and reboot to twrp again. Mount data and /system and if OS is installed boot to system, else flash a ROM of your choice.
3rd way:
3. Download FLOSSbOxIN (FLOSS/Google variant available). Extract to any desktop folder. Now open 7Zip and make a zip file with all the .img files. Choose .tar (available from 7Zip dropdown as well) and rename the tar file to say rom.tar.
Once done flash this one via AP. Ensure all checkboxes are unchecked. Reboot to TWRP following the steps in method 2 above. Format data, boot to twrp, flash dm-verity and boot to system. You can wipe cache/dalvik and /hidden if you want. Will take around 10 minutes to boot. Dont forget to boot to twrp first and flash dmverity, else you will end in bootloop.
Note: With Samsung, in case you forget to flash DMVerity, and by mistake clicked boot to system, do not worry. Switch off, or reboot to twrp and mount /system and flash. Wipe dalvik and cache, reboot. Done.
Click to expand...
Click to collapse
@vdbhb59 THANK YOU SO MUCH ,SIR.I was about to sell the phone coz TWRP could not be booted.
Finally,TWRP is booted huge thanks to you.Procedure 2 did not work(bootloop) and Procedure 3 gave me .binary error in odin(maybe i messed up in some steps).But Procedure 1 was easiest and foolproof & it booted TWRP in first try without any bootloops.
Now coming to Floss ROM(Vanilla).It was simple,clean and elegant and performance is good as well.I have not checked the battery life with this ROM but i hope it gives me more than standard battery life.Will be checking other ROMS as well-Lineage,Bliss,Turbo etc. and will be settling once i find ROM suitable for me.
Again thank you DEV for guiding me,giving me your time and most importantly contributing to this community !!
Ajayagrawal said:
@vdbhb59THANK YOU SO MUCH ,SIR.I was about to sell the phone coz TWRP could not be booted.
Finally,TWRP is booted huge thanks to you.Procedure 2 did not work(bootloop) and Procedure 3 gave me .binary error in odin(maybe i messed up in some steps).But Procedure 1 was easiest and foolproof & it booted TWRP in first try without any bootloops.
Now coming to Floss ROM(Vanilla).It was simple,clean and elegant and performance is good as well.I have not checked the battery life with this ROM but i hope it gives me more than standard battery life.Will be checking other ROMS as well-Lineage,Bliss,Turbo etc. and will be settling once i find ROM suitable for me.
Again thank you DEV for guiding me,giving me your time and most importantly contributing to this community !!
Click to expand...
Click to collapse
Anytime mate. Actually all the 3 ways I mentioned, do work. Probably, some trouble while flashing. However, no worries, I am glad you were able to boot to TWRP and flash a bloat free OS. Enjoy mate, and happy riding.
Battery life is around 1.5-2 days basis your usage. At times more, touching 3.5 days too. Again, the logic basis is always usage and background stuff.
Bliss does not boot for all, LOS does though.
BTW, which FLOSSbOxIN variant did you try? Google one will eat more battery obviously, against FLOSS one.
FLOSS(Vanilla)-[without google] review
Everything is good with the ROM but some problems i faced could be solved by following procedures:
1.If some apps does not work/launch as expected then "UNINSTALL AS SYSTEM" then REINSTALL it or INSTALL APP OF YOUR CHOICE.For eg:Vinyl player.
2.If AURORA STORE does not download apps then first give permission to Aurora Services and then rerun Store.Otherwise install GooglePlayStore manually once, update GMS and it will work.PS:You can delete PlayStore or disable if you want to.
Other than these everything is FINE.Would certainly recommend to try this ROM ?
Ajayagrawal said:
Everything is good with the ROM but some problems i faced could be solved by following procedures:
1.If some apps does not work/launch as expected then "UNINSTALL AS SYSTEM" then REINSTALL it or INSTALL APP OF YOUR CHOICE.For eg:Vinyl player.
2.If AURORA STORE does not download apps then first give permission to Aurora Services and then rerun Store.Otherwise install GooglePlayStore manually once, update GMS and it will work.PS:You one delete PlayStore or disable if wants to.
Other than these everything is FINE.Would certainly recommend to try this ROM ?
Click to expand...
Click to collapse
Thanks for this mate. Though not bugs, but the app behaviour itself. The ROM itself does not have any bugs.
October release coming soon.
Dear Dev,
Thanks for the rom.
My 3 queries
1. Getting access denied on some files like magisk, odin, and m30 database.
2. Is there any aggresive battery saver or something alike in rom which switches off all functions except calling?
3. The download link to download google version is very slow and is showing close to 17 hours to download on 150 MBps connection.
Thanks and Regards
Ashish
ashish128 said:
Dear Dev,
Thanks for the rom.
My 3 queries
1. Getting access denied on some files like magisk, odin, and m30 database. Also, you will only need the ROM, DMV erity & Magisk files anyways.
2. Is there any aggresive battery saver or something alike in rom which switches off all functions except calling?
3. The download link to download google version is very slow and is showing close to 17 hours to download on 150 MBps connection.
Thanks and Regards
Ashish
Click to expand...
Click to collapse
Hi Ashish,
Actually, AFH is having some issues. I too am unable to view files at times. Magisk and ODIN are Public files anyways. You can navigate with androidfilehost then my user, which is vdbhb59.
Battery saver is there, Ultradata by Samsung itself. You can use any 3rd party app too.
Google version link is quick here. Showing 25 minutes at 80Mbps.
Update - 20201017
Hi All,
Update released for the new version.
N.B., the update by Samsung never was for October 2020 patches, and was only a con, as they moved the apps & priv-app between the 2 folders, and added a very big BUG along with several privacy issues.
When I reached out to them with the details, I was blocked, and my account was suspended.
I have stripped away every bit and piece of bloat and BUGS (afaic). Security patch is still September.
Also, the stock camera is now replaced with 2 open variants, and much better ones. With the latest update, while trying to remove Knox, and some resources, the stock Camera breaks up fully, and the hidl does not link, rendering the app useless.
Magisk Canary 20201017
20201017 - FLOSSbOxIN_Foogle_V2_20201017
20201017 - FLOSSbOxIN_V2.2_20201017
Difference between the 2 versions
Difference between the 2 versions -->
FLOSSbOxIN_Foogle_V2_20201017 - this version is a bit smaller compared to the version 2.2 below. Version 2.2 contains a few more privacy oriented apps, and XDA app as well inbuilt, along with OSMAnd+ and UNLP. I have retained GMS Core and Maps as OSMAnd does not cover many parts of Asia and Russia.
FLOSSbOxIN_V2.2_20201017 - this version contains the following:
SMS - QKSMS
Mail - K9 & pEp - both open source. Both more reliable then stock.
Clipboard - Added function for clipboard. Probably, some apps may not work with it. Ideally, it will come as an option with pop-ups.
Maps - GMaps, OSMAnd+, UNLP
Music - Odyssey & Vinyl
Video - MPV is a great tool. VLC somehow does not integrate with Samsung while building, so have not added it yet.
SimpleTools - Gallery & Calendar alongside stock ones. Do use the open source ones, as they are fully privacy oriented. Some folks like Samsung one, but it is filth filled, and I have taken huge time out to prepare these stuffs, so do try.
Camera - OpenCamera & FreeDCam have been added. I have been using these 2 since a long time, so, do use them too.
Browser - 2 variants of Ungoogled Chromium, Bromite Webview alongside Android Webview.
Terminal - Termus. Do install the relevant addons from F-Droid/AuroraDroid and enjoy.
Downloader - Download Navi is prebuilt.
Launcher - OpenLauncher is added too, which is a better option compared to Samsung one. Use the one you prefer.
Stores - As usual F-Droid (2 variants), Aurora Store and Aurora Droid.
The ROM has been tested completely, in terms of retaining of Samsung features, and additional stuffs that I could integrate. I hope on getting Stock custom ROM soon, if the framework parts pans out, and may have inbuilt power menu options, more QS stuffs and theming, all again depending on time I can spare and framework nuisance.
It would be great if Theme option is added
vdbhb59 said:
Hi All,
Update released for the new version.
N.B., the update by Samsung never was for October 2020 patches, and was only a con, as they moved the apps & priv-app between the 2 folders, and added a very big BUG along with several privacy issues.
When I reached out to them with the details, I was blocked, and my account was suspended.
I have stripped away every bit and piece of bloat and BUGS (afaic). Security patch is still September.
Also, the stock camera is now replaced with 2 open variants, and much better ones. With the latest update, while trying to remove Knox, and some resources, the stock Camera breaks up fully, and the hidl does not link, rendering the app useless.
Magisk Canary 20201017
20201017 - FLOSSbOxIN_Foogle_V2_20201017
20201017 - FLOSSbOxIN_V2.2_20201017
Click to expand...
Click to collapse
Did they replaced system.img with super.img ? Samsumg keeps adding their security related sh**t in the name of security patches making difficult for devs to mod their Roms.
akhil093 said:
Did they replaced system.img with super.img ? Samsumg keeps adding their security related sh**t in the name of security patches making difficult for devs to mod their Roms.
Click to expand...
Click to collapse
Nope. They moved few /system/apps to /priv-app and to /vendor and made a lot of framework changes to ensure boot goes for a toss. One of the worst was how system auto cleans at a schedule. Also busybox installation fails due to /system free space being minimal.
Few more things, which I think cannot explain here.

Categories

Resources