[ROM][4.4.4] LineageOS 11.0 for LG Optimus One [OS2SD][19.03.13]

Search This thread
By:
Advanced…
J

josehbermudez

Senior Member
May 6, 2013
164
79
mns123 said:
No, I don't have GmsCoreSetupPrebuilt. Rest all there.
Flashed again. Used Gappslight and signed in Ok.
Click to expand...
Click to collapse
Dear brothers, I really suggest reading and using microG instead gapps. Just try older apps versions from uptodown or f-droid until finding the working ones Some specific apps like YouTube are not working at all but you can find similar ones that do work. Just be patient and try one by one.

I successfully installed telegram(f-droid), lite, WhatsApp tweetcaster youtubeMate (uptodown) and many more from blankstore. Recommend trying OsMand (f-droid) instead Maps.You'll find problems or FC with google dependant apps. Was impossible to run Instagram. I'm still thinking that google simply is not supporting old arm devices neither do actual apk devs.
Recent Hardlight's work opened the way to do it (deodexed it's OS2SD rom and patched it for signature spoofing for us) and worth it to try [emoji6] microG. Marvin's and ale5000's threads are well and easy explained.

Peace for you all [emoji106]

Enviado desde mi Moto E mediante Tapatalk
 
  • Like
Reactions: HardLight and mns123
M

maxim.pashuk

New member
Apr 26, 2017
1
0
Hi all

I follow this thread and sometimes I update rom on my device, and always all things was fine.

I decided to install 20170422 build on my device instead of previous build 20161229.

After successful flashing with TWRP 3.0.2, I am getting an error

"com.android.systemui has stopped" many times.

I tried "adb logcat *:w" and get an detailed error:

"java.io.FileNotFoundException: res/drawable-mdpi/status_background.9.png"

I am not sure how to deal with this message, I am not an android developer.
Am I the only one who get this message?
I tried reinstall rom several times - formatting sd card, partition through gparted and partition through TWRP, f2fs and ext4 as filesystem for /data - the result was always the same

Can somebody help me with this?
 
B

bikeride34

Member
Jul 12, 2015
7
0
I know it's been a month, but I need some help getting this working. Here is what I did first:
  1. Flash the latest TWRP OS2SD recovery here
  2. Attempted to use the recovery to partition the SD card
At which point it gives me an error (Error 4 I think) making the FAT partition and leaves the partition table empty. The only way to get the SD card accessible again is to sideload AmonRa and partition it from there.

Next thing I tried was to partition the SD card with GParted. Just the SD card plugged into my computer, not the phone mounted as a USB drive. Putting the SD card back in, I could not seem to mount it or select a zip on it. So I had to use AmonRa to partition the card again, install TWRP 2.7.0.0 for sideloading support, sideload the TWRP OS2SD recovery and repartition the SD card on my computer. I did all of that and it seemed to go smoothly. Plugged the SD card back in and sideloaded LineageOS. The installation completes "successfully", with errors mounting partitions to /system and /data, and the ROM doesn't seem to boot.

I think the problem might be that for some reason not all the partitions are /dev/mmcblk0p1, /dev/mmcblk0p2, /dev/mmcblk0p3, and /dev/mmcblk0p4. The mounts I see in fstab.p500 are /system mounted to /dev/mmcblk0p2, /data mounted to /dev/mmcblk0p4, and /cache mounted to /dev/mmcblk0p8.

Whether or not this is the problem, why can't I mount the SD card properly and how do I fix this?
 
ibub

ibub

Senior Member
Oct 22, 2012
1,728
1,522
Louisville,Ky
bikeride34 said:
I know it's been a month, but I need some help getting this working. Here is what I did first:
  1. Flash the latest TWRP OS2SD recovery here
  2. Attempted to use the recovery to partition the SD card
At which point it gives me an error (Error 4 I think) making the FAT partition and leaves the partition table empty. The only way to get the SD card accessible again is to sideload AmonRa and partition it from there.

Next thing I tried was to partition the SD card with GParted. Just the SD card plugged into my computer, not the phone mounted as a USB drive. Putting the SD card back in, I could not seem to mount it or select a zip on it. So I had to use AmonRa to partition the card again, install TWRP 2.7.0.0 for sideloading support, sideload the TWRP OS2SD recovery and repartition the SD card on my computer. I did all of that and it seemed to go smoothly. Plugged the SD card back in and sideloaded LineageOS. The installation completes "successfully", with errors mounting partitions to /system and /data, and the ROM doesn't seem to boot.

I think the problem might be that for some reason not all the partitions are /dev/mmcblk0p1, /dev/mmcblk0p2, /dev/mmcblk0p3, and /dev/mmcblk0p4. The mounts I see in fstab.p500 are /system mounted to /dev/mmcblk0p2, /data mounted to /dev/mmcblk0p4, and /cache mounted to /dev/mmcblk0p8.

Whether or not this is the problem, why can't I mount the SD card properly and how do I fix this?
Click to expand...
Click to collapse
Mount os2sd system and os2sd data and use the file manager in twrp to see if the partitions got flashed. If they are indeed populated, then the os2sd boot.img may not have been installed. Without this boot image os2sd doesn't work. On the other hand, If system got flashed to internal system partition, then you may have installed it while in internal mode instead of os2sd mode. You can also check your partitions from wipe > advanced wipe menu > repair partitions , to see if they are formatted to the proper file systems (system and data are ext4).

Sent from my LGL15G using Tapatalk
 
  • Like
Reactions: bikeride34 and xu3sno
B

bikeride34

Member
Jul 12, 2015
7
0
ibub said:
Mount os2sd system and os2sd data and use the file manager in twrp to see if the partitions got flashed. If they are indeed populated, then the os2sd boot.img may not have been installed. Without this boot image os2sd doesn't work. On the other hand, If system got flashed to internal system partition, then you may have installed it while in internal mode instead of os2sd mode. You can also check your partitions from wipe > advanced wipe menu > repair partitions , to see if they are formatted to the proper file systems (system and data are ext4).

Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse

Are there separate Internal/OS2SD modes in the latest recovery,
lineage-11.0.1-20170422-OS2SD-p500.zip? If so, how do I change the mode?
 
ibub

ibub

Senior Member
Oct 22, 2012
1,728
1,522
Louisville,Ky
bikeride34 said:
Are there separate Internal/OS2SD modes in the latest recovery,
lineage-11.0.1-20170422-OS2SD-p500.zip? If so, how do I change the mode?
Click to expand...
Click to collapse
Sorry, I forgot I use the previous twrp-multi which has both modes under the advanced menu. But you should still be able to view the os2sd partitions from the file manager. And I was mistaken about data format. It's f2fs, not ext4.

Sent from my LGL15G using Tapatalk
 
  • Like
Reactions: bikeride34 and xu3sno
B

bikeride34

Member
Jul 12, 2015
7
0
ibub said:
Sorry, I forgot I use the previous twrp-multi which has both modes under the advanced menu. But you should still be able to view the os2sd partitions from the file manager. And I was mistaken about data format. It's f2fs, not ext4.

Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse

Also, I've been using a gpt partition table in GParted, is this correct? msdos can only have one primary partition.
 
B

bikeride34

Member
Jul 12, 2015
7
0
ibub said:
Sounds familiar, but I really don't remember. It's been a couple of years since I used gparted to partition this SD. Did you find file systems in those partitions?

Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse

First, I partitioned the SD card on my computer using GParted. It's gpt with, in this order, a 7 GB FAT32 partition for sdcard, a 500 MB ext4 partition for /system, a 357 MB swap partition, and a 7 GB f2fs partition for /data.

Next, I put the SD card in and sideloaded the latest TWRP (I had a different, older version of TWRP trying to get a different rom before getting a reply here).

Finally, I rebooted into the latest TWRP and sideloaded the latest build of LineageOS. I didn't install from SD card because I know from trying it before that even though the computer can read and copy files on it, the phone cannot when put in USB mode with this partition scheme. When flashing the rom, I got the messages:
Code: 
mount: failed to mount /dev/block/mmcblk0p2 at /system: Invalid argument
unmount of /system failed; no such volume
mount: failed to mount /dev/block/mmcblk0p4 at /data: Invalid argument
unmount of /data failed; no such volume
script succeeded: result was [/system]

Rebooted into the recovery again to make sure everything was refreshed. It warned me that there was no OS installed, I continued anyway. In the mount menu I was able to mount the /system and /data partitions, but not SDCard. Looking through the file system, /system is populated all right, it seems. /data is only populated with an empty lost+found folder, however. /boot is unpopulated, I'm guessing that's where the boot img should be.

This is interesting. Following your advice, I went to repair file system to look at the partition details. /system was the proper size, about 7 GB, and the proper filesystem, ext4. However, /data was only 484 MB and using the ext4 filesystem, when I had originally formatted it in GParted as f2fs. So I'm guessing that flashing /system went okay, but flashing /data did not.

EDIT: Looking at the SD card from the computer, the partition scheme remains the same, but /data is unpopulated.
 
Last edited:
ibub

ibub

Senior Member
Oct 22, 2012
1,728
1,522
Louisville,Ky
bikeride34 said:
First, I partitioned the SD card on my computer using GParted. It's gpt with, in this order, a 7 GB FAT32 partition for sdcard, a 500 MB ext4 partition for /system, a 357 MB swap partition, and a 7 GB f2fs partition for /data.

Next, I put the SD card in and sideloaded the latest TWRP (I had a different, older version of TWRP trying to get a different rom before getting a reply here).

Finally, I rebooted into the latest TWRP and sideloaded the latest build of LineageOS. I didn't install from SD card because I know from trying it before that even though the computer can read and copy files on it, the phone cannot when put in USB mode with this partition scheme. When flashing the rom, I got the messages:
Code: 
mount: failed to mount /dev/block/mmcblk0p2 at /system: Invalid argument
unmount of /system failed; no such volume
mount: failed to mount /dev/block/mmcblk0p4 at /data: Invalid argument
unmount of /data failed; no such volume
script succeeded: result was [/system]

Rebooted into the recovery again to make sure everything was refreshed. It warned me that there was no OS installed, I continued anyway. In the mount menu I was able to mount the /system and /data partitions, but not SDCard. Looking through the file system, /system is populated all right, it seems. /data is only populated with an empty lost+found folder, however. /boot is unpopulated, I'm guessing that's where the boot img should be.

This is interesting. Following your advice, I went to repair file system to look at the partition details. /system was the proper size, about 7 GB, and the proper filesystem, ext4. However, /data was only 484 MB and using the ext4 filesystem, when I had originally formatted it in GParted as f2fs. So I'm guessing that flashing /system went okay, but flashing /data did not.

EDIT: Looking at the SD card from the computer, the partition scheme remains the same, but /data is unpopulated.
Click to expand...
Click to collapse
Data filesystem won't be built until after first successful boot. /boot won't show as a file system, because it's been compressed into an image. You could copy boot.img from the LineageOS.zip and use twrp to install it by selecting "install image" in the install menu. After selecting boot.img be sure to select to install to boot. I had a similar problem once and boot.img fixed it.

Sent from my LGL15G using Tapatalk
 
  • Like
Reactions: bikeride34
B

bikeride34

Member
Jul 12, 2015
7
0
ibub said:
Data filesystem won't be built until after first successful boot. /boot won't show as a file system, because it's been compressed into an image. You could copy boot.img from the LineageOS.zip and use twrp to install it by selecting "install image" in the install menu. After selecting boot.img be sure to select to install to boot. I had a similar problem once and boot.img fixed it.

Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse

Thank you! That got it to boot! Flashed GApps too, but there are still problems.
/data is only 500 MB. It should be 7 GB. How do I fix this?
There's no cellular. I guess there's a baseband zip that I'll have to flash?
And Unfortunately, Google Play Services keeps crashing. I guess that's not a related problem, though.
 
Last edited:
ibub

ibub

Senior Member
Oct 22, 2012
1,728
1,522
Louisville,Ky
bikeride34 said:
Thank you! That got it to boot! Flashed GApps too, but there are still problems.
/data is only 500 MB. It should be 7 GB. How do I fix this?
There's no cellular. I guess there's a baseband zip that I'll have to flash?
And Unfortunately, Google Play Services keeps crashing. I guess that's not a related problem, though.
Click to expand...
Click to collapse
Hey, that's great! Yeah, GAPPs has been a problem, but there are alternatives posted late in this thread. Just reflash system without gapps. Baseband zip might not flash to the os2sd system. If it doesn't, then you will have to unzip it and copy the contained lib files, overwriting the existing files (in /system/lib, I think). The portion of your /data might be able to be recovered via gparted. Run it in Linux, it's better.

Sent from my LGL15G using Tapatalk
 
  • Like
Reactions: bikeride34
B

bikeride34

Member
Jul 12, 2015
7
0
ibub said:
Hey, that's great! Yeah, GAPPs has been a problem, but there are alternatives posted late in this thread. Just reflash system without gapps. Baseband zip might not flash to the os2sd system. If it doesn't, then you will have to unzip it and copy the contained lib files, overwriting the existing files (in /system/lib, I think). The portion of your /data might be able to be recovered via gparted. Run it in Linux, it's better.

Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse

It seems that all of the flashing went wrong. The first partition was intended to be /sdcard, the second was intended to be /system, the third was intended to be swap, and the fourth was intended to be data. Instead, the first partition is /system, the second seems to be /data, the third is swap (as intended), and I don't know what the fourth is because I can't browse it on my computer, but GParted shows it being populated.
I know I said that /system was correctly flashed to a 7 GB partition in a previous post. I was confused.

I have attached photos.
 
ibub

ibub

Senior Member
Oct 22, 2012
1,728
1,522
Louisville,Ky
bikeride34 said:
It seems that all of the flashing went wrong. The first partition was intended to be /sdcard, the second was intended to be /system, the third was intended to be swap, and the fourth was intended to be data. Instead, the first partition is /system, the second seems to be /data, the third is swap (as intended), and I don't know what the fourth is because I can't browse it on my computer, but GParted shows it being populated.
I know I said that /system was correctly flashed to a 7 GB partition in a previous post. I was confused.

I have attached photos.
Click to expand...
Click to collapse
Yeah, gparted is also showing the partitions out of order. /dev/mmcblk0p1 should be vfat, /dev/mmcblk0p2 shows last in the list as f2fs. This is system, and explains why you are actually able to boot. /dev/mmcblk0p3 listed second shows as ext4 but should actually be swap. /dev/mmcblk0p4 (third on the list) shows as swap but should actually be data. So I'm betting that all of the data structure is written to swap, and gets washed away on every power down or reboot. WOW

Sent from my LGL15G using Tapatalk
 
Last edited:
  • Like
Reactions: xu3sno
B

bikeride34

Member
Jul 12, 2015
7
0
ibub said:
Yeah, gparted is also showing the partitions out of order. /dev/mmcblk0p1 should be vfat, /dev/mmcblk0p2 shows last in the list as f2fs. This is system, and explains why you are actually able to boot. /dev/mmcblk0p3 listed second shows as ext4 but should actually be swap. /dev/mmcblk0p4 (third on the list) shows as swap but should actually be data. So I'm betting that all of the data structure is written to swap, and gets washed away on every power down or reboot. WOW

Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse

This does, however, reflect the order that I created the partitions in GParted. I started with a 7 GB partition at the beginning, next a 7 GB partition at the end, and finally the two in the middle. I didn't think that would have an effect on things. Plus, doesn't it vary from system to system whether a partition is shown as /dev/sda1 or /dev/sda2? I was expecting that phone would put the first partition on the disk as /dev/mmcblk0p1, the second as /dev/mmcblk0p2, etc... Why would it not do that?

Rebooted the phone, apps I downloaded are still on there. Data is persistent, on the second partition of the sdcard. Maybe the partition scheme the installer expects has changed from OP? /system on the first partition, /data on the second, swap on the third and /sdcard at the end?

Also, to confirm, is the sdcard partition supposed to be FAT32 or VFAT?
 
You must log in or register to reply here.

Similar threads

mukulsoni
  • Poll
[DEV][ROM][4.4.2][CM11] KITKAT for LG-P500 [WIP][VER-12 OTA]
Replies
2K
Views
718K
kayuz
kayuz
neko95
  • Poll
[ROM] MAY-28-13 | ICySNAP v2.0 GOLDEN EYE | ICS 4.0.4 | LGE 3.1 UI | Extended FINALE!
Replies
7K
Views
1M
V
vadims746
marcomarinho
  • Poll
[ROM] [CM] [JB] [4.2] [JDQ39E] NexusBean 1.0 - Build 1 [24-11-13]
Replies
2K
Views
447K
willioth
willioth
N
[FIRMWARE] LG Optimus One P500 Original ROM's [DOWNLOAD]
Replies
55
Views
171K
niral.naik
niral.naik
N
[OFFICIAL TEST FIRMWARE] Gingerbread 2.3.3 for Optimus One P500 LEAKED!!!
Replies
322
Views
161K
N
ntnlzr

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 101
    HardLight
    HardLight

    LineageOS 11.0

    3i30r4mgbd5z3eb6g.jpg

    LineageOS is a free, community built, aftermarket firmware distribution of Android 4.4 KitKat, which is designed to increase performance and reliability over stock Android for your device.

    Code: 
    #include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


    This is LineageOS 11.0 for LG Optimus One OS2SD edition based on androidarmv6 jenkins builds. I made this edition to solve lack of space in our P500 and and improve phone performance because many todays MicroSD cards are faster then this phone internal storage. What it does, it mounts /system and /data on SD card ext4 partitions, so this way you can have as many space as you want to install apps and flash untrimmed gapps without using any a2sd mods, link2sd, manual symlinking or dalvik2cache.


    What's working:
    • Supports all android 4.4 (KitKat) features
    • Fully functional camera (preview, taking photo, recording video, panorama)
    • Full H/W acceleration with new adreno drivers, 3D modelling (yamato)
    • Hardware decoding of videos, Youtube HQ videos
    • Internet sharing (Bluetooth tethering, USB tethering, Wi-Fi hotspot)
    • Calls, SMS, MMS, 3G/2G, Mobile data, Data limit
    • Loudspeaker in call, Manual network search
    • Usb mass storage, Usb debugging
    • Wi-Fi, Bluetooth, Bluetooth headset, A2DP (Bluetooth Music), Car dock w/BT
    • GPS, Sensors, Lights, Touch screen
    • Funny SIM (128k USIMs)
    • Browser, GMail, GPlay
    • Youtube LQ/MQ/HQ
    • Offmode charging
    Known issues
    • Wi-Fi wakelock because of the old bcm4325 wireless driver
    • Swipe in stock keyboard because of missing armv6 libs
    • FM Radio (bcm4325 FM chip is depends on bluez-hcitool)
    • After Wi-Fi hotspot reboot is required to use Wi-Fi

    Installation instructions:

    I am not responsible for lost data or dead SD card, do this at your own risk.
    1. Backup all you data with Titanium Backup or alternatively use "Migrating to new file system without loosing data" method
    2. Backup all SD card contents to PC
    3. Flash TWRP recovery (20161230 or later)
    4. While in TWRP go to Advanced>Partition SD Card and use default partition sizes or adjust it depending on your needs.
      Also you can do partitioning on computer.

      Use exact order and recommended partitions sizes as listed below
      • FAT32 primary for /sdcard
      • ext4 primary for /system (448 MB or more)
      • linux swap primary for /swap (64MB or more)
      • ext4 primary for /data (1024 MB or more)
      Partitioning guides:
      MiniTool Partition Wizard (Windows):

      1. You need to start with one partition formatted with fat32 (or unallocated space to create fat32 partition and skip 2 step):

        6tj13kx6s58csij6g.jpg

      2. Right click the fat32 partition and use Move/Resize tool to shrink that partition:

        xb39bgvecvrqxqm6g.jpg

        aebpkfx789x3sz06g.jpg

      3. Right click on unallocated space and select Create. Following this create ext4, swap and again ext4 partitions:

        352sx3xdq93wb8d6g.jpg

        rutvlt7ijsb4kxx6g.jpg

        l3ff44lacezvqae6g.jpg

      4. After that you should end with this configuration (partitions sizes may differ) then hit Apply:

        jb864l6yl7b9ef26g.jpg
      GParted (Linux)

      1. You need to start with one partition formatted with fat32 (or unallocated space to create fat32 partition and skip 2 step):

        lehj5msjh8d2ja36g.jpg

      2. Click the fat32 partition and resize it to shrink partition:

        088jyp8xdcv5n8i6g.jpg


      3. On unallocated space create create ext4, swap and again ext4 partitions:

        47v7187ysp11l1k6g.jpg

        7vll4nn8o7muszl6g.jpg

      4. After that you should end with this configuration (partitions sizes may differ) then hit Apply:

        43efl3ihe5ktf3a6g.jpg
    5. Copy all SD content from PC back
    6. Flash latest Rom and Gapps
    7. After system booted restore your data with Titianium Backup or alternatively use "Migrating to new file system without loosing data" method

    Important! For f2fs rom make sure you have /data partition formatted with f2fs.
    Instructions:
    Note /data will be formated! Follow method above to backup data.
    In TWRP Go to Wipe>Advanced Wipe select Data. Then Repair or Change File System>Change File System>F2FS.
    Note: To reverse /data back to EXT4 do the same as above except select EXT4 in last step.

    Migrating to new file system without loosing data:
    What do I need to migrate without loosing data?

    1. ADB installed on your PC (somehow adb in recovery working only on linux for me) or use Terminal emuliator on TWRP
    2. sdcard with enough memory to backup whole your /data partition

    How to perform a migration?
    1. Reboot to recovery.
    2. Go to Mount menu and make sure that /data and /MicroSD are selected.
    3. Open Command Line (Windows) or Terminal (Linux/OS X) on your PC or Terminal emuliator on TWRP
    4. Type: adb shell and press ENTER (skip this if you are using Terminal emuliator on TWRP).
    5. Type: tar -cvpzf /sdcard/data.tar.gz /data
    6. Wait until operation will finish. If you see any error, it means you don’t have enough free space on your SDcard.
    7. Perform steps to format /data to new file system.
    8. Go to Mount menu and make sure that /data and /MicroSD are selected.
    9. Now type: tar -xvpzf /sdcard/data.tar.gz -C /
    10. If previous step didn’t produce any error, reboot your phone and check if it’s boot succesfully. If yes, you can safely remove data.tar.gz file from your SD card.
    11. Done. You have migrated to new file system without loosing your data!

    Recommendations:
    • Use Class 6 or even Class 10 SD card for best performance
    • CPU settings: SmartassV2 480-748 MHz
    • I/O Scheduler: I've read that for emmc devices (sd card) best choice is SIO, but Deadline is also very good, please leave your feedback

    Screenshots:

    0mm2jkaqukro8296g.jpg

    DOWNLOADS

    Thanks to:

    LineageOS for sources
    AndroidMeda, Conn O'Griofa and other members of androidarmv6 for bringing KitKat to P500
    skinbark, bigsupersquid for help on OS2SD mod

    XDA:DevDB Information
    LineageOS 11.0 OS2SD, ROM for the LG Optimus One P500

    Contributors
    HardLight
    Source Code: https://github.com/os2sd

    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.0.x
    Based On: LineageOS

    Version Information
    Status: Stable

    Created 2014-10-17
    Last Updated 2019-03-14
    View
    20
    HardLight
    HardLight
    Update 2014/12/11

    Changelog:
    Code: 
    - CyanogenMod 11.0 sources updated to 2014/12/10
- All updates from androidarmv6
- Moved CMUpdater to extras (useless on this rom)

    This is probably final update for CM 11 (unless there will be some major changes).
    I wanna say thanks for all of you because without you this rom wouldn't made this far ! :D
    Download
    View
    18
    HardLight
    HardLight
    Happy New Year

    Hi all who are still following p500 forums in 2016! :highfive:
    I couldn't let this great phone to live with 2015 OS, so here is a little New Year present to all p500.
    There are two versions: EXT4 (/data fs is ext4) and F2FS (/data fs is f2fs), choose which one is better for you.
    Also it is recommended to use twrp-2.8.7.0, although if you need twrp-multi capabilities stick with previous recovery version.

    Changelog:
    - CyanogenMod 11.0 sources updated to 2016/01/01
    - Miscellaneous security updates form CM
    - Add lz4 compression algorithm for zRAM
    - Updated zRAM
    - Decrease zRAM size to 160MB
    - Change swappiness to 80
    - Add row as the default scheduler
    - Updated f2fs
    - Other kernel updates
    Click to expand...
    Click to collapse
    View
    15
    HardLight
    HardLight
    Cm11 os2sd 20150510

    Our beloved P500 had a long but hard life. Its system partition never felt safe because phone master even once a week launched recovery... It is time to settle down little OOne :)
    As you should already realized this is last time I update my OS2SD project. I must say it was really fun to enter Android world through P500 - 5 year old phone with almost no limits because of its great community :good:
    Anyone who liked the idea of OS2SD can investigate my source on https://github.com/os2sd and build CM11 for P500 or adopt the concept for other devices.

    Changelog:
    - Full CM11 - all apps, media, binaries included (does not require larger /system because changelog #2)
    - Switched to ext4 for /system and /data (f2fs used too much space for little performance improvement in some areas)
    - Increase zRAM to 192MB for better multitasking
    - Included all locales
    - Enabled HighEndGfx mode, 16bpp surface formats and KSM by default
    - Overclock CPU by default (480-748 MHz)
    - Changed IO scheduler to SIO by default
    - Enabled MultiUser (you can switch accounts with power menu or on lockscreen in landscape mode)
    - CyanogenMod 11.0 sources updated to 2015/05/10
    Click to expand...
    Click to collapse
    If you coming from previous versions with f2fs, remember to convert /data partition to ext4 on TWRP. To backup data read "Migrating to new file system without loosing data" in OP.

    Also uploaded new Minimal Gapps package.
    DOWNLOAD ROM
    View
    11
    HardLight
    HardLight
    Twrp 2.8.3.0 multi 14/12/30

    Hey, uploaded new TWRP-multi version for p500! :D

    Changelog:
    Code: 
    What's new in 2.8.3.0:

    MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    MTP will now tell the host PC that storage is removed instead of disabling MTP completely
    MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
    Update and improve fix permissions and make fixing contexts optional
    Update SuperSU in TWRP to 2.40 and update install process
    Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
    Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
    Fix kernel panic during MTP start on some devices
    Support unicode fonts on devices with True Type Font support
    Fix slider value not showing sometimes (vibration settings page)
    Toggle MTP off during adb sideload to set correct USB IDs
    Reduce library requirements for 5.0 L decrypt
    Other minor fixes and improvements

What's new in 2.8.2.0:

    MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    Pull in all changes from Android 5.0 lollipop into TWRP
    Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
    Revert some changes to exFAT that were breaking exFAT support on some devices
    Other minor fixes and updates

Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9

So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
What's new in 2.8.1.0:

    MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    TrueT

What's new in 2.8.1.0:

    MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
    Temperature support - thanks to bigbiff
    Various other bugfixes and tweaks

What's new in 2.8.0.1:

    Fix a bug that caused weird graphics and touch issues

What's new in 2.8.0.0:

    Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
    Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
    Add support for color in the console and give error, warning, and highlight lines different colors
    Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
    Improve handling of /misc thanks to mdmower
    Improve setting of time on Qualcomm devices thanks to [NUT]
    Allow using images on slidervalue GUI objects thanks to Tassadar
    Allow using variables and addition and subtraction in variables for easier theming
    Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
    Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
    Other minor fixes and improvements

Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.

Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.

Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.

    Download
    View

New posts