Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
Hi all,
I'm trying to replace the font on bubor's CM11 ROM by means of flashing one on of the ZIPs available at http://forum.xda-developers.com/goo...-fontster-betas-flashable-font-packs-t2513985
I am using bubor's TWRP v2.7.1.
The problem I first encountered when trying to flash a font was the error message "Error executing updater binary" and thus the flashing "Failed". Based on the advice at http://forum.xda-developers.com/showthread.php?t=2290009 , I figured it would probably be a good idea to replace the update-binary with the one found in my ROM's ZIP, so I did that.
However, the ZIP still doesn't flash. Although I no longer get the "Error executing updater binary" message, now TWRP simply tells me "Error flashing zip" without offering me any explanation.
Please can you help with this, and apologies for the noob question. I have tried installing the ZIP from both internal and external SD. My SD's are swapped - could that have something to do with it?
- downlaoded http://www.mediafire.com/download/40x5qm44a24p0dg/CantarellFontPack.zip
- downlaoded http://dualhoki.vim.hu/bubor/dev/keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
bubor said:
- downlaoded /CantarellFontPack.zip
- downlaoded keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
Click to expand...
Click to collapse
I'm sorry for not being detailed enough.
I tried following your steps but unfortunately the flashing still failed. I eventually got it to work after a combination of actions, but I think the most crucial one was changing the write permissions of the \system\fonts folder from "drwxr-xr-x" to "drwxrwxrwx".
Thanks for your efforts in any case, I really appreciate all the work you're doing.
Hi,
i have install TWRP v2.8.0.0. I have several zip file install. Durin the Installation i see the following error messages. For example, I installed the following file over the TWRP Install Button.
Code:
quantal-preinstalled-phablet-armhf.zip
and
Code:
quantal-preinstalled-armel+manta.zip
Code:
Updating partition details...
E:error opening '/data/ubuntu/dev/rmai11'
E:error: Not a directory
E:error opening !/data/ubuntu/dev/ram9'
E:error: Not a directory
. . .
I have no answer to the error messages.
Can you help me?
Advance many thanks for your support.
Love greeting of
Stefan Harbich
Hello everyone,
shame that still nobody has reported. I have indeed managed to install TWRP v.2.8.0.0, but I have the Android OS 4.2.2 somehow uninstalled when the wipe command. Now I have no OS on my tablet. Well, all for over a week. I just tested a Flash Boot ZIP file to the Android version 4.2.2 Least again, to be able to install on TWRP. Different ZIP's from the XDA developers could not be installed. Either because the zip could not be installed or the possible Ubuntu Toch Version.
I would be very happy if one of you could adopt my problem, because I have not been as conscientiously as you.
Advance for your support and warm Dankf
Kind regards Stefan Harbich
I have the same problem. I've tried to install Ubuntu on Samsung S3 and now in TWRP - whatever I do (install, backup..) - these errors accur
Btw, everything works, but there are about 30 lines of errors like this about missing directories.
Any ideas?
Hello all...
I'm not sure when this happened, but I am suddenly unable to save screenshots. Thus far I have tried:
*Rebooting
*Fixing permissions - phone is unable to mount \data
*Wiping internal storage - can't mount \data
*Deleting and recreating the screenshot directory via ES File Explorer - Will not allow me to delete the screenshot directory AT ALL...
*same as above, via windows - lets me delete the file, make a new one and will show correctly in windows... but on device, folders will not update
I have never flashed this phone back to stock... this is also my first problem with the device ever.... lol
phone info:
bootloader - unlocked
S-off
4.4.2
software number nV M8
Kernel: 3.4.0-g88dafb7
I believe I am on the nameless rom (flashed upon getting the device about a year ago and haven't flashed anything else... )
Thanks everyone...
Got it working... flashed back to stock.
Hi All,
I have a LG G3 (European d855) that was previously running CyanogenMod 13, a long time ago it refused to install future updates either over the air or flashing, I left it a long time as it was only a secondary phone I used for work.
I have since decided to flash a fresh OS (Lineage and also tried AOSCP) as the only important thing on this phone was my contacts. At first TWRP was giving me an error 7 no matter what ROM I downloaded, I read to change the script in META-INF to bypass the security feature to remove the "Asserts" re-package and try again. So I used the adb push command to add the new packaged file to the device and attempted to flash. I now get a new error "could not find META-INF/com/google/android/update-binary" in the zip file (the binary file was never edited).
Also as a side note I can no longer connect with adb when I had no issues before. The phone currently has no OS and refuses to install any package.
Could I possibly have corrupt partitions?
Any help will be much appreciated