minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)
This is great. Will give this a shot today or tomorrow. Thanks!
themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.
I still get notification prompts for ota.
themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way
Hello, brand new Moto X user here. Android 4.2.2, XT1058 version.
I rooted my phone as soon as I got it (without unlocking the bootloader), and it worked right away. I read the part about needing to use MotoWpnNoMo later, to kill the write protection, but I didn't do it.
¿Why? Because after root, I typed 'adb shell getprop ro.boot.write_protect', to check if I had access, and it gave me a 0. So I thought the rooting process had indeed killed the protection.
So I started doing my usual 'Integrate update into system' with Link2SD, so I wouldn't have to update 100 apps when I did a factory reset.
The first time I tried this, Link2SD said it worked OK. When I tried with a second app, I got a 'write protect' error.
I rebooted my phone, and again it worked with the first app, and not the second. I did it about 3 or 4 more times.
Then, I start noticing the apps that I integrated are not working. Youtube, Hangouts and Chrome had a generic Android robot icon, that said 'app is not installed' when I clicked on it.
I went to Google Play and found all 3 of them, Installed them again, and they worked.
But here's my problem: I can't remember which other apps I integrated wrong. I'm not sure they showed up in the App Drawer to begin with.
I later did the whole MotoWpNoMo thing, and killed the write protection. Integrating apps works OK now.
My question is: If I do a factory reset, will those 'disappeared' apps come back? Or have I lost them forever?
I have a Samsung Galaxy J1, runnning Android 4.4.4 and TWRP 2.7.1. My phone has only 2.1GB of usable storage space.
As I installed using a zip file, SuperSU was a system app and cannot be moved to my SD card. This app was taking up 300ish MB on my system, and it came to the point where I couldn't even send a voice note on WhatsApp any more because of the little free space I had. When I saw that SuperSU was taking this much space, I tapped the [Uninstall Updates] button, finished uninstalling and my phone froze. It stayed frozen for about 3 minutes, when it started getting really hot. Then I removed the battery.
Upon restarting, the phone was very slow and unresponsive. I figured it could be a memory leak caused by some app, so I ignored it. However, my phone started locking up completely. I restarted again, opened SuperSU and disabled root since I thought that could be the cause of the slowness. It became more responsive, however apps like FolderMount and Kernel Aduitor stopped working. So I tried to fix it.
I went and flashed the latest SuperSU zip, but that did not fix the problem. I updated the binary from within the app, but that didn't work either. I selected [Cleanup for permanent unroot] inside the app, restarted, reflashed the zip and tried again. Nada. Finally, I went and dirty flashed my phone's stock firmware through Odin, reflashed TWRP, then SuperSU and that still didn't work.
I then hit up adb shell on my computer and entered the terminal, doing some /system exploration. I went to /system/xbin and noticed the lack of a su file. I then grabbed the file from my properly rooted Galaxy Tab 3 running CM 13 and SuperSU, then I pushed the file to /system/xbin using my recovery and set the persmissions to 777. I then enabled Superuser from within SuperSU, ran the su command in adb shell and got a "not executable: magic 7F45" error. I tried disabling and reenabling root in SuperSU, and then the system just hanged at the su command.
So can someone guide me into fixing my root? Lots of functions such as a custom LMK curve (for browsing Reddit using Sync and listening to music using Poweramp at the same time [having low RAM is a struggle]) and using FolderMount (to mount my massive WhatsApp folder onto my memory card to save on storage space) depend on it.
Hello World,
before I explain my problem, I am most humbly asking for one small favour:
Please(!!) nobody give me any advice along the line of: Just do a factory reset and start from scratch
I've got almost a thousand apps installed on my system and I'm in no mood to even try to reconfigure it all over again.
Some time ago I installed the latest beta of Cyanogenmod on my Samsung Galaxy Note Tablet SM-P900.
After some time I encountered so many quirks with it, that I decided to flash back to the latest stable build 12.1-20151029 (Android v5.1.1).
Since I was always able to upgrade w/o wiping data, I did the same here, but right after the downgrade the system started misbehaving.
Matter of fact, I could only boot through to the desktop, once I had removed some google.* related dirs from the data/data location. Right afterwards I reinstalled the affected apps from backup and that fixed that.
Unfortunately during the proces of peeking and poking in data/data I messed up some ownership/permission settings.
I also managed to fix those via an old backup (via: chmod/chown --reference), *but* now I am getting a popup message telling me:
"There is something wrong with your data partition..." everytime I reboot the system.
Afterwards I can work just fine with the tablet, but every 3rd or 4th day it suddenly reboots - then being stable again for another couple of days.
If I could only find out what fault this messages refers to, I could fix it manually - but I couldn't find anything useful by reviewing the logcat info.
Never had any issues with Magisk on my S8+.
However I flashed toe v17.1 Magisk zip today using TWRP and it booted just fine (first time).
Then I used a service disable app to disable my Samsung Location service (like I did a million times before for Pokémon GO) and rebooted.
It stuck on the Samsung logo.
After a force reboot it booted straight to the system (to my surprise). However the system isn't really usable at that point as an annoying message keeps popping up all the time telling me, that I have to restart my phone to use my "new" (it isn't new) SIM card.
No matter how often I reboot, the message keeps popping up.
Any ideas?
I have the same problem with my RN4. Had to downgrade to 16 from 17!
Hope they fix it soon!
Edit: i completely uninstalled magisk and reinstalled it through twrp. And that fixed the problem for 17.1!
I should have tried it. Instead I installed the V17.1 through TWRP multiple times as it worked very often on the first reboot after doing that.
However at least at every second reboot that annoying popup appeared again.
I ended up giving up and taking the "opportunity" to set up my phone from scratch. I made a backup of the most important apps with Titanium Backup and flashed the newest stock firmware from Samsung (now I have Oreo) then I flashed TWRP again and installed Magisk from there. Now my phone is working again.
Unfortunately I forgot to backup my media files of WhatsApp (only the app data with Titanium) and restored it from there instead of letting it restore from Google Drive.
Now I have my chat history but all my media files (images/videos/voicemails) are gone for good and since I noticed that too late, WhatsApp did backup that "new state" to GoogleDrive so all media files got deleted from there as well and now I'm doomed.