Develop Bugs

GW820 Custom Rom

Hi,
For those who don't fear to brick their phone, you can try this custom rom (v11) I've just made
As of now, nothing special with it, I just added Pim Backup, only to test the kitchen, so really no reason to flash it except to confirm whether it works or not. If you want to test it, use the stock rom in this thread (thanks Dark9781) to extract the files into programsdata\LGMOBILEAX folder and then replace phone\GW820-V10d-OCT-27-2009+0.dz with mine (giving it the same name).
Once again, I can't insist enough on the fact that this is experimental for now (for this test rom, I did some rebuild stuff manually, I don't know if it works). Once the tools are proved to be stable, I'll release a updated kitchen for you to play (it might take a week or so to finalize the tools, maybe less).

if u can free up rom and ram i will like to test for u. i hate only having 70% free on reset opera 10 crashes on my phone

Downloading it now. I will post to let you know if it works after I flash it.

Just tried to flash the test rom, but it keeps causing the flasher program to crash before 4%.

damn i was just about to try, dark are you on windows 7 or xp?

ManelScout4Life said:
damn i was just about to try, dark are you on windows 7 or xp?
Click to expand...
Click to collapse
I ran it on windows 7. I'm going to try it on xp now and will post the results.
UPDATE: Crashes on xp too.

Thanks for the test, Dark9781.
When you say it's crashing before 4%, what does that mean exactly ? Does is start to flash anything on your phone ? Are the 1st percents only decidacted to do checks on the file ? Do you have a log file ?
Did you try to download the rom a second time to be sure it was not a bad download ? I'm downloading it myself to check if my upload was good (I remember the 1st Incite tests were failing because of errors on upload, that's why the following tests were 7z, I'll do that on the next tests).
Also did you try to extract the stock v10d with dzdecrypt and pack it with dzcreate using another version name (-vTEST_ROM) (just to be sure it's not due to the name and/or the tools).
Sorry for all these questions but it's just to narrow the search.

spocky12 said:
Thanks for the test, Dark9781.
When you say it's crashing before 4%, what does that mean exactly ? Does is start to flash anything on your phone ? Are the 1st percents only decidacted to do checks on the file ? Do you have a log file ?
Did you try to download the rom a second time to be sure it was not a bad download ? I'm downloading it myself to check if my upload was good (I remember the 1st Incite tests were failing because of errors on upload, that's why the following tests were 7z, I'll do that on the next tests).
Also did you try to extract the stock v10d with dzdecrypt and pack it with dzcreate using another version name (-vTEST_ROM) (just to be sure it's not due to the name and/or the tools).
Sorry for all these questions but it's just to narrow the search.
Click to expand...
Click to collapse
Well, the first 4% is just a check of the rom and it is failing causing the flasher program to crash. I'm going to try and download it again to see if it was the download. I didn't try dzdecrypt to take the stock rom apart and dzcreate to put it back together, but I'll try that too.

I used dzdecrypt and dzcreate to deconstruct and reconstruct the stock rom and it flashed fine. I downloaded the test rom again and again the flasher crashes. The message I get is 3GQCT_SP_STARTER MFC (a bunch of weird symbols) stopped working. The log I posted on the last post was the wrong log. It was for another install that failed on me so please ignore that. The flasher didn't create a log for the flasher crashing.

Ok, after a check, it seems that there was a problem during upload (i've found a string "n: close cache-control" in the middle of the uploaded dz file that was not on my version).
I'm reuploading it right now, let's hope it will be fine this time.

Hoping that that was the only problem. I remember that there was a problem with uploads with the Incite. I've been having some problems with uploads lately. Seems to be happening a lot with mediafire. I'll try it again once it is uploaded.

Upload finished, link in 1st post. I've embedded a md5 in the archive.
2Am here, see you in 8h from now

We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.

Dark9781 said:
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Click to expand...
Click to collapse
EXCELLENT!
GREAT WORK GUYS!
well now i'm anxiously awaiting your step by step and what all is needed. cuz i'm ready to get down and dirty with this..

Dark9781 said:
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Click to expand...
Click to collapse
So what exactly isn't functioning correctly?

New test rom available.

Flashing your V3 now, having trouble flashing with the LG IQ Flasher so I am using my Octopusbox to flash.

Ok, phone boots up, but the screen is all black, and non of the buttons seem to work or there is a really long delay to get them to work. Start Menu doesn't work.

Just flashed test 3 and can confirm that I am getting the same results as test 2.

Test 4 gives the same results as test 2 & 3.

[How To] Installing FroYo (non official version), from firnware I9000TGYZSJP2

First of all.... flashing might cause damages bla bla bla at your own risk.
Then, this firmware has limited languages: Chinese, Korean and English... Check original thread for more informations.
Everything is did I copying/pasting bits of information from several posts and people. I edited some and changed some in other to provide a convenient flashing tutorial.
**Prerequisites**
Samsung Galaxy S (I used French 8 gig version). Also reported to work on Galaxy S from Bell Canada, I9000M.
Any firmware.
-----How To Flash your Galaxy S with FroYo (non official) (this has been done using a French Galaxy S) ---
**Flash the "stock Froyo" Rom**
Put your phone to download mode (hold down: volume down, home key, power)
DO NOT plug in your phone yet, Odin / driver does not like it at this stage.
Start Odin3 (the one coming from the "I9000TGYZSJP2" archive, see below).
Tick "Re-Partition", check that "Auto Reboot" and "F. Reset Time" have been ticked.
From this archive.
Click "PIT" button and select s1_odin_20100803.pit file.
Click "PDA" button and select "I9000ZSJP2-REV03-ALL-mid-CL505946.tar.md5" file.
Click "PHONE" button and select "I9000ZSJP2_MODEM_CL_502703.tar" file.
Click "CSC" button and select the desired version "GT-I9000-CSC-MULTI-OZS.tar.md5".
Plug in the phone and wait until Odin finds it.
Click "Start" button and wait until phone reboots with the new software version.
**English Spoken**
Then when booted to "desktop": to set English dismiss all dialogs, on home screen go to home (blue, bottom right button..) then go to settings (2nd home screen, blue gear button) then to text settings (the "A..." icon) then the first menu entry and select English.
**Gain Root**
Download root files from here.
2. Extract and copy update.zip to the root of the phone internal memory.
3. Run Odin (the one coming from the "ZSJP2_Root" archive) with Auto Reboot UN-checked, loading the i9000_Kernel.tar as PDA
4. Put the phone into download mode and flash the i9000 Kernel.
5. Pull the battery. reboot into recovery mode and flash the update.zip you put in the root folder of your sdcard.
5. Pull the battery again, reboot into download mode again.
6. Run Odin with Auto Reboot checked, loading the ZSJP2_ZIMAGE.tar as PDA
7. reboot.
**Fix lag**
Use the .apk from the marketplace: "One Click Fix Lag". This has to be done on a rooted device (see above).
**Swype languages**
US English
UK English
Deutsch
Français
Espanol
Italiano
Nederlands
Portugues Europeu
Polski
(Chinese?)
Türkçe
**Quadrant scores**
Before lagfix, about 900.
After lagfix, about 1900.
**Known issues**
A few Force Close (FC) at the begining, but it seems that they tend to disappear the more you use the phone.
Looks like restoring apps and/or system settings with Titanium Backup causes FC on Calendar and Browser. Anyone noticed that too?
**Improvements**
GPS fix seems faster than in pevious FroYo roms.
**Open VPN**
As far as I know, and as far as I've tested, OpenVPN doesn't work on this rom as there is no interface for JPx firmwares. Binaries can be installed, but the interface can't. Using the tun.ko from xda-dev forums doesn't help either. Will keep trying... but not today!
**NB**
Thread still evolving...

the multiCSC doesnt seem to work for me... any idea?

[[ Cold ]] said:
the multiCSC doesnt seem to work for me... any idea?
Click to expand...
Click to collapse
My mistake. Doesn't seem to work on this CSC file. Edited 1st post.

you say "copy to /sd on the phone" for rooting
but actually it's copying to / while from windows, or /mnt/sdcard while from android (just for the sake of precision for anyone needing such a howto and would get lost like me ^^)

By 'Use the .apk from the marketplace.' do you mean the 1 click lag fix?

m1ket said:
By 'Use the .apk from the marketplace.' do you mean the 1 click lag fix?
Click to expand...
Click to collapse
Yup, edited 1st post.
@bilboa1: Thanks, edtied 1st post aswell.

Downloading will try on my uk phone later
Quick question as far as restoring stuff using titanium can i restore settings or just apps... or none

m1ket said:
Downloading will try on my uk phone later
Quick question as far as restoring stuff using titanium can i restore settings or just apps... or none
Click to expand...
Click to collapse
I did restore apps and settings using Titanium Backup (paid version).
Edit: actually I had to wipe, restoring apps and/or system settings caused FC on calendar and browser. Now everythings works fine!

So, is it actually stable enough for day-2-day use? Cos would really like some frozen yoghurt, but both previous jp2 and jp3 were just unsusable....

Just want to update everyone. This DOES work fine on the Bell Mobility GT-I9000M.
You can use the modem file included, and I have also used the modem file from UGJH2 and both work fine. I am going to stick with the UGJH2 modem however, as it is made specifically for the 850MHZ HSPA Band here in Canada.

OK upgraded my uk galaxy s no issues
Not sure if ill bother with the lagfix right now as it seems as fast as my previous JM5 with lagfix
Setup 3g access point for three mobile no issues
Will keep an eye on it for the next day or so then report back any stability issues
EDIT: Just rooted following the instructions worked fine, as i said im going to hold off the lag fixes for now as it seems as fast

could the phone contact group sync with gmail contact group?

adrianmak said:
could the phone contact group sync with gmail contact group?
Click to expand...
Click to collapse
Just checked my gmail contacts have been import fine, i dont have many assigned to groups but the groups are there

additionally the 1 click lag fix apk from the market doesnt work for me on JP2 "new"
at this point i kind of assume the author did not test all the stuff he wrote

Is the JIT-compiler still de-activated?

Relief2010 said:
Is the JIT-compiler still de-activated?
Click to expand...
Click to collapse
Looking at the quadrant scores I'd say no.
I guess people without the 3 button recovery/download mode should stay away from this right ? Although it should technically be doable via ADB shell...
Official Froyo builds will come through Kies eventually right ? That should be safer...

bilboa1 said:
additionally the 1 click lag fix apk from the market doesnt work for me on JP2 "new"
at this point i kind of assume the author did not test all the stuff he wrote
Click to expand...
Click to collapse
You are assuming wrong. I did everything that is written in this tutorial as I gathered all the information for myself in order to modify my very own device.
One Click Fix Lag worked like a charm, but you have to use an already rooted rom (as explained in first post).

I'm jumping from JM6 to this froyo rom.
My JM6 had lagfix with EXT2.
When I flashed it with this JP2 rom, I didn't format my internal SD card.
When I run 1click lagfix APK, will it simply overwrite existing lagfix partition?
or create new one consuming additional 1.6GB?
even without the lagfix, this release is fast and snappy.
I can't wait till the real release of the 2.2
samsung has done such a great job

Electroz said:
Just want to update everyone. This DOES work fine on the Bell Mobility GT-I9000M.
You can use the modem file included, and I have also used the modem file from UGJH2 and both work fine. I am going to stick with the UGJH2 modem however, as it is made specifically for the 850MHZ HSPA Band here in Canada.
Click to expand...
Click to collapse
where can i get standalone jh2 modem.
i first flashed starting from jh2 firmware and skipped the phone part. that caused the phone not recognising sim and not being able to get to service mode. so flashed the modem from first post/ at least sim is recognised will test more

Idan73 said:
where can i get standalone jh2 modem.
i first flashed starting from jh2 firmware and skipped the phone part. that caused the phone not recognising sim and not being able to get to service mode. so flashed the modem from first post/ at least sim is recognised will test more
Click to expand...
Click to collapse
download JH2
extract using 7zip
use modem.bin
simple enough

[Q] Camera Failed

why my camera sometimes can't be used and there is a notification "Camera Failed".?
please help me...

I had this issue too..just reboot your phone and everything will works normaly again..

i hv this issue alsi when i'm using lower class memory card. now using class 10 16gb card with bionic rom without this camera failed problem.
Sent from my GT-I8150 using XDA

rinopermana said:
I had this issue too..just reboot your phone and everything will works normaly again..
Click to expand...
Click to collapse
i have reboot my phone, but that problem happen again for a next time.
please help me...

shade2112 said:
i have reboot my phone, but that problem happen again for a next time.
please help me...
Click to expand...
Click to collapse
Try to flash a new Camera.apk to you phone. Hopefully that is only software problem.

yewsiong said:
Try to flash a new Camera.apk to you phone. Hopefully that is only software problem.
Click to expand...
Click to collapse
how to flash a new Camera.apk ?
I really don't know.

I had the same problem and I solved it by uninstalling oovoo....it's only a case???

shade2112 said:
i have reboot my phone, but that problem happen again for a next time.
please help me...
Click to expand...
Click to collapse
do u have cwm on ur phone? reboot ur phone into recovery then choose advance and choose fix permission, wait until finish, then reboot ur phone after it finish

Unfortunately I have the same problem. My camera does not work anymore. I just receive the message "Camera failed". I still have the stock rom installed and I did not modify too much (I just installed some apps). I have already reset the phone to factory settings which did not solve my problem. Does anybody have an idea what I could try to fix the problem?

Please help...
I just have formatted my device and flashed it with a stock rom. Unfortunately it did not solve my problem with the camera. I still got the error message "camera failed" when I click on the camera app. Any ideas? Is it a hardware problem? Should I flash a custom rom?

I got that message once, and I panicked. Fortunately, rebooting did it just fine.
Perhaps there is something wrong with the firmware...I searched the net and found this article, maybe useful, IDK.

Thanks for the reply and for the link. Unfortunately I do not understand step 3. When I scroll to "Camera" I do not see a 2nd option which should be named as "user". I just see "camera" and "camcorder". What should I do? Do I have to root the phone?

ok, I have rooted my phone and I have tried the fix described in the link above again. However, I was not successfull. I do not get these options described in the link ("user"). Maybe I am using a wrong version of Pro Launcher. I just downloaded the new version from market...Anyone with a suggestion/idea?

Camera failed
I used to face this problem quite a lot when i was using the stock rom, but after flashing to cow's rom, the problem went away, no more camera failed anymore

Yesterday after upgrade to baseband v. i8150dxlc1 Kernel [email protected]#3 (KIES UPGRADE) i dont have that problem anymore

Help: Status 7 error while trying to update to 4.1.1

For those of you (rooted or not rooted) trying to update to 4.1.1 LJ7 but cant because of a Status 7 error, this is what worked for me:
1. Download this: http://www.androidfilehost.com/?fid=9390135922294523498
(It comes with ODIN) extract the .Tar file to a memorable location
2. unplug and power off your s3
3. Boot into download mode: Press and hold volume down+home+power
4. run Odin as administrator
5. connect USB cable to s3
6. once Odin recognizes the phone, tick Auto Reboot then click PDA
7. locate and select the .tar file
8. click start
9. let that run it will take a while,
10. when finished, you should see a green box that says PASS!, your phone should reboot and update.
Congratulations, you now have the official jellybean. Your Welcome.

I believe that error happens when you modify a system app, such as gmail or if you modified the camera or something. Revert to the original and I believe you should be fine. Someone will correct me if I'm wrong, but I also recommend searching as is has been covered.

MineralGray02K said:
I believe that error happens when you modify a system app, such as gmail or if you modified the camera or something. Revert to the original and I believe you should be fine. Someone will correct me if I'm wrong, but I also recommend searching as is has been covered.
Click to expand...
Click to collapse
Im not quite sure I understand what you mean by "revert to the original"
Original what? Im on a stock 4.0.4 ICS. The only thing I have close to a mod is an app that uses the LED as a multicolored notification, that works only with rooted s3's.

PITA but worked.
TheWzrd said:
Only way I was able to flash the jb update was to odin back to len and accept the ota's up until LI3 then I booted into stock recovery and flashed the jb update. Sucked but it worked.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse

Voodoo8648 said:
Im not quite sure I understand what you mean by "revert to the original"
Original what? Im on a stock 4.0.4 ICS. The only thing I have close to a mod is an app that uses the LED as a multicolored notification, that works only with rooted s3's.
Click to expand...
Click to collapse
I recommend the first posters advice that's easiest. Or using twrp or cwm to flash a modified version of the ota here http://goo.im/devs/billard412/d2spr...fficial_update(modified_CWM_or_TWRP_only).zip way less headaches. As a test to try n see why it kept failing for people I went all the way back to unrooted LEN and let it accept all ota's up to lj7 and surprise surprise, The Fukr Still Failed so it'd be easiest to just do what was already suggested
O ya, and use the damn search button

Hmmm just bumped into this problem during JB upgrade ... I'd modified my Sprint L710 ICS framework-res.apk file to correct a bug with cell phone power reporting ( http://forum.xda-developers.com/showthread.php?t=1732722 ) ... I might have fixed this but I've lost the original APK (the one with the factory error).
The lady @ Sprint was very nice but basically pointed out that it was out of her hands since I modifed the phone.So ... guess I'll try the solution from Voodoo8648 and hope for the best ....

Worked great. Thanks.

download ... let it run ... automagic !!
Go to the samsung page (that xda wont let me post) and download the kies software ...
h t t p :// w w w . s a m s u n g . c o m / u s / k i e s /
sorry if i break the rules ... this works

I did what the OP suggested and now my phone hangs on startup actually in android. It says android is upgrading and starting apps or something and then just freezes. Any help?

Where is my RN8P ???

hello guys I have the other Redmi Note 8 Pro phone like you. Today I just installed the AIDA64 and DevCheck app out of curiosity. After opening the first app, I found out that I don't have a xiaomi phone but a samsung s10 + !!! I tell myself that there will be an error in the app, so I run the second one and it also diagnosed my phone as SAMSUNG S10 + ... I go to settings / information about the phone / model and hardware .. and here again I find out that my phone model is SM-G975F! !! does anyone know how this is possible? or what to do? I'm using BLISS ROM (version 12.11) I tried reflash the system but it didn't help ..

Its probably something wrong with AIDA64, no need to worry about such a bug

samuuurai said:
Its probably something wrong with AIDA64, no need to worry about such a bug
Click to expand...
Click to collapse
hi it's not that i am afraid ? together i tried 5 apps for HW and SW information and they all detected my tel as SAMSUNG S10 + instead of RN8P. I noticed that even with internet payments, the site detects tel samsung instead of xiaomi ... I have no idea how it could have happened or how to return it. ??

bandos23 said:
hi it's not that i am afraid ? together i tried 5 apps for HW and SW information and they all detected my tel as SAMSUNG S10 + instead of RN8P. I noticed that even with internet payments, the site detects tel samsung instead of xiaomi ... I have no idea how it could have happened or how to return it. ?
Click to expand...
Click to collapse
It could be due to some wrong entries on the build.prop file.
Don't worry, just re-flash the stock ROM with fastboot method and come back to a Custom ROM whichever you wish...

ponnuvelpandian said:
It could be due to some wrong entries on the build.prop file.
Don't worry, just re-flash the stock ROM with fastboot method and come back to a Custom ROM whichever you wish...
Click to expand...
Click to collapse
hello
buddy i thought so too but build.prop. is fine ? it occurs to me that it could be related to the SafetyNet check in the Magisk administrator, which I did not go through a few days ago. on the BLISS ROM support pages I found a file (codm + cts.zip) which flashes via magisk. the module name HARDWARE OFF is listed in the module manager. this is the only thing that occurs to me that it could cause it, but maybe I'm also writing completely out of the bowl here
PS: after flashing the file, I go through SafetyNet without a problem ..