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.
Related
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
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
Hello people,
I got a big problem with my tablet.... so.... I use Rom Manager to do the upgrade....
In Rom Manager:
- Download ROM
- CyanogenMod Nightlies
- CyanogenMod 10 20121202
That's all ok... but now i have a P7510 without 3G....
So i go to the clockworkmod folder and i see... the flashed image to my tablet is "cm-10-20121202-Nightly-p4wifi.zip" so... i loose my 3G and in the present moment i can't connect the tablet to the computer... It is simply not recognized.
After this... i go to our friend google... and i find the (Correct ROM ( I Hope ) )....cm-10-20121202-Nightly-p4.zip, but.... when i try to flash this rom... i got this error:
assert failed getprop( ro.product.device ) == p4 getprop( ro.build.product ) == p4
status 7 error
Well ..
So my request is ... can someone help me put the correct ROM on my tablet and get back to 3G and USB?
Thank's a lot!!
Ps--> I forgot to say... i don't have my stock rom backup
mrbouli said:
After this... i go to our friend google... and i find the (Correct ROM ( I Hope ) )....cm-10-20121202-Nightly-p4.zip, but.... when i try to flash this rom... i got this error:
assert failed getprop( ro.product.device ) == p4 getprop( ro.build.product ) == p4
status 7 error
Click to expand...
Click to collapse
Unpack the zip file somewhere, keeping the directory tree intact.
In the folder META-INF\com\google\android, there's a file called "updater-script". Open that with a text editor (but NOT MS Word!! - I use notepad++ on Windows.)
You should see a pair of lines reading:
assert(getprop("ro.product.device") == "p4" ||
getprop("ro.build.product") == "p4");
Or maybe just one line:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
Either way, disable that by inserting "#" at the beginning:
#assert(getprop("ro.product.device") == "p4" ||
# getprop("ro.build.product") == "p4");
Save the new file, rebuild the zip, and it should install fine.
Before ... thanks for your help!
I did what you told me ... I put the # in front of the two lines and looked like this:
#assert(getprop("ro.product.device") == "p4" ||
#getprop("ro.build.product") == "p4");
( I use WordPad to edit the file )
Now I try to install the ROM and now I have another error .... :
E:Error in /sdcard/xxcm-10-20121202-NIGHTLY-p4.zip
(Status 6)
Installation aborted.
k1mu said:
Unpack the zip file somewhere, keeping the directory tree intact.
In the folder META-INF\com\google\android, there's a file called "updater-script". Open that with a text editor (but NOT MS Word!! - I use notepad++ on Windows.)
You should see a pair of lines reading:
assert(getprop("ro.product.device") == "p4" ||
getprop("ro.build.product") == "p4");
Or maybe just one line:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
Either way, disable that by inserting "#" at the beginning:
#assert(getprop("ro.product.device") == "p4" ||
# getprop("ro.build.product") == "p4");
Save the new file, rebuild the zip, and it should install fine.
Click to expand...
Click to collapse
Do not use wordpad. Í suggest downloading notepad++, it's available as standalone (no install required) and doesn't break linux compatible line endings.
Sent from my GT-P7510 using xda app-developers app
Thk's my friend!!!
Tablet 100% working with 3g and wi-fi.
Real a show this rom!!!
Obrigado!!!
Only one question more....
Now i connect the tablet to the computer... but don't works...
Have u any ideia???
If i put in developer mode.... the computer makes a sound... but don't recognize in windows nothing....
Can u help me??
Thk's in advance...
use usb connection settings
mrbouli said:
Only one question more....
Now i connect the tablet to the computer... but don't works...
Have u any ideia???
If i put in developer mode.... the computer makes a sound... but don't recognize in windows nothing....
Can u help me??
Thk's in advance...
Click to expand...
Click to collapse
go to settings, storage and on top right corner you will have usb connection.. click that and check the MTP checkbox... then connect to pc and check.... If it didnt work first time, try unplugging and connecting the cable couple of times...
mrbouli said:
Only one question more....
Now i connect the tablet to the computer... but don't works...
Have u any ideia???
If i put in developer mode.... the computer makes a sound... but don't recognize in windows nothing....
Can u help me??
Thk's in advance...
Click to expand...
Click to collapse
Make sure you're using a Samsung USB cable.
I just spent two days messing around trying to find out why I kept getting failures when plugging a tab into my PC. Cheapo cable doesn't work, but the OEM one does.
Yes it's the original cable of samsung... and i can't connect to the computer
ycharan said:
go to settings, storage and on top right corner you will have usb connection.. click that and check the MTP checkbox... then connect to pc and check.... If it didnt work first time, try unplugging and connecting the cable couple of times...
Click to expand...
Click to collapse
this works! flashed CM10 nightly, then went to Storage and selected MTP, and i rebooted the tablet just in case.
tablet was recognised in Win7
It seems to me that you have a recovery that is for the p4wifi instead of p4. I suggest flashing a recovery for the p4 (like the one here), so that you wont have to deal with this again in the future.
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?
Hi
I've read here https://www.tecnoandroid.it/2018/03...hone-che-dovrebbero-ricevere-android-p-324672 (in Italian) that 90% we won't get pie. I'm a little surprised.
What do you think? Are they wrong?
I didn't expect Pie, cos Mediatek is hard chipset to work with.
At this moment , I would be happy if they just release the touchscreen patch.
I am sick of seeing my TS deteriorating in Oreo.
Gentleman's : Read this : 1 , 2 , 3 , 4 , 5 .
If you read this important information's you find one important news :
1.This CPU's is very similar based on cortex a53 .
2.I can crossport rom to xa1 (lineage os) , and do pie on xa1 .
3.I do port (not tested - problem's with install and pack rom) , of lineage based on 7.1.2 nougat .
Now after do installer I have problem with script .
I plan to do port of pie based on lineage from xa2 to xa1 to december/january of this year !!
Please don't say about xa1 and impossible make pie for this device :')
I need help with make this rom's for xa1 . I welcome developers to work with me
MAREK10747 said:
Gentleman's : Read this : 1 , 2 , 3 , 4 , 5 .
If you read this important information's you find one important news :
1.This CPU's is very similar based on cortex a53 .
2.I can crossport rom to xa1 (lineage os) , and do pie on xa1 .
3.I do port (not tested - problem's with install and pack rom) , of lineage based on 7.1.2 nougat .
Now after do installer I have problem with script .
I plan to do port of pie based on lineage from xa2 to xa1 to december/january of this year !!
Please don't say about xa1 and impossible make pie for this device :')
I need help with make this rom's for xa1 . I welcome developers to work with me
Click to expand...
Click to collapse
Hi
I didn't say "impossible to get pie" I said "won't get pie from official channels".
I'm a Java developer, time allowing, if you need help, just ask :highfive:
Ok . Let's start job Faby if you can help me fix problem number 7 with twrp install
MAREK10747 said:
Ok . Let's start job Faby if you can help me fix problem number 7 with twrp install
Click to expand...
Click to collapse
Ok i can't find the zip, but to solve:
1) unzip the zip ))
2) go to META-INF/com/google/android
3) find updater-script
4) rename it to updater-script.txt
5) edit it with Notepad++ (or similar)
6) find the "assert" method, something like:
Code:
assert( codes, codes, codes);
7) delete the method
ex:
Code:
assert(1,2,3,4);
other code(6);
codes too(7);
becomes:
Code:
other code(6);
codes too(7);
8) SAVE!
9) rename back updater-script.txt to updater-script
10) rezip again
11) done
If you need language help too, just ask me (i know Spanish, French and Italian too)
For the next times, ask me help via Private Messages. I will send you there my backup TA, please patch DRM from stock kernel. Thank you :highfive:
assert don't working , I try with assert and without assert.
I have the same effect with and without ...
Please read log .
assert(getprop("ro.product.device") == "hinoki" || getprop("ro.build.product") == "hinoki" || getprop("ro.product.name") == "full_hinoki" ||
abort("This package is for "hinoki" devices; this is a "" + getprop("ro.product.device") + "".");
assert(getprop("ro.product.device") == "hinoki" || getprop("ro.build.product") == "hinoki" || abort("E3004: This package is for device: Sony XA1.");
ui_print("Target: alps/full_hinoki/hinoki:8.0.0/O00623/1526929025:user/test-keys");
ifelse(is_mounted("/system"), unmount("/system"));
and
assert(getprop("ro.product.device") == "hinoki" || getprop("ro.build.product") == "hinoki" || getprop("ro.product.name") == "full_hinoki" ||
abort("This package is for "hinoki" devices; this is a "" + getprop("ro.product.device") + "".");
assert(getprop("ro.product.device") == "hinoki" || getprop("ro.build.product") == "hinoki" || abort("E3004: This package is for device: Sony XA1.");
ui_print("Target: sony/full_hinoki/hinoki:7.0.0/O00623/1526929025:user/test-keys");
ifelse(is_mounted("/system"), unmount("/system"));
and
assert(getprop("ro.product.device") == "hinoki" || getprop("ro.build.product") == "hinoki" || getprop("ro.product.name") == "full_hinoki" ||
abort("This package is for "hinoki" devices; this is a "" + getprop("ro.product.device") + "".");
assert(getprop("ro.product.device") == "hinoki" || getprop("ro.build.product") == "hinoki" || abort("E3004: This package is for device: Sony XA1.");
ui_print("Target: alps/full_hinoki/hinoki:8.0.0/O00623/1526929025:user/test-keys");
I never believed that XA1 will get Pie - first it has MTK, for enthusiast it may not be a problem, for OEMs it is, coz they need official (aka reliable) SoC code and Mediatek rarely gives more than one update. And it's not flagship or even middle-end with Snapdragon to get more than one update (like X and Compact).
surprisekot said:
przygotuj dla mnie te rzeczy do upgrade prosba nawet na te xperie jedyny tel na ktorego twrp nie dzialaja tylko 3.0.2 odpala...dziwny ten fon
Click to expand...
Click to collapse
English Please.
MAREK10747 said:
assert don't working , I try with assert and without assert.
I have the same effect with and without ...
Click to expand...
Click to collapse
Mate I can't believe you make big claims about bringing lineageOS to the XA1 and then can't work out why you can't flash a ROM made for another device
What exactly did you do??
Clearly you did not extract this ROM to make a proper port or you would of repacked it for the XA1.
Did you just simply change the boot.img within this ROM if so it's highly unlikely it will ever work.
These issues your having are most basic and easily solved where as bringing LineageOS to our device is a huge undertaking involving some major source code editing.
bigrammy said:
English Please.
Mate I can't believe you make big claims about bringing lineageOS to the XA1 and then can't work out why you can't flash a ROM made for another device
What exactly did you do??
Clearly you did not extract this ROM to make a proper port or you would of repacked it for the XA1.
Did you just simply change the boot.img within this ROM if so it's highly unlikely it will ever work.
These issues your having are most basic and easily solved where as bringing LineageOS to our device is a huge undertaking involving some major source code editing.
Click to expand...
Click to collapse
Soo I do port of rom from x603 to xa1 . I start with nougat , because is more easy than oreo to port (for me) . I do all for make good port of rom for this device . I have always problem with fix problems with updater script and updater have problem only !! System and boot was ported fully .
MAREK10747 said:
Soo I do port of rom from x603 to xa1 . I start with nougat , because is more easy than oreo to port (for me) . I do all for make good port of rom for this device . I have always problem with fix problems with updater script and updater have problem only !! System and boot was ported fully .
Click to expand...
Click to collapse
Code:
unmount of /system failed (-1): Device or resource busy
Try This.
In TWRP toggle /system mount or unmount manually and try again.
EG:
If /system IS mounted automatically unmount it and try flash the rom.
If the /system is NOT mounted automatically then mount it and try flash the rom.
bigrammy said:
Code:
unmount of /system failed (-1): Device or resource busy
Try This.
In TWRP toggle /system mount or unmount manually and try again.
EG:
If /system IS mounted automatically unmount it and try flash the rom.
If the /system is NOT mounted automatically then mount it and try flash the rom.
Click to expand...
Click to collapse
Your method don't working ... . More often error is 7 and sometimes after script mod is error 6 in twrp .
MAREK10747 said:
Your method don't working ... . More often error is 7 and sometimes after script mod is error 6 in twrp .
Click to expand...
Click to collapse
I downloaded the ROM from your thread but I think it maybe corrupted as I was unable to extract the system.new.dat.
All that would be normally required to flash the /system and /boot would be.
Code:
ifelse(is_mounted("/system"), unmount("/system"));
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
Everything else could be removed.
I check it tomorrow . Thanks
EDIT : Don't working error code 7 . Failed to update system image
MAREK10747 said:
I check it tomorrow . Thanks
EDIT : Don't working error code 7 . Failed to update system image
Click to expand...
Click to collapse
Yes as said before I think the "system.new.dat" file is corrupted as it fails to unpack even on my PC so I think you will need to recompile it.
Update: Sony said that they will update XA series without specifying which models (they would have said "xa2", maybe there's a chance...