Related
Hi all,
i often noticed people(including me) who tried to modificate their framework-res.apk resulting in boot loops(e.g. looping at white/green quietly brilliant screen).
So i tried to find out a fast way to get back to my(original) framework-res.apk without usage of recovery console each time my framwork-res.apk did not work as expected.
How it could help you:
It's a fast way to:
check out your moddings when doing numerous modifications in different versions of your modded framework-res.apk on your way to get it to work.
if you want to get back to your original/working framework-res.apk, even when it boot loops!
Click to expand...
Click to collapse
When you do numerous modifications on framework-res.apk and your modded apk leads to a boot loop you will be able to replace the current apk through e.g. the original apk.
At this boot point(boot loop screen) Android nearly finished booting and you have access on ADB commands.
What do you need to do this:
Download and extract/install QtADB from the link below:
QtADB
to replace the erroneous(current) framework-res.apk by the original or a fixed one.
Click to expand...
Click to collapse
There's no need to describe how to get a copy of your untouched framework-res.apk from device, since there are numerous tutorials around here.
Please check this tutorials to get a copy of your apk.
Please note before beating your device:
this probably will work with the most visual moddings of framework-res.apk - but i can't guarantee it works 100%.
It probably will not work when you play around with hardware or connections setting, other apk's or other stuff in other folders, so i am not responsible if it does not work.
always backup your current ROM/settings/whatever and save a copy of your untouched framework-res.apk
There is a little catch in it in comparsion with using recovery:
After you did like described, you have to set your background image and your (google) accounts anew.
But this is just a little work and it's not necessary until your framework-res.apk is doing the modded stuff correctly - or if you want to set the original framework-res.apk back.
Click to expand...
Click to collapse
So let's start to revive your original framework-res.apk.
(Of course you can use this method to push a modded to your device, to check out if your modding works):
Boot your device and let it load until you're at boot loop
(Download, extract,) run QtADB
Navigate in left window(Computer) to your copy of original framework-res.apk(e.g. in root directory of SD card, but i recommend a folder on your computer)
Navigate in right window(Phone) to device folder /system/framework/
Use in left window(Computer) context menu on your original framework-res.apk and select copy or drag&drop it to right window to copy the original framework-res.apk to your device
(just ignore that your device is doing strange stuff then, since it cannot access your framework-res.apk correctly at this point)
Then enter shell of QtADB(at left toolbar of QtADB) and enter the following commands to set the apk's prermissions:su
cd /system/framework/
chmod 777 framework-res.apk
Reboot your device( e.g. by using top menu->tools-ADB->reboot)
Set your background image and your (google/HtcSense) accounts anew.
Hope it helps you a bit on modding,
Greetings, brush2(Stephan)
error
hey man, Im getting an error on this. I changed my transitions effects ( folder anim on framework-res.apk) using the app metamorph. well, now every time I open an app the phone ( xt920) reboot. I ask my friend that have the same phone to send me his framework-res.apk. I try to replace using this method but dont got. I draged and droped the new apk and when I would type the shell's code the last code dont work because it said that the file is a "read-only system". What can I do to have my phone back? Please help.
Thanks.
I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?
yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.
ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.
This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.
be careful, backup buid.prop and restore it after creating Box account.
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
I am having no luck finding a way to get root access from a computer.
deleted post
user error
The tumbleweeds are big around here
There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
But is there an app to copy my file over from my computer?
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.
jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...
its taking forever to install SDK
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.
yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?
So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Restore your Nandroid.
Edit: just saw that you said you didn't make one. Lesson learned, I guess. You can adb sideload files from within recovery. Do this, sideload a stock rom, flash it, and it will give you a normal build.prop.
Sent from my iPad 4
Use adb to push the backup build.prop and overwrite the current one.
I'm assuming that u have the backup on your PC? If not, then download the stock ROM and extract the build.prop from /system.
Use the following command to push it:
Code:
adb push /path/to/build.prop \system
Sent from my HTC Desire using xda app-developers app
megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
If it's stock android, you could actually just wipe /system , then using adb in recovery you can push up a zip of the stock 4.2.2 isntall, and just flash that.
If build.prop is all you changed in /system then that should be fine to do, which will be especially easy if you can just grab a pre-rooted flashable zip of 4.2.2 stock.
megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
megaman1574 said:
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
Click to expand...
Click to collapse
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
Where should I look to get a stock rom?
megaman1574 said:
Where should I look to get a stock rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
mitchdickson said:
just saw that you said you didn't make one. Lesson learned, I guess.
Click to expand...
Click to collapse
Yes, definitely. I can't remember why I didn't make a backup...
mitchdickson said:
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
Click to expand...
Click to collapse
Ok, if I can't fix it by tonight I'll download this and flash it (My download limit during the day is too small to download it. That's why I'm trying to fix it without doing that)
kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
I'm not that good with Android, how and when do use this "logcat"?
megaman1574 said:
I'm not that good with Android, how and when do use this "logcat"?
Click to expand...
Click to collapse
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
kbeezie said:
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
Click to expand...
Click to collapse
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
megaman1574 said:
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
Click to expand...
Click to collapse
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
kbeezie said:
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
Click to expand...
Click to collapse
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
megaman1574 said:
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
Click to expand...
Click to collapse
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
kbeezie said:
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
Click to expand...
Click to collapse
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
megaman1574 said:
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
Click to expand...
Click to collapse
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Ok... I had managed to move the backup of build.prop into system using TWRP's file manager but after THAT it wouldn't even show the Nexus logo. Hence the reason I said nothing about this (I thought it to be a dead end). Just as I was about to give up, I was reading an obscure post on Androidforums.com and came across a post telling the guy to pull build.prop, edit it, push it back, and chmod it to 644. I haven't the FAINTEST clue what the hell that is, but I remembered that "chmod" and "chmod 755" were two options when you tap on a file in TWRP's file manager. So I raced back in there, deleted the broken build.prop, moved the backup into system, tapped on it and pressed "chmod 755" rebooted and it worked! Anyone have any idea what is was that I did? What is chmod? But basically:
I FIXED IT YAY!!!
Thanks everyone for your help. I've been desperate to fix it, in fact, when I broke it was an hour before I had to leave for a weekend trip, so I had no phone.
kbeezie said:
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Click to expand...
Click to collapse
My Nexus 7 is rooted with TWRP and it received an OTA update. But anyway, if you refer to my last post I fixed it.
Edit: However, it did unroot it. (not hard to reroot though)
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
If you can boot to bootloader you should be able to replace the file with a standard one.
Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out
1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.
Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?
Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!
Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0
same thing happened to me.... stuck on google even after flashing stock....
dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app
Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.
RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too