• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Jiilik's custom Shine Plus ROM's

jiilik

Well-Known Member
Hi folks, this thread is a WIP. I figured my hacking efforts were getting a bit scattered. So This thread is a place for me to keep everything together.

First, some background info on these roms. I build these for personal use, to suit my personal goals. However, a good idea is a good idea, so please talk to me about what you want/need. Secondly, in the spirit of open source, I will be attempting to clearly document what I'm doing to these roms so that people can download sources and recreate them. This should hopefully help people learn rom hacking while I myself am learning rom hacking.

Okay: Getting Started

  1. Before using any of these ROMs, you must accept some degree of risk. I will generally test these on my own phone before posting them, so they should work reasonably well if you've followed instructions.
  2. You must already updated your phone to v20a (a.k.a. LG's official 2.3.3 update) in order to get a fully functional rom installation. If you do not do this, your cell phone functionality (phone, text, data) will not work. You can use LG's official updater to do this if the 2.3.3 update is listed for your phone, or use the manual radio updating thingy worked out by karendar.
  3. Download the ROM file from one of the links below. It should be in zip format. After download, copy it to your phone's micro-SD card. (If you do not know how to do this, you are probably in way over your head). Check to see that it is intact by comparing the md5sum to the one I posted. This ensures the download was not corrupted.
  4. Your phone must have a custom recovery partition installed to facilitate flashing. See http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html for details on installing this. You will need a rooted phone in order to install a custom recovery partition.
  5. Before installing any ROM (mine or otherwise), boot into the recovery partition (hold VOL-DOWN + HOME + POWER while booting). Make a nandroid backup of your phone. This will require an SD card with ~300 MB free. I am paranoid, so I backup my backups to my laptop. It lets me sleep at night.
  6. Before installing any ROM (mine or otherwise), and after you have backed up your existing system to the sd card, use the recovery program to perform a system wipe. This ensures that old programs/settings/etc. do not interfere with the new rom.
  7. Using the recovery program, flash the rom from the zipfile you saved to the sdcard earlier. If flashing fails, restore your nandroid backup and pretend like nothing happened.
  8. Upon reboot, you should be greeted by a shiny new rom. YAY! If this fails to boot, or you just don't like it, reboot into recovery and restore your nandroid backup.
Okay, now that that's out of the way, here are some ROM's I've made, starting with the oldest. If you want the latest and greatest, keep scrolling down!

karendar's original alpha 1.2 rom is the basis for my initial work: see here for details on what he did: http://androidforums.com/shine-all-...-custom-lg-shine-plus-rom-app2sd-support.html

v001: This rom is based on karendar's alpha 1.2 ROM. I replaced the zImage from LG with one compiled from their sources, to confirm that the sources were valid.
DL link: alohag_302-220_signed_112111_204448-jiilik-v001.zip
md5sum: f5e3f0d7660497226b1879e8acfcc1ad

v002-v004: failed attempts at overclocking that did not boot.

v005: This ROM contains the first overclocked kernel for the Shine Plus. It is otherwise identical to v001. See here for details: http://androidforums.com/shine-all-things-root/449855-overclocking-shine-plus.html.
For the original ZTE Blade code that inspired my patch: https://github.com/TomGiordano/kern...51f3c00b4d23f2f#arch/arm/mach-msm/acpuclock.c
DL link: alohag_signed_jiilik-v005.zip
md5sum: d4d716a99401cf9fa6580e78ae792f9c

v006: Added memory overclocking, doubling the AHB speed when running at frequencies of 480 MHz and higher. In other words, doubled the memory speed of the phone.
Also added sysro/sysrw/nano from dsi's kitchen.
Disabled the LG bootup sound.
DL link: alohag_signed_jiilik-v006.zip
md5sum: bf6315307bf907a4384d04a8960a301d

v007: Fixed default CPU speed to be 604 MHz, rather than 480 MHz. The file that needed modification was the init.qcom.post-boot.sh file in the boot ramdisk - simply changed a value from 600000 to 604800. You can unpack boot.img using dsi's kitchen if you're interested at taking a peak. Most of the commands that the phone executes at boot time are hidden in there.
DL link: alohag_signed_jiilik-v007.zip
md5sum: 0048e594c21a794b0889b77e13ee9fff

v008: recompiled the kernel again - added ext4 and swap support. Turned on AVS (Adaptive Voltage Scaling) in the hopes that it solves the GPU issues when running overclocked.
DL link: alohag_signed_jiilik-v008.zip
md5sum: 6bb7ab99d83723af55e2fa01e62daaab

Update: August, 2012: This rom has been discontinued. Please support karendar et al. and their continuation of this work. His updates are here.
 
Outstanding bugs/todo list:

- Push notifications off when screen off.
- When overclocked, a rare few apps like Gallery and Angry Birds crash and will not reload without restarting phone. Workaround: don't run overclocked for these apps (create a profile in SetCPU or similar).
- Newer version of Youtube, Superuser, Gmail, App Store, etc. on market. Workaround: update manually after flashing rom.
- Need to add Terminal to default install: Workaround: install after flashing.
- Remove some LG branding; reinsert Launcher2.apk if room.
- See if adding translations to base OS is reasonable/possible. (Spanish, etc.)

Fixed serious bugs vs stock:
v008+ may have solved LG's screen locking crash. How? *shrug*
 
hehe, excellent! Will wait patiently :)

Not too patiently, I hope :0

Anyway, I just posted v006... incremental changes, you know.

I'm hoping someone else other than me will test this one, since the speed gain is truly impressive. The thing seems really smooth now.

A couple of notes about v006. I tried to set the default CPU speed to 604 MHz. Due to the way the overclocking code works, the normal 600 MHz is no longer available. The phone, however, wants to use 600 MHz at boot for some reason (still looking into it), but since it cannot find this speed, it defaults to the next lowest one: 480 MHz. Only once SetCPU or some equivalent is used to change the upper frequency will this change. I'll investigate further.

Cheers
 
Excellent! Speed is great, phone runs smooth... great work :) been working at 802mhz... stable and quick :)... how about the wifi issue? any advances?
 
Excellent! Speed is great, phone runs smooth... great work :) been working at 802mhz... stable and quick :)... how about the wifi issue? any advances?

Well, nothing specific. Right now I've done a checkout out the android kernel source code published at The Code Aurora Forum. This seems to be the basis for all the LG kernel sources, which makes sense. The Code Aurora sources are the best basis for building phones that use any of the Qualcomm processors, like our MSM 7227.

Next step is to do some side-by-side comparisons of the two copies of the kernel source code to itemize all the changes that LG applied. Most of their changes are simply adding extra drivers to the kernel for things like the touch screen, keyboard, etc. I'll detail these in another thread, since it's useful info for many modders, not just myself.

Once I've isolated all of the LG patches, I'm going to try to get an updated version of the kernel, and forward port LG's patches. I'll try to target kernel 3.0.10 (released Nov, 2011), since that's the basis for android 4.x and is quite a bit more up to date for many things than kernel 2.6.35.7, which was released Sept 2010.

I presume this will take me a few weeks to do successfully, if its even possible.

In the meantime, v007 is working great on my phone... it's the same as v006 except with the default CPU speed set higher at boot, so if you're running v006 and you're happy, don't bother updating.
 
Just flashed the ROM and made cpu clock run at 806MHz(max/min) using setcpu.

Everything seems very good so far, very smooth, love it! Superb~~
Except when I try testing with angrybirds, there's no graphics(black screen after launching the program) but only sound and the phone is functional, I got it work the first time I launch it and it was much smoother than before until I "fire" the second angry bird and the game was frozen and force closed. Doesn't work even after reinstall. Anyway, it's no big deal cause I don't play angry bird:p

Another thing, LG home launcher is still laggy, I think it's bugged or something. Launcherpro is much better.
 
OK, here's an update.

The phone is having a weird problem.

As I mentioned, Angry Bird was not working. Now the Gallery is not working properly, Camera is fine, but when I open the Gallery(via app drawer/camera/wallpaper) the screen hangs, the phone itself does not for some reasons, the phone can operate normally if other buttons are pressed.

Oddly, after a reboot, the Gallery works fine, I am able to play angry bird 2 levels, then it hangs and was force closed. The interesting part is that it caused the Gallery to not work again...

Factory reset and cleared Dalvik cache before flashing the ROM v007
LauncherPro Plus v0.8.6
SetCPU 2.2.4 (806MHz max/min no profiles added)

I'll try testing with other games and see~

1. no luck with Angry birds seasons either...hangs and will cause gallery to not work
 
OK, here's an update.

The phone is having a weird problem.

As I mentioned, Angry Bird was not working. Now the Gallery is not working properly, Camera is fine, but when I open the Gallery(via app drawer/camera/wallpaper) the screen hangs, the phone itself does not for some reasons, the phone can operate normally if other buttons are pressed.

Oddly, after a reboot, the Gallery works fine, I am able to play angry bird 2 levels, then it hangs and was force closed. The interesting part is that it caused the Gallery to not work again...

Factory reset and cleared Dalvik cache before flashing the ROM v007
LauncherPro Plus v0.8.6
SetCPU 2.2.4 (806MHz max/min no profiles added)

I'll try testing with other games and see~

1. no luck with Angry birds seasons either...hangs and will cause gallery to not work

I had a similar issue with angry birds when running at 825 MHz, so it's almost certainly due to the overclocking. Both angry birds and the gallery app use the 3D processing part of the GPU. It's possible that the 3D bits cannot handle that speed and are crashing because of it - but then any app that uses 3D will not work until reboot. It's quite possible that your phone is stable at 806 MHz the rest of the time since it's not using the 3D bits.

Try it at reduced processor speeds to see what speeds you need to use to ensure stability. Not every processor will have the same upper limit.

(As an aside, for our CPU, the MSM 7227, there is an identical CPU out there called the MSM 7227T, where T stands for Turbo. The turbo version runs at 800 MHz out of the box, while ours runs at 600 MHz. They are the same CPU, the only difference is that the factory QC tests how fast they can run the CPU without errors and then labels them accordingly. The fact that ours are the 600 MHz CPUs would imply that the factory deemed them unstable at 800 MHz.)

If your phone is stable at 806 when not using 3D, create a profile in SetCPU that automatically reduces your phone speed to a safe speed when using one of the apps that causes problems.
 
Hi Jiilik! Congrats on the compiled kernel! Glad to see someone's picking up where I left off... I've been back in the SGS2 forums for my own phone, sadly... Will try your kernel!

By the way, for overclocking issues, most likely due to the fact you're increasing CPU speed without modding voltage profiles (Higher CPU clock = Higher voltage usually). Jiilik, do you have unver/overvolting code in your kernel? Maybe increasing voltage by .25 or .5 might help stabilize the phone a bit.

Good luck!
 
Hi Jiilik! Congrats on the compiled kernel! Glad to see someone's picking up where I left off... I've been back in the SGS2 forums for my own phone, sadly... Will try your kernel!

By the way, for overclocking issues, most likely due to the fact you're increasing CPU speed without modding voltage profiles (Higher CPU clock = Higher voltage usually). Jiilik, do you have unver/overvolting code in your kernel? Maybe increasing voltage by .25 or .5 might help stabilize the phone a bit.

Good luck!

All other threads regarding overclocking on this cpu suggest that over/undervolting is not required for anything - and in fact, the CPU is stable at quite high speeds (800+ MHz). It's the 3D GPU (Adreno 200) that's causing the instability when the CPU is overclocked as their clocks are linked...

Not sure what the solution is yet.
 
Is it correct that this ROM supports Darktremor App2SD and ext4? cause it's based on Karendar's work.

It seems that the ext4 partition of my sd card cannot be mounted....
I'm using the stock 4GB SD class 4 SD card that came with the phone.
Partitioned my sd with RA recovery
swap file=32MB
ext2 size=1024MB
ext2>ext3>ext4
then flashed the a2sd script.

I get this:
Code:
sh-3.2$ su
su
sh-3.2# a2sd check
a2sd check
Starting Darktremor A2SD version 2.7 beta 5
[ ] Mounting /system as read-write
[ ] Mounting /data as read-write
[ ] Mounting /system as read-write using Busybox Mount.
[ ] Mounting /data as read-write using Busybox Mount.
[*] Busybox already installed.
[ ] Starting A2SD in check mode
[ ] Running A2SD Check Program.
[ ] Checking for ext partition
[!] Ext partition found, but not mounted.
[ ] Checking Ext partition...
e2fsck 1.40.8 (13-Mar-2008)
/dev/block/mmcblk0p2 has unsupported feature(s): extents gdt_checksum
e2fsck: Get a newer version of e2fsck!
[ ] Mounting ext partitions
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
[X] Mounting ext partition failed.
[X] Can't continue script...aborting.
sh-3.2#
if I use ext3, it seems to work
Code:
c:\android-sdk-windows\platform-tools>adb shell
sh-3.2$ su
su
sh-3.2# a2sd check
a2sd check
Starting Darktremor A2SD version 2.7 beta 5
[ ] Mounting /system as read-write
[ ] Mounting /data as read-write
[ ] Mounting /system as read-write using Busybox Mount.
[ ] Mounting /data as read-write using Busybox Mount.
[*] Busybox already installed.
[ ] Starting A2SD in check mode
[ ] Running A2SD Check Program.
[ ] Checking for ext partition
/dev/block/mmcblk0p2 /system/sd ext3 rw,noatime,nodiratime,errors=continue,barri
er=0,data=writeback 0 0
[*] Ext partition found and already mounted.
[ ] Checking A2SD links.

A2SD Status Report
===============================================================
Busybox       - [*] Present.
                [*] Symlinks Present.
Apps          - [*] Linked to SD Card.
                [*] File .noa2sd not found.
                [*] Programs run from SD card
                To run from internal storage, type a2sd remove

Private Apps  - [*] Linked to SD Card.
                [*] File .noa2sd not found.
                [*] Private Programs run from SD card
                To run from internal storage, type a2sd remove

Dalvik Cache  - [*] Linked to SD Card.
                [*] File .nocache not found.
                [*] Dalvik runs from SD card
                To run from internal storage, type a2sd nocache

Swap           - [*] Partition present.
                 [*] File .noswap not found.
                 [*] Swap starts.
                 To deactivate swap, type a2sd noswap
ZipAlign       - [ ] Running at boot.
Property Patch  - Property not found.
                  cm.filesystem.ready or dc.filesystem.ready
                  [X] Boot image init.rc needs patch.
                      Contact Kernel/ROM Developer.
                  [X] Race condition may occur in
                      unpatched ROM.  Phone may stall
                      or loop during boot.
but what does this it mean?
Code:
Property Patch  - Property not found.
                  cm.filesystem.ready or dc.filesystem.ready
                  [X] Boot image init.rc needs patch.
                      Contact Kernel/ROM Developer.
                  [X] Race condition may occur in
                      unpatched ROM.  Phone may stall
                      or loop during boot.
Help...:(
 
Is it correct that this ROM supports Darktremor App2SD and ext4? cause it's based on Karendar's work.

It seems that the ext4 partition of my sd card cannot be mounted....
I'm using the stock 4GB SD class 4 SD card that came with the phone.
Partitioned my sd with RA recovery
swap file=32MB
ext2 size=1024MB
ext2>ext3>ext4
then flashed the a2sd script.

I get this:

Help...:(

Hi,

It's kind of funny, I was about to answer you and when I logged in, I saw your PM. ;) haha.

There is no ext4 support in the ROM currently. Haven't looked into adding this to the ROM sadly, and I have very little time to do so. For the time being I suggest simply using Ext3. I have it configured on my girlfriend's phone and works great!

Once your partition is up and a2sd detects the partition, simply type "a2sd reinstall" and it should re-symlink the ext partition and transfer all apps from data/app to it.

Good luck!
 
Jiilik,

I don't know if this is where you get your source for the kernel, but:

https://github.com/alquez

-Add Ext4
-Add Swap
-Add OC cpu clocks 120-806 mhz
-Enabled Governors
-cpufreq: Prevent memory leak in cpufreq_stats on hotplug
-Fix kernel compression support
-Set min/max ondemand frequencies if defined in config
-block: prepare I/O context code for BFQ
-block: add cgroups, kconfig and build bits for BFQ
-block: introduce the BFQ I/O scheduler
-Switch from BFQ-v2 to BFQ-v2-r1.
-time: Compensate for rounding on odd-frequency clocksources
-msm: cpufreq: Add missing cpufreq_attr

Maybe adding BFQ I/O and Ext4 might be a good idea. ;)
 
Jiilik,

I don't know if this is where you get your source for the kernel, but:

https://github.com/alquez

-Add Ext4
-Add Swap
-Add OC cpu clocks 120-806 mhz
-Enabled Governors
-cpufreq: Prevent memory leak in cpufreq_stats on hotplug
-Fix kernel compression support
-Set min/max ondemand frequencies if defined in config
-block: prepare I/O context code for BFQ
-block: add cgroups, kconfig and build bits for BFQ
-block: introduce the BFQ I/O scheduler
-Switch from BFQ-v2 to BFQ-v2-r1.
-time: Compensate for rounding on odd-frequency clocksources
-msm: cpufreq: Add missing cpufreq_attr

Maybe adding BFQ I/O and Ext4 might be a good idea. ;)

The source for the kernel comes from LG directly. I'm using their unmodified sources so far, except for the patch I applied to get overclocking to work (I used a patch courtesy of the ZTE Blade cyanogen folks - same CPU).

Adding ext4 is the easiest thing to do. I'll do it for the next version. Swap is probably easy too, but it probably needs some additional userspace tools installed to configure/control it.

Will get this done sometime later this week.

Not sure I'm a fan of adding BFQ/CFQ/etc. I think CFQ is already in the kernel, and just needs to be compiled, but BFQ is part of a kernel fork and ongoing dispute in the linux community. BFQ and such was designed for reducing the latency of desktop systems under heavy multitasking loads - since the android suspends most processes aside from the active one, I'm not sure it's actually that useful - or, at minimum, I've yet to see a compelling argument.

(to be honest, installing it on the android seems to me like installing a flared muffler on a honda civic... nothing against the honda civic, but installing a muffler that makes it sound like a more powerful car does not magically turn it into a cobra.)

Weee! Oh, if you or anyone is interesting in learning how to build kernels, let me know - I can help get you set up. That's the beauty of opensource! :)
 
The source for the kernel comes from LG directly. I'm using their unmodified sources so far, except for the patch I applied to get overclocking to work (I used a patch courtesy of the ZTE Blade cyanogen folks - same CPU).

Adding ext4 is the easiest thing to do. I'll do it for the next version. Swap is probably easy too, but it probably needs some additional userspace tools installed to configure/control it.

Will get this done sometime later this week.

Not sure I'm a fan of adding BFQ/CFQ/etc. I think CFQ is already in the kernel, and just needs to be compiled, but BFQ is part of a kernel fork and ongoing dispute in the linux community. BFQ and such was designed for reducing the latency of desktop systems under heavy multitasking loads - since the android suspends most processes aside from the active one, I'm not sure it's actually that useful - or, at minimum, I've yet to see a compelling argument.

(to be honest, installing it on the android seems to me like installing a flared muffler on a honda civic... nothing against the honda civic, but installing a muffler that makes it sound like a more powerful car does not magically turn it into a cobra.)

Weee! Oh, if you or anyone is interesting in learning how to build kernels, let me know - I can help get you set up. That's the beauty of opensource! :)

Thanks for the info. ;) Just though I'd let you know what a few of the similar kernel coders were doing...

I haven't gotten into compiling bases/kernels and the such yet, I don't actually have much time. I'm still at the decompile APK's and /system structure stage. If I ever want to get into kernel building though, I'll tell you! ;)
 
Weee! Oh, if you or anyone is interesting in learning how to build kernels, let me know - I can help get you set up. That's the beauty of opensource! :)

I've picked up a second-hand LG Shine Plus and am quite interested in modifying the kernel (and perhaps help/attempt to port CM7).

I would greatly appreciate it if you could post a step-by-step list of how you were able to setup your build environment and compile the Android+LG sources.

I'm attempting to do this in a Windows environment, and I do have experience with C++/Java programming.

Thanks!
 
I've picked up a second-hand LG Shine Plus and am quite interested in modifying the kernel (and perhaps help/attempt to port CM7).

I would greatly appreciate it if you could post a step-by-step list of how you were able to setup your build environment and compile the Android+LG sources.

I'm attempting to do this in a Windows environment, and I do have experience with C++/Java programming.

Thanks!

Hey, no problem. Windows makes things more challenging. I don't even own a windows computer, so I cannot give you step by step instructions. I can, however, give you hand-wavey generalized instructions. Windows will not work (directly). You will need one of two things to create an improvised solution.

Option 1) (Recommended): install Cygwin - it creates a linux-like layer which can live on top of windows. It should allow most linux applications to run on top of windows, but most importantly, the android compilers.

Option 2) install vmware or virtualbox. This allows you to run a full linux installation within a window. If you do this, probably use Ubuntu as the version of linux to install, since it seems to be the most common amongst the android developers. (Personally, I use a form of linux called Slackware - not for linux n00bs though - very high learning curve.)

Once you have one of these running, you will need to check out the android sources. See this link for instructions: Downloading the Source Tree | Android Open Source ***

Keep in mind that any commands they recommend may need to be adapted for use on Cygwin... for example, I'm not sure if Cygwin includes curl, so that command may be unavailable. You can install curl as an add-on package to Cygwin.

Those download instructions are for android 4.0.1 - you'll need to modify the command that says: 'repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1' to say 'repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.3_r1'

Once that's downloaded, go to the LG open source website at Open Source Main - type in C710 as the model number to get the sources for this phone.

Download and unzip those sources. There's a README file in there for building the kernel. Follow those instructions - it works for me on linux anyway.

Hope this helps! Good luck.



*** Note: the android sources here are from the AOSP. It may be that the proper sources for this phone are the ones from the Code Aurora Forum. I've not yet determined this. Will be checking out the Code Aurora Forum sources today to get a closer look.
 
Thanks for the info. ;) Just though I'd let you know what a few of the similar kernel coders were doing...

I haven't gotten into compiling bases/kernels and the such yet, I don't actually have much time. I'm still at the decompile APK's and /system structure stage. If I ever want to get into kernel building though, I'll tell you! ;)

I added swap and ext4 to the v008 kernel build - haven't really tested them though. Also turned on something called adaptive voltage scaling. Feel free to tell me I broke everything

For adding/using swap space, use busybox's mkswap, swapon, swapoff commands.
 
I added swap and ext4 to the v008 kernel build - haven't really tested them though. Also turned on something called adaptive voltage scaling. Feel free to tell me I broke everything

For adding/using swap space, use busybox's mkswap, swapon, swapoff commands.

Lovely!
Will definitely flash it tmr!

BTW, I was playing Trial Xtreme 2 at CPU 806MHz on ROM v007 and there was no crash at all....and it ran pretty smoothly too....how come:confused: That's a quite demanding game for an android, it should've pushed the GPU to the max. (not sure though)
 
Lovely!
Will definitely flash it tmr!

BTW, I was playing Trail Xtreme 2 at CPU 806MHz on ROM v007 and there was no crash at all....and it ran pretty smoothly too....how come:confused: That's a quite demanding game for an android, it should've pushed the GPU to the max. (not sure though)

Don't know anything about the game. Best guess? It didn't use the same GPU functions. Maybe it's doing pure 2D graphics on the CPU... *shrug*

Thanks for the feedback though - it's interesting to know where the phones are stable when overclocked.

Cheers
 
Do you know if default.prop is changeable within the kitchen? I've read that it's part of boot.img, so it requires unpacking and repacking.

Specifically, I've been playing around with your ROM and the following command fails:

adb remount

And from what I've read it may be just toggling a setting in default.prop:
ro.secure=1

I obtained my information from here: One way to fix "remount failed: Operation not permitted"

EDIT:
Doing a more > default.prop while in SU, shows this as already ro.secure=0.
So in that case, I'm not sure what the problem is.
 
Thanks a lot jiilik, however my experience with the flashed ROM has not been that great so far. Basically every time the screen goes dark if I lock the phone without turning off wifi and wait a few seconds first, and after I took out the battery and put it back in and restart the phone, most of the process did not respond at the start (including the qualcomm ones) and I have to flash the ROM again every time to get my phone working, only to happen again next time the phone is rebooted.

I have tried v1,v7 and v8.

I have deleted everything on my SD card and formatted it, I have also tried to wipe out all user settings/factory reset the phone in the recovery menu and set this phone up like a new phone, however none seems to work. At the moment I am trying to flash my phone back to the stock ROM first (but not sure how I can do it, so it would be great if you could help me here: http://androidforums.com/shine-all-things-root/454782-flash-stock-rom-dz-file.html) and then tried to flash to your ROM to see if I can get better results.
 
Back
Top Bottom