Database Users

Cannot for the life of me get system r/w permissions

I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.

You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.

Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.

CM7 / AOSP Boot sound [working]

Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
Credit to barnacles10 and lithid-cm
*NOTE: Anything in brackets is either description of what is happening or an action you need to perform; don't type in anything in brackets*
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Apparently some people had issues with the first link, so I uploaded it again. Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Alternate method:
For those that don't like using the terminal emulator, you can do it via adb:
navigate to your adb folder via commanda prompt, then issue the following commands:
adb remount
adb shell
cd /sdcard
ls [will list files, you should see bootsnd.sh]
sh bootsnd.sh
Like in the emulator, you will be returned with a # sign. Then place the audio file in the folder I specified. Just decided like posting an alt method. Enjoy.

Nice post I'm going to do this now!
Sent from my PC36100 using XDA Premium App

Well I do hope you enjoy it.

Excellent, trying this now!
Edit: Works great on CM7 7.0.2.1!!! Nice find!
.........at 8 am today someone poisons the coffee....do not drink the coffee. More instructions will follow.
Cordially,
Future Dwight

teh roxxorz said:
Well I do hope you enjoy it.
Click to expand...
Click to collapse
And I must say it has worked flawlessly.. I maintain a small network off friends rooted phones and this is one off the "hit" fixed so far everybody loves it. Thanks again for the help with this the other day..
Sent from my PC36100 using XDA Premium App

I really want this.. I just found this thread after searching and searching for an answer.. I just about gave up but I think I still my have a problem. My hboot version is 2.10 and dont think this will allow me to use pushboot.... any ideas

opps.. guess I should have read the whole post..... I am bout to give it a try

frikin awesome thanks a bunch.. I dont know what that little file did but it worked .. wooohoooooooooooo

teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse

@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...

youdoofus said:
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse
The file should save as a .sh. If it doesn't show up as .sh when you are saving it, save it as all file types, and that should work as well.
If you double click it, it should prompt you with the "no program found...do you want to...blah blah" And it should show bootsound.sh
Click to expand...
Click to collapse

gReeNzZz said:
@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...
Click to expand...
Click to collapse
Well AOSP roms [i.e CM7] wasn't designed to have boot souns, so it probably won't be integrated [my speculation].
And if you ever want to "thank" anyone, at the bottom of every post, you'll see a "thanks" button, and then you have "thanked" them, and the user can see it.

Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App

chefrjd33 said:
Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Well if its a zip file. Extract the file, it should be an mp3 inside. Rename that file to android_auido [should have .mp3 extension already].

It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App

chefrjd33 said:
It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Where are you opening the file that its making it open from rom manager?

teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Click to expand...
Click to collapse
Ok just tried this without using adb as I think its million times better to just use a ftp app and get this done in seconds. But I dont know why its not working. I check the name to make sure I wasnt putting in the .mp3 twice and for some reason it wont play the file. And its in MP3 format.

I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO

Or tell me what steps udid do.
Kings GB Destroyed EVO

cmurray77 said:
I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO
Click to expand...
Click to collapse
Really well I actually tried the audio from the driod just to see but I try a couple more. Yeah the problem with using those they are more timely and both USB ports are beyond ****ed right lol. But I should just be able to do this over FTP. Was there anything similar to the ones that worked to the ones that did.

Free 50 GB Box Account HELP

I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?

yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?

bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.

bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.

ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.

This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.

be careful, backup buid.prop and restore it after creating Box account.

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse

I am having no luck finding a way to get root access from a computer.

deleted post
user error

The tumbleweeds are big around here

There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/

But is there an app to copy my file over from my computer?

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug

I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.

yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.

jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...

its taking forever to install SDK

This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.

yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?

[Q] How to delete PUSHED files from "/sdcard/"

Hello, so I've done some light searching, but can't seem to find the answer to my question.
I've just finished installing a custom ROM to my Nexus 4, and in doing so, I pushed a few files to my phone via ADB
(ADB PUSH FILENAME.ZIP /SDCARD/FILENAME.ZIP) and am now wondering how to REMOVE these files that I no longer need.
When I am in recovery and select "install from zip" obviously, I am able to see the files, as that is how I installed them. However!
I can not view them via MTP (not that I've ever had much success with MTP) nor using ASTRO or File Manager.
Where are these files truly located and how can I delete them?
Ideally, I would like to learn how to view this directory, but would be happy enough just to know which ADB commands would list these files
and which commands will allow me to remove them one by one.
Thank you
*ISSUE RESOLVED*
After looking within CWM as to where sdcard contents were being sourced "/data/media"
I rebooted the phone, and attempted to locate this directory within File Manager with no luck....at which point, I realized that File Manager didn't have root privileges.
After giving root privileges to File Manager, I was able to navigate to /data/media and locate the pushed files and remove them.

If I were you I'd use adb shell and then the Linux remove command
That means:
Code:
adb shell
cd /sdcard/
rm - r FILENAME.zip
That's it, hope it works
Sent from my Nexus 4 running Android 4.3

Thank you for your reply! The only issue I have with that method, is not necessarily knowing the file names...
I would assume there are quite a few files within this directory, given that this isn't the first ROM I've installed.
I'd really like to be able to view the contents of the true location. Does anyone happen to know where it is on the Nexus 4 that CWM
is looking for the zip files? I would assume that this would tell where the files are located, and perhaps I could point an explorer to it.
What was puzzling was that searching the entire phone for "gapps" in ASTRO yielded no results.... as I am certain more than one of the zips I have pushed contain this within their file name.

losballatopg said:
Thank you for your reply! The only issue I have with that method, is not necessarily knowing the file names...
I would assume there are quite a few files within this directory, given that this isn't the first ROM I've installed.
I'd really like to be able to view the contents of the true location. Does anyone happen to know where it is on the Nexus 4 that CWM
is looking for the zip files? I would assume that this would tell where the files are located, and perhaps I could point an explorer to it.
What was puzzling was that searching the entire phone for "gapps" in ASTRO yielded no results.... as I am certain more than one of the zips I have pushed contain this within their file name.
Click to expand...
Click to collapse
adb shell
cd /sdacrd/
ls
then u see the names
or to delete all zips(i dont know if this will work, i only tried with del *.exe on Windows)
adb shell
cd /sdcard/
rm - r *.zip

use a file explorer, go into your sd card storage, find the files, long press and delete.

simms22 said:
use a file explorer, go into your sd card storage, find the files, long press and delete.
Click to expand...
Click to collapse
Yeah....so perhaps you didn't read either of my posts.....the files don't show up in any file explorer that I've tried. That was basically the main issue...

opssemnik said:
adb shell
cd /sdacrd/
ls
then u see the names
or to delete all zips(i dont know if this will work, i only tried with del *.exe on Windows)
adb shell
cd /sdcard/
rm - r *.zip
Click to expand...
Click to collapse
Once I have entered the /sdcard/ directory, running "ls" shows nothing..... :-/
I just don't know how this topic hasn't been discussed more often.....
What does everyone else do? Just keep filling that directory every time they push something and leaving it until the next wipe?

losballatopg said:
Yeah....so perhaps you didn't read either of my posts.....the files don't show up in any file explorer that I've tried. That was basically the main issue...
Click to expand...
Click to collapse
if you successfully pushed the files to /sdcard/, then thats where they should be, they cant be anywhere else. make sure that you arent looking in/sdcard/download/. what file explorer are you using btw? use a root file explorer(like root explorer), not a regular file explorer.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
losballatopg said:
Once I have entered the /sdcard/ directory, running "ls" shows nothing..... :-/
I just don't know how this topic hasn't been discussed more often.....
What does everyone else do? Just keep filling that directory every time they push something and leaving it until the next wipe?
Click to expand...
Click to collapse
because no one else has an issue with this. im guessing its the file explorer that you chosen to use or user error somewhere.

simms22 said:
if you successfully pushed the files to /sdcard/, then thats where they should be, they cant be anywhere else. make sure that you arent looking in/sdcard/download/. what file explorer are you using btw?
Click to expand...
Click to collapse
Yes, this would seem to be the logical answer wouldn't it? This isn't my first "Android Rodeo"...however, as Android and handsets have developed, directories are no longer always as they seem (or titled)
Luckily I was able to resolve my issues.....
After looking within CWM as to where sdcard contents were being sourced "/data/media"
I rebooted the phone, and attempted to locate this directory within File Manager with no luck....at which point, I realized that File Manager didn't have root privileges.
After giving root privileges to File Manager, I was able to navigate to /data/media and locate the pushed files and remove them.
Thank you for your efforts, and hopefully this helps someone else down the road who finds themselves in the same situation.

simms22 said:
if you successfully pushed the files to /sdcard/, then thats where they should be, they cant be anywhere else. make sure that you arent looking in/sdcard/download/. what file explorer are you using btw? use a root file explorer(like root explorer), not a regular file explorer.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
because no one else has an issue with this. im guessing its the file explorer that you chosen to use or user error somewhere.
Click to expand...
Click to collapse
I tried Solid Explorer, ASTRO File Manager, and the File Manager provided with CM 10.2
Were you to have simply informed me that files pushed to "/sdcard/" were located at "/data/media" my issue would have been resolved through the logic I ended up using.
Something tells me you prefer the blame game
Thanks anyway

losballatopg said:
I tried Solid Explorer, ASTRO File Manager, and the File Manager provided with CM 10.2
Were you to have simply informed me that files pushed to "/sdcard/" were located at "/data/media" my issue would have been resolved through the logic I ended up using.
Something tells me you prefer the blame game
Thanks anyway
Click to expand...
Click to collapse
first off, i dont use cwm, i use twrp recovery. all my files get pushed to wherever i push them, period.
if you look at my thanks at least, you can see that i dont prefer the blame game, but i do prefer helping people. and personally, that hurts my feelings, thanks

simms22 said:
first off, i dont use cwm, i use twrp recovery. all my files get pushed to wherever i push them, period.
if you look at my thanks at least, you can see that i dont prefer the blame game, but i do prefer helping people. and personally, that hurts my feelings, thanks
Click to expand...
Click to collapse
Well, then it seems that we have both learned something today. Glad we could be such a great!
No hard feelings

losballatopg said:
Well, then it seems that we have both learned something today. Glad we could be such a great!
No hard feelings
Click to expand...
Click to collapse
both learned something? im lost, what did i learn
oh nevermind. enjoy.

simms22 said:
both learned something? im lost, what did i learn
Click to expand...
Click to collapse
Well...you didn't seem to have prior knowledge of the fact that pushing to "/sdcard/" places files in the "/data/media" directory
(at least for when pushing within CWM Recovery on a Nexus 4, and from what I've read, all other recent versions of Android with no external SD)
Unless you're choosing to ignore this information...I'd call it something learned.

losballatopg said:
Well...you didn't seem to have prior knowledge of the fact that pushing to "/sdcard/" places files in the "/data/media" directory
(at least for when pushing within CWM Recovery on a Nexus 4, and from what I've read, all other recent versions of Android with no external SD)
Unless you're choosing to ignore this information...I'd call it something learned.
Click to expand...
Click to collapse
not while using twrp. but, point taken. i did learn something today, i learned of another reason why not to use cwm recovery

simms22 said:
not while using twrp. but, point taken. i did learn something today, i learned of another reason why not to use cwm recovery
Click to expand...
Click to collapse
I concur.

wow just read this thread and I must admit simms22 is quite helpful and even in some instances more helpful than he needs to be... LOL
now if pushing a file to /sdcard sends it to data/media then I truly agree as well CWM is a problem. I must admit though when using CWM I have never had that issue. Usually pushing a file to whatever folder I choose it normally goes there.
Also as a personal preference Root Explorer is a hell of a file manager..Jus Sayin'

Thinking of selling HTC Desire 816

hi all, i am Thinking to sale Htc desire 816 from yesterday because i am tired of its low internal storage.. actually i m a heavy gamer and before buying i thought i would be able to move game data to external sd card and also to delete system apps and bloatwares so i unlocked my bootloader and rooted and then i have tried every method and software available on earth to do what i stated but failed..... i cant delete system apps at any cost ... also cant move game data........ i have tried many apps like Gltosd or root file explorer or a very popular one named Sdfix but all failed......i also tried moving wp.ko module to system/ libs/ modules but that didnt helped as well .. now i think i should have gone for a phone having at least 16gb built-in memory... what you guyzz say? any suggestions

I am using gl to sd app works fine for me maybe u haven't properly flashed the sd fix
Sent from my HTC D816w using XDA Premium 4 mobile app

i think ur sytem is protected try to disable it by using "wp_mod.ko" ...

Use wp mod.ko...I'm currently using it.....
Backup your cell before doing this
Do step by step very carefully....Or else, you'll have to flash the backup
Then try root uninstaller app

jithumon said:
Use wp mod.ko...I'm currently using it.....
Backup your cell before doing this
Do step by step very carefully....Or else, you'll have to flash the backup
Then try root uninstaller app
Click to expand...
Click to collapse
i already have done wp.ko method ... no profit.... it doesnt work... when i uninstall system app and reboot it come back again.... sdfix and root uninstaller is not working also........

after activating wp_mod.ko with insmod-command you have to do another command in terminal as su :
mount -o remount,rw /system
now the wp_mod.ko takes effect und you can edit /system (carefully)
after rebooting the device /system is writeprotected again and you have to renew the command
greetings

n70shan said:
i already have done wp.ko method ... no profit.... it doesnt work... when i uninstall system app and reboot it come back again.... sdfix and root uninstaller is not working also........
Click to expand...
Click to collapse
Do below steps for a permanent system write access
Do step by step very carefully. After this, install root uninstaller(Search Google play). If installed, uninstall & reinstall after this.
1 install TWRP
2 Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh*
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time.

n70shan said:
hi all, i am Thinking to sale Htc desire 816 from yesterday because i am tired of its low internal storage.. actually i m a heavy gamer and before buying i thought i would be able to move game data to external sd card and also to delete system apps and bloatwares so i unlocked my bootloader and rooted and then i have tried every method and software available on earth to do what i stated but failed..... i cant delete system apps at any cost ... also cant move game data........ i have tried many apps like Gltosd or root file explorer or a very popular one named Sdfix but all failed......i also tried moving wp.ko module to system/ libs/ modules but that didnt helped as well .. now i think i should have gone for a phone having at least 16gb built-in memory... what you guyzz say? any suggestions
Click to expand...
Click to collapse
for backup app with data, no matter its system app or what, TRY TITANIUM Backup.
I thought i could help.:angel:

jithumon said:
Do below steps for a permanent system write access
Do step by step very carefully. After this, install root uninstaller(Search Google play). If installed, uninstall & reinstall after this.
1 install TWRP
2 Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh*
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time.
Click to expand...
Click to collapse
thanks man......... i confirm that only this way you can have write access to your system and this is the only working method at the moment...... Grakernel ruined my camera and battery....... for all those who needs proper write access to delete system apks or move app data to external sd card must use this method attention ally........ now i m not selling my phone,,,,,,,,,

n70shan said:
thanks man......... i confirm that only this way you can have write access to your system and this is the only working method at the moment...... Grakernel ruined my camera and battery....... for all those who needs proper write access to delete system apks or move app data to external sd card must use this method attention ally........ now i m not selling my phone,,,,,,,,,
Click to expand...
Click to collapse
That's a great news.... Congo bro...

jithumon said:
Do below steps for a permanent system write access
Do step by step very carefully. After this, install root uninstaller(Search Google play). If installed, uninstall & reinstall after this.
1 install TWRP
2 Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh*
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time.
Click to expand...
Click to collapse
So with this method I can move all games completely to SD card?

Kabo22562 said:
So with this method I can move all games completely to SD card?
Click to expand...
Click to collapse
You can move game data by using Gl to Sd after this

jithumon said:
You can move game data by using Gl to Sd after this
Click to expand...
Click to collapse
Thanks for the reply, man, but is there any tutorial I could follow those steps? I mean is there any videos or somehow? because this seems too much complicated to me, as I am still new to android world after getting addicted to Nokia mobiles..

Do games run smoothly on this phone since we're talking about moving the to SD?

Toyeboy said:
Do games run smoothly on this phone since we're talking about moving the to SD?
Click to expand...
Click to collapse
Yeah, it runs smoothly epically. I didn't face any lag problems except for asphalt 8. It just lags on high graphics, but works fine for both medium and low..
Still waiting for someone to help me doing the up procedure. :/

Kabo22562 said:
Thanks for the reply, man, but is there any tutorial I could follow those steps? I mean is there any videos or somehow? because this seems too much complicated to me, as I am still new to android world after getting addicted to Nokia mobiles..
Click to expand...
Click to collapse
Fist make your SD writable. Then install GL to SD.
Google for GL to SD tutorial.
Don't wait for anyone, Google is a good teacher.

I have already sold it…. Now am in htc m8

mbwambo said:
I have already sold it…. Now am in htc m8
Click to expand...
Click to collapse
Yikes, never HTC again after my experience with this phone. Buying the s5 tomorrow, hopefully I don't regret it.

FoxyDrew said:
Yikes, never HTC again after my experience with this phone. Buying the s5 tomorrow, hopefully I don't regret it.
Click to expand...
Click to collapse
What happened that changed your mind on the 816? You've always seemed like you were enjoying the phone.
Sent from my 710C using Tapatalk

Antiph3d said:
What happened that changed your mind on the 816? You've always seemed like you were enjoying the phone.
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
Might just be bad luck for me, but my headphone jack stopped working, my sim card slot broke, and my SIM card spring broke. Also I didn't like the limited storage and awkward buttom placement.