Hi all,
Because I only use my Nexus tablets for reading.
Never used for mail, calendar at all.
So I always delete unnecessary files after root.
It works quite well for me in Nexus 7 2013 with Android 4.
Now I have upgraded to Nexus 9 around 1 month ago.
I found it does not work on both Android 5.1 and 6.0.
After I factory reset Nexus 9 (with Android 6.0 image from Google), I then flash TWRP 2.8.7.0. Flash SuperSU 2.52.
Install ES Files Manager.
Starting to delete the files I don't need to reduce memory usage and more space.
But can't never boot-up.
Is there anything new implemented on Android 5.11 and 6.0 to prevent user delete the files in \System\APP & \Systsem\Priv-APP
TIA
Related
I have painted myself into a corner with a Samsung Galaxy S 2. It is my
girlfriend's phone and she wanted to play Pokemon Go. The Android
version there was 4.2 (CyanogenMod) with appropriate Google Apps. It has been
working reasonably well.
Pokemon Go needs to have at least Android 4.4, so an update was due. There was
a CyanogenMod snapshot of 12.1 (Android 5.1) which was installable from within
the old CyanogenMod. I hoped that this would go through well and we did the
upgrade. After the upgrade it indeed had Android 5.1. However, the Google Apps
directly crash, especially the Trebuchet launcher. This means that one cannot
start any apps or use any Google services. Especially the Google Play Store
does not work, it shows the error message [RH-01].
I first thought that we had upgraded to Android 4.4, therefore I installed the
Open GApps nano for 4.4:
(Due to forums policy I am not allowed to hotlink or link to the images.
So this is the best I can do now.)
http ://i.imgur.com/DRHqxNx.jpg
This then (unsurprisingly) failed:
http ://i.imgur.com/qjzrDKw.jpg
At least the error message was really helpful! So then I downloaded Open
GApps nano for 5.1. This then also failed because the GApps that I
have installed together with CyanogenMod years ago were not Open GApps but some
other package:
http ://i.imgur.com/0tI6eEn.jpg
At this point I got uneasy. Her phone turned into a paperweight with a
lockscreen. Since I could not seem to move the GApps forward without flashing
the ROM again, I tried to to so without wiping the data. For this I selected
the update mechanism in Cyanogen Recovery and flashed the Android 5.1
ROM onto the device. After this I tried to install the GApps again. However,
those still fail to install. Here I would guess that the CyanogenMod 12.1
“installer” does not wipe the system partition and leaving remnants of the old
GApps package there.
Since it got late I tried to at least get back to the old state and downloaded
the CyanogenMod with Android 4.2. Trying to flash this failed as the device
type was not picked up correctly:
http ://i.imgur.com/yZ9ilM1.jpg
I do not understand this error. This (or a very similar) version of CyanogenMod
has been present on the device up til yesterday. Why doesn't that work any
more.
A friend of mine suggested to replace the Cyanogen Recovery with the
TWRP. For this I have downloaded the appropriate IMG file from Team Win.
Then using heimdall-frontend on Linux I pulled out the PIT file and put the PIT
file back with the twrp.img file onto the recovery partition. Although the
heimdall-frontend told me that I had a success, there was still the Cyanogen
Recovery.
My current guess is that this phone has hardware which does not allow for a
separate recovery partition unless there is an IsoRec kernel installed. The
CyanogenMod 12.1 should have that, but the recovery is probably the one from
the CyanogenMod 10.1 as the option to update the recovery partition was not
checked when performing the OTA upgrade.
I'm stuck and I have no idea how to get the phone into a working condition. Do
you perhaps have an idea what I could do now?
Hi,
CM12.1 Snapshot unfortunately doesn't have isorec, hence you can not install the twrp .img file.
You can flash this and it will give you isorec kernel:
https://www.androidfilehost.com/?fid=24407100847293132
You will then be able to flash TWRP here:
http://forum.xda-developers.com/devdb/project/dl/?id=17876
Once that's install, reboot back into the recovery and you should have TWRP.
Wipe /system, /cache and /dalvik cache.
Flash ROM then flash gapps, then flash isorec kernel again (because once you flash ROM, you will have overwritten the kernel).
If you can't install gapps and it says you have insufficient space, use opengapps 5.1 pico instead.
gsstudios
I managed to install the IsoRec kernel. Then flashing TWRP worked and I was able to use it. The installation of Android 5.1 has worked, but I still had issues after cleaning up /system. Installing Android 4.2 or 4.4 did not help, it kept crashing either way. 4.2 even had an infinite boot loop.
Then I ended up wiping /data and installed 5.1 and the GApps Pico package. Then everything worked, even Pokémon Go.
Thank you for your help, you saved a phone from being unusable .
I have a smiliar issue. I updated to CM 13.0 as well to newest TWRP. I wanted now to install Open Gapps Pico package but can't flash because of insufficient system space.
Do you have an idea what to do now ?
Achi92131 said:
... but can't flash because of insufficient system space.
Click to expand...
Click to collapse
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Python Guy said:
Perhaps you should open up a new thread as this one does not have the correct heading for it.
As far as I have understood, one can use odin/heimdall and some modified PIT file to repartition the device and make /system larger. I suggest you further look into the partitioning of the system and make /system larger.
Click to expand...
Click to collapse
Thanks Phyton Guy, I will do that.
Tired of failed installed GAPPS ? Different reasons and many many lost time ...
Here is alternative :
1. Install UC Browser
2. Inside , you will find : 9Apps ( the same app as PlayStore )
3. Install 9Apps
- same app as PlayStore
- every app related to Google : working fine.
*** BONUS - install Video Downloader for UC Browser - search Google for this as APK file .
you can download on your phone any video on youtube , inside UC Browser .
That's it ! It's so simple and ...No more Google domination on your Phone !
User @kokos00074 from 4pda has posted a FUSEd stock ROM.
It's based on the September 14 ROM. No root, no Xposed framework.
I will try this after testing Booroondook's latest 5.1.1. Kingo root works on the September ROM and I don't really need Xposed.
Original post here
Download the ROM here
Tried but getting black screen after boot
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
Tried but getting black screen after boot
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
what mcu do you have..
I would assume that because m00n61's sig says he is using a 'KLYDE MTCC 10inch for Suzuki Vitara' that this rom is for MTCC? So question is will it work on MTCB and if not then that could be the black screen problem.
Luv-Kush said:
Tried but getting black screen after boot
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
On my KLYDE MTCC unit the rom works (volkswagen with a EONON GA6153F)
Did you go back into recovery and did a "whipe all , clear cache" ?
First time it booted i got a black screen too , with only the top statusbar wich was non functional.
I read somwhere if going from normal to FUSE you needed to whipe everything, because the partitions are different.
After a longer then normal boot , everything needed to reinstall, i got to the launch screen. I did not try everything but the radio works , and the car info is nicer then my old one. The rest looked ok too.
Have mtcB kgl 2.83. Did wipe before and after but no go. Might try again.
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
Have mtcB kgl 2.83. Did wipe before and after but no go. Might try again.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't waste time. It will work only on MTCC.
This is for me the fastest 5.1.1 ROM to date. I guess stock ROM could have been also but I like FUSE
MTCC ONLY!
Here is my setup, step by step:
Part1. ROM install
Because this ROM includes a 5.1.1 recovery, the Rockchip Upgrade disk tool is needed.
1.Created the bootable SD
2. Also copied update.img onto a USB stick
3. Inserted both SD card and USB stick to unit
4. Started the unit
5. When prompted, removed the SD card
6. In the recovery menu, selected option 5: Update from USB and delete all
Part2. ROM cleanup
1. Set up WiFi
2. Installed Kingo root and rooted
3. Uninstalled Kingo root and Super Battery
4. Added Google account
5. Entered Play Store and downloaded Total Commander - it's my favorite file manager
6. Waited for updates to finish
7. Entered Settings->Apps, tab All and disabled all apps that I do not use, including Google Maps, Google App, PinYin IME, Gmail, Email and Exchange client
8. Started Total Commander, clicked Configure and checked the last option - root everywhere
9. Edited build.prop for DPI 160. I have a 10 inch screen and this is a good DPI. Plus, it uses less resources than 240.
10. Deleted all useless apps from /system/app and system/priv-app
11. Replaced MTC bluetooth and MTC Music with apps that can actually scale, from previous versions
12. Installed Quick Reboot from Store.
13. Rebooted
14. Installed Waze and Igo
At this point this ROM works as fast as a 4.4 ROM
Actually, it was so fast I put back Google Maps. GM is moving OK, not fast but not as annoyingly slow as before. I guess the combination GM + Xposed + Google App is way too much for these units. Luckily I have a Parrot BT borad which comes with ists own voice dialing so no real need for Google App.
pa.ko said:
Don't waste time. It will work only on MTCC.
Click to expand...
Click to collapse
m00n61 said:
This is for me the fastest 5.1.1 ROM to date. I guess stock ROM could have been also but I like FUSE
MTCC ONLY!
Here is my setup, step by step:
Part1. ROM install
Because this ROM includes a 5.1.1 recovery, the Rockchip Upgrade disk tool is needed.
1.Created the bootable SD
2. Also copied update.img onto a USB stick
3. Inserted both SD card and USB stick to unit
4. Started the unit
5. When prompted, removed the SD card
6. In the recovery menu, selected option 5: Update from USB and delete all
Part2. ROM cleanup
1. Set up WiFi
2. Installed Kingo root and rooted
3. Uninstalled Kingo root and Super Battery
4. Added Google account
5. Entered Play Store and downloaded Total Commander - it's my favorite file manager
6. Waited for updates to finish
7. Entered Settings->Apps, tab All and disabled all apps that I do not use, including Google Maps, Google App, PinYin IME, Gmail, Email and Exchange client
8. Started Total Commander, clicked Configure and checked the last option - root everywhere
9. Edited build.prop for DPI 160. I have a 10 inch screen and this is a good DPI. Plus, it uses less resources than 240.
10. Deleted all useless apps from /system/app and system/priv-app
11. Replaced MTC bluetooth and MTC Music with apps that can actually scale, from previous versions
12. Installed Quick Reboot from Store.
13. Rebooted
14. Installed Waze and Igo
At this point this ROM works as fast as a 4.4 ROM
Actually, it was so fast I put back Google Maps. GM is moving OK, not fast but not as annoyingly slow as before. I guess the combination GM + Xposed + Google App is way too much for these units. Luckily I have a Parrot BT borad which comes with ists own voice dialing so no real need for Google App.
Click to expand...
Click to collapse
If you pre-install Xposed and @dsa8310's MCU fooling addon (can remember the name of it offhand) it WILL work on MTCB as well.
By the way it WILL work as is on units running the last 2 or 3 versions of MTCB KLD6 MCUs as these can run MTCC ROMs.
typos1 said:
If you pre-install Xposed and @dsa8310's MCU fooling addon (can remember the name of it offhand) it WILL work on MTCB as well.
By the way it WILL work as is on units running the last 2 or 3 versions of MTCB KLD6 MCUs as these can run MTCC ROMs.
Click to expand...
Click to collapse
If there is no built-in xposed and exact dsa fooling module, how to preinstall xposed and mod on ROM prior to required Factory reset in recovery needed to rebuild fused partitions?
pa.ko said:
If there is no built-in xposed and exact dsa fooling module, how to preinstall xposed and mod on ROM prior to required Factory reset in recovery needed to rebuild fused partitions?
Click to expand...
Click to collapse
Doh, soz, I m guilty of not reading the first post correctly and assuming that it was @m00n61 who built the ROM and therefore could also inject Xposed, when actually he just found it on 4pda.ru
But theres no reason why Xposed and root cant added by someone on their pc before its used on a unit.
I left the rom unrooted , is it normal that when i go to settings , apps , i cannot disable the gallery app ?
What is special about the gallery app ?
bk227865 said:
I left the rom unrooted , is it normal that when i go to settings , apps , i cannot disable the gallery app ?
What is special about the gallery app ?
Click to expand...
Click to collapse
Its normal behaviour on Android - the gallery app is a system app and can only be removed if youre rooted.
Hello everyone, the other day I decided, after 3 years of stock ROM (5.1.1), to change ROM on my Note 3 Neo (N7505). I installed TWRP, I downloaded a build of Lineage 14.1 and installed it. But stupidly I didn't read the list of things that don't work, such as the camera and the dial app. So I decided to return temporarily to the stock ROM. Later I found a Cyanogen build compatible with my N7505 without any particular problems, so I installed it. No problems here. But when i had a glance at the "memory" section of the settings, I found that the space occupied by the system was equal to 4.6 GB. A little unusual. Using the ES file manager I found two folders, a /system that weighs 400 mega (probably the one where is Cyanogen) and a /sys with 4 GB (with inside 200.000 files and 60.000 subfolders!). I think the problem is the folder /sys, probably when I changed rom I didn't wiped something, and there are still the files of the Lineage and the stock, stored in this folder. Now I have 4 gigabytes of useless files, and what I would like to do is delete everything and then install the cyanogen. But among the TWRP wipes there isn't /sys, only /system; with the root permissions I can't delete it, and I also tried with ADB, but it's a mess. It's like 4 days that I look on the net how to fix it, but I didn't find anything that could help me. I thought about making a cut of the / sys files and past 'em in / system and then wipe everything from TWRP, but I don't know how ADB works and I wouldn't mess it up. If anyone has better ideas I'll really appreciate it, thank you very much in advance.
Also, sorry for bad English but is not my native language.
Hello all,
I have a Samsung S8 phone running stock Android 8.0 no root or recovery or whatsoever..
I would like to save a backup of my Whatsapp key in order to save my database along with it on my PC
I have seen there is a tool that can extract the key and DB from an Android phone but it doesn't work on Android 8, I think the problem is linked to the fact that you need whatsapp 2.11 installed (I have 2.19 but as far as I understand only up to version 2.11 allowed adb backup) and on android 7+ you cannot downgrade an app..
I tried to install whatsapp's previous version copying its apk on the phone without success, using MyPhone Explorer and Adb but it doesn't install..
If I use an old phone with android 4+ it works without problems..
Is there a way to work around this problem?
Thanks
I bought my Moto G Power with Android 10 and after I rooted with Magisk. I can't remember if the duplicate files were there from the beginning but I upgraded to Android 11 and when I saw there was an issue with Titanium Backup getting stuck on Media Storage and the possibility of fast battery drain, I decided to downgrade to Android 10. I did this by tricking Motorola Rescue Assistant. I replaced the Android 11 files with Android 10 but kept the download folder labelled Android 11.
That is when I started noticing the duplicate files in Titanium Backup. I thought they somehow accumulated from me going back and forth between the 2'firmwares but maybe they are supposed to be there it just seems odd. I then upgraded to 11 again as there was a working recovery for it and I thought if I could completly format the phone and start fresh, maybe it would solve the problem. I soon realized that I can only really hard reset the phone through recovery I somehow remember years ago being able to wipe the phone of its firmware but I am maybe mistaken.
I have attached screenshots. Can somebody let me know if they are supposed to be there or not and if not, is there any way I can wipe my phone so that there is no firmware on it and start completely fresh?
Thank you.
I've got a similar situation on my moto G play after upgrading to Android 11. But those aren't duplicates of the same file, they are just labeled the same. If I'm not mistaken those are the Moto Styles overlays, each corresponding to color, font typeface, and icon shape. At least on my g play that is the case.
Great! Thanks!