Hi! I played with my phone, and used Lucky Patcher to delete my odex files and now I can't use my phone. When I want to sideload an apk I get an error: Package corrupted. I can't download anything using chrome, and if I do a screenshot it says that can't take screenshot due to limited storage. I tried to restore a backup made with TWRP before using Lucky Patcher and nothing!
Fixed! I did a factory reset and everything is good now.
Related
I have modified several of the updates to be installed in ClockworkMod Recovery so that it will not overwrite CWM Recovery and should also preserve root. I still recommend protecting root using Voodoo OTA Rootkeeper in case something goes wrong and it is always a good idea to make a nandroid backup in ClockworkMod Recovery before installing any update. Also after updating Titanium backup said that my su had the wrong permission and it wanted to correct it (I allowed it to fix it). I am not sure why this happened as I thought I set the permissions properly in the update but go ahead and run Titanium after updating and let it fix it for you if there is a problem. These updates will still check all of your system apps so you need to restore them (copying and pasting them back into the /system/app folder and setting the proper permissions with Root Explorer is one of the easiest ways to do this). You can also make your own modifications to the update and remove the checks if you like (some people have done this with no problems but one guy reported that android wouldn't boot after updating with no checks so I leave it up to you to decide for yourself). I posted instructions for modifying the update here. The changes I made to the update were to remove the Indigo check (because it was giving me an error) commented out the lines that delete the current recovery and install the new recovery, removed the line that deletes Superuser.apk, added an su file to the update so that it reinstalls su after deleting it, and finally added lines to symlink and set permissions for the su file.
Install instructions:
Protect root with Voodoo OTA Rootkeeper (just in case)
Copy the proper update.zip to your external sdcard (if you are US or WE you must install 086 before 089)
Make sure your battery is well charged (having your battery die during the update would be very bad)
Turn off TpT and boot into recovery by turning on and repeatedly pressing the volume up key
Wipe cache partition
Make a nandroid backup (not necessary but highly recommended)
Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
Let the install run and then choose reboot system now in the CWR main menu
The first boot will take a long time, don't worry this is normal (if it takes more than 30min you may want to hold power to turn off and reboot again)
ThinkPadTablet_A310_02_0037_0076_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
ThinkPadTablet_A310_02_0039_0086_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0089_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0087_UK_CWR.zip
ThinkPadTablet_A310_02_0039_0089_ROW_CWR.zip
ThinkPadTablet_A310_02_0039_0089_SC_CWR.zip
ThinkPadTablet_A310_02_0039_0090_JP_CWR.zip
Flash at your own risk! I am not responsible if this totally bricks your tablet, breaks your root, or creates any other problems for you! Make sure that you install the correct version for your region.
Worked great for me. Thanks!
Is it also necessary to temporarily unroot before applying the update? Thanks again.
I don't believe I needed to do a tempory un-root to apply the updates. I just followed the instructions. I did have to power down during the first installation since it stayed in .. rebooting.. mode for 20 to 25 minutes. After powering down and rebooting, _86 was installed.
I did have to re-install Busybox to get LUKS Manager to work after the installation of 86 and 89.
Thanks, but I got in trouble with OTA2 by not unrooting first, and the OP is the one who helped me with it. I need to make sure before I make a move.
It should not matter, the update deletes and reinstalls su.
Thank you. I'll give it a try later today.
great thanks.
a sticky would be great
I just applied OTA 2.5, now my market consistently force crashes. Anybody else having this issue?
try to download and install new "Play Store"
mandrsn1 said:
I just applied OTA 2.5, now my market consistently force crashes. Anybody else having this issue?
Click to expand...
Click to collapse
My market is working fine on OTA 2.5. Maybe you have two versions of the same app installed after updating (for example if you removed FlexT9 in system and installed the full FlexT9 keyboard from the market and then restored the system app to update). It could also be a problem due to the change over to the new Play Store as quyTam suggested. If all else fails a factory reset would likely fix the problem but then you will have to set everything up again.
jhankinson said:
My market is working fine on OTA 2.5. Maybe you have two versions of the same app installed after updating (for example if you removed FlexT9 in system and installed the full FlexT9 keyboard from the market and then restored the system app to update). It could also be a problem due to the change over to the new Play Store as quyTam suggested. If all else fails a factory reset would likely fix the problem but then you will have to set everything up again.
Click to expand...
Click to collapse
Nope, i unfroze apps before i updates and made sure there were no replaced system apps when I installed.
I have tried stock market, 3.4.4 (honeycomb 3.2 market) and 3.4.6 (Play store) and they all force crash. Sounds like a factory reset may be needed.
mandrsn1 said:
Nope, i unfroze apps before i updates and made sure there were no replaced system apps when I installed.
I have tried stock market, 3.4.4 (honeycomb 3.2 market) and 3.4.6 (Play store) and they all force crash. Sounds like a factory reset may be needed.
Click to expand...
Click to collapse
Something else must be messed up. I factory restored and still am having issues.
I got an error message after trying to install file from SD Card. It said
"Installing: /sdcard/ThinkPadTablet_A310_02_0039_0089_ROW_CWR.zip
Finding update package...
Opening update package...
Installing update...
Verifying Current system...
assert failed: apply_patch_check("/system/app/FlexT9ChineseIME.apk", "222668fd99a68916eb4d6784c3795801ea0698bd" , "8c4feb3af89ec0ff3791c0d5acf30bad168b4600")
E:Error in /sdcard/ThinkPadTablet_A310_02_0039_009_ROW_CWR.zip
(Status 7)
Installation aborted.
I'm currently using 0074ROW
Could someone advise how to fix this?
Put back the system file indicated - FlexT9ChineseIME.apk.
toenail_flicker said:
Put back the system file indicated - FlexT9ChineseIME.apk.
Click to expand...
Click to collapse
Thanks but where can I found it?
That depends on what country you're from. There's a couple of system dumps here on xda.
same here can't ota update coz i deleted some of the apps so can anyone know where can find the dump for the 0074 row dump? or could someone please provide the dump here?
thx for the help!!!
You can also go to the Lenovo download page to find your previous download file, unzip it, and find the file to put back.
toenail_flicker said:
You can also go to the Lenovo download page to find your previous download file, unzip it, and find the file to put back.
Click to expand...
Click to collapse
thx for the help. just asking are you referring to this:
download.lenovo.com/slates/think/tablet1
the worse thing is i deleted the drmprovider.apk and the odex as well which i couldn't see that apps in those zip.
so could anyone help here?
thx!!!
Hi,
I rooted my N4 recently and since then it seems no apps can write the SDCard, I can still download files and install apps but Line can not download stickers, Whatsapp can not download attachments and the final clue that pointed me in the right direction the camera can not store the pictures I take.
After some deubugging I found that camera is trying to write to /storage/legacy/0/DCIM but I have not that pseudo symlink ( I only have /storage/legacy/DCIM )
I am not sure how this happened and how ti fix it, what I did is a adb pull /sdcard to backup all my data before unlocking,
then used Wug's Nexus Root Toolkit v1.6.2 to back up apps and apps data,
unlocked,
rooted,
installed TWRP,
restored everything (including adb push /sdcard)
and finally installed Franco's kernel
I am not sure if the problem is with the adb push or what but I really want to fix this, I will provide logs or test whatever you want, I am open to reinstall everything, but having an unusable SD for apps is a big problem.
Thanks in advance
If someone could at least point me in the right direction it will be great
I would recommend formatting your SD in recovery.
Sent from my Nexus 4 using xda premium
I was trying to allow universal writing to external SD card. I tried doing as I have done before on other Android devices, modifying platform.xml. I added in <group gid=”media_rw” /> to WRITE_EXTERNAL_STORAGE. I also made sure the permissions were RW-R--R--. Of course I made a backup just in case. When I rebooted, internal & external sd card are not visible. In es file explorer I can only browser \device. Any app not installed on root drive will not work. (such as droid mote & wireless controller) controller works when plugged in.
I booted into twrp and replaced the original file but no dice. I even removed a file (can't remember which file, but it started with a letter P) that was said to be altered with changes to platform.xml which would be recreated. I also tried "fix permissions" in twrp.
Where I'm at now is i downloaded the OS 1.2 images from nvidia. I did an adb backup of I assume only what was it device root (familiar screen from helium!).
Is it possible to just flash the system image to fix this? Or do I need to factory reset & re root?
Hi
I understand what you tried to do, to just give a small tip the program FOLDERMOUNT (gplaystore) will fix the inability to write to sd for your, when you start it for the first time after rooting your shield.
This works on all my shield devices (Portable & Tablet), on the shield tv you will have to sideload it possibly
I guess the best thing to do is go back tot the original release 1.2 from nvidia and reroot, sideload foldermount and see if it works.
Many alternative images for the shield have great new features but unfortunately don't support the wireless controllor protocol used by nvidia yet , they haven't release the drivers either.
Hope this helps & enjoy your Shield Box!
greetings
Jostiband
JohnHenryIron said:
1) I was trying to allow universal writing to external SD card. I tried doing as I have done before on other Android devices, modifying platform.xml. I added into WRITE_EXTERNAL_STORAGE. I also made sure the permissions were RW-R--R--.
2) Of course I made a backup just in case. When I rebooted, internal & external sd card are not visible. In es file explorer I can only browser \device.
3) Any app not installed on root drive will not work. (such as droid mote & wireless controller) controller works when plugged in.
4) I booted into twrp and replaced the original file but no dice. I even removed a file (can't remember which file, but it started with a letter P) that was said to be altered with changes to platform.xml which would be recreated. I also tried "fix permissions" in twrp.
Where I'm at now is i downloaded the OS 1.2 images from nvidia. I did an adb backup of I assume only what was it device root (familiar screen from helium!).
Is it possible to just flash the system image to fix this? Or do I need to factory reset & re root?
Click to expand...
Click to collapse
Thanks. I'll give it a shot. I should have made a nandroid before editing the file. Unfortunately, I thought making a backup of the file itself would be enough. I had just finished setting up all my emulators, mapping controls to my ps3 controllers & changing settings. I should have done this first.
I went ahead and restored my ShieldTV by unzipping the OS package I downloaded from Nvidia into my adb folder and running the included batch file
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
(I first flashed system & boot but still was no good)
As soon as I got SuperSU up & running I sideloaded NextApp SDfix
http://forum.xda-developers.com/showthread.php?t=2684188
That seemed to have done the trick. SD is now unrestricted.
The only issue I have now is whenever I boot, leanback launcher crashes: "leanback launcher has stopped working". It done it a few other times, but it seems to be random. Was restoring the way I did the best way to completely wipe the system or could it be something left behind that could be causing issues?
[Update] I don't know what has corrected the force close issue, but I have not had any more crashes. Everything's working smooth.
i just rooted, download SDFIX: kitkat writable sd on my phone, backed up the apk, installed on the shield and used that.
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Edit: found out I'm unable to uninstall system apps for some reason. So the issue isn't space related.
Toilet Clauger said:
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Click to expand...
Click to collapse
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Click to expand...
Click to collapse
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Toilet Clauger said:
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Click to expand...
Click to collapse
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
toolhas4degrees said:
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
Click to expand...
Click to collapse
I was actually able to find the issue. Space was the issue. I guess there's a space buffer needed from what a file explorer says is left and what's actually left. I uninstalled a couple system apps I disable anyway and was able to insert files/apps into system again.
I made space easy I have the new OnePlus camera apk 125mb the old one is 67mb
I have the global version of OnePlus 6t. Ever since I rooted my device, I used fastboot to boot the twrp .img then, I flashed the newest OTA, then twrp, then Magisk apk. I can no longer Download anything from Chrome or The Magisk app. I also cannot create any new folders in my internal storage when using either of the default file manager apps. They also do not show any folders in the internal storage. It's like I no longer have write permissions. I would post a screen shot but it also says I cannot save screenshots when I try.
I am able to download off the play store and got a file manager with root access, and that's the only way I can see or create folders, but I can't access those folders anywhere except there.
Please help, I'm new to all of this and am beginning to think I am in over my head as far as rooting a device goes.
Did you format data then do a factory reset in twrp before you flashed the full ota?
I suggest formatting data in twrp, not data wipe but format where it makes you type in "yes" and swipe to proceed. Just remember that wipes all your pictures and everything. You can also do format data from your PC with fastboot just do: sudo fastboot -w
Then reboot system. You should be good then.