Twas the night.......nah that's not gonna work...
Anyways, I had just compiled froyo from android source and wanted to flash it
But apparantly I needed a specific spl when I did "fastboot flashall -w" (one of them being 0.95.0000 or whatever, too lazy to remember..but it was one that didn't support fastboot....which is dumb lol since fastboot is saying to use it)...
So I decided to install engineering spl
I had danger spl and the 2.something radio it needs
I decided to flash it from recovery
BRICK!
So really g1s are impossible to brick...if you flash radio and spls from fastboot not recovery
(Most of this knowledge is from a thread about g1s and spls and bricking that I'm too lazy to link to)
What happens is that recovery FORCES the g1 to boot to recovery on next boot...even if you press buttons
And with a mismatched radio/spl recovery will not start
So you have a brick...
Moral: use fastboot not recovery
Anyways so my solution...
I had a really messed up rogers dream that had a cracked screen and bad ribbon cables...
Pretty much everything was broken except for the motherboard...
Well I decided to try and put this rogers motherboard into my tmobile g1
It worked!
Even booted up into the rom I used to have (biffmod) on the rogers dream before it got screwed up beyond usability
I am posting from my g1 with a rogers motherboard in it as I speak...post....
Moral 2: you can mix motherboards between dreams
One problem is that this ROM still has the keymap for the rogers dream and my home and call button don't work
Hopefully flashing a new rom it will detect the tmobile keyboard
Well this was fun...but I don't know if I'm gonna try to flash my aosp froyo or not again...
Comment please on how you manage to flash a compiled aosp froyo...maybe ill try flashing engineering spl again through fastboot this time
Edit: oh and I like this motherboards vibrate more
Its quieter...
The old one rattled like crazy
So this actually a very win situation
I got Frayo back on and everythings beautiful
In a rom's zip there is this file:
META-INF\com\google\android\updater-script
Try to open it and read the first lines, there are the asserts generally (the part that tells to the device that particular SPL/Radio/Files are needed to proceed the install)
Here's an example of an assert:
assert(getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire");
assert(getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.0013d");
This assert checks many things, with logical operators (|| that's or; == that's equal; "" that's a string; () that's an argument; etc). If you've ever programmed, you'll understand very fast how to change the assert to make it less agressive of checking this things and anothers and not let you install.
The previous assert cheched that the device, or product, ot board where "trout" or "sapphire". Also it needs an specific bootloader ("1.33.0013", or "1.33.2013", or"1.33.3013", or "1.33.0013d").
It's an good idea tho check the updater-script that's in your zip installation file, view what installs it, add/remove asserts and unwanted things, and then, proceed to install it safely from recovery and the SPL/Radio combo that you prefer. Also, it's an good idea to flash an alternative kernel (ezterry one's are very good).
Remember that the only thing that's really recommended to install from fastboot is the SPL and the Radio. Other things are installable from wherever you want (fastboot, OS, recovery) without an potential hard brick risk.
So, if you want to install an ROM (AOSP FroYo as you described), it's not needed to install it from fastboot, and it will not represent an brick risk if it really is only a ROM installer what you have.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Oh, and if you can paste here the updater-script it would be usefull, more than one buddy will say you how to change it to let you install everithing by a correct and safe way.
Yes yes I know all of that
I'm using fastboot because the compiled output is not an update.zip
Its all the image files and I am supposed to do "fastboot flashall"
Its alright though...I got cm6 source working
That will work
Sent from my HTC Dream using Tapatalk
It should be also fun to convert your images to a zip format.
When you flash those full images, you don't know if it will flash more things than needed. Zip files give you more control, and the updater-script also.
The "fastboot flashall" command is kinda risky with images that touchs radio/spl/partitions layouts/etc. It's really recommended to do a wipe of everithing from fastboot when you're installing this images, and also, of course, know what those images will install and be carefull to have the right pre-requisites to don't harm the device.
Good to know you got it working after all !
Alright maybe putting images into zips will be an adventure for later
As of now, the AOSP froyo source and built images are in the deep dark room of a PC's deleted files
Thanks for the tip about flashall!
frankdrey said:
Alright maybe putting images into zips will be an adventure for later
As of now, the AOSP froyo source and built images are in the deep dark room of a PC's deleted files
Thanks for the tip about flashall!
Click to expand...
Click to collapse
No need for flashall
instead of using
Code:
make
use
Code:
make otapackage
You will find a zip ready for flashing
if you are building cm6 then use
Code:
squisher
to optimise the zip
have a look in the opticharger script to make improvements like replacing pngcrush with something better
Scrip said:
No need for flashall
instead of using
Code:
make
use
Code:
make otapackage
You will find a zip ready for flashing
if you are building cm6 then use
Code:
squisher
to optimise the zip
have a look in the opticharger script to make improvements like replacing pngcrush with something better
Click to expand...
Click to collapse
Thanks
And here I was about to go and start extracting the images and writing an updater-script
And I went back to AOSP
CM6 has too many missing files that I don't want to go through the trouble of finding
frankdrey said:
...And here I was about to go and start extracting the images and writing an updater-script...
Click to expand...
Click to collapse
OTA packaging is easier and more simple, I agree... but something is true... fighting with those extractions and updater-script is kinda funnier
Happy source-compiling
Alright I have the zip and all
It checks for the spls though
Should I just remove that from the script?
And try with DangerSPL?
DangerSPL is a port of the mytouch spl right?
Maybe I shoulda built for mytouch?
Also, it looks like it patches recovery after install.
Is that safe? Should I remove the entire folder and entry in the update script?
You must do a little change.
First, open the updater-script, then find the bootloader assert
It will be like this:
assert(getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.0013d");
Just be shure to add the SPL version that you've installed on your phone already. For example, if I've a 1.33.2222 bootloader, then the change will be this:
assert(getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.2222" ||
getprop("ro.bootloader") == "1.33.0013d");
It doesn't matter if you put the new bootloader assert on the beginning or at last or in the middle, it'll be the same. Also, you can delete some asserts if you want to. Be carefull to keep right the sintax.
And the recovery thing, it's better to delete that part, zip will give less troubles whithout that part. And better to delete it from the script and the zip!
I recommend you to use the 1.33.0013d SPL, it'll give you extra RAM and is fully compatible with AOSP FroYo. Just be shure that after flashing the ROM, you flash the right kernel to let the OS boot up.
And remember, if you use Amon_RA recovery, you'll need to re-sign the zip that you modify, if you don't do it, the verification part of the flashing will fail.
Ok thanks I thought all of that too, just wanted to make sure
Oh, and I forgot it...
DON'T edit the script with notepad on windows, it leaves an "Error 6" in recovery when flashing.
In windows you can use notepad++ (google it, it's free), or if you're using other text editor just be shure that the "Enter" (new line in text) key is on right encoding, it's kinda of Unicode if I've good memory yet
mishamosher said:
Oh, and I forgot it...
DON'T edit the script with notepad on windows, it leaves an "Error 6" in recovery when flashing.
In windows you can use notepad++ (google it, it's free), or if you're using other text editor just be shure that the "Enter" (new line in text) key is on right encoding, it's kinda of Unicode if I've good memory yet
Click to expand...
Click to collapse
Yes I have edited them before
Related
OK, this started out mostly for my own amusement but it worked so I thought I would put this out there for anyone who wants to mess with it.
This is the Amazon Browser (Silk / Cloud9) that just shipped on the Kindle Fire. Someone asked if it could be ported so I gave it a shot. Just a few files to get it working.
BUT....to be more reasonable for use on a phone I think it needs some graphics tweaking as this was intended for a 7" tablet.
Something to tinker with if someone wants to...flash the file in recovery or you can extract and push the files as well. There are (2) apps and a few lib files. I only tested this on my Tbolt running BAMF Forever, so beyond that I can't guarantee anything but "in theory" it should work on just about any android rom since it's dependencies are the lib files.
I would double check and make sure you don't have any of these libs already as overwriting them could cause issues, but likely they don't already exist.
DOWNLOAD HERE
Thanks mate Will try, Gonna throw this on my transformer as well and see how well it works
Pyrot1c said:
Thanks mate Will try, Gonna throw this on my transformer as well and see how well it works
Click to expand...
Click to collapse
If it doesn't and you know how to do a logcat, give me the output of the logcat file and I can see if additional dependencies are needed.
I had a lot of feedback on Rootzwiki and while many had it working, some on CM7 and a couple of other ROMs had FC issues.
I have a Nook Tablet now and I'm hoping we get root soon on it, I'd like to see how it does on the Nook.
Tried to install this using cwm on my cyano touchpad...got an Assert Failed getprop("ro.product.device") == "mecha" || getprop("ro.build.product") == "mecha" || getprop("ro.product.board") == "mecha" E:Error in /sdcard/dropbox/Amazon_Browser.zip(Status 7)
Going to try to do it manually.
sytanek said:
Tried to install this using cwm on my cyano touchpad...got an Assert Failed getprop("ro.product.device") == "mecha" || getprop("ro.build.product") == "mecha" || getprop("ro.product.board") == "mecha" E:Error in /sdcard/dropbox/Amazon_Browser.zip(Status 7)
Going to try to do it manually.
Click to expand...
Click to collapse
You will need to use a different updater script for another device, or edit the existing to work on the device. You could likely just remove the getprop line from the script to get it to work.
Cm7 having FC issues here too. I guess I'll check Rootz to see if any progress has been made there.
Is this Thunderbolt specific or would this work with other phones, too?
yahoowizard said:
Is this Thunderbolt specific or would this work with other phones, too?
Click to expand...
Click to collapse
I guess reading two posts above yours is a little inconvenient
Let me rehash it for ya...In order to put this on any other device you will need a different update script...in layman's terms...no
*Madmoose* said:
I guess reading two posts above yours is a little inconvenient
Let me rehash it for ya...In order to put this on any other device you will need a different update script...in layman's terms...no
Click to expand...
Click to collapse
Oh, whoops. I just saw that "Tried to install this using cwm on my cyano touchpad...got an Assert Failed getprop("ro.product.device") == "mecha" || getprop("ro.build.product") == "mecha" || getprop("ro.product.board") == "mecha" E:Error in /sdcard/dropbox/Amazon_Browser.zip(Status 7" stuff he was referring to and just didn't bother to read what he responded. My bad, but yeah, I guess not for us then until someone decides to port it over.
Hi guys, so my problem is this. After my tablet went into infinite boot I flashed my galaxy Tab 10.1 GT-P7500 with a restore ROM(ICS 4.0.4)that i had saved, but now when I try to flash CM10 throught CWM 6.0.xx I get a status 7 error.
Any one had the same problem?
Thanx!
I have download CM10 again for my device but I still get a status 7 error, anyone know how to fix this???
Thanx in advance!
drefcom said:
I have download CM10 again for my device but I still get a status 7 error, anyone know how to fix this???
Thanx in advance!
Click to expand...
Click to collapse
Flash the latest recovery from droidbasement, which is in the CM10 folder you've downloaded.
Status 7
Getting status 7 error, I am finding a lot of 'solutions' so far none have worked. Does anyone have a current solution? Using CM 10.1 on Galaxy 10.1 rooted with Clockwork Mod Recovery v4.0.0.4. Not my first ( or second root), but I'm still basically a noob.
!!! Solution for status 7 error in cwm !!!
A final solution for the status 7 problem is described below (this can be a little tricky but won't harm your device ):
1.Extract the ROM in a new folder, but remember the name of the ROM so you can repack it later for flashing...
2.Go to this address: ROM FOLDER ( the folder originally containing META-INF and system folders and boot.img)\META-INF\com\google\android\
3.open the "updater-script" file with notepad++ or another code editor...
4.the model checking assert is perhaps placed in the first line or is spread over the few first lines, and is this:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
this wicked (!) but sometimes useful model checking prevents flashing on some devices, mostly when flashing Cyanogenmod 10.1...
to tell the CWM system to omit that, you can turn it to a comment (!) by placing a "sharp" sign (#) in the beginning of the line, that will make it like this:
#assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
5. Happy Flashing!
sorry, I forgot: it doesn't matter if you flash a P7510 ROM on P7500, but I haven't tested it reverse (flashing P7500 ROM on P7510)...
Thanks!!!
Many, many thanks, this solution works!!
arashtarafar said:
A final solution for the status 7 problem is described below (this can be a little tricky but won't harm your device ):
1.Extract the ROM in a new folder, but remember the name of the ROM so you can repack it later for flashing...
2.Go to this address: ROM FOLDER ( the folder originally containing META-INF and system folders and boot.img)\META-INF\com\google\android\
3.open the "updater-script" file with notepad++ or another code editor...
4.the model checking assert is perhaps placed in the first line or is spread over the few first lines, and is this:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
this wicked (!) but sometimes useful model checking prevents flashing on some devices, mostly when flashing Cyanogenmod 10.1...
to tell the CWM system to omit that, you can turn it to a comment (!) by placing a "sharp" sign (#) in the beginning of the line, that will make it like this:
#assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
5. Happy Flashing!
sorry, I forgot: it doesn't matter if you flash a P7510 ROM on P7500, but I haven't tested it reverse (flashing P7500 ROM on P7510)...
Click to expand...
Click to collapse
This is a port of [ROM][KK][4.4]CyanAOSP KK4.4 for the Samsung Captivate.
All the hard work was done by ts1506 so spam his thanks button!
Main Features
1. Fast, stable and intended for gamers
2. Built from CM11 source with O3 optimizations, heavily debloated , no 3rd party apps are installed.
3. Trasparency and other KitKat effects enabled
4. Additional tweaks ( vary from version to version )
5. For those people who love ROMs with lots of themes , customizations , apps etc , please leave now , you will be disappointed , this ROM is not for you.
DOWNLOAD CyanAOSP v3.4.0
DOWNLOAD ts1506 GAPPS
DOWNLOAD ART COMPATIBLE GAPPS
If you need more customization install Xposed Framework and Gravity Box: most of the Gravity Box mods will work.
A special thank to pawitp, Alberto96, mohammad.afaneh and cannondaleV2000 for the kernels.
OLD RELEASES:
DOWNLOAD CyanAOSP v2.9.0
DOWNLOAD CyanAOSP v2.8.0
DOWNLOAD CyanAOSP v2.6.0
Not Working For Captivate I-897
When selecting the ROM for update it pauses for a second or two and gives the following error:
Installing update...
This package is for "galaxys.galaxysmtd.GT-I9000.GT-I9000M.GT-i9000T" devices this is a "SGH-I897"
E:Error in /storage/sdcard1/CyanAOSP-KK4-v1.1.0.zip
(Status 7)
Installation aborted.
viiron said:
When selecting the ROM for update it pauses for a second or two and gives the following error:
Installing update...
This package is for "galaxys.galaxysmtd.GT-I9000.GT-I9000M.GT-i9000T" devices this is a "SGH-I897"
E:Error in /storage/sdcard1/CyanAOSP-KK4-v1.1.0.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
1. After you flash for the first time it gives you this message.
2. Now you have to reboot recovery.
Then the new recovery will appear and you can flash.
3. Enjoy
Sorry i did not mention this.
OP updated with instructions
Its ART Working or does get bootloops?
...the tiny italic text...
Hello, I dirty flash over slim 4.3 and boot ok and seems to work ok but have 1 problem. settings FC when clicking Developers Options. It supposed to work if I wipe everything?
Seems fast and stable apart from that.
Thanks!!
ktouy said:
Its ART Working or does get bootloops?
...the tiny italic text...
Click to expand...
Click to collapse
Yes, ART works.
But you need to install ART compatible gapps (find the link in my CM11 thread)
carlosgardel said:
Hello, I dirty flash over slim 4.3 and boot ok and seems to work ok but have 1 problem. settings FC when clicking Developers Options. It supposed to work if I wipe everything?
Seems fast and stable apart from that.
Thanks!!
Click to expand...
Click to collapse
At the moment I am not running this, on the rom I am running now developer options works, but device settings FC.
Do a nandroid backup, try to see if wiping data makes it works.
And you can also restore your backup later.
Awesome! Thanks!
...the tiny italic text...
Monfro said:
Yes, ART works.
But you need to install ART compatible gapps (find the link in my CM11 thread)
At the moment I am not running this, on the rom I am running now developer options works, but device settings FC.
Do a nandroid backup, try to see if wiping data makes it works.
And you can also restore your backup later.
Click to expand...
Click to collapse
I resolved clearing Settings data. Thanks!
Monfro said:
1. After you flash for the first time it gives you this message.
2. Now you have to reboot recovery.
Then the new recovery will appear and you can flash.
3. Enjoy
Sorry i did not mention this.
OP updated with instructions
Click to expand...
Click to collapse
Yea this didn't work either. I did the usual..wiped data/factory reset, wipe cache, tried to install rom and received error. rebooted recovery, flashed again and got the same message. did this a few times with no luck.
I'm coming from HellyBean (Android 4.3.1) 10242013
For ****s and giggles I just flashed AoCP 6.4.1u and that flash went well. But even trying from that rom and redownloading the CyanAOCP-KK4 it gives the same error.
Nevermind it was my fault. I was downloading the copy from andromirror (since it was faster) than the sucky ass time/bandwidth limiting site. But since I got that one it installed just fine.
Monfro said:
1. After you flash for the first time it gives you this message.
2. Now you have to reboot recovery.
Then the new recovery will appear and you can flash.
3. Enjoy
Sorry i did not mention this.
OP updated with instructions
Click to expand...
Click to collapse
On your next build, extract the updater script, open it with notepad ++ and remove the following lines at the top. Then save and replace back into your zip.
Code:
assert(getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T");
anwarkhan25 said:
On your next build, extract the updater script, open it with notepad ++ and remove the following lines at the top. Then save and replace back into your zip.
Code:
assert(getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T");
Click to expand...
Click to collapse
I guess they are removed...
i just now checked it..
and the rom installs fine for me..
anwarkhan25 said:
On your next build, extract the updater script, open it with notepad ++ and remove the following lines at the top. Then save and replace back into your zip.
Code:
assert(getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T");
Click to expand...
Click to collapse
Might also want to take a look at the following code changes so ro.vold.switchablepair works again for those of us that have broken internal sd cards: https://github.com/aperezdc/android_system_vold/commit/14231cf55570643e49c481dca5cf2a3f3249792f
viiron said:
Might also want to take a look at the following code changes so ro.vold.switchablepair works again for those of us that have broken internal sd cards: https://github.com/aperezdc/android_system_vold/commit/14231cf55570643e49c481dca5cf2a3f3249792f
Click to expand...
Click to collapse
He isn't building from source, he's just porting. I don't he'll be able to include those code changes.
I have to say my Cappy loves this Rom. Its really smooth and stable. Im using Dalvik, tried Art for a while but I prefer Dalvik till all the apps I use work with it. Thanks, my Captivate is 3 years old and runs perfect with this. I not use the phone a lot but previous Roms i used deplete the battery fast in standby but not this. With light usage but wifi and location enabled its been 25 hours and have 57% battery. Great work!!
Thanks!
Yeah just put this on my wife's cappy. I am impressed, runs really smooth didn't have to mess with overclocking.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Version 1.3.0 posted.
Changelog
1. CM 11 source synced as of 01/12
2. Advanced Settings added into launcher (mDNIE and TV Out working now)
3. Launcher3 included in ROM ( Same as Google Launcher, but 1/10th size and without google now integration )
4. CM Account removed.
5. Slimmed down a little (from 153MB to 147MB)
6. NeatKernel by mohammad.afaneh
Depending on the system partition your Captivate is using installing CyanAOSP 1.3.0 with NeatKernel may give error about different partition layout and if try to flash it gonna delete data.
If so do this:
1. Make a nandroid backup of CyanAOSP 1.1.0
2. Flash CyanAOSP 1.3.0
3. Restore data nandroid backup of CyanAOSP 1.1.0
4. Wipe dalvik+cache and Reboot device
Do these steps one after the other, staying in recovery from point 1 to point 4.
asharx said:
Yeah just put this on my wife's cappy. I am impressed, runs really smooth didn't have to mess with overclocking.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thanks!!! I'm using yesterdays along with the neat kernel, and it works fine for me! Plain, fast, and stable.
Sent from my SGH-I897 using xda app-developers app
Can we get some screenshots? Does it look exactly like 4.4 with transparent statusbar, and swipe from left to enter google now?
Monfro said:
Version 1.3.0 posted.
Changelog
1. CM 11 source synced as of 01/12
2. Advanced Settings added into launcher (mDNIE and TV Out working now)
3. Launcher3 included in ROM ( Same as Google Launcher, but 1/10th size and without google now integration )
4. CM Account removed.
5. Slimmed down a little (from 153MB to 147MB)
6. NeatKernel by mohammad.afaneh
Depending on the system partition your Captivate is using installing CyanAOSP 1.3.0 with NeatKernel may give error about different partition layout and if try to flash it gonna delete data.
If so do this:
1. Make a nandroid backup of CyanAOSP 1.1.0
2. Flash CyanAOSP 1.3.0
3. Restore data nandroid backup of CyanAOSP 1.1.0
4. Wipe dalvik+cache and Reboot device
Do these steps one after the other, staying in recovery from point 1 to point 4.
Click to expand...
Click to collapse
Curse you hotfile! I hate hot file and it won't let me download ! Grrrr... Anyone have a mirror please?
I have a moto X1058 with:
fastboot-ghost_retar-user-4.4.2-KXA20.16-1.26-24-release-keys-cid12-Latam-AR.zip
bootloader unlocked
rooted with supersu
philz_touch_6.41.6-xt1058.zip custom recovery
The update to 4.4.3 came so I dl it, but the update wont work because of my custom rom (I think) so I have to modify the updater-script inside the official OTA Blur_Version.161.44.26.ghost_row.Latam.en.AR.zip if not, I always got the "Status 7" error message.
So first I delete the bold lines:
mount("ext4", "EMMC", "system", "/system");
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/ghost_retar/ghost:4.4.2/KXA20.16-1.26/24:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/ghost_retar/ghost:4.4.3/KXA21.12-L1.22/58:user/release-keys" ||
abort("Package expects build fingerprint of motorola/ghost_retar/ghost:4.4.2/KXA20.16-1.26/24:user/release-keys or motorola/ghost_retar/ghost:4.4.3/KXA21.12-L1.22/58:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
assert(getprop("ro.product.device") == "ghost" ||
getprop("ro.build.product") == "ghost" ||
getprop("ro.product.device") == "ghost" ||
getprop("ro.build.product") == "ghost");
ui_print("Verifying current system...");
(I thinks this makes the checks pass... I dont know if this will brick the phone if the OTA update is for different from the phone model)
Then I run the update from clockworkmod recovery I have, it gives an error about some APKs that are expected to be on my phone, but arent because I root uninstall them, so it wont update.
Then I delete the each line giving errors, i.e. plusone.apk music2.apk cloudprint.apk etc (each one I uninstalled)
i.e. if I had root uninstall cloudprint.apk I had to delete the lines:
apply_patch_check("/system/app/CloudPrint.apk", "6ae7e170d4f44c6e0f42f200b3861102b86fe92c", "df3f0829bf636b8719245296533bb9e4ca2b62ce") || abort("\"/system/app/CloudPrint.apk\" has unexpected contents.");
and
assert(apply_patch("/system/app/CloudPrint.apk", "-",
6ae7e170d4f44c6e0f42f200b3861102b86fe92c, 3643274,
df3f0829bf636b8719245296533bb9e4ca2b62ce, package_extract_file("patch/system/app/CloudPrint.apk.p")));
Then I tried again the update and it worked
Hope it helps in someway...
PS: to get the OTA zip update I have to let the OTA update asks me to be downloaded, let it download, then with a root file explorer went to /cache/... on the phone and looked for the Blur_Version.161.44.26.ghost_row.Latam.en.AR.zip
If you are on the stock rom the OTA.zip is intended for, but just rooted and removed/changed things (like editing the build.prop, removed bloat APKs, etc), then it is relatively safe to unzip the OTA.zip, edit the manifest file to eliminate some of the checks, then re-zipping and manually applying.
sebadamus said:
....
(I thinks this makes the checks pass... I dont know if this will brick the phone if the OTA update is for different from the phone model)
...
Click to expand...
Click to collapse
The first 3 bold lines in your post show that the update is looking for a specific ROM and version be on your phone by looking in the /system/build.prop file that is currently on your phone, and if your phone doesn't match that, it wont install. Deleting them as you have, the OTA.zip could be applied to any phone. However, some files still wont get updated because their checksum in the manifest wont match the version on the phone (or in your case were not on the phone). That would either cause the OTA to fail, or the wrong versions might get placed on the phone.
If the OTA is for a different mode phone (XT1053 vs XT1058), or different rom (i.e. its a 4.4.3 update and you are applying it to a phone with stock 4.4), then it can get dangerous because you'd end up with mismatched files on your phone, or files that could be incompatible with your model. That is why there is a version check before the OTA installs.
Thanks KidJoe! So if my update is the right one, and the updated files haven been modifiend on my phone from its stock version, but I have a modified recovery, rooted phone or build.prop modified, this way is the only I could find to update applying OTA updates.
I could update to 4.4.4 from 4.4.3 (motox 1058 rooted, custom recovery philz) :good:
Ok guys,, been a long time since ive updated my vs995, an old old version of resurection remix back in the day. I remember there was a fix for it, i think it was the meta tag or something back in the day was wrong and id have to change it or something... It wont let me flash anything vs995..
Any suggestions on how to correct it? Thanks
Try updating your twrp. Here is my latest vs995 build (thread is here). Basically I suspect you're running one of the old "Elsa" twrp builds when what you're trying to flash may have stopped checking for it. This is all is if you're getting an error like "E3004: This package is for device: vs995; this device is elsa". It can be manually bypassed by deleting a line like
Code:
assert(getprop("ro.product.device") == "vs995" || getprop("ro.build.product") == "vs995" || abort("E3004: This package is for device: vs995; this device is " + getprop("ro.product.device") + "."););
in the updater-script file a few folders deep in the meta-inf folder of the zip.
Did you happen to download these roms with chrome on your phone? Chrome won't download them correctly because it thinks it's a harmful file. On the PC version you can choice to download anyway. On the Android version I haven't figured out how to do that yet.