[Q] Build.prop keeps reverting after reboot - Moto X Q&A

So I rooted, and I was playing with my build.prop file to try and get Google Wallet working. It never did, so I restored my old build.prop to go back to normal. However, my edited build.prop keeps restoring itself somehow after a reboot. I've tried different editors, I've tried pushing the file via ADB, editing via ADB, nothing seems to work. I've seen a few other people with random other phones having this issue, and the answer is always 'just flash another ROM!'. Well, that isn't an answer, esp since we can't flash ROMs yet. Anyone have any idea how to either fix this or flash back to 100% stock on a Verizon XT1060? Thanks!

You are rooted, so make sure you are booted into "recovery" so you have system write access. Then restore your unedited build.prop and reboot.
You can also flash back to 100% stock firmware using RSDLite and the VZW software.

rmead01 said:
You are rooted, so make sure you are booted into "recovery" so you have system write access. Then restore your unedited build.prop and reboot.
You can also flash back to 100% stock firmware using RSDLite and the VZW software.
Click to expand...
Click to collapse
Thanks. I tried using the Verizon dump, but I'm on a Linux box. Using fastboot to flash took everything but the system.img which failed. I'll just wait until I get home to use a Windows box to run RSDLite. Much appreciated.
Isn't it strange that I can edit it just fine from Root Explorer the first time, but not a second time though?

icase81 said:
Thanks. I tried using the Verizon dump, but I'm on a Linux box. Using fastboot to flash took everything but the system.img which failed. I'll just wait until I get home to use a Windows box to run RSDLite. Much appreciated.
Isn't it strange that I can edit it just fine from Root Explorer the first time, but not a second time though?
Click to expand...
Click to collapse
Well, what I mean was that when you root the phone, /system is only readable. In order for it to be writeable you need to boot into recovery. That is where you have a copy of the OS that has a writable /system. So I would boot to recovery, make your build.prop changes, then reboot into the standard mode. That should save the build.prop from the previous bootup when you were able to right it. This would also explain why root explorer could write it the first time (in recovery) and maybe why it couldn't the second time (not in recovery)
I haven't tried using fastboot at all with the phone, but I've use RSDLite to restore my ATT phone twice no with no issues.

rmead01 said:
Well, what I mean was that when you root the phone, /system is only readable. In order for it to be writeable you need to boot into recovery. That is where you have a copy of the OS that has a writable /system. So I would boot to recovery, make your build.prop changes, then reboot into the standard mode. That should save the build.prop from the previous bootup when you were able to right it. This would also explain why root explorer could write it the first time (in recovery) and maybe why it couldn't the second time (not in recovery)
I haven't tried using fastboot at all with the phone, but I've use RSDLite to restore my ATT phone twice no with no issues.
Click to expand...
Click to collapse
I would like to add that by boot into recovery they don't mean the same thing as every other android root. You aren't going into recovery and flashing thing like normal. You reboot you phone into "recovery mode" which is the same as normally booting your phone but you have read/write access to the system files.

Same issue here. Bootloader unlocked and rooted with supersu.zip. Editors can only modify the build prop once per editor. Weird.
Sent from my XT1056 using XDA Premium 4 mobile app

magui43212 said:
Same issue here. Bootloader unlocked and rooted with supersu.zip. Editors can only modify the build prop once per editor. Weird.
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, Root Explorer will create a backup. I delete build.prop, rename build.prop.bak to build.prop, reboot, its like I never did anything at all and this thing still thinks is an L710 Sprint Galaxy S3

icase81 said:
Yeah, Root Explorer will create a backup. I delete build.prop, rename build.prop.bak to build.prop, reboot, its like I never did anything at all and this thing still thinks is an L710 Sprint Galaxy S3
Click to expand...
Click to collapse
So what the phone does is it automatically restore build prop backups every reboot? That seems weird.
Sent from my XT1056 using XDA Premium 4 mobile app

magui43212 said:
So what the phone does is it automatically restore build prop backups every reboot? That seems weird.
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly. And it restores my build.prop.bak file too, which was created by root explorer. I tried using other apps to edit, tried to do it with ADB, it does it no matter what. I think I'm just gonna RSD-Lite it back to factory and go from there.

Related

just rooted

using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1323946
i would like to install that faster rom everyone os raving about because my phone is dog slow. what rom comes with this method that i just did? can i install that gingervolt rom using this root or do i have to re-root using another method?
onlyoneromeo said:
using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1323946
i would like to install that faster rom everyone os raving about because my phone is dog slow. what rom comes with this method that i just did? can i install that gingervolt rom using this root or do i have to re-root using another method?
Click to expand...
Click to collapse
root is root. as long as you have root and CWM you can flash Gingervolt no problem.
onlyoneromeo said:
using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1323946
i would like to install that faster rom everyone os raving about because my phone is dog slow. what rom comes with this method that i just did? can i install that gingervolt rom using this root or do i have to re-root using another method?
Click to expand...
Click to collapse
If that is the root method you used, you do not have cwm recovery yet. You either need to run the newest version i posted earlier (yes it is ok to run the root.bat even if you already have root!), use RevoToolkit, or install manually. Then you can install the rom.
Ok I'm going to go do that now . I'm going to use the revotoolkit. So basically what that tool kit does is allow you to install custom roms? I hope that ginger volt can speed my phones processes up. I really don't want to ask for another htc device and my only two choices to swap for was the charge and this phone. Ugh I'm so frustrated...
ok so used revtoolkit and installed it and then downloaded the gingervlt zip file to my sd card. i rebooted the phone while pressing the power and vol down key an it came up w a screen asking if i wanted to erase everything. i watched a youtube vid that said to proceed with that and nothing would be erased and it did erase everything. how do i get into that screen to exract that zip file?
onlyoneromeo said:
ok so used revtoolkit and installed it and then downloaded the gingervlt zip file to my sd card. i rebooted the phone while pressing the power and vol down key an it came up w a screen asking if i wanted to erase everything. i watched a youtube vid that said to proceed with that and nothing would be erased and it did erase everything. how do i get into that screen to exract that zip file?
Click to expand...
Click to collapse
The root method you used is out dated and does not remove the files to make clockwork stick. Reuse revotoolkit to reinstall cwm, after confirmed to have worked, while still in revotoolkit press menu and hit reboot recovery.
Sent from my VS910 4G using xda premium
ok i reinstalled the cwm and when i click on the reboot option the screen on the phone is on but blank. am i missing something?
so if i use the all in one package root and unroot method you posted in the other board i should be able to install the rom i want without all the problems im having now?
onlyoneromeo said:
so if i use the all in one package root and unroot method you posted in the other board i should be able to install the rom i want without all the problems im having now?
Click to expand...
Click to collapse
Yep
Sent from my VS910 4G using xda premium

[How to] Stock to Stock/CM9 Dual Boot

I've been struggling installing custom roms on my phone so I figured I'd document the process to help out anyone else starting out. I'd like to thank everyone for helping me figure this out and for the hard work of the community for making this possible.
Edit: My goal was to come up with a way to install CM9 while leaving the original system it came with and all my settings and apps. I understand how to do TitaniumBackup and how to save specific apps/files to but I wanted an exact backup of my original system alongside any custom rom so I just wrote down the steps I used to make it happen.
Root the system
1.First apply one click root using this tool
Further instructions here: http://forum.xda-developers.com/showthread.php?t=1319653
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
Droid 3 CWM (ClockWorkMod)
2. Install this apk onto the phone and click the first button then the second button
http://forum.xda-developers.com/attachment.php?attachmentid=882933&d=1328117678
3. Boot into recovery and make a backup of your system
4.Apply Fastboot package for UMTS XT860 Iusacell Mexico using RSD Lite 5.5
Further instructions here:
http://rootzwiki.com/topic/4370-sbf...959-and-56890/page__view__findpost__p__100987
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
RSD Lite: http://www.multiupload.com/T6NOEBKKLO
5. Reroot using 2.3.6 Zerg tool
Basically after flashing with RSD Lite then re-root using this tool:
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
6.Re-install CWM (Droid 3 Bootstrapper from step 2) and then apply the Bell rar file as a nandroid restore.
Further instructions here: http://forum.xda-developers.com/showpost.php?p=21446640&postcount=112
https://rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar
7. Reboot into the system and let the OS load again then re-install cwm (no need to reroot) and reboot back into recovery.
the trick to booting into recovery the second time is to turn the phone off, hold the m key while pressing the power button, plug in the phone to usb, choose bp tools
source: http://forum.xda-developers.com/showpost.php?p=21474818&postcount=120
restore your original backup from step 3 using advanced restore and restore the Data only and then wipe cache and dalvik cache
8. Remove CWM and install safestrap instead it involves using adb shell and removing certain files instructions found here:
http://www.droidforums.net/forum/dr...d-help-removing-clockworkmod.html#post1801072
9. Install SafeStrap once CWM is removed just install it, reboot and press the menu key while booting
http://dl.xda-developers.com/attach...5/7/9/2/5/Droid3_Safestrap_Tweaked_v1.08d.apk
10. ICS Install, at this point you have prepped your system so you can install CM9 otherwise it won't boot on the stock Bell 2.3.4
Instructions here: http://forum.xda-developers.com/showpost.php?p=22254669&postcount=61 (start at step 8 or 9 in those instructions)
-Apply CM9 Alpha 6 Zip
http://www.hash-of-codes.com/files/cm9-droid3-20120130-1730.zip
-Apply XT860 Sub-Patch (by Rick#2) for ICS Zip
http://bit.ly/Ah5b6d
Further instructions here: http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Great tutorial
As a note, in step 6, you could flash any custom rom to /system. You might not be able to restore /data though. Can try and if no go do a data wipe. If you backup apps with titanium backup and call logs/sms/mms with mybackroot its not such a big deal. Just redownload those 2 apps and restore everything(honestly I rarely nandroid, only if im doing something im confident will end in a fastboot flash, I just use those 2 apps). Im running liberty in /systemorig and eclipse in /system
Sent from my XT860 using xda premium
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Endoroid said:
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks for the tip I wouldn't have been able to get this far without your help Endoroid. I'll edit the How-To to use the same root twice, I wish mods would sticky more useful posts like zerg's root instead of pete's root and How-To such as this one.
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
ncho2233 said:
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
Click to expand...
Click to collapse
First, you may wish to just go with safestrap and try flashing g rom in safe mode. If it bootloops no harm done because your bell /system is intact
If that fails you can try using motofastboot instead of rsdlite to just flash /system. You can restore your /system with your nandroid.
As far as I know roms should work with bell 2.3.6.
If you do end up flashing the whole fastboot package with rsdlite you can make your phone appear to be bell stock. You can restore your nandroid and then mod the build.prop so about phone shows bell info. The warranty guys would have to look deep to see its been changed.
Its up to you ultimately but as I said I don't think you would have to flash the fastboot. Safestrap should work as is on bell 2.3.6. As long as you don't mess with /systemorig (nonsafe mode) its easy to remove the evidence. Uninstall safestrap recovery and remove su/superuser
If I recall correctly dasilva had his issue due to being on 2.3.4 and unable to update.
Sent from my XT860 using xda premium
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
ncho2233 said:
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
Click to expand...
Click to collapse
Correct
Safestrap was built with the idea of keeping your phone intact. You can still easily receive OTA updates and can return your phone to stock if you need to get warranty repair done
Sent from my XT860 using xda premium
dasilva333 said:
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
Click to expand...
Click to collapse
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
白い熊 said:
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
Click to expand...
Click to collapse
+1
1of16 said:
+1
Click to expand...
Click to collapse
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
danifunker said:
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
Click to expand...
Click to collapse
Thanks, and I can use it on my XT862 too?
is it possible to install the latest OTA (5.7.906), which I want to use as stock rom?

New firmware

I just got an Ota update. I537UCUCNH3. Can't find any info online about this firmware. Anybody have any info?
does towelroot or any form of root still work?
Do not take the ota. Im capturing it right now. Once ive inspected and cleaned the updater I will post it. As far as i know it's firmware update and some updated samsung features and apps. Just hang on.
Code4U said:
Do not take the ota. Im capturing it right now. Once ive inspected and cleaned the updater I will post it. As far as i know it's firmware update and some updated samsung features and apps. Just hang on.
EDIT... It tries to patch the stock recovery/knox system/selinux setup. Im going to remove them and see what happens. Ive already cleaned the ota and made it a zip.Will report back very soon.
Click to expand...
Click to collapse
interesting. i'll wait and see what happens. i'm most importantly just trying to make sure i don't lose root.
Ive gotten it install fine but I cant stop wifi from getting forked. Im going to have to dig around some more. This happened on the first KK update because of selinux. Same is happening here also.
http://www.att.com/esupport/article.jsp?sid=KB420364&cv=820#fbid=0tcKX5Fkc73
What's changing?
Connectivity improvements related to receiving calls and text messaging
Security patch
Updated Google apps
Click to expand...
Click to collapse
Edit...Got it working perfect see post further down.
Code4U said:
I still cannot get it update and keep wifi. I took the dive and ota'd to see if its rootable. It is not,thank god for odin. Someone with more experience is going to need to look at this.Sorry guys I tried.
Click to expand...
Click to collapse
Can you post the update zip?
Yeah man do you want what I altered already, or the stock ota in zip form.
Please can you post the stock OTA zip?
Thanks
Get your upgrade here....
Here ya go OTA in original cfg. Adb push to cache/fota. Go to update and click continue. Reboot after you push, so it shows up in update section.
https://docs.google.com/file/d/0B5FxQlt9ZPF6T3k2T2o5MGJxNUE/edit?usp=docslist_api
Cfg will wipe your data,most likely will kill root and prevent re-rooting.
Here is the ota in zip form 100% stock. I just made in zip form and removed the patch checks so you can flash in safestrap.
https://drive.google.com/file/d/0B5FxQlt9ZPF6dThpek1sMHFidjA/view?usp=sharing
Flashable works fine allows you to keep root and safestrap. Here is what I did. Restore back to stock,wipe caches. Flash the zip. Mount system delete SU app from recovery file manager,leave the binary. Reboot. Check all is fine. Reboot back to recovery,flash su zip. This worked perfectly for me.
Hey guys, just letting you know if you apply the stock cfg file manually, it will wipe your data. So backup before update... I just got screwed.!!!
salwansk said:
Hey guys, just letting you know if you apply the stock cfg file manually, it will wipe your data. So backup before update... I just got screwed.!!!
Click to expand...
Click to collapse
If you need help going back to previous KK version let me know. Its really easy. Then you can use the zip to upgrade back with safestrap.
Code4U said:
Get your upgrade here....
Here ya go OTA in original cfg. Adb push to cache/fota. Go to update and click continue. Reboot after you push, so it shows up in update section.
https://docs.google.com/file/d/0B5FxQlt9ZPF6T3k2T2o5MGJxNUE/edit?usp=docslist_api
Cfg will wipe your data,most likely will kill root and prevent re-rooting.
Here is the ota in zip form 100% stock. I just made in zip form and removed the patch checks so you can flash in safestrap.
https://drive.google.com/file/d/0B5FxQlt9ZPF6dThpek1sMHFidjA/view?usp=sharing
Flashable works fine allows you to keep root and safestrap. Here is what I did. Restore back to stock,wipe caches. Flash the zip. Mount system delete SU app from recovery file manager,leave the binary. Reboot. Check all is fine. Reboot back to recovery,flash su zip. This worked perfectly for me.
Click to expand...
Click to collapse
sorry, could you be a little more specific with these? I'm still a little new. What did you do to restore back to stock? I've currently removed bloatware through titanium, so no longer have at&t software. also, i'm rooted. Am I correct in assuming this is the order?
1 - Restore to stock
2 - Wipe caches
3 - Flash the zip (The entire i537_Update.zip?)
4 - Mount system (Does this mean use the "Mount" feature in SafeStrap and navigate to the specific "System" folder?)
5 - Delete SU app from recovery file manager (completely lost as to how to do this. Is it the file manager in the "Advanced" section of SafeStrap? If so, is that only for files or can I uninstall apps?)
6 - Leave the binary (also not sure what to do here)
7 - Reboot
8 - Check everything is fine
9 - Reboot into recovery
10 - Flash su.zip (Where is this file located?)
Sorry to be a pain, just hoping to get my facts straight. Thanks.
pinyata said:
sorry, could you be a little more specific with these? I'm still a little new. What did you do to restore back to stock? I've currently removed bloatware through titanium, so no longer have at&t software. also, i'm rooted. Am I correct in assuming this is the order?
1 - Restore to stock
2 - Wipe caches
3 - Flash the zip (The entire i537_Update.zip?)
4 - Mount system (Does this mean use the "Mount" feature in SafeStrap and navigate to the specific "System" folder?)
5 - Delete SU app from recovery file manager (completely lost as to how to do this. Is it the file manager in the "Advanced" section of SafeStrap? If so, is that only for files or can I uninstall apps?)
6 - Leave the binary (also not sure what to do here)
7 - Reboot
8 - Check everything is fine
9 - Reboot into recovery
10 - Flash su.zip (Where is this file located?)
Sorry to be a pain, just hoping to get my facts straight. Thanks.
Click to expand...
Click to collapse
No problem man you got it very close. Restore back to stock,needs to be 100% stock NE3,reboot to recovery,wipe caches,install zip.Do not reboot yet,in safestrap navigate to mount,click on system, then click advanced,click file manager,navigate to where su app is(most likely in system/app) just delete it.binary is in xbin so just dont worry about it but dont delete it.Reboot.Once you see the upgrade popup,reboot recovery flash su zip and your done.I could not strip out knox or disable selinux because it screwed up wifi. theres a de-knoxing zip somewhere on here just use that after your all booted up.
Code4U said:
No problem man you got it very close. Restore back to stock,needs to be 100% stock NE3,reboot to recovery,wipe caches,install zip.Do not reboot yet,in safestrap navigate to mount,click on system, then click advanced,click file manager,navigate to where su app is(most likely in system/app) just delete it.binary is in xbin so just dont worry about it but dont delete it.Reboot.Once you see the upgrade popup,reboot recovery flash su zip and your done.I could not strip out knox or disable selinux because it screwed up wifi. theres a de-knoxing zip somewhere on here just use that after your all booted up.
Click to expand...
Click to collapse
how do you restore to stock? odin flash the NE3 files? If so, doesn't that mean I lose root, and therefore SafeStrap?
pinyata said:
how do you restore to stock? odin flash the NE3 files? If so, doesn't that mean I lose root, and therefore SafeStrap?
Click to expand...
Click to collapse
Yes flash the odin files. Dont worry about losing root just use towelroot and install safestrap again. Then flash SuperSU zip and continue. If I could make it easier I would. I spent a few hours trying to avoid all this,but there was no way around it.
If you update via OTA you will not be able to re-root using towelroot just a FYI.
I'll stay on MF3 its not big changes... I'm waiting for kitkat 4.4.4
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Root
So the only way to root is flashing an older kernel and root with towelroot and flash the newer kernel again?
That is at least what I see for other phones that have gotten updates that broke towelroot.

[Q] Nexus File access from Recovery

Been trying to search this but can't find a way to access my Nexus 6 file system from recovery.
I tried editing my build.prop (phone is rooted, no custom rom) rebooted and now stuck on the Google boot screen with the unlock symbol.
Hoping to restore by file (have backup) rather then reset to default.
Fastboot sees it (mac os) but adb does not)
Any help would be greatly appreciated.
mhennigan1377 said:
Been trying to search this but can't find a way to access my Nexus 6 file system from recovery.
I tried editing my build.prop (phone is rooted, no custom rom) rebooted and now stuck on the Google boot screen with the unlock symbol.
Hoping to restore by file (have backup) rather then reset to default.
Fastboot sees it (mac os) but adb does not)
Any help would be greatly appreciated.
Click to expand...
Click to collapse
you cant edit your build.prop from your recovery. you can access it, but you cant edit it back.
I didn't think so but i wanted to ask. THanks for the reply. I just flashed the system image again thankfully that was painless.
mhennigan1377 said:
I didn't think so but i wanted to ask. THanks for the reply. I just flashed the system image again thankfully that was painless.
Click to expand...
Click to collapse
what did you change in your build.prop to make it not boot? it couldve also just been a spelling error as well. i make a nandroid backup in recovery every two weeks, and keep it on my phone at all times. i frequently change things, and dont boot. at that point, i just restore a nandroid backup
simms22 said:
what did you change in your build.prop to make it not boot? it couldve also just been a spelling error as well. i make a nandroid backup in recovery every two weeks, and keep it on my phone at all times. i frequently change things, and dont boot. at that point, i just restore a nandroid backup
Click to expand...
Click to collapse
I was adding a line to stop the provisioning check for tethering. Not sure what I could have done?
net.tethering.noprovisioning=true
Definitely need to look at doing those backups again.
mhennigan1377 said:
I was adding a line to stop the provisioning check for tethering. Not sure what I could have done?
net.tethering.noprovisioning=true
Definitely need to look at doing those backups again.
Click to expand...
Click to collapse
odd, ive that in my build.prop and it boots up fine. im guessing a spelling error was included in it.

I have MAJORLY screwed up.

Okay, so at this point I have no idea what to do, and am hoping for some help.
I was able to unlock with Sunshine via temproot with Kingroot (was on the latest stock 5.1 OTA) last night, and pretty much everything was fine. I attempted to install Supersu via TWRP, but the binaries were out of date (this was after uninstalling Kingroot from in app). After a few attemts to update (within Android and in TWRP), I attempted to uninstall SuperSU to start over, no dice, wouldn't go. After that I went rooting around TWRP (not a good idea if you're new) and used the 'Fix Permissions' feature. Not only did that not fix SuperSU, but after that all hell broke loose within the OS, with Google Play Services crashing all the time. I tried clearing the cache, updating after diabling Services, no dice. Infally I tried a Factory Restore, and that still didn't help. Tried two more times, evebn without restoring my app data, it still would crash. I attempted reflashing TWRP through ADB a couple times, but it wasn't having an effect.
Then, the really bad part, I attempted flashin in TWRP, and accidently selected BOOT instead of RECOVERY, now either one brings me to TWRP. I tried restoring to stock firmware in RSD Lite, no dice, tried running the batch file that came with the firmware, nothing, it apparently tried loading the parsechunks, but had no effect.
I can still get into both TWRP and Fastboot on the phone, and it will connect via USB (shows up as a fastboot device in adb), but other than that my phone is stuck.
Anyhelp would be VERY appeciated, I should have just left things alone.
Why not just try installing cm12.1 and see what happens?
Wonder if entering twrp needs to be done via vol down and power so to not be on the boot side... If that makes sense...
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Why not just try installing cm12.1 and see what happens?
Wonder if entering twrp needs to be done via vol down and power so to boy be on the boot side... If that makes sense...
So you've tried flashing stock ?
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Tried flashing the stock frimware, and it didn't work.
Was able to find a clean copy of the boot.img from computerfrrek and it has allowed me to get back into Android, however, play services still appears to have issues.
At least the phone is operational again.
Odd problems.
I'm thinking rsd now?
Sent from my XT1254 using XDA Free mobile app
---------- Post added at 01:45 AM ---------- Previous post was at 01:45 AM ----------
You have a system directory problem it sounds a clean flash should fix it.
Sent from my XT1254 using XDA Free mobile app
Just go get one of my mofo imgs unzip it and fastboot the .img all but recovery and the big system img. Then fast boot twrp. And then you can flash my new rom that is ready to download now.
the thing that messed you up was the fix permissions. find out how to "fix"/ "undo" the fact that you hit fix permissions and then flash stock and start over
computerfreek274 said:
Just go get one of my mofo imgs unzip it and fastboot the .img all but recovery and the big system img. Then fast boot twrp. And then you can flash my new rom that is ready to download now.
Click to expand...
Click to collapse
Thanks, I ended up flashing the boot.img you uploaded yesterday and all I'm back in Android again, not just figuring out the SuperSU/GPlay Services issue, do you thing the ROM would help with that?
diabl0w said:
the thing that messed you up was the fix permissions. find out how to "fix"/ "undo" the fact that you hit fix permissions and then flash stock and start over
Click to expand...
Click to collapse
Yeah, it's a matter of fixing the damage done by the 'Fix Permissions' command now.
CtrlAltConstruct said:
Yeah, it's a matter of fixing the damage done by the 'Fix Permissions' command now.
Click to expand...
Click to collapse
I uninstalled and then reinstalled Play Services a couple times. Mostly because I had to force stop Titanium Backup after it sat for 15 minutes without completing the uninstall. For me, everything seems to be working, except my old texts didn't show up in Hangouts. I just searched around here and found a thread with all the Play Service apks and grabbed the right one from there. I'm about to try installing computerfreek's ROM, so we'll see if that does anything else for me.
Everything seems fixed after installing the ROM.
AVELLIN said:
Everything seems fixed after installing the ROM.
Click to expand...
Click to collapse
Flashed the ROM, still have issues, do you recomend uninstalling via Titanium and re-flashing?
CtrlAltConstruct said:
Flashed the ROM, still have issues, do you recomend uninstalling via Titanium and re-flashing?
Click to expand...
Click to collapse
Yeah, I'd give it a try. Mine's still going strong, got all my stuff set back up and it's smooth.

Categories

Resources