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...
Related
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?
Hello i have a xiaomi redmi note 1w device .i had allready root it and instal twpr recovery
last night i try to flash the new beta rom from the 3g but i get error
can u please advice redmi note 1w is diferent from 3g?
demomi said:
Hello i have a xiaomi redmi note 1w device .i had allready root it and instal twpr recovery
last night i try to flash the new beta rom from the 3g but i get error
can u please advice redmi note 1w is diferent from 3g?
Click to expand...
Click to collapse
i receive a msg that this package is is for 'lcsh_wet_jb9" devices.this is a 'minote'
can u please help
check in the following path of the ROM..... META-INF\com\google\android\
in updater-script
and delete lines similar with below example:
assert(getprop("ro.product.device") == "sample" ||
getprop("ro.build.product") == "sample" ||
abort("This package is for device: samplex; this device is " + getprop("ro.product.device") + ".");
Be careful because if the package is not intended for your device you may BRICK YOUR DEVICE!!!
I think your device is "lcsh92_wet_jb9"
resofty said:
check in the following path of the ROM..... META-INF\com\google\android\
in updater-script
and delete lines similar with below example:
assert(getprop("ro.product.device") == "sample" ||
getprop("ro.build.product") == "sample" ||
abort("This package is for device: samplex; this device is " + getprop("ro.product.device") + ".");
Be careful because if the package is not intended for your device you may BRICK YOUR DEVICE!!!
I think your device is "lcsh92_wet_jb9"
Click to expand...
Click to collapse
check in the following path of the ROM..... META-INF\com\google\android\
in updater-script
can u please advice how to find these and where?
You have to be more precise. Copy the EXACT error so we can help you.
The solution resofty posted helps only if you are trying to install a ROM not intended for your device, which is moreover a WRONG and BAD thing to do.
Probably the problem is another. Copy TWRP output here.
I have an ALE-L21 with B170 and I received the information about the B188 OTA update but, everytime I try to update the system stopped at 7-11%. I have unlocked bootloader and root so I believe that this is the problem.
I decided to anayze the update package that consist of:
three directories:
META-INF
patch
system
and a file:
update.app that I extracted using Huawei update extractor and it contains:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
Click to expand...
Click to collapse
I decided to analyze the updater-script in META-INF that I have attached and analyzing it I found that after verifying the version of the phone:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "hi6210sft/hi6210sft/hi6210sft:5.0/LRX21M/jenkins12081438:user/test-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "hi6210sft/hi6210sft/hi6210sft:5.0/LRX21M/jenkins10091506:user/test-keys");
assert(file_getprop("/system/build.prop", "ro.product.device") == "hi6210sft" ||
file_getprop("/system/build.prop", "ro.product.device") == "hi6210sft" ||
file_getprop("/system/build.prop", "ro.build.product") == "hi6210sft" ||
file_getprop("/system/build.prop", "ro.build.product") == "hi6210sft");
Click to expand...
Click to collapse
it starts to verify the sha1 checksum of files in cust and system directory
assert(apply_patch_check("/cust/channel/tr/xml/global_operator_name.xml", "b3ea5fa1a6affbeaf760e5f8e74d4cf681c57595", "371f5afc57db71120281b063752512e6e4dd6ed8"));
set_progress(0.004016);
[...]
before applying the patch:
apply_patch("/cust/channel/tr/xml/global_operator_name.xml", "-",
b3ea5fa1a6affbeaf760e5f8e74d4cf681c57595, 39876,
"371f5afc57db71120281b063752512e6e4dd6ed8",
package_extract_file("patch/cust/channel/tr/xml/global_operator_name.xml.p"));
set_progress(0.004016);
[...]
I believe that is during this part that something doesn't match after unlocking bootloader and rooting the system.
Is there a way to do a sha1 checksum of the files in cust and system directory and then compare to the one listed in this script?
at the end of the script there are some command that I don't understand:
ui_print("Unpacking new files...");
package_extract_dir("system", "/system");
package_extract_dir("modem", "/modem");
package_extract_dir("3rdmodem", "/3rdmodem");
package_extract_dir("cust", "/cust");
Click to expand...
Click to collapse
but modem and 3rdmodem package are not present anywhere
that is present only in this command:
ui_print("write radio image...");
write_firmware_image("UPDATE.APP", "radio");
Try to full unroot and system files like build.prop and other must be in original format(untouchable)
When I running this version of firmware many times install this OTA over the B170, so if you have EU model(ALE-L21 cust C432) should not be a problem to install it
sokkoban said:
Try to full unroot and system files like build.prop and other must be in original format(untouchable)
When I running this version of firmware many times install this OTA over the B170, so if you have EU model(ALE-L21 cust C432) should not be a problem to install it
Click to expand...
Click to collapse
I already did a full unroot but with no luck.
I never modify build.prop; how could I check if the other system file are in original format? I updated PlayStore to the latest version and integrated in system.
You want to update to 6.0?
If it's already been released the Italian dual sim version, I would install 6.0 happily
Sure, use B560. If not by local update then by fastboot commands...
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.