Database Develop

[Q] Anyone had V20h stock rom for LG Optimus 2x SU660 (Korean Model)?

anyone had the new V20h stock rom for LG Optimus? I only found the SU660(Optimus-2X)_Android_GingerBread_V20h source code from LG
lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU660
Do any of you compiled this into a stock rom?
Because there is already a CyanogenMod 7.1 port for SU660 but it needs V20h stock rom installed
see code.google.com/p/open2x/downloads/detail?name=update-cm-7.1.0-Optimus2X-SU660-KANG-signed-fixed.zip

eatblueorange said:
anyone had the new V20h stock rom for LG Optimus? I only found the SU660(Optimus-2X)_Android_GingerBread_V20h source code from LG
lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGSU660
Do any of you compiled this into a stock rom?
Because there is already a CyanogenMod 7.1 port for SU660 but it needs V20h stock rom installed
see code.google.com/p/open2x/downloads/detail?name=update-cm-7.1.0-Optimus2X-SU660-KANG-signed-fixed.zip
Click to expand...
Click to collapse
update-cm-7.1.0-Optimus2X-SU660-KANG-signed-fixed.zip
Is a test version. Many BUG

七恰八叶 said:
update-cm-7.1.0-Optimus2X-SU660-KANG-signed-fixed.zip
Is a test version. Many BUG
Click to expand...
Click to collapse
I think this kang has no bugs.
It works fine on my su660.
But the kernel is not stable yet.
I heard he (open2x builder) resolved almost all issues.
I'm looking forward to his new kernel.

kitty's_daddy said:
I think this kang has no bugs.
It works fine on my su660.
But the kernel is not stable yet.
I heard he (open2x builder) resolved almost all issues.
I'm looking forward to his new kernel.
Click to expand...
Click to collapse
How did you manage to install, what version of clockworkmod did you use?
I removed assert error by removing the first line in the updater-script
I managed to install it but it goes to a loopless boot animation of cyanogen logo
the installation logs show something similar to these:
set_perm: chown of /system/etc/install-recovery.sh to 0 0 failed: No such file or directory
I already rooted the device using nvflash and installed busy box thru busy box installer in the android market.

eatblueorange said:
How did you manage to install, what version of clockworkmod did you use?
I removed assert error by removing the first line in the updater-script
I managed to install it but it goes to a loopless boot animation of cyanogen logo
the installation logs show something similar to these:
set_perm: chown of /system/etc/install-recovery.sh to 0 0 failed: No such file or directory
I already rooted the device using nvflash and installed busy box thru busy box installer in the android market.
Click to expand...
Click to collapse
P990's int sdcard partition number is 9 ,but su660's is 10.
I think some errors on cwm(for p990) were due to this difference.
But cwm 4.0.0.5 and 3.0.1.5 worked fine on su660. (these support only ext sd)
Try this.

thanks, kitty's_daddy
I managed to install CyanogenMod 7.1 using ClockworkMod Recovery 3.0.1.4 (Modaco R1) using an apk that I found on a korean website. I attached it to this post so that people who have SU660 can install it also.
I installed the CyanogenMod Kang nightly from code.google.com/p/open2x/downloads/list
and it works perfectly except for the camera screen size seems to be in portrait mode or doesn't occupy the phone's screen (having black borders on the screen) but the pictures taken are good. I installed other CyanogenMod for SU660 like cm_su660_full-184.zip that i found from a vietnamese website but it is very buggy and the phone shuts down itself randomly while the update-cm-7.1.0-Optimus2X-SU660-KANG-signed-fixed.zip from open2x seems stable and worked perfectly except for the camera size that doesn't fill up the whole screen. Is there a tweak fix for the camera size like a config to modify perhaps inside the system files? I tried to replace the camera.apk from the system and replace it with the camera from cm_su660_full-184.zip but the screen size is still the same.

eatblueorange said:
thanks, kitty's_daddy
I managed to install CyanogenMod 7.1 using ClockworkMod Recovery 3.0.1.4 (Modaco R1) using an apk that I found on a korean website. I attached it to this post so that people who have SU660 can install it also.
Click to expand...
Click to collapse
I have seen this app, but it is paul's recovery app.
Don't share. It's not free.
And you can fix camera with replacing system/lib/hw/overlay.tegra.so from original CM nightly.
Sent from my CM7 on SU660

thanks kitty's_daddy, I installed the latest kang build and it seems stable now, they fixed the camera and fixed also the in-call bug when making a phone call and fix the mp3 and audio problems . I have no problems with this cyanogemod port for SU660. Open2x uploaded a new kernel too that fixes the black screen bug on the phone

eatblueorange said:
thanks kitty's_daddy, I installed the latest kang build and it seems stable now, they fixed the camera and fixed also the in-call bug when making a phone call and fix the mp3 and audio problems . I have no problems with this cyanogemod port for SU660. Open2x uploaded a new kernel too that fixes the black screen bug on the phone
Click to expand...
Click to collapse
Yes. It's perfect now.

Ive just updated my su660 to v20h but the problem is i cannot root my phone anymore,kindly teach me how did you manage to install this cm7 rom
thanks in advance...

vision2040 said:
Ive just updated my su660 to v20h but the problem is i cannot root my phone anymore,kindly teach me how did you manage to install this cm7 rom
thanks in advance...
Click to expand...
Click to collapse
You can root your su660 with Rusty's awesome nvflash script like p990.
Check here.
And you must change cwm.img if you want restore or back up on su660.
Also CM-kang for su660 was made by open2x kernel builder. here.
All link and the reason is in this thread.

thanks kitty's_daddy one more thing is there a way than i can use my KTF SHOW USIM card cuz' Ive tried already the kyuHyuk rom KTF usim still not working
can you help on how to install this cm7 rom i always have an error when i chose the update file on cmw

vision2040 said:
thanks kitty's_daddy one more thing is there a way than i can use my KTF SHOW USIM card cuz' Ive tried already the kyuHyuk rom KTF usim still not working
can you help on how to install this cm7 rom i always have an error when i chose the update file on cmw
Click to expand...
Click to collapse
I don't know about kyuhyuk rom. I think it is cheat mod.
If you want to install original CM nightly onto su660, you must delete first line in updater-script.
=> assert(getprop("ro.product.device") == "p990" ~~
It checks device to prevent bricking.
I recommend CM-kang-for su660 with open2x kernel.
And what's your cwm version?

i use the 3.0.1 cmw and i use this "update-cm-7.1.0-Optimus2X-SU660-20111126-KANG-signed.zip" and put it to my external sd card but everytime i try to use this update zip it gives an error saying " update aborted blah...blah..
thanks for being noob friendly...

vision2040 said:
i use the 3.0.1 cmw and i use this "update-cm-7.1.0-Optimus2X-SU660-20111126-KANG-signed.zip" and put it to my external sd card but everytime i try to use this update zip it gives an error saying " update aborted blah...blah..
thanks for being noob friendly...
Click to expand...
Click to collapse
Is it paul's cwm3.0.1.4?
You must use paul's 3.0.1.4 or 4.0.0.5 onto su660.
Others has a few errors on su660.
Sent from my CM7 on SU660

i also get error while trying flash" update-cm-7.1.0-Optimus2X-SU660-20111126-KANG-signed.zip. I am using cwm 4.0.0.5.

ganaa said:
i also get error while trying flash" update-cm-7.1.0-Optimus2X-SU660-20111126-KANG-signed.zip. I am using cwm 4.0.0.5.
Click to expand...
Click to collapse
I don't know why it couldn't. It worked fine.
Backup and factory reset, then try install again.
Also, would you upload updater-script at here?
Ps:
Do you know that CM7 is ext4 rom?
If you want to restore stock rom,then you need backtoext3.
You had better copy this into your sd card.

I did back up/ factory reset and tried install few times , but receiving error each time:
assert failed: getprop(''ro.product. device")==SU660 II getprop("ro.build.product") ==su660 etc....
Status 7
Installation aborted.
Pls. help

ganaa said:
assert failed: getprop(''ro.product. device")==SU660 II getprop("ro.build.product") ==su660 etc....
Status 7
Installation aborted.
Click to expand...
Click to collapse
i also have this error too

ganaa said:
I did back up/ factory reset and tried install few times , but receiving error each time:
assert failed: getprop(''ro.product. device")==SU660 II getprop("ro.build.product") ==su660 etc....
Status 7
Installation aborted.
Pls. help
Click to expand...
Click to collapse
I suggest this way.
Extract update zip file.
And open \META-INF\com\google\android\updater-script with notepad++ .
Delete first line all (assert(getprop("ro.product.device") ~ ~ == "su660"); ).
Save & exit.
Zip extracted folder with non-compressed option. (I recommend to use 7zip.)
Try install again.

Can`t install any ICS ROM

I tried to install several ICS ROMs on my Galaxy s, but none of them worked. I did all wipes like 3 times before any rom install... I only managed to boot up SGS2 ICS rom, wich was extremely laggy and etc:L Any advices of what i can do?

Flash back to gb with this kit (unzip, read .txt first)
http://db.tt/MOGZx01S
Then go to slim website and read the installation instructions(use a nightly, not a kernel where you see the choice)
Re read, make sure you are clear what to do, make sure you have all that you need on your internal sd (nightly/i9000 file/ common file/ modem from here http://forum.xda-developers.com/showthread.php?t=1158783
[CM7/MIUI/ICS/CM9][06.01.12] Modems + Bootloaders(MD5)
Proceed, take your time, be near a computer, breath deeply, don't panic of things go wrong, post on thread of they do.

Try this.
Download the latest CM9 nightly (you will find it if you Google it)
Go to recovery
Wipe
Format system (mount and storage)
Flash in this order
CM9
Reboot recovery
Modelxxx.xxx
Slim common
Reboot.
Then enjoy
Sent from my GT-I9000 using Tapatalk 2

trying to install AOKP, it gives me error:
assert failed: run_program("/tmp/updater.sh") == 0
Click to expand...
Click to collapse
let me try install other ICS rom.... all life of my galaxy s it was on stock roms.now i decided to update to ICS. first time trying to upgrade to ICS (only used to flash GB roms before)

What exactly is your process in flashing ics, (from gb)
Sent from my GT-I9000 running remICS-UX using XDA premium

calum96 said:
What exactly is your process in flashing ics, (from gb)
Sent from my GT-I9000 running remICS-UX using XDA premium
Click to expand...
Click to collapse
Here is it:
1) get into recovery
2)Data / cache / dalvik-cache wipe
3) format /system
4)again wipes
5)mount everything i can
6) go and install file
it opens aroma installer...
pick needed items and press "install" after that it gives me error

foggydisaster said:
Here is it:
1) get into recovery
2)Data / cache / dalvik-cache wipe
3) format /system
4)again wipes
5)mount everything i can
6) go and install file
it opens aroma installer...
pick needed items and press "install" after that it gives me error
Click to expand...
Click to collapse
Unless the ROM you are installing is specifically telling you to "mount everything", do not do it. Try it again, but this time do not mount anything manually, installing from Zip should do it automatically. If it still doesn't work, make sure the ROM you are trying to install is supposed to be installed from Recovery, some do also provide files for flashing through Odin/Heimdall
EDIT: I do recommend flashing CM9 first, get the newest nightly from here: http://get.cm/?device=galaxysmtd and google apps (if you want them) from here: http://goo.im/gapps/gapps-ics-20120429-signed.zip which is the recommended one for usage with CM9 ICS.

Can't Root Galaxy Mini (GT-S5570)

Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.

xsam123 said:
Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
Click to expand...
Click to collapse
I think, you have followed the tutorial of rooting wrongly..
If you wanna root your mini, you can try this tutorial..

xsam123 said:
Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
Click to expand...
Click to collapse
First...you were supposed to root first and then replace the recovery...
Second...I didnt wanted to thanks...
Sent from my GT-S5570 using xda app-developers app

Try flashing a custom rom in your phone They usually comes up with a super user access (it means that you are rooted )
[ROM][CM7.2][ODEXED][30-04-2013] New Experience v9.8.0 - xda-developers
http://forum.xda-developers.com/show....php?t=1648213
This rom also comes up with many scripts/tweaks!
This is the one that I'm using
Im not saying its the best, there are many roms that have different features !
Please press thanks if I helped!

One workaround for 'assert failed' during CM install

Error message during failed install of CM zip: assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
Solved: See below.
When I first got my HD+, I did an SD "install" of CM 11. Then I installed CM 11 to the emmc, via CWM, per all the instructions on the xda website.
Once CM 11 was installed, I changed to TWRP 2.6.3.0. (I like being able to name the backups.)
Then I did a wipe and dropped down to CM 10.2.1. (More stable.) I did the install from TWRP.
Then I installed the fuzz kernel from TWRP.
Last, I updated to TWRP 2.6.3.0a when I couldn't get Succulent's CM 11 to install.
Okay, so tonight I wanted to do a clean install of CM 10.2.1, without gapps this time.
So I booted to recovery, did a wipe, and tried installing CM 10.2.1.(The build came direct from Cyanogen mod's website for the Ovation.)
I get an error similar to what I got when I tried to install Succulent's CM 11. Here's the error message:
assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
I dropped back to CWM and tried installing the ROM from three different versions: CWM 6.0.4.5, 6.0.4.5b, and CWM 6.0.4.6.
I tried installing CM 10.2.1 from the internal and the external SD card.
No joy. Fortunately, a Nandroid backup beforehand and I've restored to where I was.
Any ideas what's wrong? It shouldn't be this hard. It doesn't seem that a ROM install should be Recovery Dependent . But maybe it is?
==========
Solved. leapinlar, in the thread where I originally posted this question, said to use an older version of CWM to install. Apparently some incompatibility between versions of CWM (and TWRP) and the ROM zip.
Another solution was alluded to by King200 in another forum, but it sounded arcane and hard to do. It wasn't.
Here are Windows instructions:
++++++++++
Note: This method removes the "sanity check" built into the recovery image which checks to make sure the ROM you're installing is compatible with your tablet. Obviously, flashing the wrong ROM can/will brick your tablet.
So be warned.
Since I only have one tablet that I flash CM 10.2.1 on, no problem for me. If you have more than one tablet, perhaps you should delete your hacked zip after you install, to be safe.
Okay?
But for educational purposes, here's what I did to work around the problem.
++++++++++
You do this with 7-Zip. (So install 7-Zip if you don't have it already.)
Right click on the ROM that you're trying to install.
A 7-Zip context menu opens.
Select "Open Archive."
Drill your way down to
/META-INF/com/google/android/updater-script
Right click on the updater-script and select "Edit."
Open updater-script with Notepad.
Delete the first line of code, all the way up to the first semicolon. And delete the first semi-colon as well.
Save the edited file in Notepad. You'll get a 7-zip message asking if you want to incorporate your changes back into the archive. "Yes."
Now the ROM will install with later versions of CWM or TWRP.
Note: I had to do with this with the "fuzz" kernel too.
P.S. I don't know how to read code, so I don't understand exactly what the problem here is. I peeked at the scripts. I have an "ovation" tablet. Both the ROM and the Recovery image mention "ovation" in their updater scripts. Seems like they ought to talk to each other.

Please don't do this procedure. It is dangerous. It could brick your device. And the issue is not whether you have more than one tablet, it is if you accidentally download a hummingbird (HD) zip when you have an ovation (HD+) and try to flash it to an HD+. If you remove that assert statement the HD zip will merrily install to an HD+. And you will have a real mess.
A real case happened where a Nook Color user tried to flash a Nook Tablet ROM to his Color. The assert statement which was designed to prevent that did its job and prevented it. However, another user recommended he remove the assert statement, which he did, and thus flashed the Tablet ROM to his Color. His Color ended up bricked.
NEVER REMOVE AN ASSERT STATEMENT!
There are two more safe procedures.
One, use an older version of CWM to flash the older zips.
Two, do as the procedure says by opening the archive, but don't edit the updater-script file to remove the assert line. Look in a newer zip like CM11 and extract the file 'update-binary' and copy it to the old zip replacing the old update-binary file there. Then the old zip is flashable with the newer CWM/TWRP recoveries.
Sent from my BN NookHD+ using XDA Premium HD app

ERROR: (Status 7)

I have a problem, i install [ROM][UB][4.4.2][T/TX] Carbon Rom KK Unofficial {built from source} since recovery (T4.3_PhilZCWM_6.0.4.7_LB_v1.7)
and when it is installing, put ERROR: (Status 7)

Download zip again, might be broken.
Sent from my Xperia V using Tapatalk.

done
WhiteNeo said:
Download zip again, might be broken.
Sent from my Xperia V using Tapatalk.
Click to expand...
Click to collapse
i have it done! and it follows like before.

Takezo8 said:
I have a problem, i install [ROM][UB][4.4.2][T/TX] Carbon Rom KK Unofficial {built from source} since recovery (T4.3_PhilZCWM_6.0.4.7_LB_v1.7)
and when it is installing, put ERROR: (Status 7)
Click to expand...
Click to collapse
This is most likely due to you trying to install the build that isn't for your device. What phone do you have?
Some developers like to add a command at the beginning of the "updater-script" file that checks if your phone matches the file you're trying to install, and generally it outputs a messages. In some cases it doesn't, as is the case with several of the custom ROMs I've found here.
In my case, before flashing anything I always delete the entire first line with the "assert(getprop)..." statement, because sometimes the conditions specified in that command don't match what is specified in the ROM I'm on in the build.prop, especially when coming from Stock ROM, I think. I've done this with every ROM I've flashed, including the Carbon ROM, and deleting this line lets the installation continue.
On the other hand, this is a safeguard to prevent people from installing a ROM that is not for their phone, since there tend to be people who flash ROMs without having a clue of what they are doing or what the risks might be if something were to go wrong. So I'd make sure you have the right build for your phone, if it is, use 7zip to extract the updater-script file, delete that line, add it back with 7zip, reflash ROM.

I had the same problem. It has one solution change your recovery try with clockworkmod or philz touch