Related
my NT is not working, if you can please click here to help me
anyway, before that - when it was working, i tried to root it by using this method:
http://forum.xda-developers.com/showthread.php?t=1354487
at debloat menu, i chose "extreme" because i want to delete all of B&N content. i just want a normal android tablet, i know i can still read books by using the NOOK app for android.
so i chose extreme mode. and the command prompt window closed right after that.
so my NT was rooted, but not successfully, it was even worse than it was before i rooted.
i open the batch file (NookandZergy.bat) to see what the command lines are to find the reason why it didn't work. and i saw this:
adb shell rm -r /system/app/Accessories.apk
Click to expand...
Click to collapse
i opened command prompt, and typed this. and i got something like "failed because the file is not exist." -> i knew the batch script was wrong in some ways. i was going to unroot and root again with the option "full debloat" (not extreme), but before i do that, i was trying to remove netflix, i wanted to type this to the command line to see what will happen.
adb shell rm -r /system/app/netflix.apk
Click to expand...
Click to collapse
but i accidentally type adb shell rm -r /system/app/, and then it removed everything in /system/app/
i got the error in the nook tablet's screen, i don't remember what the error is, but when i pressed "force close", it kept showing me that error, i tried about 20 times but still not work.
i turned off my NT, and when i boot it, it stuck at "read forever",
that's why i created this thread.
my question is: how do i do "extreme debloat"? i want to remove everything from B&N. can you please give me the correct "command lines" to do this? and how to use that "command lines"?
prepare a sdcard to boot into ClockworkMod (CWM) which is a custom recovery (replaces stock recovery). And from there flash this ROM, for extreme-debloat is easy you can modify the script just to debloat or i can make it for you. First focus in restore your system.
As i said in my last post in your other thread read my FAQ and you will find your what you need there, if you have any question me or any other user will try to help.
PS: here is post i made for a user about how to re-bloat but the thing is that i post the list of all the B&N apps for reference to you so it might be helpfull.
~ Veronica
i have a little knowledge about batch file, so i think i can edit the script
(just edit the wrong file name -> make it become correct file name)
but i don't know what files are inside the folder /system/app/
for example: the file Accessories.apk is not exist, so how should i edit the script
nooktablet said:
i have a little knowledge about batch file, so i think i can edit the script
(just edit the wrong file name -> make it become correct file name)
but i don't know what files are inside the folder /system/app/
for example: the file Accessories.apk is not exist, so how should i edit the script
Click to expand...
Click to collapse
Well you got the error probably 'cause when you ran the script it removed that file so when you typed the same command again it won't remove it because is already gone.
In the link i provided is the list of all the B&N applications that are removed in the extreme debloat option. So you basically have keep that part of the code plus the intro to get in adb shell.
In that post you will also find a link to the complete system/app folder just in case you by "playing around" with adb remove any important system app, so you can push it back.
~ Veronica
lavero.burgos said:
Well you got the error probably 'cause when you ran the script it removed that file so when you typed the same command again it won't remove it because is already gone.
In the link i provided is the list of all the B&N applications that are removed in the extreme debloat option. So you basically have keep that part of the code plus the intro to get in adb shell.
In that post you will also find a link to the complete system/app folder just in case you by "playing around" with adb remove any important system app, so you can push it back.
Click to expand...
Click to collapse
no, when i chose extreme debloat, it closed the command prompt window, before it closed, i saw something "failed...". when i typed the command again it showed "failed...", i'm sure it's exactly what it said before,
and i know after debloat, it should go back and do other command like "thank you for using" (i read the batch file). i also saw B&N apps were still on my NT, debloat didn't work because of the missing file -> the script stopped.
btw, you said i can use adb to push the apps back. so that means i can also use adb to remove apps? can i not debloat when rooting, and after root, i use adb to remove apps later? will adb work at that time?
and can i use adb to explore what files are in the /system/app/ folder? or any other program?
nooktablet said:
no, when i chose extreme debloat, it closed the command prompt window, before it closed, i saw something "failed...". when i typed the command again it showed "failed...", i'm sure it's exactly what it said before,
and i know after debloat, it should go back and do other command like "thank you for using" (i read the batch file). i also saw B&N apps were still on my NT, debloat didn't work because of the missing file -> the script stopped.
btw, you said i can use adb to push the apps back. so that means i can also use adb to remove apps? can i not debloat when rooting, and after root, i use adb to remove apps later? will adb work at that time?
and can i use adb to explore what files are in the /system/app/ folder? or any other program?
Click to expand...
Click to collapse
Yes adb works at anytime even in dockworkers (CWM) .
To know how to use adb go to my FAQ (link below in my signature) and look in the how-to's made by me section for the how to use and install adb.
"adb shell rm -r" is one of the adb commands and is used for remove files.
adb shell = is to get superuser permissions (root/su)to run advanced commands.
rm = remove
-r = recursive
~ Veronica
Sent from my Nook Tablet using xda premium
I installed the Galaxy S3 Retail Mode found in Google Play but had problems setting it up so I uninstalled it.
Now, I have a folder in /sdcard/ named RetailMode that contains photos used by the RetailMode application. But no matter what I do, I can't delete it. Can't delete any of the photos either.
I tried changing owners and changing permissions but failed. I even tried via adb shell.
Any ideas of how I can delete it?
Thanks in advance!
Beach_Head said:
I installed the Galaxy S3 Retail Mode found in Google Play but had problems setting it up so I uninstalled it.
Now, I have a folder in /sdcard/ named RetailMode that contains photos used by the RetailMode application. But no matter what I do, I can't delete it. Can't delete any of the photos either.
I tried changing owners and changing permissions but failed. I even tried via adb shell.
Any ideas of how I can delete it?
Thanks in advance!
Click to expand...
Click to collapse
Could try running a KIES update or one of the Jellybean OTA's that will wipe the internal sd card
Are you trying to do so as root? If you open a terminal (download Android Terminal from the market) and run:
Code:
su
rm -rf /sdcard/RetailMode
(upper/lower case is important!) what is the output?
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Steve_max said:
Are you trying to do so as root? If you open a terminal (download Android Terminal from the market) and run:
Code:
su
rm -rf /sdcard/RetailMode
(upper/lower case is important!) what is the output?
Click to expand...
Click to collapse
Beach_Head said:
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Click to expand...
Click to collapse
Reboot?
Tried that first. No go.
Since Retail Mode is installed and activated as a Device Administrator, I think it modified some settings. I just don't know what those settings are.
I don't want to re-flash so hopefully someone can help me with this...
kulisap said:
Reboot?
Click to expand...
Click to collapse
first you have to deactivate RetailMode as an administrator. than check if is also disabled in Accessibility also, just in case. than try to delete it. It might work.
Did that already too.
This is so frustrating...
Chaitanyapatel8880 said:
first you have to deactivate RetailMode as an administrator. than check if is also disabled in Accessibility also, just in case. than try to delete it. It might work.
Click to expand...
Click to collapse
only one choice left than... Full wipe...
There has to be another way...
Chaitanyapatel8880 said:
only one choice left than... Full wipe...
Click to expand...
Click to collapse
Had this one before but the app was smart app protector. Deleted it but it left a folder and cant delete it even in the pc. But iwas able to delete it using root explorer.
Sent from my GT-I9300 using Tapatalk 2
Beach_Head said:
Yes. Tried via ConnectBot on the phone and adb. Issued the exact same command you posted.
The reply was: rm failed for -rf, No such file or directory
I wonder what the problem is...
Click to expand...
Click to collapse
Install a BusyBox from the market (if you already have it, reinstall). if "rm" is trying to remove "-rf", it's NOT a standard "rm", which can explain your problems. Then try again.
After having followed the above: Should you get a "permission denied" as root (execute 'whoami' on the console to make sure you're root!)
then the file(s) is most probably flagged as immutable.
Executing the following will then resolve the issue: chattr -iR /sdcard/RetailMode
This is what I get when I issue that command: reading flags on /sdcard/RetailMedia: innapropriate ioctl for device
d4fseeker said:
After having followed the above: Should you get a "permission denied" as root (execute 'whoami' on the console to make sure you're root!)
then the file(s) is most probably flagged as immutable.
Executing the following will then resolve the issue: chattr -iR /sdcard/RetailMode
Click to expand...
Click to collapse
This is a common error that occurs with the Play Store sometimes after flashing ROMs without wiping data, or with an incomplete un-installation (apk corruption, etc.)
What is it?Basically, there is some app data left behind from a previous installation of the app. The Play Store sees that data when trying to install the app and throws a -24 error, because it doesn't know what to do with it.
So, how do you solve it?Simple to fix:
(I'm assuming you're rooted, chances are you are if you get this error)
- YOU'LL LOSE YOUR DATA FOR THAT APP (You would have done anyway, if it was uninstalled properly) -
1.) Using a root file manager, go to /data/data
2.) Find the package name of the app you're wanting to install
(Don't know the package name? Find the app you're wanting to install on the Play Store online and it's in the URL)
3.) Delete that folder. All of it.
4.) Try to install your app again, it should work now
5.) If you like, hit the thanks button
If you're unrooted, you can try this:
Run this in adb
Code:
adb shell rm -R -f /data/data/<packagename>
Replace <packagename> with the package name of your app (if you don't know it, see above)
If that doesn't work, a factory reset is your only option, sorry
Great write up man .
TEAM MiK
MikROMs Since 3/13/11
you just saved me Thanks a bunch!
F*ck, you're a genius man, many thanks to you !
Thx so much, you really saved me with your guide!!! :good:
I did all that but am still getting the same error with Beautiful Widgets, I just upgraded from 4.1.2 to 4.2.2, any other advice...
My device (Galaxy S4) is unrooted and i never root or install any custom rom on this device so i use the adb shell and enter the above command,
i get rm failed for /data/data/com.miui.mihome2, Permission denied
Any other suggestion or advice??Is factory reset the only option??
Hey guys, I did this, but it still isn't working. Any help?
Nexus Prime, powered by CyanogenMod and LeanKernel.
It keeps saying that no such file or directory exists.... I have my phone plugged in, debugging is on, and I open ADB in command prompt...
Thanks
It worked, Swype was the software
I upgraded my S4 Octa-core from 4.2.2 to 4.3, the Swype keyboard, the paid version, did not appear, so I tried to install it from Google Play (several times), error -24, I looked for an answer in the Swype forum, nothing, then I found this thread (why the hell I did not look for it here in the first place...? ), and this did the trick.
:victory: All this story just to say Thank you a lot man, you saved my day, stock keyboard is not bad, but Swype is awesome.
Has anyone had any luck using the command below?
Code:
adb shell rm -R -f /data/data/<packagename>
I'm unrooted and I'm trying to delete /data/data/com.whatsapp but receive this error:
Code:
rm failed for /data/data/com.whatsapp, Permission denied
Shreedhan said:
Has anyone had any luck using the command below?
Code:
adb shell rm -R -f /data/data/<packagename>
I'm unrooted and I'm trying to delete /data/data/com.whatsapp but receive this error:
Code:
rm failed for /data/data/com.whatsapp, Permission denied
Click to expand...
Click to collapse
got it too. I've a N5 and I don't want to root for the moment
StErMi said:
got it too. I've a N5 and I don't want to root for the moment
Click to expand...
Click to collapse
Im in the same situation, hopefuly answer to it somewhere
thank you, your guide is very good!
andy46 said:
Im in the same situation, hopefuly answer to it somewhere
Click to expand...
Click to collapse
Same problem here.
My guess is that we use the wrong package name..
Phunkiest said:
Same problem here.
My guess is that we use the wrong package name..
Click to expand...
Click to collapse
Yeah I am having the same problem. However, I have checked and I am pretty sure that the package name indeed is com.whatsapp. No idea what's going on.
Sigh.. suggestion removed. Doesnt work!
You need root.
For the people that got the "permission denied" error after entering the command:
You need root. Deleting data from apk files and/or installing/uninstalling apk files needs special permissions that only su (superuser) and system has. (Root IS su)
Now, reading that, you may think:
"But what about PackageManager or the Play Store that allows you to install apk files?"
Those are given permissions as system.
Correct me if I'm wrong.
t0ny0 said:
you just saved me Thanks a bunch!
Click to expand...
Click to collapse
Thanks a lot, now I can install the latest whatsapp with ART runtime in my Nexus 4
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
Code:
ln -s /vendor/etc/charger /system/etc/charger
*You can actually use adb within OS:
adb root
adb remount
adb pushor you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Dil3mm4 said:
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
*You can actually use adb within OS:
adb root
adb remount
adb push
or you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Click to expand...
Click to collapse
Error pushing on adb, Doesn't work on mate 9,will appreciate if you provide more instructions for installation.
Thank you!
The partitions are mostly to small partitioned... On honor 9 lite i used product partition instead...
Its not forever... every dirty flash on system or updating vendor security patch level will drop it. A magisk module dont work cause its mounted to late...
Darkest-Dark said:
The partitions are mostly to small partitioned... On honor 9 lite i used product partition instead...
Its not forever... every dirty flash on system or updating vendor security patch level will drop it. A magisk module dont work cause its mounted to late...
Click to expand...
Click to collapse
"Nothing lasts forever and we both know hearts can change"
-Guns 'N' Roses
Anyways, yeah, updates on vendor will wipe this "hack".
But, better than nothing
No need for this if you wipe data with stock recovery and then flash ROM + GApps, and then factory reset in stock recovery. My phone chargea fine in "offline mode."
Dil3mm4 said:
"Nothing lasts forever and we both know hearts can change"
-Guns 'N' Roses
Anyways, yeah, updates on vendor will wipe this "hack".
But, better than nothing
Click to expand...
Click to collapse
Directly modifying /system/etc/charger also seems to be effective.Could you make it into a magisk module?
Ccboxes said:
Directly modifying /system/etc/charger also seems to be effective.Could you make it into a magisk module?
Click to expand...
Click to collapse
Here's your answer. Read the thread first.
Darkest-Dark said:
A magisk module dont work cause its mounted to late...
Click to expand...
Click to collapse
Thanks for this Fix. Works awesome on Mate 10 lite with RR Official.
I installed on other way cause ADB provided to many Error Messages.
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Done and works awesome Thank you Dil3mm4 !
Dil3mm4 said:
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
Code:
ln -s /vendor/etc/charger /system/etc/charger
*You can actually use adb within OS:
adb root
adb remount
adb pushor you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Click to expand...
Click to collapse
Hey,
I did everything like destriben, but it did not work for my Mediapad M5,
it still boots up when I wanted to change while my device is powered off.
anyone to tell me how i can use this on aosp 8,1 treble rom ? i am new on huawei, treble rom ... thanks
leap_ahead said:
anyone to tell me how i can use this on aosp 8,1 treble rom ? i am new on huawei, treble rom ... thanks
Click to expand...
Click to collapse
anyone ?
leap_ahead said:
anyone ?
Click to expand...
Click to collapse
Dude, there is this new term called reading the thread, i know it's a bit hard to take in at first, but you'll get the hang of it. If you can't read, then you shouldn't be here.
This cause reboot constantly.
i've p8 lite 2017 (Pra-LX1) with GSI 8.1
crayonicle said:
Dude, there is this new term called reading the thread, i know it's a bit hard to take in at first, but you'll get the hang of it. If you can't read, then you shouldn't be here.
Click to expand...
Click to collapse
I read the instruction.but many user and me have problem with this,
so its not my false
leap_ahead said:
I read the instruction.but many user and me have problem with this,
so its not my false
Click to expand...
Click to collapse
if many users, including you, that have this problem, then all of you should read the thread, again and again until you understand
the instructions are very clear on what to do.
Everytime we flash a new system image this command has to be executed, right @Dil3mm4?
Will it work if @phhusson includes the "ln" command to the script rw-system.sh, after identifying the device as an Huawei device?
that`s good
I have already post a second variant of tutorial. Works 100% and its easy.
TUT 2:
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Reboot and done
Copkiller2010 said:
I have already post a second variant of tutorial. Works 100% and its easy.
TUT 2:
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Reboot and done
Click to expand...
Click to collapse
same things done but not working, huawei p20 lite android 10
I have this offline charging problem also in my Lenovo s5.