Database Info

To root before or after OTA?

Hey everyone. Just got the Samsung Nexus S... and I've got a question.
I've read on these forums that the OTA makes it so you have to flash CWM recovery everytime you want to reboot into recovery to flash a ROM and that it's more difficult to root.
Should I flash the OTA then root or root prior to OTA?
Thanks in advance.
m00n
Sent from my SGH-T959 using XDA App

You should get the OTA before you root and it is very easy to make the root stick. I did it with root explorer but I heard you can do it without it.
Sent from my Nexus S using XDA App

tominater12 said:
You should get the OTA before you root and it is very easy to make the root stick. I did it with root explorer but I heard you can do it without it.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Which method did you use to root. And how did you manage to use root explore to get root access when root explorer needs root access first in order to operate? Thanks for your response.
Sent from my SGH-T959 using XDA App

No after you root you can use root explorer to make the recovery stick and there are like 5 guides on how to root on every OS in the android development sub-section. (They are stickied)
m00nshake said:
Which method did you use to root. And how did you manage to use root explore to get root access when root explorer needs root access first in order to operate? Thanks for your response.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App

Thanks again for your response and for the clarification about using root explorer. I have read the stickies regarding rooting the phone, and because there are a few, I was wondering which method you used. I've read that superboot is the easiest and that you can rename a particular system file so the recovery sticks. Thanks again for your response.
Sent from my SGH-T959 using XDA App

m00nshake said:
Thanks again for your response and for the clarification about using root explorer. I have read the stickies regarding rooting the phone, and because there are a few, I was wondering which method you used. I've read that superboot is the easiest and that you can rename a particular system file so the recovery sticks. Thanks again for your response.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Get the OTA.
Apply it.
Boot up to make sure everything is ok. Then boot to bootloader
fastboot oem unlock, confirm it, wipes everything including your internal sd.
flash clockwork mod recovery.
go to clockwork mod recovery from bootloader menu.
mount "internal sd" copy the su-2.3.6.1-ef-signed.zip you downloaded (from the guide) to your internal sd.
unmount internal sd.
mount /system
flash the su-2.3.6.1-ef-signed.zip file.
reboot phone as normal.
login to your gmail account. go to market, download a rooted app like titanium backup free version, and also download rom manager, and buy/get root explorer.
install all those make sure super user is granted and works.
use root explorer to rename/delete the file in: /etc/recovery.sh file or whatever it's actually called.
go to rom manager, and flash the latest clockworkmod recovery (3.0.0.5)
turn off phone and boot to recovery and make sure it's clockwork mod 3.0.0.5, if it is, you're set.

Very helpful post, nxt. Thank you very much.
Sent from my Nexus S using XDA App

nxt said:
Get the OTA.
Apply it.
Boot up to make sure everything is ok. Then boot to bootloader
fastboot oem unlock, confirm it, wipes everything including your internal sd.
flash clockwork mod recovery.
go to clockwork mod recovery from bootloader menu.
mount "internal sd" copy the su-2.3.6.1-ef-signed.zip you downloaded (from the guide) to your internal sd.
unmount internal sd.
mount /system
flash the su-2.3.6.1-ef-signed.zip file.
reboot phone as normal.
login to your gmail account. go to market, download a rooted app like titanium backup free version, and also download rom manager, and buy/get root explorer.
install all those make sure super user is granted and works.
use root explorer to rename/delete the file in: /etc/recovery.sh file or whatever it's actually called.
go to rom manager, and flash the latest clockworkmod recovery (3.0.0.5)
turn off phone and boot to recovery and make sure it's clockwork mod 3.0.0.5, if it is, you're set.
Click to expand...
Click to collapse
Don't you need the android sdk?

tominater12 said:
Don't you need the android sdk?
Click to expand...
Click to collapse
Yes, you need to have the Android SDK properly installed and you're able to do a 'fastboot devices' command properly and your Serial number comes up.

Transfer Titanium backups to new phone?

I am getting a new phone tomorrow. Can I make backups of my apps with titanium and then just transfer the backups to my new phone, reinstall titanium and restore? I'd like to think it's a simple yes.
Sent from my Crespo using xda premium

Yes.
Use TI to make the backups, copy the backup folder to the new phone (its super easy if they both have microSD),then reinstall TI and restore apps. Be careful with system apps as they probably will not work on the new phone unless it is the same model.

Bumping this thread because I want to be exactly sure.
I want to transfer my Ti backup of all my downloaded users apps & data from my current Nexus 7 to the new one I just purchased.
So if I go to File Explorer and go to my main SDcard directory :
/storage/emulated/0/
And scroll down until I see the folder labelled
TitaniumBackup
Copy the entire folder to USB drive and then copy that entire folder over to the SDcard storage in the new tablet
Once I reinstall amd start upTi backup, it should automatically recognize my apps backup from the TitaniumBackup folder, right?
Sent from my Nexus 7 using Tapatalk 2

brunswick000 said:
I am getting a new phone tomorrow. Can I make backups of my apps with titanium and then just transfer the backups to my new phone, reinstall titanium and restore? I'd like to think it's a simple yes.
Sent from my Crespo using xda premium
Click to expand...
Click to collapse
in titeniam back up there is a option called
send backup(s)

prantoroy said:
in titeniam back up there is a option called
send backup(s)
Click to expand...
Click to collapse
Where? In the batch actions or the regular settings menu
Sent from my Nexus 7 using Tapatalk 2

kayone73 said:
Where? In the batch actions or the regular settings menu
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
in batch action create a update.zip of app+data to flash via recovary.

prantoroy said:
in batch action create a update.zip of app+data to flash via recovary.
Click to expand...
Click to collapse
So this will flash in TWRP? Nice
Sent from my Nexus 7 using Tapatalk 2

kayone73 said:
So this will flash in TWRP? Nice
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
yes.
will work

can you rename the folder? Since there are more than one update.zip folders in different locations...

Hi. is this still possible? i want to make a back up and transfer it to a new phone. thanks

in a new phone tb will only work if its rooted??? then whats the point if warranty goes away on the 1st day

since its same topic would titanium backup be able to restore for LineageOS onto the default Samsung TouchWiz ROM on the same or different device

Why can't I edit build.prop or push to /system/app?

Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?

mitchellvii said:
Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?
Click to expand...
Click to collapse
Did you try another root explorer?
Root explorer can be finicky.
Also try clearing it out of super su and and reallowing it. Or wipe app data.
But from my experience with root explorer, I have always hated it!! Try File Manager HD, It is great and has root explorer and system mountable all the time

BeerChameleon said:
Did you try another root explorer?
Root explorer can be finicky.
Also try clearing it out of super su and and reallowing it. Or wipe app data.
But from my experience with root explorer, I have always hated it!! Try File Manager HD, It is great and has root explorer and system mountable all the time
Click to expand...
Click to collapse
Downloaded File Manager HD. Tried replacing the Snotes.apk. No dice. All attempts do do anything with that .apk fail. Seems pretty well locked down.
Same thing with build.prop. No changes will save.

mitchellvii said:
Downloaded File Manager HD. Tried replacing the Snotes.apk. No dice. All attempts do do anything with that .apk fail. Seems pretty well locked down.
Same thing with build.prop. No changes will save.
Click to expand...
Click to collapse
Hmm..
I will try it on my note and see if it works.
Also did u make sure it was called the right name and have the right permissions?
I will let you know tomorrow or maybe tonight if it works

Yep. I've done all this many times before. They have Snotes locked down tight.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Yep. I've done all this many times before. They have Snotes locked down tight.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
You don't have proper root. Reroot and try again. Works like a charm! See below.
Sent from my GT-N8013 using XDA Premium HD app

Huh that seems odd as everything that requires root to work seems to work just fine. Oh well will give it a shot.
Curious as to which method you used to achieve root?
Sent from my GT-N8013 using Tapatalk 2

did you make sure to mount the system folder as r/w? i've never memorized the command since i just use root explorer.

madsquabbles said:
did you make sure to mount the system folder as r/w? i've never memorized the command since i just use root explorer.
Click to expand...
Click to collapse
Yes I did everything correctly. Just not working. That's OK.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Huh that seems odd as everything that requires root to work seems to work just fine. Oh well will give it a shot.
Curious as to which method you used to achieve root?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Custom Recovery, root.zip, TriangleAway. Although root access is being granted, there may be an issue with permissions on "/system". Tried fixing permissions yet?
Sent from my GT-I9300 using XDA Premium HD app

Mister_Mxyzptlk said:
Custom Recovery, root.zip, TriangleAway. Although root access is being granted, there may be an issue with permissions on "/system". Tried fixing permissions yet?
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
No haven't done that. Will run a permissions fix.

mitchellvii said:
No haven't done that. Will run a permissions fix.
Click to expand...
Click to collapse
I was wondering if you have resolved this issue because im having the same problem now. Do you recall doing anything that may have caused this issue? Everything for me started going heywire once i installed init.d support just a second ago. I Can r/w and r/o in certain parts of the system but i cant paste anything anywhere. I also noticed increase cpu load afterwards. Might i add this is the second time i have had these issues after installing init.d support script. The way i solved this the first time was i had to odin stock firmware and this solved everything. Id like to refrain from doing this again though because ill loose all my stuffs and have to set everything up again.
Sent from my GT-N8013 using Tapatalk 2

How did you achieve root? In other threads, problems with write access to /system are reported when a rooted firmware was flashed. Only the method with CWM (install CWM, flash SuperSU) did work.

akxak said:
How did you achieve root? In other threads, problems with write access to /system are reported when a rooted firmware was flashed. Only the method with CWM (install CWM, flash SuperSU) did work.
Click to expand...
Click to collapse
Oh the first time i rooted with the CWM method. But the second time, i did odin a rooted firmware Now that i think about it, the first time i was able to write to /system but now i can't after a rooted firmware flash. So the init.d script wasnt the problem. I just made an assumption because before, i havent touched anything in /system but when i installed init.d script it was actally the first time i tried to edit /system after the rooted firmware. So yes looks like im going to have to odin a stock non-rooted firmware. Thanks man! Makes alot of since now.
edit: couldn't i just try the cwm method and see it it overwrites, cause the only UEALGB firmware i can find is prerooted. I don't want to switch to UEALH2.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?
Click to expand...
Click to collapse
me to same error

Try Root Explorer(or ES File Explorer) & enable R/W for system files
Check your SuperSU/Superuser app.
See if your access is granted & not denied.
If SuperSU/Superuser asking for update, update it (usually binary update)
If your SuperSU/Superuser is gone, re-install it from Play Store & run it for the first time to update binary.
Retry modifying your system file(s)

Bro I cannot change build.prop product model....
I tried root explorer and es explorer
From yuphoria

Is that cannot or don't know how.
One is no root two is edit.
Sent from my SM-N930F using XDA-Developers mobile app
---------- Post added at 02:13 PM ---------- Previous post was at 01:20 PM ----------
JJEgan said:
Is that cannot or don't know how.
One is no root two is edit.
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
Edit is at the top of the RH side.
Sent from my SM-N930F using XDA-Developers mobile app

I have the same problem...
I can change my build.prop but after a reboot all the changes are gone.
I have rerooted it 2-3 times already. I can just change it sucessfully at the beginning but after some time it doesn't work anymore.
I have a samsung galaxy a3 2017.

Try forum for your phone .
Post lacks any information to help.
Suggest FX Explorer.

CWM Backup file

Hi all,
Just wanted to know where the nandroid backup from cwm gets saved? It says sdcard/cwm/backup .But there's no folder such as backup in the cwm folder, although it shows up in recovery mode (the backup file). I was hoping I could find the file and move one of them to my PC so as to save some space on the phone.
Any help would be appreciated..
Thanks
Sent from my Nexus 5 using xda app-developers app

/mnt/shell/emulated/clockworkmod/backup. It's in a difficult place to find
Sent from my Nexus 5

Yeah,no kidding! Thanks a lot man, found the files
Sent from my Nexus 5 using xda app-developers app

jd1639 said:
/mnt/shell/emulated/clockworkmod/backup. It's in a difficult place to find
Sent from my Nexus 5
Click to expand...
Click to collapse
no problem, glad I could help
Sent from my Nexus 5

Its in data/media/clockworkmod (which is a slightly quicker way to get there)
And I explain why here:
[ info] Storage: Nexus 5 Data (info / loss / recovery / prevention)
http://forum.xda-developers.com/showthread.php?t=2534010
Which is also why I would recommend switching recovery to either Philz or TWRP
Sent from my Nexus 5 using Tapatalk

Nice thread man.. Thanks for the link..
Sent from my Nexus 5 using xda app-developers app

rootSU said:
Its in data/media/clockworkmod (which is a slightly quicker way to get there)
And I explain why here:
[ info] Storage: Nexus 5 Data (info / loss / recovery / prevention)
http://forum.xda-developers.com/showthread.php?t=2534010
Which is also why I would recommend switching recovery to either Philz or TWRP
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I just backed up my N5 with CWM and I can't find the file... I tried all locations shown here with ES file explorer and these dirs are empty... Or at least they show empty.
Any idea what I'm doing wrong?
N5 - rooted - Stock rom - franco kernel - CWM recovery

SonicAngel said:
I just backed up my N5 with CWM and I can't find the file... I tried all locations shown here with ES file explorer and these dirs are empty... Or at least they show empty.
Any idea what I'm doing wrong?
N5 - rooted - Stock rom - franco kernel - CWM recovery
Click to expand...
Click to collapse
After a backup has been taken, does the storage show less space available?
How about taking another backup and see whether it's working or not?
PS: Instead of CWM, can you try Philz? It's based on CWM with added goodies! I find it a lot better.

SonicAngel said:
I just backed up my N5 with CWM and I can't find the file... I tried all locations shown here with ES file explorer and these dirs are empty... Or at least they show empty.
Any idea what I'm doing wrong?
N5 - rooted - Stock rom - franco kernel - CWM recovery
Click to expand...
Click to collapse
If you haven't given ES root permissions, any /data directory will show as empty

rootSU said:
If you haven't given ES root permissions, any /data directory will show as empty
Click to expand...
Click to collapse
Figures. I thought it wasn't showing hidden files even though I checked the "show hidden files" box.
Clicked "Root Explorer" and lo and behold, there's a **** ton of stuff in there.
This was driving me insane (and filled up my storage too grrrrrrrrrrrrr), thanks rootSU.
Ok one last question, is there a way to view all files in windows as well when the device is connected via USB?

No probs

Anyone pay for Titanium Backup years ago?

So when I initially bought TiBU, it wasn't a key in the PlayStore, it's a .txt file. My question is, how do I get TiBU to recognize this .txt file so I can unlock the pro version? Or do I have to purchase again?

s197 said:
So when I initially bought TiBU, it wasn't a key in the PlayStore, it's a .txt file. My question is, how do I get TiBU to recognize this .txt file so I can unlock the pro version? Or do I have to purchase again?
Click to expand...
Click to collapse
Have you tried reaching out to the developers? I have purchased it.. but I think when I did they had already moved to a different type of verification as I install the app, then the 'premium' one to get all my paid for features.. I found this.. http://www.titaniumtrack.com/kb/tit...ackup-licensing.html#text-license-not-working on their site... did this work?

jbarcus81 said:
Have you tried reaching out to the developers? I have purchased it.. but I think when I did they had already moved to a different type of verification as I install the app, then the 'premium' one to get all my paid for features.. I found this.. http://www.titaniumtrack.com/kb/tit...ackup-licensing.html#text-license-not-working on their site... did this work?
Click to expand...
Click to collapse
Sent them an email but you get an automated message back saying they receive lots of emails so try their FAQ site. Maybe they'll respond, eventually. I did try what was in the link but it didn't work. It says to place at the root of the SD card, but this phone has no SD card so perhaps that's the problem.

s197 said:
So when I initially bought TiBU, it wasn't a key in the PlayStore, it's a .txt file. My question is, how do I get TiBU to recognize this .txt file so I can unlock the pro version? Or do I have to purchase again?
Click to expand...
Click to collapse
I purchased it years ago and just put the txt file in my SD root. It always recognizes the file and unlocks.
Sent from my SM-G920V using XDA Free mobile app

krypto1300 said:
I purchased it years ago and just put the txt file in my SD root. It always recognizes the file and unlocks.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
What part of the storage did you put this file? OP is having trouble locating the root of the Sdcard since we don't have one...

jbarcus81 said:
What part of the storage did you put this file? OP is having trouble locating the root of the Sdcard since we don't have one...
Click to expand...
Click to collapse
Oh sorry, it's...
storage/sdcard0 or
storage/emulated/0
using root explorer.
Sent from my SM-G920V using XDA Free mobile app

krypto1300 said:
Oh sorry, it's...
storage/sdcard0 or
storage/emulated/0
using root explorer.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
Cool...hopefully that helps OP..

That's Where I have it, wonder why it's not seeing it.

s197 said:
That's Where I have it, wonder why it's not seeing it.
Click to expand...
Click to collapse
That's weird. I've never had a problem with the old txt file.
Sent from my SM-G920V using XDA Free mobile app

i am from the txt file days as well and ended up just paying again for the apk version as i switch phones and mess around so much i got tired of moving it around

Make sure it's named TitaniumBackup_license.txt exactly, and it seemed like Titanium used to require a reinstall after placing the text file.