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

Root ICS/CM9-JB/CM10 Development Thread

The Play store was force closing on me, mkdir /cache/download to fix.

This guy actually found the typo that fixed my problems with Play Store. Question for TDM: Did you fix the text color on the Superuser notifications popup that comes up at the bottom of the screen? Its a black background with black fuzzy text.
 
This guy actually found the typo that fixed my problems with Play Store. Question for TDM: Did you fix the text color on the Superuser notifications popup that comes up at the bottom of the screen? Its a black background with black fuzzy text.

I wasn't aware of that. But being cosmetic, it wouldn't be a high priority.
 
I'm designing a unified installer, and I'm just wondering what the baseband version and ro.product.model on the stock ROM looks like for lg855 and as855.
 
Wow, tdm, this has been incredibly stable for me for such an early release - just so cool. I initially flashed LS855 alpha1a, not preceding with a wipe and was very surprised it upgraded as well as it did. Ended up doing a wipe/cache clear/dalvik clear, install alpha1b, boot, download gapps-ics-20120429-signed.zip, reboot to recovery and flash gapps.

I think the CM9 boot screen is about the coolest thing I've ever seen on my marquee! :D

Play store experience has been very stable. Vibrate is not working as expected.

GPS doesn't seem to work for me either. I saw an earlier note that there were problems with this, but is that still a known issue? I did notice some oddity where setting were configured to use "external" gps. Switched to internal, but still no luck, and now oddly the "external" options is no longer available.

Just awesome, though. I'll be watching the thread and doing whatever I can to help though limited by my android knowledge. If GPS is not working and you have any quick ideas for tracking it down, I'd certainly take a whack.
 
  • Like
Reactions: tdm
If you don't need to return the old one, perhaps there is a dev that could use one.....

Sorry tdm, they confiscated it. But I have my new marquee. Now I just have to bust it down to ZV3 so I can root...
 
Sorry tdm, they confiscated it. But I have my new marquee. Now I just have to bust it down to ZV3 so I can root...

If you're using windows 7, make sure you have service pack 1 installed or it won't work properly. I was beating my head against the wall trying to figure that out.
 
I'm designing a unified installer, and I'm just wondering what the baseband version and ro.product.model on the stock ROM looks like for lg855 and as855.

Here's the AS855

AS855ZV2-M6600A-SCAUTSZ-3.0.40T

Code:
ro.build.description=lge_bproj-user 2.3.4 GRJ22 ZV2.422aa87e release-keys
ro.build.fingerprint=lge/lge_bproj/AS855:2.3.4/GRJ22/ZV2.422aa87e:user/release-keys

ro.build.product=AS855
 
  • Like
Reactions: tdm
something bad happened... tried to wipe sd card from this. after installing monsters gapps and rebooting a couple of times... I tried to wipe the sd card from within ics. seemed unresponsive, so i tried to reboot to recovery. now phone is dead. pulled battery, tried different buttons. plugged in/out... no response.

Back to Best Buy for my replacement! Bought the Insurance. Will be back tomorrow... just wanted to let you know.

thats funky. sounds like its looking at the wrong mount and wiped recovery instead.
 
Did a little bit of research on basebands and modems. Looks like the modem is on /dev/pts1. It does standard Hayes type commands (remember those .. ATDT and all that? The first command that rild writes is "ATE0Q0V1". Ah, the nostalgia .. almost brought tears to my eyes. Yeah I'm old :p) The command for baseband appears to be "AT$LGMR", eg:

Code:
AT$LGMR
$LGMR: LS855ZVC-M6600A-SCAUTSZ-3.0.40T

OK

Other interesting commands:

"AT+LGSN" = read some 32-bit number and serial number (MEID) in hex
"AT+CNUM" = read 10-digit cell number
"AT$LGMIN?" = read 10-digit MIN number (see note below)
"AT$LGPRLVER?" = read PRL version

Found "ATD#777" in there. Anyone know what the phone number "#777" means?

On a side note, I never was really interested in rild, cell modems, or anything of the sort. I just wanted to build ROMs and have a reasonably modern phone on my sweet VM plan. I only found this because I've been forced to trace the rild and modem commands to make 3G work and find the baseband info. I really wish the manufacturers would just stick to standard and open ways to communicate with the main system and not feel the need to be different or "innovative" or proprietary.

What is the MIN aka MSID?

The MIN (Mobile Identification Number) is a unique number associated to your account, using the same area code of your locale. It is required to program your device.

-- PRL, MDN, MIN, MEID, SPC??? What does all this mean?
 
thats funky. sounds like its looking at the wrong mount and wiped recovery instead.

Yes, I thought it was weird. I've tried out lot's of stuff around here, and I never had that happen.

I hope it doesn't happen to someone else, and I hope you guys can look into it. Good News. I got my new marquee today and successfully rooted. (But I must say, busting this thing down to ZV3 has always been a pain for me! Took all afternoon.) This is now my 4th Marquee. Not complaining, but the folks at Best Buy are getting suspicious :rolleyes: Anyway, I'll keep testing!
 
Oh, just in case anyone was wondering, I plan to use the baseband info in the installer edify script to figure out which files to install. Example:

Code:
# The program read-model will look for a model override in a special
# file (say, /sdcard/.model).  If not found, it will read the model from
# the baseband by communicating with the modem.  In any case, the
# model will be placed in the system property "install.model".
package_extract_file("read-baseband", "/tmp/read-model");
set_perm("/tmp/read-model", 0755);
run_program("/tmp/read-model");

# Do the install
# ...

# Install model specific files
if getprop("install.model") == "LS855" then
    # Install Sprint files
endif
if getprop("install.model") == "LG855" then
    # Install Boost files
endif
if getprop("install.model") == "AS855" then
    # Install Ignite files
endif
if getprop("install.model") == "VM855" then
    # Install VM files
fi
 
Hmm ... I wonder if the if/endif mess could be collapsed to:

Code:
# Extract models/xx855 to /system
package_extract_dir("models/" + getprop(install.model), "/system");
 
so I've been trying to figure out wtf is going on with the CPU and so far all I've come up with is the kernel is either missing something from the Linux kernel 3.0.1 that it needs for ICS, or it has nothing to do with the kernel at all and something in the ROM is causing it.

I know nothing in Hyper is causing it since I took the stock kernel source, threw in the updated GPU drivers so it would boot, built it with the toolchain LG says to use and flashed it. the CPU does the same shit as it does with Hyper and gets stuck on 1000 mhz no matter what its set to and it never scales down, I've also had it get stuck on 300 a couple times after a reboot and not scale up too.

heres a screenshot, the screen was off for 20 mins while I went to fold some laundry and when I came back the CPU never left 1000 mhz

Screenshot_2012-08-05-20-39-49.png


btw tdm, those 20 mismatches you asked me about before also happen with the stock kernel/toolchain.
 
Yeah the mismatches are fine, it was using -O3 that caused errors with the codesourcery toolchain.
 
for those who want to remove "Roaming Indicator Off" from lock screen and drop down, flash this: LINK

this actually sent me into a loop at the lg screen too. flashed everything over and tried again and it still happened.

just reflashed alpha 1b and gapps, no issues in the play store now.
 
so I've been trying to figure out wtf is going on with the CPU and so far all I've come up with is the kernel is either missing something from the Linux kernel 3.0.1 that it needs for ICS, or it has nothing to do with the kernel at all and something in the ROM is causing it.

I know nothing in Hyper is causing it since I took the stock kernel source, threw in the updated GPU drivers so it would boot, built it with the toolchain LG says to use and flashed it. the CPU does the same shit as it does with Hyper and gets stuck on 1000 mhz no matter what its set to and it never scales down, I've also had it get stuck on 300 a couple times after a reboot and not scale up too.

heres a screenshot, the screen was off for 20 mins while I went to fold some laundry and when I came back the CPU never left 1000 mhz

Screenshot_2012-08-05-20-39-49.png


btw tdm, those 20 mismatches you asked me about before also happen with the stock kernel/toolchain.

Earlier today I saw (using CPU master widget) that my phone scaled briefly between 300, 600, and 1300. Weird. After a reboot it didn't do it again
 
Back
Top Bottom