[Q] I9505G OTA Upgrade Fails - Galaxy S 4 Q&A, Help & Troubleshooting

I rooted my I9505G running 4.4.2 bit did not replace the boot loader or the ROM. I just installed Supet-SU.
I've had two 4.4.3 OTA downloads but they fail an assert for build.prop. I've checked \system\build.prop and it if unaltered and contains the string the assert is linking for.
Do I need to unroot before upgrading? I just assumed that I would have to reroot after upgrading. I didn't expect a fail as I haven't altered the boot loader.

Yes you'll need to flash original FireWire with Odin but before proceeding with the flash run triangle away it should be ok then
Sent from my GT-I9505 using Tapatalk

FireWire? What's that? I don't think I flashed anything like that.

ruidh said:
FireWire? What's that? I don't think I flashed anything like that.
Click to expand...
Click to collapse
I think he means "Firmware" :highfive:
ruidh said:
I rooted my I9505G running 4.4.2 bit did not replace the boot loader or the ROM. I just installed Supet-SU.
I've had two 4.4.3 OTA downloads but they fail an assert for build.prop. I've checked \system\build.prop and it if unaltered and contains the string the assert is linking for.
Do I need to unroot before upgrading? I just assumed that I would have to reroot after upgrading. I didn't expect a fail as I haven't altered the boot loader.
Click to expand...
Click to collapse
*SOLUTION: Take a look this guide for flash android 4.4.3 in your device: HERE

Thanks. I'll give that a try.

Joku1981 said:
I think he means "Firmware" :highfive:
Click to expand...
Click to collapse
I'm not sure about Odin here. I never altered the stock recovery.
*SOLUTION: Take a look this guide for flash android 4.4.3 in your device: HERE
Click to expand...
Click to collapse
That page has some problems. Power+VolUp is needed to boot into recovery, not Power+VolDown. I can get into recovery and select install from external memory. I copied the update onto my sdcard but it still fails with the same assert fail
Verifying update package...
assert failed: get.prop("ro.product.device")== "jgedlte" || [...]
checking \system\build.prop I see the line
ro.product.device=jgedlte
as clear as day.
Build KOT49H.S001.131204
Android version: 4.4.2
Baseband version: I9505GUEUCML4

ruidh said:
I'm not sure about Odin here. I never altered the stock recovery.
That page has some problems. Power+VolUp is needed to boot into recovery, not Power+VolDown. I can get into recovery and select install from external memory. I copied the update onto my sdcard but it still fails with the same assert fail
Verifying update package...
assert failed: get.prop("ro.product.device")== "jgedlte" || [...]
checking \system\build.prop I see the line
ro.product.device=jgedlte
as clear as day.
Build KOT49H.S001.131204
Android version: 4.4.2
Baseband version: I9505GUEUCML4
Click to expand...
Click to collapse
It's not my problem if you don't know read.

I followed Method 2. I see what you're saying now.

None of these upgrade methods worked. I still had assert failures. I removed SuperSU after restoring all changes I made to /etc.
Somehow this morning the phone failed to connect to data services. Several apps failed when they tried to access the network.
I eventually reflashed a 4.4.3 rooted image from here http://forum.xda-developers.com/showthread.php?t=2772043 and restored my Titanium Backup.

OTA upgrade to 4.4.4 succeeded after turning of SuperSU and reverting my change to \etc\permissions

Related

OTA update in update.zip format with root options

The update in conventional zip format, with root options is here!
P
Works mint! I was running Modoco 1.3 ROM, heres the steps I performed:
recovery install: update-nexusone-ERE27-signed.zip
recovery install: update-nexusone-radio-32.24.00.22U_4.03.00.21_2-signed.zip
./fastboot-linux boot boot.ERE27.superboot.img
./fastboot-linux flash zimage zImage-2.6.29.6
./adb remount
./adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Can I flash this manually WITHOUT being rooted?
I posted a thread on updating without root: http://forum.xda-developers.com/showthread.php?t=627533
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
I'm completely stock rom / not rooted and I just did this:
http://androidforums.com/nexus-one/41504-how-force-2-2-2010-ota-update.html#post316090
1. Get the update from Google: http://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip
2. Put the update on your SD card & rename it to update.zip
3. Boot in recovery mode (hold down trackball + power)
4. Go to bootloader -> recovery
5. Now there's a picture of a droid with a triangle
6. Press the power button + volume up
7. Apply sdcard:update.zip
8. Updating
9. Reboot system now
10. Enjoy the multitouch
Click to expand...
Click to collapse
Worked great.
Thanks Paul. That's what I first tried, and it failed. I posted the details here, but haven't heard anything back yet.
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Mine is ROOTED, but stock, so.....
tonyx3 said:
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Paul22000 said:
Can I flash this manually WITHOUT being rooted?
Click to expand...
Click to collapse
yes, just did it 5 min ago
PhantomRampage said:
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Click to expand...
Click to collapse
http://www.nexusforum.net/nexus-one-help-forum/493-how-manually-retrieve-new-update-your-nexus-one.html#post2000
check that guide out, it was simple and easy to follow...
Thanks JHaste.
But those are pretty much the exact instructions I followed that gave me the error.
My phone is rooted, but running the stock rom.
No custom rom, no patched browser.
The only changes I've made since rooting it are to copy some Thai fonts into the fonts directory.
The exact specifics of my error are posted in:
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Very similar to what PhantomRampage listed, but a slightly different cause, I think... (his is an error on Browser.apk)
JHaste said:
-Removed quoted link since i cant post them yet-
check that guide out, it was simple and easy to follow...
Click to expand...
Click to collapse
Thanks for trying but as i said before, i tried that and it fails because i have an unlocked bootloader.
Sorry if my first post was confusing, ill try again.
I unlocked my bootloader and rooted my N1 the other day, i also modified and added some files to get pinch-to-zoom working on the native browser. To do that i followed some tutorial on theunlockr, i cant post direct links so google it and you'll find it easily.
So, now i want to apply the new OTA update but it fails, either because i have root access or because i tampered with the browser files im guessing.
Knowing all that, what can i do to install the new update?
Also, will i have to download patched updates from now on since i rooted my phone? I'm really hoping i dont have to; i'd prefer to install the ota updates as they come out officially.
might have found a solution
check out:
forum (dot) androidcentral (dot) com / google-nexus-one/6469-will-my-n1-receive-ota-ere27-update-cyanogen-mod (dot) html
seems to be just what i was looking for but i think i want to re-flash the stock firmware instead, i want to stay as stock as possible so i can install future OTA updates without having to go through all this trouble. Can anyone help me with that please?
Anyways, i hope my link will help some people. Sorry for the double post
Closing Double Thread (it's also at Development).
Please do not duplicate threads if not necessary.

4.2 Update Recovery Error - Unique Issue

I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
JFMFT said:
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
Click to expand...
Click to collapse
dont know how to fix the error, but there is a newer bootloader version (4.13)
http://forum.xda-developers.com/showthread.php?t=1989319
Have you flashed a custom kernel? Some of the custom kernels also update that file so it is no longer stock, and hence it fails the assertion check on upgrade.
You can download the original stock 4.1.2 file here:
http://forum.xda-developers.com/showpost.php?p=34057950&postcount=221
:good:
Forgot to mention, you'll also need the stock 4.1.2 kernel installed if it isn't already, you can grab a copy here:
http://forum.xda-developers.com/showpost.php?p=33030559&postcount=4
Cheers,
Dave.
I have the same issue with assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so").
I have the stock kernel 4.1.2 and even installed 4.13 bootloader but this error is still there.
I'm under 4.1.2 stock, unlocked/rooted, that's all.
Any idea how to solve that ?

Phone not booting after attempt to update 4.4

So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?
bankmaggot said:
So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?
Click to expand...
Click to collapse
Update: I was able to get to the recovery mode hitting down+power. I'm kind of lost at this point. Just give me 4.3 anything at this point.:crying:
I am in the same boat!! Any ideas, i have tried to do a sideload but i get an error installing //sideload.zip
checking for md5 file
skipping md5 check : no md5 file found
warning no file_contexts
file_getprop: failed to stat "/system/build.prop": No such file or directory
e:error executing updater binary in zip '//sideloader.zip'
download factory image and flash it via fastboot..for instructions -->Click Me!
anto.danny said:
download factory image and flash it via fastboot..for instructions -->Click Me!
Click to expand...
Click to collapse
Brilliant, that fixed. Thank you :good:

Moto G 4G/LTE 4.4.4 OTA - 21.1.46.en.EU (XT1039)

Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
Updates from Android 4.4.3 (21.1.31.peregrine_reteu.reteuall.en.EU) to Android 4.4.4 (21.1.46.peregrine_reteu.reteuall.en.EU)
Update brings:
Android 4.4.4 Kitkat
SD Card Fixes
Requirements:
21.1.31.en.EU peregrine (Moto G 4G) --> WILL NOT WORK IF en.US, en.BR, OR en.UK
Locked bootloader ONLY:
1. You should get the OTA notification. Otherwise go to Settings --> About Phone --> System Updates to Download & Install.
2. If it says latest (and you are on 4.4.3), Download the OTA here and place in root internal SD directory.
3. Repeat Step 1
4. Done
Unlocked bootloader + Root/Recovery ONLY
1. Follow this thread and flash the latest 4.4.4
OR MANUALLY
1. You should get the OTA notification. Otherwise go to Settings --> About Phone --> System Updates to Download & Install. If you have recovery error (stock recovery) or nothing happens in recovery and it keeps restarting (custom recovery) then go to Step 2.
2. You may have altered your system partition (e.g. modified hosts file, uninstalled system apps). If it's reversible (try disabling Xposed, restoring hosts file) you can try and undo it and attempt to install again. If this does not work, you will need restore /system partition to stock by flashing just the system.img chunks through fastboot (from stock firmware).
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
NOTE: If you feel uncomfortable to do this and are happy to stay with 4.4.3, then fastboot erase cache to stop phone restarting and trying to update.
3. Once flash is complete, reboot and go back to Step 1 to reinstall OTA.
4. Still no luck?? Download the OTA here and place in root internal SD directory. If you have stock recovery go to Settings --> About Phone --> System Updates to Download & Install. Otherwise go to CWM/TWRP and Install the OTA.
Well, first of all, my sd card worked fine on 4.4.3, I had no single problem with it...
Wenn I updated to 4.4.4 and rebooted the phone, the first messagge I saw was: sd card unexpectedly removed, I really was in shock...
Motorola, what the hell did you do??????
So now I think I'm gonna downgrade te 4.4.3 again...
jkoetsier said:
Well, first of all, my sd card worked fine on 4.4.3, I had no single problem with it...
Wenn I updated to 4.4.4 and rebooted the phone, the first messagge I saw was: sd card unexpectedly removed, I really was in shock...
Motorola, what the hell did you do??????
So now I think I'm gonna downgrade te 4.4.3 again...
Click to expand...
Click to collapse
Can't say I've had any problem with Android 4.4.3 or 4.4.4 with SD card. So it hasn't affected me that way. Did you try reinserting and rebooting?
Ok, so I tried this, and when trying to flash Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip using cwm-touch I get this:
Code:
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/peregrine_reteu/peregrine:4.4.3/KXB21.14-L1.31/27:user/release-keys or motorola/peregrine_reteu/peregrine:4.4.4/KXB21.14-L1.46/42:user/release-keys; this device has .
E:Error in /data/media/0/Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip
(Status 7)
Installation aborted
I looked the compilation number in about phone, and it's this: KXB21.14-L1.31
And the system version is: 21.1.31.peregrine_retgb.retgball.en.GB retGB
The only system modification I had done was install Xposed, and some modules. But I disabled the modules and uninstalled it before trying this.
Some help would be great =)
Edit: Tried with TWRP and I get a similar error.
Got it installed thanks to your guide.
Had to root again after the update, and reinstall busybox.
Thanks again !
Seems that there are even different versions of soft for Europe, I have vs 21.1.31.pregrine_retgb.retgball.en.GB.retgb (XT1039) and my phone does not provide any update yet. Anyone here with this system version?
gartzen said:
Ok, so I tried this, and when trying to flash Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip using cwm-touch I get this:
Code:
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/peregrine_reteu/peregrine:4.4.3/KXB21.14-L1.31/27:user/release-keys or motorola/peregrine_reteu/peregrine:4.4.4/KXB21.14-L1.46/42:user/release-keys; this device has .
E:Error in /data/media/0/Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip
(Status 7)
Installation aborted
I looked the compilation number in about phone, and it's this: KXB21.14-L1.31
And the system version is: 21.1.31.peregrine_retgb.retgball.en.GB retGB
The only system modification I had done was install Xposed, and some modules. But I disabled the modules and uninstalled it before trying this.
Some help would be great =)
Edit: Tried with TWRP and I get a similar error.
Click to expand...
Click to collapse
Appears to be a mismatch. I would not advise to install this OTA if you do not have en.EU even though you have the same model number....
I believe there are many variations sold around the world including US (XT1045), BRAZIL (XT1040), EUROPE (XT1039), and now UK (XT1039). Here in Australia we use en.EU because of the same LTE bands.
I guess I'll have to wait my OTA to tell me there's an update, or a CM version for our phone!
Thanks anyway
Work in XT1045?
Luckily I fixed the sd card issue by formatting it...
Incredible, all 3g 444 versions are out, the 444 eu lte is out, the only missing yet is the 444 eu 3g
It works, sadley I had to restore the system partition. Afterwards most systemfiles fc's. Gladly I had my downloaded OTA backed-up. Afterwards I could only flash the OTA with a custom recovery.
Now everything works again and is updated.
reef2009 said:
It works, sadley I had to restore the system partition. Afterwards most systemfiles fc's. Gladly I had my downloaded OTA backed-up. Afterwards I could only flash the OTA with a custom recovery.
Now everything works again and is updated.
Click to expand...
Click to collapse
Recommend to clear cache and dalvik cache after restoring system partition. The OTA download is provided in the OP if required. Glad it worked out.
vpnair said:
Recommend to clear cache and dalvik cache after restoring system partition. The OTA download is provided in the OP if required. Glad it worked out.
Click to expand...
Click to collapse
I did clear cache and dalvic, So I don't know what's the problem.
Besides that 4.4.4 fixes all fc's.
Since last year I don't have the time to figure out what's wrong but it works and that's the thing
AlbertoJOG said:
Work in XT1045?
Click to expand...
Click to collapse
I don't think it does. I have one too but we have the US version and they have the EU. Guess we just gotta wait.

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

Categories

Resources