Root CM12.1 Alpha Progress...

drumgod552 · Nov 20, 2015

Sorry to barge in, but I do believe this is the only action (at least I can find) going on for the vs450pp..it just tripps me out how two identical devices can be so different. I have the L70 me 323 and they are practically twins, but just shows how Verizon has to always screw with a good phone and ruin everyone's fun. I was just tickled when I got my g4 and discovered how it had been robbed of alot of stuff. But every Verizon model of a phone I've dealt with had weird shit going on under the hood. My l70 is beat all to hell but I've got a ton of ROMs for it that I cannot use on this brand new Exceed2. I bought both from a crack head for 5 bux each so I'll gladly test anything you guys need hammered. Just not brave enough to attempt that g4 root yet and there's no real toys much yet anyway so I'll wait. These lil lg's honestly blow my mind, especially the ms323 , I can get more balls outta it than my g4 lol. For now...

jacob019 · Nov 20, 2015

Got CM12.1 running on my VS450PP by copying over entire flash image from my LS620. Here's what I did:
1. backed up modemst1 and modemst2
2. while in TWRP, I took a backup of the full flash from the LS620:
adb pull /dev/block/platform/msm_sdcc.1/mmcblk0
3. gzip mmcblk0
4. copied the full flash image over to the VS450PP in TWRP
adb push mmcblk0.gz /sdcard/
5. restored the ls620 full flash image to my vs450pp
adb shell
zcat /sdcard/mmcblk0.gz | dd of=/dev/block/platform/msm_sdcc.1/mmcblk0 bs=64k
6. pulled battery
7. boot into recovery, restored modemst1 and modemst2
8. successfully boot into CM12.1

This confirms that it is not a hardware issue. It must have something to do with partition layout or the contents of those partitions. I don't see why the layout would make a difference, because they are referred to by name. The VS450PP doesn't have a carrier partition, but I don't think CM uses that. I'll keep experimenting.

elisam98 · Nov 20, 2015

Thanks everyone for the testing and commenting!

I have a new build up with the keymaster fix here:
https://www.androidfilehost.com/?fid=24269982087000841

*Unfortunately, I messed up the keylayout on this build while trying to include a home button fix o_O

I created a quick zip file to temporarily patch the hardware buttons. They won't work until you flash this quick-fix zip file:
https://www.androidfilehost.com/?fid=24269982087000851

The core system seems to be functioning well, but there are 3 issues I'm still seeing with this build:

For some reason, the phone is having a problem transitioning from recovery to the regular system. This was the issue all along and the reason why we have to pull the battery after flashing in order to boot into the regular system.
I think the phone is randomly rebooting, but I haven't had much time to check into it before posting this.
I tried to flash another GAPPS package in this update, but Play Services is still crashing!

Still on the agenda:

Fix the camera
Fix the led ring on the home button

If I missed anything, please let me know.

I'm away for the weekend, so I won't be doing much more today and tomorrow.
But if anyone would like to post any logcats of these or other issues, please feel free!

I will try to capture some of my own when I return.

Good Luck!

jacob019 · Nov 20, 2015

Thanks for all of your hard work. It's awesome to have CM12 on such an inexpensive device. I'll keep testing.
About the problem transitioning from recovery, I don't have that problem.

elisam98 · Nov 21, 2015

Figured out why GAPPS are crashing: SELinux is set to enforcing.
I assume the best way to deal with this is to write a custom init.d script? Is there another another way (such as compiling the kernel with SELinux disabled by default)?

Googling now for a solution...

elisam98 · Nov 21, 2015

UPDATE: Got the SELinuxModeChanger App for a temporary fix. I used the app to change SELinux to permissive at every boot-up...
After installing the app, you can flash the GAPPS package of your choice

Here is the app:
http://forum.xda-developers.com/showthread.php?t=2524485

* Due to the small size of internal storage, you will need to flash one of the smaller GAPPS packages such as the "micro" or "pico" versions.

elisam98 · Nov 22, 2015

I tried compiling a new boot image with SELinux disabled as per these instructions:
http://graemehill.ca/compiling-permissive-android-kernel

So far, it's not working

However, I fixed the boot image up a little to solve the the other two problems that were present in the Friday's (11/20) build:
https://www.androidfilehost.com/?fid=24269982087002191
(fixes transitioning from recovery and random reboots)

Oh, and I cleaned up the first post a little.

vm03 · Nov 22, 2015

elisam98 said:
I tried compiling a new boot image with SELinux disabled as per these instructions:
http://graemehill.ca/compiling-permissive-android-kernel

So far, it's not working

However, I fixed the boot image up a little to solve the the other two problems that were present in the Friday's (11/20) build:
https://www.androidfilehost.com/?fid=24269982087002191
(fixes transitioning from recovery and random reboots)

Oh, and I cleaned up the first post a little.

For disable selinux, just add
androidboot.selinux=permissive
to BOARD_KERNEL_CMDLINE in BoardConfig.mk

foolsh · Nov 24, 2015

Wow, thanks for all the hard work on this. Love it!

Just wanted to ping back after flashing this to my ls620.

Everything already mentioned,
1. needs keymap fix
2. selinux workaround for gapps
3. camera not work yet
4. home button led

Not mentioned,
1. backlight adjustment not working

Thanks again for this!

elisam98 · Nov 24, 2015

Hey everyone,
I have updated the first post with the newest kernel!
This kernel has SELinux set to Permissive by default, so now you can go ahead and flash GAPPS without worries

I have also recompiled a new zip with all the current fixes (keymaster, keylayout, SELinux) and hopefully some LED support, but there seems to be some issue with the zip file...
Annoyingly, TWRP will only give me a general error message about my updater binary not working

I have been working on this mostly from my 1x data (don't ask - RingPlus

) phone while logging into my Jenkins build server via browser and ssh. This works for compiling, but I'm kinda limited in what I can do with zips.

If anyone wants to take a look at the current zip, here's a link:
https://www.androidfilehost.com/?fid=24269982087003852
It would be awesome if someone took a look at this to help me troubleshoot.

In case anyone's wondering, I'm running the 11/20 package with today's kernel/boot image update and it's working really well!

*As far as the backlight is concerned, I'm not having any adjustment issues - it's working for me. That may have been an issue on Friday's kernel, but I don't see it on today's update...

EDIT: recompiling a possible fix now. I'll keep you posted...

foolsh · Nov 24, 2015

Thanks again elisam98, I got (cm12.1-20151124-UNOFFICIAL-ALPHA-w5c) installed and it fixed the backlight issue. But only after some messing with it.

What I tried:
First, I tried installing cm12.1-20151124-UNOFFICIAL-ALPHA-w5c, it failed with a generic error like you said. Tried a factory reset and the install again, still it failed. I wiped everything and restored my stock backup.

Later, I reinstalled the boot image in the first post. And then installed (cm12.1-20151120-UNOFFICIAL-ALPHA-w5c) still the backlight didn't work right. When I was messing with getting selinux gapps etc installed, I noticed an OTA update cm-12.1-20151121-UNOFFICIAL.

I downloaded it, thought twice about installing it, but figured if it messed my phone up. I could always restore. It failed to install as well, with wrong machine type error. After this, and while I was still in recovery mode, I thought well maybe I'll try the latest again. So while I was in TWRP I tried to install 20151124 with success!

TL;DR;
I got the cm12.1-20151124-UNOFFICIAL-ALPHA-w5c installed, but only after a few tryes and after trying to install an update pushed out OTA (cm-12.1-20151121-UNOFICIAL), but was not the correct machine type (needed w5c) was for w5, w5d

EDIT: Wow I'm sticking to this for my daily use. Much credit to the people involved, awesome job!

jacob019 · Nov 27, 2015

elisam98 said:
If anyone wants to take a look at the current zip, here's a link:
https://www.androidfilehost.com/?fid=24269982087003852
It would be awesome if someone took a look at this to help me troubleshoot.

There is something wrong with /META-INF/com/google/android/updater-binary. I replaced it with the one from the 20151120 build and it worked fine.
http://jacobstoner.com/cm12.1-20151124-UNOFFICIAL-ALPHA-w5c-fix.zip

Double tap to wake isn't working.

T3ch42 · Nov 28, 2015

Hi. Been lurking here lately and have seen a bit of the progress which is pretty impressive to say the least.
I picked up a few VS450PP phone last month for myself and my wife and have been using mine as a mp3 player and GPS tracker for running etc. I modified it using the deodexed/de-bloated fw, but haven't been completely satisfied with the results.
I tried flashing your 11-24-15 image, but that didn't work of course. Is there an image of the flash and modems to apply to the phone first? I'm assuming since the layout isn't the same, that flashing the fw was incomplete for the exceed 2. (I received the warning no os was installed so immediately restored my android bkup).
Thank you for all of the work and progress so far. If there is something I could do to get this working on these phones, I'd be excited. Side-note, I'm also interested in getting these phones on the ring+ network. Will I need donor l70c s msid to use for each of the verizon phones?
Thanks again. If there is anything I can do to try or help out with in this development process, I'll give it a shot.

jacob019 · Nov 28, 2015

@T3ch42 The only way to flash this build to the VS450PP is to replace the entire partition layout, better wait for a proper VS450PP build. To flash it over to sprint/r+ you must replace the modem and flash an ESN, HA, and AAA from a donor phone, that's all I wish to share on the subject.

@elisam98 I think I know why it isn't working on the VS450PP. The vendor sources have hard coded partition sizes that don't match. I think we'll need a different build for it with the following added to BoardConfig.mk:

BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1363148800
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2055733248

elisam98 · Nov 28, 2015

jacob019 said:
@elisam98 I think I know why it isn't working on the VS450PP. The vendor sources have hard coded partition sizes that don't match. I think we'll need a different build for it with the following added to BoardConfig.mk:

BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1363148800
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2055733248

OK. Just forked @vm03 's msm8610-common device tree and updated the partition sizes. Building now...
https://github.com/elisam98/android_device_lge_msm8610-common

elisam98 · Nov 28, 2015

(deleted)

T3ch42 · Nov 30, 2015

jacob019 said:
@T3ch42 The only way to flash this build to the VS450PP is to replace the entire partition layout, better wait for a proper VS450PP build. To flash it over to sprint/r+ you must replace the modem and flash an ESN, HA, and AAA from a donor phone, that's all I wish to share on the subject.

Ah. That answers most of my question. I'll do some more research on the donor topic. Thanks for the answers and development for these phones.

T3ch42 · Dec 5, 2015

Any suggestions for a homemade hack for flashing the realm CyanogenMod to the VS450pp in the meantime? I'm torn between that and trying to get my exceed 2 on the sprint network- would be awesome to have both....It seems that would only be a matter of flashing the modem for the sprint network and trying to sweettalk them into allowing the ESN onto their network.
I've spent a bit of time talking to Verizon tech support regarding activating on a different network, and I'm sure that others have too. Maybe its naivety, but I would hope to get a phone over to sprint without having to flash a "sprint" ESN, haa etc.. Just some thoughts.

jacob019 · Dec 7, 2015

Earlier I posted my recipe for flashing the LS620 full flash image over to the VS450PP. You'll need both phones. Activate first because you won't be able to activate after flashing. As to sweet talking sprint into allowing the ESN, that's not going to happen. Only way is to use a donor, and it isn't worth it when you can pick up an LS620 on ebay for so cheap.

jenco420 · Dec 9, 2015

Has there been any progress towards the vs450pp? Like a flashable zip without having to have both the realm and the exceed.

T3ch42 · Dec 14, 2015

jacob019 said:
...
1. backed up modemst1 and modemst2
2. while in TWRP, I took a backup of the full flash from the LS620:
adb pull /dev/block/platform/msm_sdcc.1/mmcblk0
3. gzip mmcblk0
4. copied the full flash image over to the VS450PP in TWRP
adb push mmcblk0.gz /sdcard/
5. restored the ls620 full flash image to my vs450pp
adb shell
zcat /sdcard/mmcblk0.gz | dd of=/dev/block/platform/msm_sdcc.1/mmcblk0 bs=64k
6. pulled battery
7. boot into recovery, restored modemst1 and modemst2...

Well, I've done these items, but haven't gone to the cm12.1 image yet. Still working on getting the ls620 right.
Have had the boot error, stuck at the lg boot screen for the bumped boot.img and not able to flash the cm 12.1 as it tells me "this is for a w5c, your device is ..."
Not sure if that was something addressed already.
I went ahead in the ls620fw first
Anyhow, I don't think I reflashed my modemst1.bin back right, as I still show 0000000s for all my phone info.
I saw where a proper method for restoring modems would be through fastboot, but you went through adb and twrp. Is that just dd if=modemst1.bin of=/dev/...(not at home so I don't recall the actual partition)be=512 or something like that? I went with the dd input output, but still had blank phone info.
Thanks

jacob019 · Dec 14, 2015

If you correctly flash the LS620 full flash then your phone will become an LS620, and you can install CM12 just like you would on an LS620. When I did it, I already had CM12 running on my LS620 so I didn't have to install anything.

After flashing, you must pull the battery and reboot into TWRP before restoring the EFS. If you did it in the same session, then I recommend reflashing the entire image. After the LS620 full flash image has been loaded onto the VS450PP, you just need to restore the modemst1 and modemst2 partitions:
dd if=/path/to/modemst1_backup of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/path/to/modemst2_backup of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
Did you restore modemst2 also? You need both.

T3ch42 · Dec 14, 2015

Thanks. I think I may have tried to flash them both incorrectly. I'll give it a shot when I get home.
I do have an update though.
Had my vs455 with me today at lunch, and updated to the 11-20 cm12.1 along with the touch update. I used the first bumped boot image from the beginning of the thread. Factory reset, and it allowed to flash ROM. I may have missed that before, but I never saw that prompt.
Seems to be working right now, will see about the modems this evening.
Thanks!

jacob019 · Dec 14, 2015

deleted

T3ch42 · Dec 15, 2015

T3ch42 said:
Thanks. I think I may have tried to flash them both incorrectly. I'll give it a shot when I get home.
I do have an update though.
Had my vs455 with me today at lunch, and updated to the 11-20 cm12.1 along with the touch update. I used the first bumped boot image from the beginning of the thread. Factory reset, and it allowed to flash ROM. I may have missed that before, but I never saw that prompt.
Seems to be working right now, will see about the modems this evening.
Thanks!

No luck with the modems so far. Not sure what is going on, but I was only able to successfully flash the Verizon modemst.bins I backed up. I haven't looked at the ls620 modem yet to see what's inside, but something is wrong. After flashing, I have unknown msl and meid is 00000000000000.
Have followed through multiple times but thinking I'm missing something simple. Like I said before, I was able to get the Verizon version working, but that was a unintended test. The next version recommended seems to be working better, but I still can't log into the play store yet.

Root CM12.1 Alpha Progress...

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Android Expert

Lurker

Well-Known Member

Lurker

Member

Newbie

Member

Well-Known Member

Well-Known Member

Newbie

Newbie

Member

Lurker

Newbie

Member

Newbie

Member

Newbie

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads