Database Info

[Q] Details regarding Unlocking Bootloader, Rooting and Deleting apps from rom

Hello,
I will really appreciate if you can help to understand few basic issues:
1) When rooting the phone, is the boot-loader must be unlocked? i.e., if I've rooted the phone successfully using some 3rd party utility, it means that the boot-loader was unlocked during the rooting process or it was unlocked in advanced?
2) If the answer to the first question is "yes" (i.e. bootloader must be unlocked before rooting), how it is possible that my data wasn't wiped after rooting? This means that the boot-loader was unlocked in advance? Or maybe the 3rd party application backed up the data before unlocking the boot-loader and than restored it?
3) I heard that in order to install SU, the stock-recovery must be changed to a custom one. Is it necessarily true?
4) How can I check which recovery is installed on the phone?
5) If the recovery is changed to a custom one, does it mean that I stop receive OTA?
6) Can I backup up the stock recovery before changing it? Or how can I know which one it is to search on the net?
7) Do applications, like Titanium, change the recovery upon installation?
8) How applications, like Titanium, move apps, that are not supposed to move in regular installation,from ROM to SD? Can it harm the performance of the app?
9) When deleting apps from ROM (System or Data) manually, do I need to delete other files or folders besides .apk files in system/app or data/app? Is there any cache or other data to delete?
10) Do I need (or should I in case of lack of space) clean some cache files from ROM? (Like Dalvik or others...) If yes, which ones and how?
Sorry for the long post, but It will really help me to understand all these issues, once and for all.
Thank you in advance!

yuri_feigin said:
Hello,
I will really appreciate if you can help to understand few basic issues:
1) When rooting the phone, is the boot-loader must be unlocked? i.e., if I've rooted the phone successfully using some 3rd party utility, it means that the boot-loader was unlocked during the rooting process or it was unlocked in advanced?
2) If the answer to the first question is "yes" (i.e. bootloader must be unlocked before rooting), how it is possible that my data wasn't wiped after rooting? This means that the boot-loader was unlocked in advance? Or maybe the 3rd party application backed up the data before unlocking the boot-loader and than restored it?
3) I heard that in order to install SU, the stock-recovery must be changed to a custom one. Is it necessarily true?
4) How can I check which recovery is installed on the phone?
5) If the recovery is changed to a custom one, does it mean that I stop receive OTA?
6) Can I backup up the stock recovery before changing it? Or how can I know which one it is to search on the net?
7) Do applications, like Titanium, change the recovery upon installation?
8) How applications, like Titanium, move apps, that are not supposed to move in regular installation,from ROM to SD? Can it harm the performance of the app?
9) When deleting apps from ROM (System or Data) manually, do I need to delete other files or folders besides .apk files in system/app or data/app? Is there any cache or other data to delete?
10) Do I need (or should I in case of lack of space) clean some cache files from ROM? (Like Dalvik or others...) If yes, which ones and how?
Sorry for the long post, but It will really help me to understand all these issues, once and for all.
Thank you in advance!
Click to expand...
Click to collapse
Im sorry but Ive already answered all of these questions and one in fact could take a good couple paragraphs to explain.
Maybe tonight I'll answer or you could check out xda university.

yuri_feigin said:
Hello,
I will really appreciate if you can help to understand few basic issues:
1) When rooting the phone, is the boot-loader must be unlocked? i.e., if I've rooted the phone successfully using some 3rd party utility, it means that the boot-loader was unlocked during the rooting process or it was unlocked in advanced?
2) If the answer to the first question is "yes" (i.e. bootloader must be unlocked before rooting), how it is possible that my data wasn't wiped after rooting? This means that the boot-loader was unlocked in advance? Or maybe the 3rd party application backed up the data before unlocking the boot-loader and than restored it?
3) I heard that in order to install SU, the stock-recovery must be changed to a custom one. Is it necessarily true?
4) How can I check which recovery is installed on the phone?
5) If the recovery is changed to a custom one, does it mean that I stop receive OTA?
6) Can I backup up the stock recovery before changing it? Or how can I know which one it is to search on the net?
7) Do applications, like Titanium, change the recovery upon installation?
8) How applications, like Titanium, move apps, that are not supposed to move in regular installation,from ROM to SD? Can it harm the performance of the app?
9) When deleting apps from ROM (System or Data) manually, do I need to delete other files or folders besides .apk files in system/app or data/app? Is there any cache or other data to delete?
10) Do I need (or should I in case of lack of space) clean some cache files from ROM? (Like Dalvik or others...) If yes, which ones and how?
Sorry for the long post, but It will really help me to understand all these issues, once and for all.
Thank you in advance!
Click to expand...
Click to collapse
1) To my knowledge, yep. (Not much experience with locked bootloaders, sorry!)
2) But then again, different phones have different bootloaders, they might work In different ways.
3) Nope. Most (if not all) root tools install SU without custom recovery.
4) when your phone is powered-off, press Vol up, home and power button (this depends on your phone, this is Samsung standard, what phone are u using?
5) Go to download mode, (Vol down, home and power button, again Samsung standard) and check if: System Status: Official. If yes, OTAs can be taken. If System Status: Custom, you cant take OTAs.
6) U most probably can. Use Online Nandroid Backup, free from Google play store, and backup recovery only. That should work.
7) No.
8) Depends on the app.
9) Again, depends on the app.
10) Cache and dalvik cache can be wiped from recovery. The custom recovery will do it for u. Wiping dalvik cache from recovery won't be useful, as it recreates itself on reboot.
No problem with the long post, always glad to help
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.

Thank You
Lgrootnoob said:
Im sorry but Ive already answered all of these questions and one in fact could take a good couple paragraphs to explain.
Maybe tonight I'll answer or you could check out xda university.
Click to expand...
Click to collapse
I would really appreciate if you could answer, or refer me to the correct paragraph in XDA university or give a me a link to your previous answers.
Thank you very much.

Irwenzhao said:
1) To my knowledge, yep. (Not much experience with locked bootloaders, sorry!)
2) But then again, different phones have different bootloaders, they might work In different ways.
3) Nope. Most (if not all) root tools install SU without custom recovery.
4) when your phone is powered-off, press Vol up, home and power button (this depends on your phone, this is Samsung standard, what phone are u using?
5) Go to download mode, (Vol down, home and power button, again Samsung standard) and check if: System Status: Official. If yes, OTAs can be taken. If System Status: Custom, you cant take OTAs.
6) U most probably can. Use Online Nandroid Backup, free from Google play store, and backup recovery only. That should work.
7) No.
8) Depends on the app.
9) Again, depends on the app.
10) Cache and dalvik cache can be wiped from recovery. The custom recovery will do it for u. Wiping dalvik cache from recovery won't be useful, as it recreates itself on reboot.
No problem with the long post, always glad to help
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
Click to expand...
Click to collapse
Thank You for your help.
Regarding the last issue: if I wipe the cache, something bad can happen to the applications ot their data? I mean, should I do it only when flashi rom or is it healthy to do it in a while in order to clean unnecessary files?

yuri_feigin said:
Thank You for your help.
Regarding the last issue: if I wipe the cache, something bad can happen to the applications ot their data? I mean, should I do it only when flashi rom or is it healthy to do it in a while in order to clean unnecessary files?
Click to expand...
Click to collapse
The cache is actually a temporary section of the disk that does not contain any application cachery but things along the lines of software upgrade files. It is only wiped merely to make sure there is space for other mod's temp storage.
The data partition contains the data for yourr applications and the 'cache' as you see in settings for apps is for imagery and stuff so regardless if that is removed it wont matter.
The dalvik cache is compiled bytecode for the dalvik vm for each app. (Look up Java vm to get an idea of what I mean and then look up odexing and deodexing on xda university)
Here is some info on the thread http://forum.xda-developers.com/showthread.php?p=48151745#post48151745

Lgrootnoob said:
The cache is actually a temporary section of the disk that does not contain any application cachery but things along the lines of software upgrade files. It is only wiped merely to make sure there is space for other mod's temp storage.
The data partition contains the data for yourr applications and the 'cache' as you see in settings for apps is for imagery and stuff so regardless if that is removed it wont matter.
The dalvik cache is compiled bytecode for the dalvik vm for each app. (Look up Java vm to get an idea of what I mean and then look up odexing and deodexing on xda university)
Here is some info on the thread http://forum.xda-developers.com/showthread.php?p=48151745#post48151745
Click to expand...
Click to collapse
Thanks a lot!
I have few more questions, please:
1) So what will be the best way to clear the cache partition? Only from recovery? Even from stock recovery?
Is there any other way, like a feature in some application or can I delete it manually?
2) Regarding the data partition, I guess I can go each application and clear its cache and/or data from application manager... Is there a better way? By away, if I delete the data of application (not the cache), I loose all the configuration and personal data. What I mean by "cleaning" is to erase some false data that remained by mistake, not to remove the necessary data of the apps. It is especially important for apps installed on ROM. What will be the best way?
3) Is sometimes remains unnecessary junk data in Dalvik Cache? If yes, how to remove it? (not the all Dalvik Cache)?
4) By away, what is the best way to check whether my bootloader is unlocked and to check which recovery is installed? (custom/stock)
5) If I want to mess with the start-up task manager, using some ROM application - what are the "receivers" that are connected to the apps? what is the difference between disabling an app/task/service and disabling receivers?
6) What is the difference between recovery boot mode and bootloader boot mode? When do I need to use the bootloader mode?
6) And another question, with your permission, is what kind of backups are exist beside nandroid? ADB is a backup? Do they back up all the ROM? I guess I will need a custom recovery to restore those backups.

yuri_feigin said:
Thanks a lot!
I have few more questions, please:
1) So what will be the best way to clear the cache partition? Only from recovery? Even from stock recovery?
Is there any other way, like a feature in some application or can I delete it manually?
2) Regarding the data partition, I guess I can go each application and clear its cache and/or data from application manager... Is there a better way? By away, if I delete the data of application (not the cache), I loose all the configuration and personal data. What I mean by "cleaning" is to erase some false data that remained by mistake, not to remove the necessary data of the apps. It is especially important for apps installed on ROM. What will be the best way?
3) Is sometimes remains unnecessary junk data in Dalvik Cache? If yes, how to remove it? (not the all Dalvik Cache)?
4) By away, what is the best way to check whether my bootloader is unlocked and to check which recovery is installed? (custom/stock)
5) If I want to mess with the start-up task manager, using some ROM application - what are the "receivers" that are connected to the apps? what is the difference between disabling an app/task/service and disabling receivers?
6) What is the difference between recovery boot mode and bootloader boot mode? When do I need to use the bootloader mode?
7) And another question, with your permission, is what kind of backups are exist beside nandroid? ADB is a backup? Do they back up all the ROM? I guess I will need a custom recovery to restore those backups.
Click to expand...
Click to collapse
1: Only recovery.
2: "Cleaning" is not possible So the application manager is the only way and yes it would basically reset an application if you delete its data.
3: Its not necessary but can save space for more apps to be installed if you have removed apps manually or with titanium backup. However if you have uninstalled with the app manager in the settings app then the dex files in the dalvik cache are automatically removed. "Unnecessary junk", I have exactly what you are looking for: use Titanium backup's feature in the menu to remove unsused dalvik cache elements and integrate system dalvik into rom. (In the same section when you press the menu button)
4: What phone? (This is neccessary because of the variation in phones.)
5: The only legitimate way of stopping tasks is to disable the intent of the task(I think that is the reciever ). To do this you could use Autostarts from the Play store or you could use the Bootmanager Xposed module. Don't use any task manager unless you want problems. Disabling an app in settings would actually completely freeze the application meaning you could also not start it manually and it wouldnt be started at boot.
6: The bootloader loads recovery or Android. The bootloader is usable depending on the features given by your phone manufacturer. You would know the difference when you use recovery and if you have a Nexus device when you are in bootloader mode. Samsung devices have Download mode which is technically part of the bootloader and allows you to load custom software such as recovery, data partition, system partition etc.
7: You will use recovery to backup/restore.(I don't think that there is any other way because you are using the data that you are backing up or restoring if you didi it while you were running android. Adb cannot backup either but you could pull a recovery backup with adb from the sd card. Adb has a sideload feature for loading software in recovery with your computer. Again I need your phone model.
It seems you seek info on recovery and backing up, This will help a lot: http://xda-university.com/as-a-user/android-dictionary Specifically the Nandroid and Recovery section.
I will be more than happy to expand on any of these topics.

@yuri_feigin
I revised my answer to better suit what you were asking.
Are you still with me?

[Q] is it safe to delete everything on a 2nd hand phone - including system folders

Hi - i bought a 2nd hand phone and in case there is any spyware on it, i want to delete everything on it, including all the system folders using clockwork mod. is this safe?
i am wondering, will the imei numbers be preserved ? (ie, are they actually written on a chip that is read only, or are they in the system folders too?) i am wondering this with a few model phones --- galaxy nexus (which i believe does get the imei reset), sony xperia t, nexus 4, etc

temp4285 said:
Hi - i bought a 2nd hand phone and in case there is any spyware on it, i want to delete everything on it, including all the system folders using clockwork mod. is this safe?
i am wondering, will the imei numbers be preserved ? (ie, are they actually written on a chip that is read only, or are they in the system folders too?) i am wondering this with a few model phones --- galaxy nexus (which i believe does get the imei reset), sony xperia t, nexus 4, etc
Click to expand...
Click to collapse
just boot into recovery, and do format, wipe data, etc.

Kobro said:
just boot into recovery, and do format, wipe data, etc.
Click to expand...
Click to collapse
Never Try to delete system folders on your phone you will surely get a brick and no one would be able to fix it....
Just Go to setting and find Factory Reset Option that would be the solution to your question...
Hit thanks if i helped......

N'ayam Amarsh'e said:
Never Try to delete system folders on your phone you will surely get a brick and no one would be able to fix it....
Just Go to setting and find Factory Reset Option that would be the solution to your question...
Hit thanks if i helped......
Click to expand...
Click to collapse
yes, but surely someone can leave a virus or eavesdropping tool in the system folder ?
i plan to put a custom rom on after that anyway - so is it safe to remove the system folder ?
the only thing i can see that may cause problems is the IMEI number ?

temp4285 said:
yes, but surely someone can leave a virus or eavesdropping tool in the system folder ?
i plan to put a custom rom on after that anyway - so is it safe to remove the system folder ?
the only thing i can see that may cause problems is the IMEI number ?
Click to expand...
Click to collapse
if you wipe with cwm it will erase everything that can be safely erased.

Kobro said:
if you wipe with cwm it will erase everything that can be safely erased.
Click to expand...
Click to collapse
not true - because if you delete the system folder - which you can - on some phones the imei resets, i believe, to something generic
any thoughts anyone ?

If you delete a folder that the os needs, it will rebuild it when it boots

[Great Trouble] Apps stopped

[My first post on xda, plz help!]
My N5, 4.4.4 not rooted, has faced those problems for about a month or two:
1.My gallery force stopped when I tried to use the default gallery photo editor (the little pencil button at the left corner of the screen) to edit a photo of any format, but luckily I still have Pixlr Express and Photoshop to edit photos, nevertheless, it is still uncomfortable to see. ?
2.My YouTube and YouTube studio app also force stopped when I tried to share a video. It is very troublesome to me as I need to share my videos for promotion! ?
3. My Instagram also force stopped when I tried to choose a picture from my gallery in the camera page of the app. However, when I go to the gallery and directly share the photo to Instagram, it works. It is kinda strange.
4. It is a terrible problem and limitation for android users, but still not the worst for me (you will see when you read the next bullet point). My phone can't install apks! I have no screen filter and the install page doesn't even completely show up as the package installer stopped message comes up ahead of it.
5. The worst problem of all... Settings is malfunctional, I can't force stop, or clear cache, or change default settings of the apps because when I go to the list of apps and tap one of them, "Unfortunately, Settings has stopped" message jumps out and I am never able to solve the problems of the apps above. What's more, when I go to "About Device" and keep tapping on the Android Version 4.4.4, the easter egg animation doesn't show up! ?????????
So, this is it. I plan to factory reset my phone but I am not free to back up my data yet, so would it help? Additionally, one more piece of information may help you guys find out the clue: I have a File Manager that can open folders over the sdcard folder (I am not pro so I can't explain well) so I can access to system folders containing things like system apps, boot animation, kernel etc. So is it abnormal for a unrooted phone?
Hope that some of you can help me. ???
Sent from my Nexus 5 using XDA Free mobile app

No... Its not abnormal for a file manager to view system folders... U can't edit the folder nor can you see contents of other folders... Actually just boot a custom recovery and wipe data without wiping the internal storage... It may solve the issue... To do that use towel root method of rooting flash the custom recovery using some app or unlock the boot loader using bootunlocker apk...
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Then in case you are a noob just go to boot loader after downloading the recovery image as well as adb drivers and use command fastboot boot name of your recovery.zip or fastboot flash recovery nameofrecovery.zip...

Sukrith said:
No... Its not abnormal for a file manager to view system folders... U can't edit the folder nor can you see contents of other folders... Actually just boot a custom recovery and wipe data without wiping the internal storage... It may solve the issue... To do that use towel root method of rooting flash the custom recovery using some app or unlock the boot loader using bootunlocker apk...
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Then in case you are a noob just go to boot loader after downloading the recovery image as well as adb drivers and use command fastboot boot name of your recovery.zip or fastboot flash recovery nameofrecovery.zip...
Click to expand...
Click to collapse
I would wipe everything and start over.
If you're on stock Android, I have a link to the images in my signature.

Aerowinder said:
I would wipe everything and start over.
If you're on stock Android, I have a link to the images in my signature.
Click to expand...
Click to collapse
This too... [emoji1]

Sukrith said:
No... Its not abnormal for a file manager to view system folders... U can't edit the folder nor can you see contents of other folders... Actually just boot a custom recovery and wipe data without wiping the internal storage... It may solve the issue... To do that use towel root method of rooting flash the custom recovery using some app or unlock the boot loader using bootunlocker apk...
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Then in case you are a noob just go to boot loader after downloading the recovery image as well as adb drivers and use command fastboot boot name of your recovery.zip or fastboot flash recovery nameofrecovery.zip...
Click to expand...
Click to collapse
you don't need to root your phone and flash a custom recovery to wipe data. 1. you can do it in stock recovery 2. you can do it in the main settings, backup and reset(factory reset).

simms22 said:
you don't need to root your phone and flash a custom recovery to wipe data. 1. you can do it in stock recovery 2. you can do it in the main settings, backup and reset(factory reset).
Click to expand...
Click to collapse
It'll wipe internal storage!!!

Never mind, I will backup
Sent from my Nexus 5 using XDA Free mobile app

Sukrith said:
It'll wipe internal storage!!!
Click to expand...
Click to collapse
why would a factory reset wipe internal storage?

simms22 said:
why would a factory reset wipe internal storage?
Click to expand...
Click to collapse
Because N5 doesn't have removable SD card... In phones with SD card also, the internal storage will be wiped and only the SD card is left alone as it gets unmounted on power off...

By the way, if I ignore these problems now and wait until the android L update, will they be solved after the update? I am. using stock android, no root.
Sent from my Nexus 5 using XDA Free mobile app

simms22 said:
why would a factory reset wipe internal storage?
Click to expand...
Click to collapse
Stock recovery.
Isthatjjk said:
By the way, if I ignore these problems now and wait until the android L update, will they be solved after the update? I am. using stock android, no root.
Click to expand...
Click to collapse
Just fix it. Pretending it doesn't exist and hoping an update fixes it gets you nowhere. Copy your SD card to a computer, and wipe it. Just do it. Stop putting up with this crap.

Thx, I fixed it now (temporarily) by turning to recovery mode and wipe data.
However, before I did so, I used the factory reset in settings and when it came to erase data, the 'erase all data' button had no response, it is weird. But anyway the problem has solved ?
Sent from my Nexus 5 using XDA Free mobile app

Isthatjjk said:
Thx, I fixed it now (temporarily) by turning to recovery mode and wipe data.
However, before I did so, I used the factory reset in settings and when it came to erase data, the 'erase all data' button had no response, it is weird. But anyway the problem has solved ?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
FYI you could have used ADB to back up the phone data.

so, deleting data in the stock recovery did not wipe your storage?

Isthatjjk said:
Thx, I fixed it now (temporarily) by turning to recovery mode and wipe data.
However, before I did so, I used the factory reset in settings and when it came to erase data, the 'erase all data' button had no response, it is weird. But anyway the problem has solved ?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
dude just reflash the factory image and be done with all the issues... that will actually solve everything:good:

need help - how to copy TWRP nandroid backup to device?

how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.

Latest TWRP has MTP mode.

but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB

You'll need to give us more information.
Why did it fail? Why did your phone stop booting?

1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop

gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.

how can you copy using twrp while in recovery? are you able to access your PC from recovery?

gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.

ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??

Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty

No. Do a full flash of userdata.img

Please explain
What would I achieve by flashing it?

gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.

Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working

gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.

I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5

gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup

build.prop modification caused loss of root, now stuck with bad build.prop

Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery

memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop

-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.

memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache

-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help

memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site

Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.