Related
I found a thread over in the I9000 section that may explain our problems with the Market on JH2.
http://forum.xda-developers.com/showthread.php?t=757461
This would seem to suggest that if you are running an unreleased firmware you need to replace the build.prop file from the released version in order to fix the market.
I have not tried this yet, I need to find the build.prop file from the original firmware first.
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Explorer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
I found this JF6 build.prop file in the stock system dump here. Let's see how this works:
http://forum.xda-developers.com/showthread.php?t=730226
Uploaded the stock build.prop to /system. It seems to make no difference in terms of availibility of the missing apps (only tried Fandango, but still missing). Grrrrr...need solution.
This did work for me. Thanks for the JF6 build.prop file.
This requires a rooted phone. You can brick your phone messing around with root. Not my fault...
I shut down the Market app, cleared its cache in Settings/Applications/Market (Filter select All Files to show Market app).
I added the JF6 build.prop to /system, replacing the JH2 version. I use root explorer to move the file on and off the SD internal.
Changed the permissions back to rw-r-r, using root explorer permissions. When the file is transferred back to the phone from the SD, the permissions will be rw-rwx-rx. Changed ownership back to root.root on the phone using terminal emulator:
$ su
# chown root.root /system/build.prop
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
rajendra82 said:
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
Click to expand...
Click to collapse
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
dontshakepandas said:
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
Click to expand...
Click to collapse
Working now. This is great. Now with the last issue resloved, I can keep the new firmware around. This needs a sticky, with all these weekly firmware releases from samsung-firmwares showing up.
daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Can you post the commands used to do this for users who aren't as knowledgeable.
yes. walkthrough please?
would love to get this working, I don't want to have to flash back to original.
kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
Edited post with details
kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
daverup said:
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
Click to expand...
Click to collapse
Either that, or get a full flash of the newly released Froyo firmware with GPS Fix in September (hoping and praying), and flash it forward to the new stock version. Of course, not all parts of the system are fooled. Checking Settings -> About Phone, still shows the correct JH2 information.
Nice. Seems to have worked. Funny, it didn't work until after i installed/ uninstalled a couple items.
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
staySICK said:
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
Click to expand...
Click to collapse
I am guessing that your root privilages are not working. Does you phone give you a popup when you do su in ADB shell. If so, tell the phone to allow su privlages to ADB in that popup. If you do, ADB should not complain. If that doesn't work, you have to redo your rooting procedure, as something might be messed up there.
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
staySICK said:
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
Click to expand...
Click to collapse
Probably best to ask about this issue in that thread, as more knowledgeable folks might know how to overcome this.
rajendra82 said:
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app.
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
Click to expand...
Click to collapse
This worked for me, one thing to note, when I ran the last command from Root Explorer "# chown root.root /system/build.prop" Root Explorer responded with
chown: unknown user/group root:root
But after restarting and installing/uninstalling a few apps Fandango shows up where it did not before.
Thanks.
Was running FROYO 2.2. Rooted using z4root.1.3.0 following the video instructions at Mobile.Tech.Videos.com, a great site. In the video, he talks about side loading Titanium Backup. I installed it straight from the Market without side loading. Do I need to un-install it and re-install it by side loading?
thanks
retnuh
no. you will just want sideloading enabled on your phone
retnuh said:
Was running FROYO 2.2. Rooted using z4root.1.3.0 following the video instructions at Mobile.Tech.Videos.com, a great site. In the video, he talks about side loading Titanium Backup. I installed it straight from the Market without side loading. Do I need to un-install it and re-install it by side loading?
thanks
retnuh
Click to expand...
Click to collapse
Any app loaded outside of market is considered "side loaded".
Enabling side loading is done typically by setting the appropriate option in the database file. This could be done manually at command prompt or through any of the programs available.
For TB to install apps from backup, it needs side loading to be enabled.
"For TB to install apps from backup, it needs side loading to be enabled."
Does TB automatically enable "side loading" when you select to restore apps?
retnuh said:
"For TB to install apps from backup, it needs side loading to be enabled."
Does TB automatically enable "side loading" when you select to restore apps?
Click to expand...
Click to collapse
Nope. Its a process u need to do.
Steps to enable side loading using adb
What you’ll need:
* Android SDK
* BusyBox
o If you don’t have BusyBox, go search “BusyBox” on the Android Market
o Once installed, open up the BusyBox app and follow the full installation directions to enable it
* Samsung Captivate with root
* SQL Database Manager
o We suggest trying the SQLite plugin for Firefox, you can find it here.
Process:
1. Turn on USB debugging: Settings >> Applications >> Development
2. Plug in your Samsung Captivate
3. Open up Command Prompt on your computer (Windows: start, search, type “cmd”, right click cmd, Run as Administrator)
4. Type in: cd _____PATH TO ANDROID SDK FOLDER______\tools
Example:
cd C:\Users\USERNAME\Desktop\android-sdk-windows\tools
Press ENTER
5. Type in: adb shell
Press ENTER
6. Type in: su
Press ENTER
7. Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Press ENTER
8. Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db.backup
Press ENTER
9. Type in: exit
Press ENTER
10. Type in: exit
Press ENTER
11. Type in: adb pull /sdcard/settings.db %userprofile%\desktop
Press ENTER
Leave Command Prompt open
12. Open SQLite Manager in Firefox by pressing Tools >> SQLite Manager
13. Click “Database”
14. Then click “Connect Database”
15. Navigate to “settings.db” on your Desktop
16. Expand the tables
17. Click “Secure” on the panel
18. Scroll down to ID 6, “install_non_market_apps”
19. Double click it and change “value” from 0 to 1.
20. Close SQLite Manager
21. Go back to the command prompt window, type in: adb push %userprofile%\desktop\settings.db /sdcard
Press ENTER
22. Type in: adb shell
Press ENTER
23. Type in: su
Press ENTER
24. Type in: cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings
Press ENTER
25. Type in: chmod 777 /dbdata/databases/com.android.providers.settings/settings.db
Press ENTER
26. Type in: reboot
Press ENTER
27. Disconnect your Captivate from your computer while your phone reboots.
Congratulations! You can now sideload non-market applications on your Samsung Captivate.
Excellent sideloading advice. Question, once you have sideloading enabled...do you lose this functionality if you flash a new ROM?
NISMOFO said:
Excellent sideloading advice. Question, once you have sideloading enabled...do you lose this functionality if you flash a new ROM?
Click to expand...
Click to collapse
Yes. Most i9000 based roms have this option enabled by default. If not, u would need do this anytime u flash a new rom.
diablo009 said:
Yes. Most i9000 based roms have this option enabled by default. If not, u would need do this anytime u flash a new rom.
Click to expand...
Click to collapse
Last question, can I used the AC Sideload Wonder Machine instead without messing with any code?
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
duvnjak said:
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
Click to expand...
Click to collapse
My kindle is this model: kindle fire p48wvb4
duvnjak said:
My kindle is this model: kindle fire p48wvb4
Click to expand...
Click to collapse
BUMP Please help me
duvnjak said:
bump please help me
Click to expand...
Click to collapse
**** you everyone **** youuuuu!
mine just updated to 11.3.2.6 yesterday w/o my knowledge
ugh, I'll never get to root this guy
duvnjak said:
**** you everyone **** youuuuu!
Click to expand...
Click to collapse
No need to flame. We all saw your request.
Head over to kfsowi.com which will porbably redirect you to another site where you can find a rooting guide.
Root for "11.3.2.6_user_326002520"
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite: https://github.com/secretdevwork/KindleSuite/wiki
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Calibaan said:
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite:
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Click to expand...
Click to collapse
Just says waiting for device after i select 11.3.2.5
Of course you still need an ADB connection and a fastboot cable for rooting the 7" Kindle and according to the "Waiting for device..." ADB connection is not established.
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
dry3333 said:
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
Click to expand...
Click to collapse
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
ajbiz11 said:
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
Click to expand...
Click to collapse
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
dry3333 said:
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
Click to expand...
Click to collapse
That's exactly what I'm referring to (The settings thing)
Lemme go find that command for you
---------- Post added at 06:00 AM ---------- Previous post was at 05:56 AM ----------
Wish I knew this existed when I was working on the L port
There's an app to do exactly what you need without looking up partitions
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Although if you want to go through terminal, here's a tutorial
http://ckirbach.wordpress.com/2012/11/27/how-to-remount-system-as-read-write-in-android/
Basically, you use grep to find the name of the system partition, then run the mount command to remount the partition you found in that precious step
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
dry3333 said:
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
Click to expand...
Click to collapse
The remount app should do exactly that
Try the command option and make your changes then reboot
ajbiz11 said:
The remount app should do exactly that
Try the command option and make your changes then reboot
Click to expand...
Click to collapse
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
dry3333 said:
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
Click to expand...
Click to collapse
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
ajbiz11 said:
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
Click to expand...
Click to collapse
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
You can remove it from the ViperROM zip and format ONLY system and reflash
That SHOULD work
That's like...the be all end all
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
nkk71 said:
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
Click to expand...
Click to collapse
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
dry3333 said:
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
Click to expand...
Click to collapse
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
nkk71 said:
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
Click to expand...
Click to collapse
The windows drivers don't work with recovery mode (usually)
ajbiz11 said:
The windows drivers don't work with recovery mode (usually)
Click to expand...
Click to collapse
they do for me, but sometimes (after flashing a new/different version) i have to manually select the drivers, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
dry3333 said:
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
Click to expand...
Click to collapse
sure, no problem :good: :good:
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
Just to inform you all with Marshmallow there is an app to edit the default doze settings and get better battery life
Thanks to @p0isonra1n
p0isonra1n said:
[Root] Doze Settings Editor (Android Marshmallow Only)
Requires Root
This app is a simple editor of the settings or parameters which affect the operation of Doze.
If no root is available then it will offer an ADB command that will modify the doze settings.
Because there is no root on open it will always load the default settings.
Click to expand...
Click to collapse
I had problem activating Doze new settings via app so I had to use the adb (even though my device is rooted)
here is how :
1- enable usb debugging from settings> developer options
2- There are plenty guides on how to install and run adb, you can google it or use this or this or ...
3- connect your device
4 - in terminal run
Code:
adb start-server
adb shell dumpsys deviceidle
if the values shown are same as default , then you have my problem, go to step 5. if values are what you set in the app profiles ... then you dont need to proceed
5- revoke "Doze Settings" su permissions from super su app
6- run the app , su permission will be denied and it give u a command to copy, copy it to a text file and send the file to your pc
7- open the file in your pc and copy the text
8- paste the copied line in the adb terminal and hit enter
reboot device and run the "adb shell dumpsys deviceidle" from terminal again, it should show new values.
It helps! Thanks!