Could somebody please send me the /system/build.prop from a stock 4.2.2 Nexus 4?
I can't install the 4.3 OTA zip unless my build.prop passes the integrity check that is built into the OTA...I modified mine to enable LTE with an LTE-enabling script that didn't make a backup. It's not clear what needs to be changed back and I'm pretty sure it needs to be exactly default for it to pass the check (i.e. spaces, order of the parameters, etc...needs to precisely as it was before...)
It would be much appreciated if somebody could please upload the build.prop somewhere.
I've attached the backup of my JDQ39 build.prop file in a zip to this post. I was able to flash the 4.3 OTA update using this build.prop so it should be fine.
For anyone else in the same boat (OTA failing because build.prop not passing check in install), the above build.prop worked for me. I don't have root and I'm still 1/2 n00b so I pushed it into /system/build.prop using the nexus toolkit and it's insecure boot image (choice 13). Then I rebooted into recovery and followed the normal instructions for using ADB sideload to install the OTA (section A here: http://forum.xda-developers.com/showthread.php?t=2145848)
Related
Hi there, i've got a problem updating, like many it seems and I'm pretty new to rooting etc. so please bear with me.
I have 4.2.1 stock rom, rooted and with twrp v2.4.1.0 recovery. I was originally rooted with CWM recovery (using n7 toolkit) but I have flashed twrp to try and update with no luck either.
Anyway I get an error (see attachment image) via ota or via downloading the zip and copying it to the n7 then browsing for it in recovery and installing it that way. I'm basically wondering if there's a quick fix to this problem and can you please help me with it even if there isnt a quick fix. I really don't want to reset my device and have to set everything back up again.
Also, i dont know if this is related, probably is, I cant boot into recovery using the power off hold volume down trick, getting into fastboot mode and then selecting recovery as it just brings up the google logo forever and I have to reset the tablet due to it doing nothing. The only way I can get into recovery is to clear data from google services framework and do an ota update (1970 thing) and that reboots into recovery. I then get the error 7 message in attached photo.
Plz help?!?!
Thanks in advance
Here's what to do.
First, look at those errors in the image you posted very very carefully.
2nd, use the search function on this forum: try the terms "OTA debuggerd" (without the quotes)
3rd, read those posts.
4th, decide if you want the hassle. You are not obligated to perform an upgrade.
5th, Download from Google the 4.2.2 Factory images and extract the "boot.img" and "system.img" files
(make sure you understand that nakasi == grouper == WiFi N7, and nakasig == tilapia == 3G N7)
Hint: search on Google for "Google Nexus Factory Images"
finally
fastboot flash boot name-of-boot-image-file.img
fastboot flash system name-of-system-image-file.img
This will remove root from the ROM, so you will need to flash a SuperSU or Superuser root kit.
Doing things this way is a band-aid. You need to learn how to make full backups & perform full restores; how to flash individual partitions - using both fastboot & the custom recovery; know exactly what the roles of each partition are; know the difference between a kernel, ramdisk, and boot image; understand how to retrieve a small number of files from prior backups; and to know where the installer scripts are located inside flashable .zip files & be able to read them so you can understand what they do.
Finally, you should understand what apps like Titanium Backup and Carbon are capable of, and how backup of System app&data has different consequences upon restore than similar operations for user-installed apps.
OK - get started.
I have n7 with root, custom recover and enable tether.
Will it correct if I change updater-script in saved OTA?
1. set new md5sum for build.prop and framework-res.apk
2. remove install new bootloader:
ui_print("Writing bootloader...");
package_extract_file("bootloader.raw", "/dev/block/platform/sdhci-tegra.3/by-name/USP");
Will I lost root?
Also I don't know what to do with last lines:
apply_patch("/system/build.prop", "-",
6b364f8e7af4085324762096091b319f6dd0bb2c, 2696,
2876fd5f06d489630faeb705cd77d28c602930cc, package_extract_file("patch/system/build.prop.p"));
I restored original files and flashed
You might want to have a look at my blog, there I described a very easy way for updating to 4.3
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
When I tried to update my rooted stock N7 to 4.4.2 from 4.4.0, the script always failed saying "debuggerd has unexpected content."
This is apparently a known issue revolving around stickmount. Unfortunately, I didn't have a replacement debuggerd and didnt' want to take the time to find and install the right one... So, if you need a quick list of things to do to get the update working (Used Windows 7)
Please note that
:
1) Download
the stock 4.4.0 image from https://developers.google.com/android/nexus/images#nakasi
the Android SDK bundle from here: https://developer.android.com/sdk/index.html
SuperSU from http://forum.xda-developers.com/showthread.php?t=1538053
The actual update file if you don't have it already (mine was already in /cache when I started down this road)
Install the Android SDK.
Run the Android SDK manager and make SURE you get the USB drivers.
Enable Android debugging on the N7 and plug it in via USB to the computer.
Once it fails to find a driver for one of the options, open the device manager.
Locate the "Nexus 7" in "other devices"
Right click and select "update driver"
Tell Windows to look in the ...\adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver directory
Once the driver is installed, open a command prompt and CD to the ...\adt-bundle-windows-x86_64-20131030\sdk\platform-tools directory
Run "adb devices"
You should get a prompt on the N7 asking for permission. Allow it.
You should see your device in the list.
put the SuperSU update file on the N7 by running:
adb push {downloadpath}\UPDATE-SuperSU-v1.80.zip /sdcard/
if needed, push the OTA file to the same place.
adb push {downloadpath}\{taht awfully long name} /sdcard/
run adb reboot bootloader
You should be in the bootloader.
Another device driver should install. After that "fastboot devices" should show your device.
Extract the 4.4 factory image to its own directory
Locate the "image-nakasi-krt16s.zip" file in the "nakasi-krt16s" subdirectory.
extract that .zip file to it's own directory
CD to that last directory in the command prompt
run fastboot flash-image system system.img
use the bootloader interface to boot into recovery
Flash the OTA file
Flash the SuperSU update
wipe cache and Dalvik
reboot normally.
In my case, I used TWRP and created a flash queue to flash both the OTA file and SuperSu. When I rebooted, everything came up. The first boot was a little long, and I got the normal post-OTA "Optimizing app n of 200" count.
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
khaytsus said:
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
Click to expand...
Click to collapse
Well, I'm not that up on editing update scripts. Then someone posts the factory image URLs.... That would have been SOOO much faster. That's how I got to 4.3. I used fastboot to flash the 4.3 system image....
Sent from my Nexus 7 using Tapatalk 4
khaytsus said:
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
Click to expand...
Click to collapse
I have the zip, where is the script located?
Sent from my Nexus 7 using Tapatalk
redmonke255 said:
I have the zip, where is the script located?
Click to expand...
Click to collapse
./META-INF/com/google/android/updater-script
Remove every line related to power.grouper.so and LNX:5109760 (part partition reference). There's two of each, one apply_check_patch and one apply_patch plus a set_metadata for the power.grouper.so
I could put the file on Dropbox but I think it's more useful to see what's going on than just handing it out. As they say, give a man a fish and you'll feed him for a day. Teach a man to fish and he'll sit out in a boat drinking beer all day.
khaytsus said:
./META-INF/com/google/android/updater-script
Remove every line related to power.grouper.so and LNX:5109760 (part partition reference). There's two of each, one apply_check_patch and one apply_patch plus a set_metadata for the power.grouper.so
I could put the file on Dropbox but I think it's more useful to see what's going on than just handing it out. As they say, give a man a fish and you'll feed him for a day. Teach a man to fish and he'll sit out in a boat drinking beer all day.
Click to expand...
Click to collapse
That's good information. I know last time someone posted details exactly what lines in updater-script needs to be removed (i believe it was 4.3 OTA update). it would be wonderful if someone posts an updated updater-script here, so avoid any kind of other issues.
looking forward to see updater-script attached here!
bunch of thanks!!
small correction on command: run fastboot flash system system.img
in my case, I had to flash boot as well (wrong kernel I guess), otherwise TWRP was giving the emmc error, when flashing the OTA "emmc /dev/block/platform/msm_sdcc.1/by-name/boot 71"
I did fastboot flash boot boot.img
and then flashed the OTA in recovery, followed by SuperSU. And everything was back to normal, including xposed framework, which I had disabled prior to starting the OTA flashing.
I try to install rom using sideload but unfortunately system abort installation after verification! I tried few roms but result is the same in all cases. This is an issue because I recently accidently delete rom on my device, so, only way to recover the system is sideload
Please advice what can I do to improve situation
PS - run_program("/tmp/loki.sh") - Installation aborted I get that message all the time when initiate sideload installation.
Frist i dont believe you can use sideload from stock recovery .
1.will your phone boot?
2.if it can read on everything before doing anything to this phone.
P.s are you rooted
I will watch this thread for your reply i will help you any way i can.
Sent from my LG-LS980 using xda premium
Brick cause of Buil.prop edit
Is there a way to by pass the phone model dll ?
have been trying to revive a friends G2.
after taking the zv8 update, instead of spr my friend for some reason put open, that too not using a build.prop editor,
but he took a copy of the build.prop into windows, does the edit and copies it back to /system/ folder. reboots.
phone stuck on lg boot logo. basically a softbrick.
THE PROBLEM.
because of the edit in build.prop, while trying to flash the stock firmware with the right dll and the right tot file,
it gives a fail saying that the phone model is diff. This error has to be related to the edit done to the build.prop.
now the only way to reboot the phone is to either somehow we are able to replace the build.prop file with a complete stock one.
anybody has any idea as in how to create a flashable build.prop file ? adb sideload works.
i created a build.prop.zip file using zipme in my phone and tried to sideload it, it aborts.
can anybody shed some info on sideload or adb push.
thanks
pvinodnayak said:
Is there a way to by pass the phone model dll ?
have been trying to revive a friends G2.
after taking the zv8 update, instead of spr my friend for some reason put open, that too not using a build.prop editor,
but he took a copy of the build.prop into windows, does the edit and copies it back to /system/ folder. reboots.
phone stuck on lg boot logo. basically a softbrick.
THE PROBLEM.
because of the edit in build.prop, while trying to flash the stock firmware with the right dll and the right tot file,
it gives a fail saying that the phone model is diff. This error has to be related to the edit done to the build.prop.
now the only way to reboot the phone is to either somehow we are able to replace the build.prop file with a complete stock one.
anybody has any idea as in how to create a flashable build.prop file ? adb sideload works.
i created a build.prop.zip file using zipme in my phone and tried to sideload it, it aborts.
can anybody shed some info on sideload or adb push.
thanks
Click to expand...
Click to collapse
I'm stuck in the same boat.
roooted...twrp 2700...then installed CM11/gapps to make it work with "US CARRIERS"
it didnt flash right...although TWRP log says " flash successful
same issue....LG flash tools saying phone model diff (d801) but infact its ls980....go figure
i have a working recovery. how can i download a rom file to the PHONE STORAGE VIA TWRP?
whats my options here guys?
thanks in advance, i hope my noobiness doesnt tickle anyones nerves too much.