Database Develop

Samsung Captivate Multiple issues

So I'm trying to install a ROM onto my Samsung Captivate. I've went through this process multiple times, although not with this phone. Im in CWM recovery (Version 2.x, which is probably the problem), first I realize my ext-SD won't mount. I find a simple work around and load the .zip onto my internal SD. So I try to install it again and and it it has some long error message (I'll post it on here in a few minutes), ending with "Installation aborted".
Any ideas of what I need to do? My only idea is to update recovery but I can't get around to that right now. I'm just trying to avoid anymore roadblocks.
Sent from my Desire HD using xda app-developers app
EXACTLY WHAT IT SAYS ON MY PHONE:::::
ClockwordMod Recovery v.2.5.1.0 SpeedMod ULFK
-- Installing: SDCARD:cm-10-20121004-NIGHTLY-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.product.device") == "
captivate" I I getprop("ro.build.product") == "ca
ptivate" I I
getprop("ro.product.device")
== "captivatemtd" I I getprop("ro.build.product")
== "captivatemtd" I I
getprop("ro.product
.device") == "SGH-I896" I I getprop(ro.build.pro
duct") == "SGH-I897" I I getprop("ro.build.p
roduct") == "SGH-I897"
E:Error in /mnt/sdcard/cm-10-20121004-NIGHTLY-ca
ptivatemtd.zip
(Status 7)
Installation aborted.

That means you have a device/ Rom file mismatch. However, that seems to be in order since you say you have a captivate and you are flashing the file for captivate. Your build prop must be modified by your current Rom. Try flashing a kernel first, then redoing the installation from the new recovery.
Sent from my SGH-I777 using xda premium

Okay. Quick question, can I flash a kernel .zip using the recovery I have right now?
Sent from my Desire HD using xda app-developers app

Try loading a gingerbread stock rom that has been updated to contain cwm recovery using 1-click package(there is thread with all 1-clicks). If you never had a gb rom before then select a package with bootloader so that you'll have gb bootloader too. Then flash CM10. That should work.

[Q] Paranoid Android on I9305 (LTE)

Hello,
I was trying to install the Paranoid Android ROM (http://forum.xda-developers.com/showthread.php?t=2203301).
I did everything as always but unfortunately I receive an error:
Code:
CWM-based Recovery v.5.5.0.4 :: CF-v.1.5
-- Installing: /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
Finding update package...
Opening update package...
[COLOR="DarkRed"]Installing update...
assert failed: getprop("ro.product.device") == "m3" || getprop("ro.built.product") == "m3" ||
getprop("ro.product.device") == "i9305" || getprop("ro.built.product") == "i9305" ||
getprop("ro.product.device") == "GT-I9305" || getprop("ro.built.product") == "GT-I9305"
E:Error in /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
(Status 7)
Installation aborted[/COLOR]
Im not a software developer for mobile phones but I guess it is trying to tell me, that the ROM which I'm trying to install isnt working on my device.
But I am absolutely sure that I got an I9305 as you can see on the attached screenshot.
Any ideas?
I have also redownloaded the ZIP and tried it multiple times but always ended up with the same error.
I really would appreciate any help!

Celaniry said:
Hello,
I was trying to install the Paranoid Android ROM (http://forum.xda-developers.com/showthread.php?t=2203301).
I did everything as always but unfortunately I receive an error:
Code:
CWM-based Recovery v.5.5.0.4 :: CF-v.1.5
-- Installing: /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
Finding update package...
Opening update package...
[COLOR="DarkRed"]Installing update...
assert failed: getprop("ro.product.device") == "m3" || getprop("ro.built.product") == "m3" ||
getprop("ro.product.device") == "i9305" || getprop("ro.built.product") == "i9305" ||
getprop("ro.product.device") == "GT-I9305" || getprop("ro.built.product") == "GT-I9305"
E:Error in /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
(Status 7)
Installation aborted[/COLOR]
Im not a software developer for mobile phones but I guess it is trying to tell me, that the ROM which I'm trying to install isnt working on my device.
But I am absolutely sure that I got an I9305 as you can see on the attached screenshot.
Any ideas?
I have also redownloaded the ZIP and tried it multiple times but always ended up with the same error.
I really would appreciate any help!
Click to expand...
Click to collapse
Try to install the latest CWM!
Sent from my GT-I9305 using xda premium

update your recovery. I suggest philz

Awesome! This ROM really rocks!
Is there any way to disable the 3 button-elements as my phone already has real buttons?

yes, Google it

Celaniry said:
Awesome! This ROM really rocks!
Is there any way to disable the 3 button-elements as my phone already has real buttons?
Click to expand...
Click to collapse
If you go into the settings where you set tablet, phablet or stock ui mode you can go deeper into those settings from there. Can't remember what they're called right now. In stock ui you can reduce the soft buttons percentage to 0.
Hope this will help you.
Sent from my GT-I9305 using xda premium

"semi bricked" i9305 using Odin Mobile App
Hi guys,
I decided to flash Paranoid Android 4.2.2 onto my SIII i9305 and was successful using the Odin Mobile App after several other failed options.
I was about 5 minutes into enjoying the new ROM and I thought wait a second have I installed the Google Apps to the phone (NB I had placed the gapps on the external SD card along with the ROM.
In a moment of utter stupidity I opened up the Odin Mobile App again and selected flash gapps. Then when the phone was rebooting it just stuck on the recovery screen and when I selected "apply update from external storage" and chose the ROM (pa_i9305-3.65-9JUL2013-gokussjx.zip). It then displayed
E: failed to verify whole-file signature
E: signature verification failed
I cannot get beyond the recovery screen at all and when I select reboot system now the "Samsung Galaxy S3 GT i9305" screen appears 3 times and then returns back to the recovery screen.
I have no idea what to do and have googled possible solutions and come up with one that looks like a possible fix: iandroidblog.com/how-to-unroot-galaxy-s3-lte-i9305/
Waiting for my girlfriend to bring home her PC from work so I can let you know how it goes but in the interim does anyone have any ideas?
Cheers!

Try to get into download mode and flash a stock image using odin.
After that, you can root and flash CWM/TWRP again and flash your favorite custom ROM.
Edit: Make sure to wipe/factory reset when going back to Stock from AOSP/AOKP as the layout is totally different and may cause boot loops in itself (from my own experience)

latest version
PA i9305 3.99 RC2
The latest version incl. Modem and working Kernel.

BACON - i9305 trouble
tried to install PA today,on my i9305, but got error, not suported deveice, pakage for BACON a00001, this is m0
Is it possible to have PA on my device?
No i install CW, but i really would like PA.
Thanks!

Link to Paranoid ROM
Can anybody pleaase help me?
I cant find a paranoid rom that lets me install it.WHen install i get error. So therfore please give me a link for rom, and for gaps for the rom.
Thanks so much in advance!!!
Torsoen

torsoen said:
Can anybody pleaase help me?
I cant find a paranoid rom that lets me install it.WHen install i get error. So therfore please give me a link for rom, and for gaps for the rom.
Thanks so much in advance!!!
Torsoen
Click to expand...
Click to collapse
what error?

[Q] LG P880 Error 7 and Error 6. X3 or P880?

Hi everyone.
I'm new to Android(And I hate it). I jumped to Android from Apple iOS few days ago.
My LG P880 has 4.1.2 JB installed which is very laggy.
I tried to install 4.4.2 many times but It gives error statuses 7 and 6.
Error:
assert failed: getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880"
E:Error in /external_sd
i already have the latest version of CWM, i flashed it through rom manager.
I used this method too. but useless...
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Please tell me what to do now..
Why the ROMS are recognizing my device as X3 but not P880?

saqibjdn said:
Hi everyone.
I'm new to Android(And I hate it). I jumped to Android from Apple iOS few days ago.
My LG P880 has 4.1.2 JB installed which is very laggy.
I tried to install 4.4.2 many times but It gives error statuses 7 and 6.
Error:
assert failed: getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880"
E:Error in /external_sd
i already have the latest version of CWM, i flashed it through rom manager.
I used this method too. but useless...
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Please tell me what to do now..
Why the ROMS are recognizing my device as X3 but not P880?
Click to expand...
Click to collapse
do tell which cwm version you have? if it's not 6.0.4.5, flash it manually

Flying_Bear said:
do tell which cwm version you have? if it's not 6.0.4.5, flash it manually
Click to expand...
Click to collapse
I used "recovery-clockwork-6.0.4.5-p880"
How to install manually on my damn "LG 4X HD P880 X3".

saqibjdn said:
I used "recovery-clockwork-6.0.4.5-p880"
How to install manually on my damn "LG 4X HD P880 X3".
Click to expand...
Click to collapse
I believe that @Flying_Bear meant "By not using rom manager", but manually selecting a zip to be flashed after having booted your phone in recovery mode (Power on + Vol down).
Anyhow, let me say that your approach to the problem is not inviting for people to help you. You can be disappointed by the device, but your disappointment can be interpreted as arrogance, and people don't like very much arrogant people asking for help.
Relax and try to enjoy it all the same.

Use phillztouch modified cwm or latest twrp, clearly something is wrong with the one you are using now

[SOLVED] error status 6 and error 7/ X3/P880 model issue.
wow wow wow.. Thanks God.... Finally I installed 4.4.2 Carbon rom on my Phone.
Thank you so much guys for helping me out...
Love you all...
I installed philz_touch_6.12.8-p880 and it worked..
Whoever is facing error 7 or error 6 kindly use this method.
1. Install ADB
2. Unlock bootloader.
3. Root device.
4. Install TWRP first.
5. Go to recovery mode using volume down+Power. and Install "philz_touch_6.12.8-p880"
6. Now Power off phone and Restatrt using Volume up + Power button.
7. Format Factory data, wipe delvik from "advance" menu. Install CUSTOM ROM from sd card option. Install GAPPs and restart your phone.

X3\p880 Naming problem
Sorry if I'm hijacking this thread.
I've got a p880 stuck in a bootloop after installing a custom recovery. Can't remember which one.
The phone is rooted has 4.1.2 on it.
I've tried booting to recovery and wiping the cache and doing a factory reset.
I'm posting here because I tried sideloading 10.2. It fails with error message saying that the phone is an X3 not a p880.
I also tried sideloading phils_touch as mentioned above but get the same error message: the software is for the p880 not the X3.
Can anybody point me in the right direction?
Thanks
Brendan

bpjh56 said:
Sorry if I'm hijacking this thread.
I've got a p880 stuck in a bootloop after installing a custom recovery. Can't remember which one.
The phone is rooted has 4.1.2 on it.
I've tried booting to recovery and wiping the cache and doing a factory reset.
I'm posting here because I tried sideloading 10.2. It fails with error message saying that the phone is an X3 not a p880.
I also tried sideloading phils_touch as mentioned above but get the same error message: the software is for the p880 not the X3.
Can anybody point me in the right direction?
Thanks
Brendan
Click to expand...
Click to collapse
Just one question, have you unlocked the bootloader?
Greetings from my Nexus 7 2013 Flo!

Thanks for the reply.
I've managed to get the phone to work.
Found a software upgrade combination (vol up, connect usb I think), then used LG Mobile support tool. I think I'm back at stock,unrooted firmware!
Ran adb reboot oem-unlock to unlock bootloader.
Tried again to run adb sideload cm-11. Transfers file to phone ok but installation fails with usual firmware is for p880 this phone is an X3.
Tried to root with o4xr but it fails also.
Have checked usb debugging and unknown sources.

bpjh56 said:
Thanks for the reply.
I've managed to get the phone to work.
Found a software upgrade combination (vol up, connect usb I think), then used LG Mobile support tool. I think I'm back at stock,unrooted firmware!
Ran adb reboot oem-unlock to unlock bootloader.
Tried again to run adb sideload cm-11. Transfers file to phone ok but installation fails with usual firmware is for p880 this phone is an X3.
Tried to root with o4xr but it fails also.
Have checked usb debugging and unknown sources.
Click to expand...
Click to collapse
There's a way to get around this.
You have to look in the zip file you want to flash and search for a text file.
In this text file (something with update as far as I remember) there's a line called getprop="X3" (in your case.
Delete this line and you should be good to go.
Sent from my LG-P880 using XDA Premium 4 mobile app

I've unpacked the cm-11 archive using 7zip.
Found a text file called updater-script.
The file starts;
assert(getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880" || abort("This package is for \"p880\" devices; this is a \"" + getprop("ro.product.device") + "\".")
If I delete all of this, save and remake the archive using 7zip it fails with "Verifying Update Package...installation aborted"
I tried changing it to:
assert(getprop("ro.product.device") == "x3" || getprop("ro.build.product") == "x3" || abort("This package is for \"x3\" devices; this is a \"" + getprop("ro.product.device") + "\".")
Same error.

bpjh56 said:
If I delete all of this, save and remake the archive using 7zip it fails with "Verifying Update Package...installation aborted"
Click to expand...
Click to collapse
Use winrar, edit the file from within the archive and just save the changes without changing compression parameters
Check the encoding used with your text manager, use notepad++
In any case your problem is the recovery. Download twrp 2.7 from omni rom's thread
extract zip file there's an recovery.img file
open terminal and execute:
adb reboot oem-unlock
fastboot flash recovery c:/path/to/recovery.img (or drag the file inside the temrinal window)
fastboot reboot

Do you mean delete the first section or change p880 references to x3?
You're right about the recovery.
I installed cyanogen rom manager from play store and installed cm recovery from there. The idea was to try and upgrade from the sdcard.
Now the recovery does not work at all.
Pushing vol down and power I just get a red error message. Same goes for vol up and add usb cable.
Phone still works though.
Will your recovery procedure fix the bootloader?
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Actually I can't flash the recovery image because adb no longer detects my phone.
Not correct, After normal booting of phone it adb does detect it

bpjh56 said:
Do you mean delete the first section or change p880 references to x3?
You're right about the recovery.
I installed cyanogen rom manager from play store and installed cm recovery from there. The idea was to try and upgrade from the sdcard.
Now the recovery does not work at all.
Pushing vol down and power I just get a red error message. Same goes for vol up and add usb cable.
Phone still works though.
Will your recovery procedure fix the bootloader?
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Actually I can't flash the recovery image because adb no longer detects my phone.
Not correct, After normal booting of phone it adb does detect it
Click to expand...
Click to collapse
Did you get the recovery working yet? The red error message upon trying to boot into recovery usually indicates the bootloader isn't properly unlocked. Could you check the secret menu or S/W upgrade mode to see if it's actually unlocked? If that's not the case, restore everything again with the LGMobile Support Tool, unlock the bootloader, check if it's unlocked, flash a custom recovery and try to flash your ROM using that recovery. In that case you shouldn't have to worry about changing updater scripts. Good luck!
Sent from my LG-P880 using xda app-developers app

Used 3845#*880#
Bootloader reported as locked. This after using adb reboot oem-unlock.
If I reinstall using the LG Mobile tool how do I unlock the bootloader?
Will reinstall also repair the bootlaoder?

I''ve reinstalled the firmware using the LG Support tool.
This has fixed the bootloader.
The bootloader is reporting as being locked though after I run adb reboot oem-unlock.

[SOLVED] [Q] Nook HD Only boots to CWM

PROBLEM SOLVED thanks to digixmax for the bootloader zip
http://forum.xda-developers.com/showpost.php?p=57096448&postcount=11
Cyanogenmod 11.
Tablet was acting weird. Wasn't turning on in general, just black. Then I tried to reset it using the n and power buttons for 30 seconds. It did boot up eventually.
Then it froze and rebooted, and ever since only boots to CWM.
I've tried factory reset and reflashing to no avail, only cwm will boot.
I read it might have something to do with bootdata.
Like I said, I got it to work initially after it would only boot to a black screen, then it froze, now this. I'm worried I might have corrupted the EMMC way way back with an older rom.

It's likely that your problem is one that is described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1 (the post was written for the Nook Tablet, but the BCB & BootCnt exist and work same way for the HD/HD+), in which case you can try to reset/restore BCB & BootCnt by flashing flashable_fix_bootdata-hummingbird.zip available at http://www.mediafire.com/download/04qhwylk36sofbl/flashable_fix_bootdata-hummingbird.zip.
If resetting BCB & BootCnt does not help then I'd suggest you try re-installing CM11.

thx for the advice
albeit, I received an error when flashing the file using cwm.
Code:
EMMC CWM-based recovery v6.0.4.6
-- Installing: /external_sd/flashable_fix_bootdata-hummingbird.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /exteranl_sd_flashable_fix_bootdata-hummingbird.zip
(Status 4)
Installation Aborted.

Status 4 is a problem with the script in the zip. Double triple checked search and I've seen it before myself.
http://forum.xda-developers.com/showthread.php?t=2355223
Just a thought that since you can get into cwm, you could try using adb and browsing the emmc to see if its there and intact. twrp (just put it on an sdcard) has a file manager built-in as well. Is that worth doing? If need be you could save files that way too if its still intact.

Thistleknot said:
thx for the advice
albeit, I received an error when flashing the file using cwm.
Code:
EMMC CWM-based recovery v6.0.4.6
-- Installing: /external_sd/flashable_fix_bootdata-hummingbird.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /exteranl_sd_flashable_fix_bootdata-hummingbird.zip
(Status 4)
Installation Aborted.
Click to expand...
Click to collapse
I fixed the error in the file-name of "updater-script" in the flashable zip file.
You can re-download flashable_fix_bootdata-hummingbird.zip and give it another try.

redownloaded the same zip as instructed: flashable_fix_bootdata-hummingbird.zip; in the 1st mediafire link http://www.mediafire.com/download/04...ummingbird.zip you have posted. (which has an uploaded date of 9-21-2014) Same issue.
btw. I have flashed cm11 over this, that will flash (but not fix my nook, still boots only to cwm). However, this update file will not take.
How should this file structure look like unzipped? I keep reading about an update script file. the only file I see named update is buried way deep in some android subfolder
update-binary
updater-script-bootdata

Okay, I figured out what I was supposed to fix to get past error 4
Name: META-INF/com/google/android/updater-script
SHA1-Digest: 29co0QiSKyDerOQ5Ggv0EV16f9g=
so i changed updater-script-bootdata to updater-script in the META-INF/com/google/android/ folder
then...
I got a different error
Code:
assert failed: getprop("ro.product.device") == "hummingbird" || getprop("ro.build.product") == "ovatino"
E:Error in /external_sd_/flashable_fix_bootdata-hummingbird-diff.zip
(Status 7)
Some flag check fails. This is a nook hd with cm11 emmc installed

Thistleknot said:
Okay, I figured out what I was supposed to fix to get past error 4
Name: META-INF/com/google/android/updater-script
SHA1-Digest: 29co0QiSKyDerOQ5Ggv0EV16f9g=
so i changed updater-script-bootdata to updater-script in the META-INF/com/google/android/ folder
then...
I got a different error
Code:
assert failed: getprop("ro.product.device") == "hummingbird" || getprop("ro.build.product") == "ovatino"
E:Error in /external_sd_/flashable_fix_bootdata-hummingbird-diff.zip
(Status 7)
Some flag check fails. This is a nook hd with cm11 emmc installed
Click to expand...
Click to collapse
You need to use a CWM older than v6045. The ones made for CM11 will not work.
Sent from my BN NookHD+ using XDA Premium HD app

The script could be fixed to eliminate status 7 error on cm11 recovery, but without any changes its like leapinlar says.

leapinlar said:
You need to use a CWM older than v6045. The ones made for CM11 will not work.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?

Thistleknot said:
redownloaded the same zip as instructed: flashable_fix_bootdata-hummingbird.zip; in the 1st mediafire link http://www.mediafire.com/download/04...ummingbird.zip you have posted. (which has an uploaded date of 9-21-2014) Same issue.
btw. I have flashed cm11 over this, that will flash (but not fix my nook, still boots only to cwm). However, this update file will not take.
How should this file structure look like unzipped? I keep reading about an update script file. the only file I see named update is buried way deep in some android subfolder
update-binary
updater-script-bootdata
Click to expand...
Click to collapse
Use this link for the corrected zip file: http://www.mediafire.com/download/30leabd7tjeytn4/flashable_fix_bootdata-hummingbird.zip.
Updater-script in folder META-INF\com\google\android\ is indeed the script used to flash BCB and BootCnt into /bootdata.
---------- Post added at 05:10 PM ---------- Previous post was at 04:45 PM ----------
Thistleknot said:
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Click to expand...
Click to collapse
You can get the old version of verygreen's CWM from his CM10.1 thread or from https://www.mediafire.com/#6a4rivb8kkdfu -- the EMMC version is (recovery.img) in his flashable cwm-recovery-ovation-3.zip, the SD version is (ramdisk.cwm) inside his emmc-cwm-early2.1.img or inside verygreen_emmc-cwm-early2.1-boot.zip at https://www.mediafire.com/#6a4rivb8kkdfu (verygreen_emmc-cwm-early2.1-boot.zip has the same complete set of CM10.x compatible SD-based boot/CWM files as emmc-cwm-early2.1.img but packed in a .zip file).

Thistleknot said:
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Click to expand...
Click to collapse
From my HD/HD+ CWM thread linked on my signature.
Sent from my BN NookHD+ using XDA Premium HD app

looks like
Use this link for the corrected zip file: http://www.mediafire.com/download/30...ummingbird.zip.
Click to expand...
Click to collapse
is working. I got past cwm at least.
derp, sorry I missed your [leapinlair] signature links. I swear I looked and didnt' see them.
WORKING GUYS. You guys are really too good to the community.

Upgrade from 18s to 19s - Failed to Update!

I've been trying to upgrade my LeEco S3 to version 5.8.019S. Each time I do it, it gets almost half way through the upgrade process and then says "Failed to update! Cause: Installation failed.". See here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried resetting to factory defaults and clearing data... Nothing works.
Any help is greatly appreciated!

Re-enable any apps you disabled?

abel408 said:
I've been trying to upgrade my LeEco S3 to version 5.8.019S. Each time I do it, it gets almost half way through the upgrade process and then says "Failed to update! Cause: Installation failed.". See here:
I've tried resetting to factory defaults and clearing data... Nothing works.
Any help is greatly appreciated!
Click to expand...
Click to collapse
was your phone rooted?
unroot your phone.
disabled OEM unlock in Developer settings

smokin901 said:
was your phone rooted?
unroot your phone.
disabled OEM unlock in Developer settings
Click to expand...
Click to collapse
It was rooted, but now it's fully stock. OEM unlock is disabled and all apps are back on the system.

If system partition has been modified (rooted or even accessed in read/write mode by TWRP) then updates will not work.

wpbear said:
If system partition has been modified (rooted or even accessed in read/write mode by TWRP) then updates will not work.
Click to expand...
Click to collapse
So the very act of doing fastboot boot twrp.img and subsequent "Keep Read Only" in TWRP modifies the system partition? How so?
I've got some stock TWRP images of 18S and 19S (generated using a temporary boot into TWRP - rather than flashing recovery - and keeping system read-only). I suppose, though, that since restoring them to the system partition would require modifying it in the first place, that breaks OTAs?
I've also got the 19S OTA zip. Not sure what would need to be modified to flash it, though.

rczrider said:
So the very act of doing fastboot boot twrp.img and subsequent "Keep Read Only" in TWRP modifies the system partition? How so?
I've got some stock TWRP images of 18S and 19S (generated using a temporary boot into TWRP - rather than flashing recovery - and keeping system read-only). I suppose, though, that since restoring them to the system partition would require modifying it in the first place, that breaks OTAs?
I've also got the 19S OTA zip. Not sure what would need to be modified to flash it, though.
Click to expand...
Click to collapse
You need to modify part which verifies the installation.
Post installation script from ota
Sent from my Le X526 using Tapatalk

smokin901 said:
You need to modify part which verifies the installation.
Post installation script from ota
Click to expand...
Click to collapse
META-INF/com/google/android/updater-script ?
Code:
get_device_compatible("le_s2_na") == "OK" || abort("This package is for \"le_s2_na\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Start to check root...");
ifelse(root_check() == "root", abort("The phone has root!
"), ui_print("The phone is OK, start to OTA update.
"));
ui_print("Source: LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801810091S/39:user/release-keys");
ui_print("Target: LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801910272S/61:user/release-keys");
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801810091S/39:user/release-keys" ||
getprop("ro.build.fingerprint") == "LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801910272S/61:user/release-keys" ||
abort("Package expects build fingerprint of LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801810091S/39:user/release-keys or LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801910272S/61:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:11091240:76343e8329de11d0279fc48e2e1cc2ea3a70e391:11091240:22302e5527893ac327ff04fa478d19532c1d1c05") || abort("\"EMMC:/dev/block/bootdevice/by-name/boot:11091240:76343e8329de11d0279fc48e2e1cc2ea3a70e391:11091240:22302e5527893ac327ff04fa478d19532c1d1c05\" has unexpected contents.");
# ---- radio update verification ----
ui_print("Verifying radio-update...");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/modem:79092224:580467b7ef83c3f71ad6991e3624b77a1379c8fa:79092224:55c73357a7923ba6ce7099c2c3a4bccdba049ed6") || abort("\"EMMC:/dev/block/bootdevice/by-name/modem:79092224:580467b7ef83c3f71ad6991e3624b77a1379c8fa:79092224:55c73357a7923ba6ce7099c2c3a4bccdba049ed6\" has unexpected contents.");
apply_patch_space(79092224) || abort("Not enough free space on /system to apply patches.");
if (range_sha1("/dev/block/bootdevice/by-name/system", "134,1,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,878904,884736,884738,884993,884995,885503,917503,917504,917506,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "165a725a008e94b0fde64d19bd4ead3d310134d1" || block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
abort("system partition has unexpected contents");
endif;
# ---- start making changes here ----
ui_print("Patching system image after verification.");
show_progress(0.900000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "136,0,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "127f8d73efdc54efcd9ed606b81300f0c4a5c6a0" then
if range_sha1("/dev/block/bootdevice/by-name/system", "142,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,883371,884224,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,923940,949760,950272,950274,950786,982528,983040,983042,983554,1015296,1015808,1015810,1016318,1040310,1040311") == "9192c3ab8d6affd1d695787c2ec307d8f235a74c" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
ui_print("Patching boot image...");
show_progress(0.100000, 10);
apply_patch("EMMC:/dev/block/bootdevice/by-name/boot:11091240:76343e8329de11d0279fc48e2e1cc2ea3a70e391:11091240:22302e5527893ac327ff04fa478d19532c1d1c05",
"-", 22302e5527893ac327ff04fa478d19532c1d1c05, 11091240,
76343e8329de11d0279fc48e2e1cc2ea3a70e391, package_extract_file("patch/boot.img.p"));
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("patch/firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("patch/firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("patch/firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("patch/firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("patch/firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("patch/firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("patch/firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("patch/firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("patch/firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("patch/firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("patch/firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("patch/firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
package_extract_file("patch/firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("patch/firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1bak");
), "");
msm.boot_update("finalize");
package_extract_file("patch/firmware-update/devinfo.bin", "/dev/block/bootdevice/by-name/devinfo");
package_extract_file("patch/firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
apply_patch("EMMC:/dev/block/bootdevice/by-name/modem:79092224:580467b7ef83c3f71ad6991e3624b77a1379c8fa:79092224:55c73357a7923ba6ce7099c2c3a4bccdba049ed6",
"-", 55c73357a7923ba6ce7099c2c3a4bccdba049ed6, 79092224,
580467b7ef83c3f71ad6991e3624b77a1379c8fa, package_extract_file("patch/firmware-update/NON-HLOS.bin.p"));
package_extract_file("patch/firmware-update/misc.img", "/dev/block/bootdevice/by-name/misc");
package_extract_file("patch/firmware-update/splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("patch/firmware-update/oemconfig.img", "/dev/block/bootdevice/by-name/OEMCONFIG");
package_extract_file("patch/firmware-update/ddr.bin", "/dev/block/bootdevice/by-name/DDR");
set_progress(1.000000);

rczrider said:
META-INF/com/google/android/updater-script ?
Click to expand...
Click to collapse
check what is the output of
fastboot oem device-info
from the script this is the part you should remove
Code:
if range_sha1("/dev/block/bootdevice/by-name/system", "136,0,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "127f8d73efdc54efcd9ed606b81300f0c4a5c6a0" then
if range_sha1("/dev/block/bootdevice/by-name/system", "136,0,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "127f8d73efdc54efcd9ed606b81300f0c4a5c6a0" thenif (range_sha1("/dev/block/bootdevice/by-name/system", "134,1,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,878904,884736,884738,884993,884995,885503,917503,917504,917506,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "165a725a008e94b0fde64d19bd4ead3d310134d1" || block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
abort("system partition has unexpected contents");
endif;
else abort("system partition has unexpected contents after OTA update");
endif;
do this if and only if you have not modified any of the apps that comes with stock rom..
is there a stock rom zip available for S3. like it is available for S2(Indian Version).

smokin901 said:
check what is the output of
fastboot oem device-info
Click to expand...
Click to collapse
Code:
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
If I run fastboot oem unlock-go, it changes to:
Code:
(bootloader) Device unlocked: true
But of course that doesn't stick after a reboot.
smokin901 said:
from the script this is the part you should remove
do this if and only if you have not modified any of the apps that comes with stock rom..
Click to expand...
Click to collapse
Thanks! I've already updated my S3, but I should have another one here early next week that I can test it out on. If anyone else on 18S wants to give it a shot, it can be downloaded here: https://mega.nz/#F!SE9hlbxa!Q2ZTtBaW16Qccb77BT1Pxw
Just rename "IFXNAOP5801910272S-edited.zip" to "update.zip", place in the root of your internal storage, go to Settings > System update > settings (3 dots at top right) > Local update
smokin901 said:
is there a stock rom zip available for S3. like it is available for S2(Indian Version).
Click to expand...
Click to collapse
Not that I'm aware of. Unfortunately.

Im in the same boat. trying to get my previously TWRP/rooted now on stock recovery and rom - S3 to update but is giving me the failure notice.
I dont quite understand the above, can you dummy it down for me?
Thanks
Rico

iamrico00 said:
Im in the same boat. trying to get my previously TWRP/rooted now on stock recovery and rom - S3 to update but is giving me the failure notice.
I dont quite understand the above, can you dummy it down for me?
Thanks
Rico
Click to expand...
Click to collapse
which part do you need help with?

I downloaded the file and placed it in the root directory on the phone. Went to update and clicked the 3 dots to do a manual update. It went to the update screen and it still says failed.
Do you have a recovery? I flashed one for the s3 I found on some website. Can you upload that? I doubt it's the issue but it may be.
Thanks Rico

I know why OTAs are not working, if you try and flash the OTA update zip with TWRP it will say that the update is for the S2_na and that the device is the S2.
in other words, the unrooting and stocking process stated here for our S3 converts our phones in S2s, which means, OTAs will never install.
Solution here is, wait for a Stock S3 Rom.

Ok. So how do I return to stock so I can get OTA update?
Rico

CpaoV said:
I know why OTAs are not working, if you try and flash the OTA update zip with TWRP it will say that the update is for the S2_na and that the device is the S2.
in other words, the unrooting and stocking process stated here for our S3 converts our phones in S2s, which means, OTAs will never install.
Solution here is, wait for a Stock S3 Rom.
Click to expand...
Click to collapse
Your probably using the wrong version of TWRP...Only the Chinese version works right, not the new official one for S2,and anyways unless you take out a part of update script,and I have not figured it all out as yet no update will work on S3 if you have used twrp in any way on the phone it seems

britdude said:
Your probably using the wrong version of TWRP...Only the Chinese version works right, not the new official one for S2,and anyways unless you take out a part of update script,and I have not figured it all out as yet no update will work on S3 if you have used twrp in any way on the phone it seems
Click to expand...
Click to collapse
I tried with both versions of TWRP, I tried with stock recovery as well, I cleaned all my phone and flashed everything back manually, and yet, it still gives error when trying to update either via OTA or via Zip.
So, it's either a bad update file or my phone was permanently banned from OTAs until a full clean stock ROM is available.
Currently, I gave up, this 19S is pretty good actuallt, today I just got 6.5 hrs SOT (Lots of multitasking between Chats and Media, PoGo, Shooter games, youtube, downloading stuff) and it's fluent enough, now I kinda don't wanna ruin that.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
---------- Post added at 07:00 PM ---------- Previous post was at 07:00 PM ----------

Not a bad update, like I have said, once we use twrp ,OTA's will fail..
I am looking into what can be changed in OTA file to get it to install

Just restating what many of you have already said. I never had TWRP installed, but did use the "fastboot boot twrp.img" command to install SU and root my phone. I never touched the stock recovery, and the OTA failed even after a factory reset.
Of course this update isn't really a huge one, but I would like to have compared the camera changes and possibly use the stock apps, such as remote, if they fixed the permissions (constantly asking for location and access to contacts seemed fishy to me).
This does however pose a bigger problem when and if a new 7.0 Nougat update is released and those of us who can't OTA are stuck on 19s indefinitely.
I wonder if those with the Pro3 are having the same issue. At least the Pro3 has the option of installing available custom roms.

You Relocked Bootloader ?