Database Users

Can't upgrade to CWM

I can't seem to find the / cust_backup file to replace the recovery.img any ideas?
I used superoneclick to root my u8800. I've tried holding the vol+/ vol- and power button together to get to the pink screen but when I plug in my USB data cable to my PC nothing comes up. Before on froyo it would and I could see the Image file which allowed me to replace the recovery.img
I've looked on the guides to upgrade to 5.5.0.4 and 5.0.2.7 and they all require me to find the ./cust_backup file which I can't find
Sent from my SGH-I777 using XDA

did you sucessfully rooted your device?
You'll need a File Explorer with root permissions to find ./cust_backup folder.

yes it is successfully rooted, I've checked with various apps and superoneclick itself

How are you trying to access /cust_backup?
You'll need Root Explorer or something similar, because you have locked bootloader

Thank you so much it worked with root explorer!
I was using es file explorer but I guess it doesn't work

dabien101 said:
Thank you so much it worked with root explorer!
I was using es file explorer but I guess it doesn't work
Click to expand...
Click to collapse
es file explorer does not have root access(by default, but you can activate it through es file explorer settings). It means that cannot access to the entire filesystem.
Glad it worked

Es file explorer, has root access(just needed to be activated from settings).
dabien101
You should flash the unlocked bootloader from 518 rom(there is a thread called "get your pink screen back" by bluefish), to have more options to recover the device if something going wrong.

Loureiro said:
es file explorer does not have root access. It means that cannot access to the entire filesystem.
Click to expand...
Click to collapse
Some screenshots...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my U8800 using Tapatalk 2

dancer_69 said:
Es file explorer, has root access(just needed to be activated from settings).
dabien101
You should flash the unlocked bootloader from 518 rom(there is a thread called "get your pink screen back" by bluefish), to have more options to recover the device if something going wrong.
Click to expand...
Click to collapse
That's interesting! never knew that was possible.
Thanks for that

Rooted My Nexus 7 but cant change system files..

I'm quite new to the whole android scene .. Got a Nexus 7 couple of days ago rooted it using the tool kit:
Its now unlocked and has SuperUser installed.
However I want access to files in the system/media which I can get via Android Commander but it's saying Im not Rooted ( Meaning I cannot swap or replace any stock files on the device)
Any ideas?

Try using Root explorer or ES File explorer (enable root access in settings). Did you get a popup from SuperUser asking to grant/deny root access?

goofball2k said:
Try using Root explorer or ES File explorer (enable root access in settings). Did you get a popup from SuperUser asking to grant/deny root access?
Click to expand...
Click to collapse
Ill try ES now.. and Yes SuperUser does notify me for request which I grant.

Root explorer lets you remount the filesystem you are in like below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clicking the button sites between Read Only and Read/Write Modes.
Sent from my Nexus 7

krelvinaz said:
Root explorer lets you remount the filesystem you are in like below
Clicking the button sites between Read Only and Read/Write Modes.
Sent from my Nexus 7
Click to expand...
Click to collapse
So for instance now I have enabled Root access in ES explorer How can I swap files from the tablet to the PC?

Normally, you will have placed the file(s) from the PC you want to use on the SDcard first, then you can use the file manager to access where you want, move/copy etc...
Would suggest you have a decent backup (or nandroid backup) first and if you are replacing system files, it is always a good idea to have a copy of the original so you can put it back if needed.

krelvinaz said:
Normally, you will have placed the file(s) from the PC you want to use on the SDcard first, then you can use the file manager to access where you want, move/copy etc...
Would suggest you have a decent backup (or nandroid backup) first and if you are replacing system files, it is always a good idea to have a copy of the original so you can put it back if needed.
Click to expand...
Click to collapse
Well I may have found the other stored Image files for the boot, but I cant move them .. meaning i still dont have root access? I don't know it's making me rage.

cant install apps

this is so strange happend since rootin etc
after doin titanium backup n run all me programs i have a issue i cant install apps normally i mean apps ive downloaded from other sources/xda
i click on the app i try and click the install but it dosent work i cantget it to work its so weird i canel the install
the onlyu other way for me to get to intsall is to es file explore and use root explore one click install but if a app require extre permission i like play store im unable to install the app
any help would be great full thanks
ps i use foldermount n once first installed it tell me i have a issue with system it fixes the system so that i can mount app data on me external sd card
also my system is read only i have to use a script to make it read and write
thanks spud

daddyspud said:
this is so strange happend since rootin etc
after doin titanium backup n run all me programs i have a issue i cant install apps normally i mean apps ive downloaded from other sources/xda
i click on the app i try and click the install but it dosent work i cantget it to work its so weird i canel the install
the onlyu other way for me to get to intsall is to es file explore and use root explore one click install but if a app require extre permission i like play store im unable to install the app
any help would be great full thanks
ps i use foldermount n once first installed it tell me i have a issue with system it fixes the system so that i can mount app data on me external sd card
also my system is read only i have to use a script to make it read and write
thanks spud
Click to expand...
Click to collapse
Did you goto your settings and check Unknown Sources?

P1NK13P13 said:
Did you goto your settings and check Unknown Sources?
Click to expand...
Click to collapse
yes i have that setting check i also unchecked google verify as well
but still the same issue if i do a full format and reintall all ok then after restoring apps i have this issus and even adb commands n programs like atadb tells me my system w/o not w/r very strange

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Q] Cannot write to sdcard0 without root - Can I fix it?

I have a Sprint GN3. I've rooted with CF Auto Root, flashed TWRP, flashed Jellybomb, and then restored back to stock from a nandroid backup.
I'm not sure when it started, but it appears that I can't write to sdcard0 or Emulated/0 without root or system permissions. For example, I can use Astro to create a new folder in extSdCard just fine, but it fails if I try to create a folder in sdcard0. It works from Total Commander or Root Explorer but I also get the "...has been granted superuser permissions" popup.
I can't download any files in Chrome or Dolphin, and downloads from Ambiance also fail, I'm assuming because it's failing to write to sdcard0, and Audible throws an error when it tries to create my data file in /emulated/0.
But setting the storage location for the camera to Device seems to work just fine.
Below are the permissions I'm seeing in Root Explorer. Does anything look obviously wrong? Is sdcard0 supposed to be owned by Root while extSdCard is owned by System? Or what else should I look for?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Samsung Galaxy NOTE 3 UnRoot-Bricked-Fixed
Kennedy808 said:
I have a Sprint GN3. I've rooted with CF Auto Root, flashed TWRP, flashed Jellybomb, and then restored back to stock from a nandroid backup.
I'm not sure when it started, but it appears that I can't write to sdcard0 or Emulated/0 without root or system permissions. For example, I can use Astro to create a new folder in extSdCard just fine, but it fails if I try to create a folder in sdcard0. It works from Total Commander or Root Explorer but I also get the "...has been granted superuser permissions" popup.
I can't download any files in Chrome or Dolphin, and downloads from Ambiance also fail, I'm assuming because it's failing to write to sdcard0, and Audible throws an error when it tries to create my data file in /emulated/0.
But setting the storage location for the camera to Device seems to work just fine.
Below are the permissions I'm seeing in Root Explorer. Does anything look obviously wrong? Is sdcard0 supposed to be owned by Root while extSdCard is owned by System? Or what else should I look for?
Try this app from the play store FREE worked great for me...
SOLVED!!!!
Had the same issue and its cuz the USB debugging was turned off in the Developer apps to my luck I had it on, but turned it off 1 week prior to my ph crashing... lol I tried EVERYTHING for 3 days and I'm tech savy lol What I ended up doing was using my fiance's note 3 to back up all her files via the SD card on her phone and then loaded it into mine and it worked like a charm. It's even a free app from the play store called "Root Browser" and NO you do not have to root their phone to copy their files... Copy the files, on the broken phone do the recovery mode (Volume Up + Home Key + Power Button) then load from external source. Be sure to wipe your data and all that before installing on the broken ph.... and bada-bing bada-bang! FIXED!
I suggest downloading that in the future and keeping that spare SD card in the GUN SAFE!!! just in case you happen to re-root your phone later lol
Hope this helps out since I about threw my Note 3 at the wall from all the looping frustration...lol Tried Odin, Kies3 and nothing... even the ABD cmd and no luck.... Idk why I didn't think about doing that in the past lol GOOD LUCK!:fingers-crossed:
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Can't delete supersu folder on internal storage

How Can I delete the supersu folder using twrp or adb? I had root then let the SuperSU app do a full unroot and the supersu folder is still there. I even flashed the stock rom and the suspersu folder is on the internal (root) storage.
Thanks in advance
update: twrp internal storage wipe didn't help

Was it systemless root? I only ask because system root places folder in /system/app or in /data/app if installed as a regular app. I never tried systemless root so not sure where that goes but would assume the same place. Wiping internal with twrp should have erased it if it's in /sdcard. Since you can see the folder can you open it?

Fe Mike said:
Was it systemless root? I only ask because system root places folder in /system/app or in /data/app if installed as a regular app. I never tried systemless root so not sure where that goes but would assume the same place. Wiping internal with twrp should have erased it if it's in /sdcard. Since you can see the folder can you open it?
Click to expand...
Click to collapse
SR1-SuperSU-v2.78-SR1-20160915123031 is the version I sued, but I sued with Android 7.1.1 preview...Phone wouldn't boot so i flashed the latest 7.0 z stock. Now I can get rid of this /supersu folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try from TWRP file mamager

rquinn19 said:
Try from TWRP file mamager
Click to expand...
Click to collapse
Yeup, I can delete but it comes right back after reboot so i think the permissions are messed up.

Hi...i know this is old thread unsolved.
If after a year changed there are way to remove /supersu folder please share..thanks
Edit:after few time changing twrp version to test which version could remove "supersu" folder.file inside that folder change.i think not supersu keep creating it but twrp itself.it's just my conclusion