Important information:
This thread is for LineageOS 18.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
Google Drive
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Changelog:
Changes for wt88047x
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@nicknitewolf, Lineage Team
ROM OS Version: 11.x R
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS
Please do note that you HAVE to resize your partition with the tool above, otherwise the ROM will NOT install.
If the link above wasn’t clear enough:
nicknitewolf said:
Please do note that you HAVE to resize your partition with the tool above, otherwise the ROM will NOT install.
Click to expand...
Click to collapse
Hey brother, First of all thanks a lot for keeping this device alive! Any idea about LTE? It seems to not be working in my device, the ROM is fluid smooth and works without any bugs! Thanks brother!
Oops! forget to mention few things for the people who want to install this ROM:
1.You have to RESIZE the SYSTEM PARTITION! without doing so, the ROM won't install!!!
2. How to resize the system partition? Here's how:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
Go to the above link and follow the instructions to resize your system partition.
(Recommended resize gb is 2.00gb)
3. After installing the ROM, it could take 40 to 45 minutes to boot into the system (mine took 30 min).
4. When you boot into the ROM, it might be very laggy and the device might heat up very rapidly, it's not a problem, wait for 10min or so for the device to cool down then start using your device. It'll become smooth like butter.
HUGE THANKS TO THE DEVELOPER (@nicknitewolf) OF THIS ROM FOR KEEPING REDMI 2/ REDMI 2 PRIME ALIVE!!!!
THANKS @nicknitewolf !!!!!!!
Thank you master
thank you, bro
nicknitewolf said:
Please do note that you HAVE to resize your partition with the tool above, otherwise the ROM will NOT install.
Click to expand...
Click to collapse
I got an error when executing the resize partition script, it said unknown partition detected (or something like that). I did that with latest official TWRP.
So I try to download the reccomended TWRP from the OP, but the link seems not working.
Any suggest to past that error? I don't try the other partition resizer methode yet... Thanks in advance
didhiy said:
I got an error when executing the resize partition script, it said unknown partition detected (or something like that). I did that with latest official TWRP.
So I try to download the reccomended TWRP from the OP, but the link seems not working.
Any suggest to past that error? I don't try the other partition resizer methode yet... Thanks in advance
Click to expand...
Click to collapse
I got the same problem as you mentioned above, please use this link and follow the methods to resize the partition:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
This should resize your partition.
thanks dev, good rom even if the features are not many ... it is enough to change the system size to 1.5gb to install this rom. 1 day of use has not found a bug.
Initial impressions of LOS 18.1
1. Rom runs smoothly without gapps (i think gapps are causing higher boot time)
2. No bugs till now using for more than a day.(i will report if anything found)
3. system partition of minimum 1.5 gb required to install.
What's about battery ?? It's completes fast or it's better ?
Nicknitewolf pls reply why battery is draining fast in custom roms ??
didhiy said:
I got an error when executing the resize partition script, it said unknown partition detected (or something like that). I did that with latest official TWRP.
So I try to download the reccomended TWRP from the OP, but the link seems not working.
Any suggest to past that error? I don't try the other partition resizer methode yet... Thanks in advance
Click to expand...
Click to collapse
Thats you have resized your partitions before. You have to have the original partition layout before you are able to flash my script in OP
resize_v2_wt88047x.zip
drive.google.com
ilikephones98 said:
Hey brother, First of all thanks a lot for keeping this device alive! Any idea about LTE? It seems to not be working in my device, the ROM is fluid smooth and works without any bugs! Thanks brother!
Oops! forget to mention few things for the people who want to install this ROM:
1.You have to RESIZE the SYSTEM PARTITION! without doing so, the ROM won't install!!!
2. How to resize the system partition? Here's how:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
Go to the above link and follow the instructions to resize your system partition.
(Recommended resize gb is 2.00gb)
3. After installing the ROM, it could take 40 to 45 minutes to boot into the system (mine took 30 min).
4. When you boot into the ROM, it might be very laggy and the device might heat up very rapidly, it's not a problem, wait for 10min or so for the device to cool down then start using your device. It'll become smooth like butter.
HUGE THANKS TO THE DEVELOPER (@nicknitewolf) OF THIS ROM FOR KEEPING REDMI 2/ REDMI 2 PRIME ALIVE!!!!
THANKS @nicknitewolf !!!!!!!
Click to expand...
Click to collapse
Please do not use this method… I will not be supporting it. Consider using my tool here:
resize_v2_wt88047x.zip
drive.google.com
I guess it was too buried in my OP
nicknitewolf said:
Please do not use this method… I will not be supporting it. Consider using my tool here:
resize_v2_wt88047x.zip
drive.google.com
I guess it was too buried in my OP
Click to expand...
Click to collapse
Hi Nick devoloper, can you provide information or instructions how to use resizev2 tool .just need flash zip from twrp or extract zip,use some instructions to extended partitions.
Update.2---ok I got it .just flash zip.forgot above question.
nicknitewolf said:
Please do not use this method… I will not be supporting it. Consider using my tool here:
resize_v2_wt88047x.zip
drive.google.com
I guess it was too buried in my OP
Click to expand...
Click to collapse
Just asking:
I know the resize tool will make the OEM partition bigger than stock, but it's still too small for vendor image without compressed using squashfs.
Why didn't you make it to fit uncompressed vendor image altogether?
How to install digital wellbeing on mindgapps gapps.opengapp have option to download microgapp to get Google digital wellbeing.Here playstore didn't search offical Google digital welling .is their another version of mindgapps including digital wellbeing to get digital wellbeing features?
nicknitewolf said:
Thats you have resized your partitions before. You have to have the original partition layout before you are able to flash my script in OP
resize_v2_wt88047x.zip
drive.google.com
Click to expand...
Click to collapse
Nope, I never resizing my partition before.. I believe I still have the original partition layout.
This guy before me have the same error then he try the unsupported methode, while I still figure out how to pass the error on official tool.
Additional info, mine is 1/8 not 2/16 model...
ilikephones98 said:
I got the same problem as you mentioned above, please use this link and follow the methods to resize the partition:
[TWRP][AROMA][WT88047] Resize System partition Easily
With this tool is possible resize the system partition. Precautions and warnings: This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups. Increasing the size of the system will...
forum.xda-developers.com
This should resize your partition layout
Click to expand...
Click to collapse
didhiy said:
Nope, I never resizing my partition before.. I believe I still have the original partition layout.
This guy before me have the same error then he try the unsupported methode, while I still figure out how to pass the error on official tool.
Additional info, mine is 1/8 not 2/16 model...
Click to expand...
Click to collapse
@nicknitewolf
Same here too. And i used unsupported method to resize partition after failed attempts with the official one.
My device is 1/8 one.
If anyone want Gapps and try above nano for arm for andriod 11.
OpenGApps - Browse /arm/test/20210110 at SourceForge.net
OpenGApps daily releases
sourceforge.net
dabakale said:
@nicknitewolf
Same here too. And i used unsupported method to resize partition after failed attempts with the official one.
My device is 1/8 one.
Click to expand...
Click to collapse
I can’t really test the 8gb version. I would need the original partition layout. (I HAVE TO EMPHASISE TO USE THE ORIGINAL UNMODIFIED PARTITIONS BEFORE DOING THE FOLLOWING)
Import parted into recovery as per this thread: https://forum.xda-developers.com/t/wt88047-redmi-2-resize-system-partition.3612933/
Code:
./parted /dev/block/mmcblk0
u b p
Reply with the output.
EonJone said:
If anyone want Gapps and try above nano for arm for andriod 11.
OpenGApps - Browse /arm/test/20210110 at SourceForge.net
OpenGApps daily releases
sourceforge.net
Click to expand...
Click to collapse
Use MindTheGapps
nicknitewolf said:
I can’t really test the 8gb version. I would need the original partition layout. (I HAVE TO EMPHASISE TO USE THE ORIGINAL UNMODIFIED PARTITIONS BEFORE DOING THE FOLLOWING)
Import parted into recovery as per this thread: https://forum.xda-developers.com/t/wt88047-redmi-2-resize-system-partition.3612933/
Code:
./parted /dev/block/mmcblk0
u b p
Reply with the output.
Use MindTheGapps
Click to expand...
Click to collapse
@nicknitewolf
Here is my partition layout (I first reverted to stock rom by flashing through Mi flash then took this)
And the error screenshot.
Related
Temasek's UNOFFICIAL CM13.0 BUILDS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.
DISCLAIMER
Code:
/*
* 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. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
FAQ: "Q: Have problems connecting to your Wi-Fi router? -> A: Make sure you have selected the correct region/country code in the advanced wi-fi settings!"
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
@temasek
@arter97
@Chainfire
@benand - for highlighting a dam error that i had missed for over a month, thanks
CM Team]
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
Temasek
Rom Source
Changelogs
Temasek Github Changelog
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65559375&postcount=2252
Basketbuild Download - Backup Download Location (OR for those not in Google Shares)
https://basketbuild.com/devs/Joshndroid/Temasek Roms/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
joshndroid said:
more maybe
Click to expand...
Click to collapse
Any plans to support P601 variant, only Phone calls & 3G to be activated or added.
Much appreciated if you got the time to add this to your rom building,
Unfortunately not. Firstly because I don't have the device. Secondly I don't have the skill set to create a working device tree from relative scratch. Lastly Samsung suck for exynos based devices, sorry.
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Unfortunately not. Firstly because I don't have the device. Secondly I don't have the skill set to create a working device tree from relative scratch. Lastly Samsung suck for exynos based devices, sorry.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thought as long as they have the same Hardware , same tree would be applied and just adding a modem to it.
lsherif said:
Thought as long as they have the same Hardware , same tree would be applied and just adding a modem to it.
Click to expand...
Click to collapse
Lol
Not so simple.
temasek said:
Lol
Not so simple.
Click to expand...
Click to collapse
I know that for sure it is not that simple, but if you got the time to support this , would be my pleasure to test
need p601
p601 support please all devs i beg for this
thank,merci
hello thanks you for this new rom
Nice job!
P605/P607 please someone. A realible working one!
I'm using temaseks build for my note 3 and love it. Is there anyway to get it ported for the 605 lte model? I'd try but I have no idea how to build/port roms
davitox87 said:
I'm using temaseks build for my note 3 and love it. Is there anyway to get it ported for the 605 lte model? I'd try but I have no idea how to build/port roms
Click to expand...
Click to collapse
Running it on my S5 and I love it. P605 or P607 for me would be lovely.
after I tested...
I have this rom installed on my P601...
Not workings:
Camera
Flash light
Mobile Data and Sim Card
SuperSU
And some more...
But there is some thing that i love this rom... And it's because VPN connections works well
And it doesn't become so hot.. And will not die anymore... Nice work..:good::good:
Well at least you know it is not for your device? lol...
I always flash latest version of supersu and never rely on inbuilt su... I believe it may be addressed in temasek source though
New build tomorrow being a shift worker sucks sometimes.
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Well at least you know it is not for your device? lol...
I always flash latest version of supersu and never rely on inbuilt su... I believe it may be addressed in temasek source though
New build tomorrow being a shift worker sucks sometimes.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
SuperSU built-in from next build.
I might even totally remove Superuser.
BTW I'm a shift worker too and I spin builds like nobody business.
How is battery life with this one? And stylus functionalities? Not that I use it... ever. Just wondering how close it is getting.
Since it's tema's name in the name of the rom, I'm considering tearing my warranty into pieces
Any additional encouragements (or discouragements)?
temasek said:
SuperSU built-in from next build.
I might even totally remove Superuser.
BTW I'm a shift worker too and I spin builds like nobody business.
Click to expand...
Click to collapse
Yeah I have been reading github for additions
It's just the lack of time, a fresh cleaned out folder takes about an hour to build with lollipop no matter device. Takes 4 minutes with a dirty out folder. Comparison kitkat took 36 minutes with a fresh out folder and about 16 for a dirty. I want to be able to eventually build for about 4 or 5 devices so Just grabbed a new charger for my older i7 qosmio laptop... Gonna throw a big ssd in it coupled with a 1tb hdd and use it as a dedicated build box, rather burn that out churning builds than my clevo beast..
perozu said:
How is battery life with this one? And stylus functionalities? Not that I use it... ever. Just wondering how close it is getting.
Since it's tema's name in the name of the rom, I'm considering tearing my warranty into pieces
Any additional encouragements (or discouragements)?
Click to expand...
Click to collapse
I'm getting good battery life as for stylus I'll try my note 3 stylus and report back
Sent from my SM-N9005 using Tapatalk
Stylus works as it should the little mouse arrow shows and can even move the pointer around without actually touching the screen
Sent from my SM-N9005 using Tapatalk
Nexus 4 Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Installation
HTML:
# Before processing further we highly recommend you to use our TWRP which has support of EFS/Persist backup
# Or you might lose your IMEI/WIFI + BT mac addresses
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors.
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you using this guide to restore your phone back
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- ddaggebi for 8GB model layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 4 Repartition, Tool/Utility for the Google Nexus 4
Contributors
Clamor, sudokamikaze
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. To be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You shoud check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to discribe what you did and enclose partition.log to your post.
MAKO STOCK
Code:
21 159383552B 1040187391B 880803840B system
22 1040187392B 1627389951B 587202560B cache
MAKO MODIFIED
Code:
21 159383552B 1732247551B 1572864000B system
22 1732247552B 1994391551B 262144000B vendor
23 1994391552B 2099249151B 104857600B cache
4. If you have touchscreen problems use common instructions till you reach entering word. Than plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
5. Flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
bgoel4132 said:
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
Click to expand...
Click to collapse
Plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
ddaggebi said:
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
Click to expand...
Click to collapse
PM me, I need a partition table and I'd ask you to test if you have 8GB model.
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
cyberon said:
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
Click to expand...
Click to collapse
Sure. In PM.
OK so my nexus 4 can't transfer files to or from PC at all so if I do this and have the ROM downloaded it will wipe the ROM and the ROM would be gone and my phone would be a nice brick because I can't transfer any files to my PC like it charges with the PC but data transfer doesn't work so again would I be screwed?
@Nathan4923 correct. Usb connection and PC are mandatory
For those who downloaded repartition pack before this message is published, please redownload pack since previous version might have a problems with repartition. If repartition was already made, don't worry everything should be fine. Just use up-to-date pack.
can i return back to old partition if i want to? i hope someone would post a video tut for this one
@jluspo you can with same zip and same steps as for repartition. You didn't read first post carefully.
Clamor said:
@jluspo you can with save zip and same steps as for repartition. You didn't read first post carefully.
Click to expand...
Click to collapse
im using xda appits different layout on browser
I'm I doing it right? I still can't flash gapps
failed to mount Vendor, any suggestions ?
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are designed to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Clamor said:
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are desined to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Click to expand...
Click to collapse
Thanks for the help !
I've found that even with that error, i still succed the process
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Mato_xXx said:
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Click to expand...
Click to collapse
just read the OP carefully it already mentioned that you had to resize system after installing rom
you can do that by going to advanced wipe in twrp
- T R E B L E Y -
Android Partition Treblerizer
A tool able to seamlessly create / remove the vendor partition from within TWRP
INTRODUCTION
The creation of a tool able to create and remove the supplier partition from TWRP, so a computer was not required. So I created this flaming TWRP ZIP which can create and remove the vendor partition from the userdata system or partitions without a computer and without deleting the files in the mother partition in the recommended configuration.
Trebley, finally, also expands on our much loved Galaxy Note 8, bringing with it Project Treble on the much loved device.
The tool will try to resize the mother partition without deleting it, either during the creation and removal of the supplier partition. However, this can only be done when the mother partition is ext4, only when the supplier partition is at the end of the mother partition and when the mother partition is not encrypted. The recommended configuration is the one that is obtained by selecting the first option in each option: subdividing 512 MB from the end of the system partition. A reboot is required after applying the patch to the partition table because the kernel needs to reload it before doing anything else.
REQUIREMENTS
Due to the use of a key detection binary, it is compatible only with ARM and ARM64 devices running TWRP. So far I have tested it in the Samsung Galaxy Note 8 but It should work in any compatible device. I made it this way so other legacy devices could transition to Treble ROMs + GSI, and Android Pie. Please let me know about other devices using this tool!!!!!
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED AND IF YOU FOLLOW MY STEPS BELOW, YOU WILL LOSE YOUR WARRANTY, KNOX WILL DISPLAY 0x1! I'M NOT RESPONSIBLE FOR ANY DAMAGED DEVICE!.
!!! Whatever you do, it is at your own risk !!!
Either for creating or removing a vendor partition, follow these steps:
1. Download the TWRP ZIP tool to your External SD card.
2. Boot to TWRP recovery, under Install, flash the ZIP file as any other ROM or MOD file to execute the tool.
3. Reboot to recovery again to ensure the changes are applied properly.
4. In some cases you will need to format the mother partition after adding or removing the vendor partition next to it.
CREATE A VENDOR PARTITION:
So far these are the available options:
Mother partition selection: system / userdata
Split position: Splitting from the end / start of the mother partition.
Vendor partition size: 512 / 915 MB
REMOVE THE VENDOR PARTITION:
Should a Vendor module already exists, Trebley offers to remove it, returning to a Non-Treble partition table. It will return the space to the mother partition, system or userdata. So, older non Treble ROMs could be flashed after the mandatory reboot.
DOWNLOAD
Trebley_APT_v1.0_ARM_20190215-signed.zip
SOURCES
All rights reserved to the project: Party and its creator(@Oki).
CAUTION
Currently, we recommend the use of Trebley, exclusively to developers, as until now there has been no development of material related to the project treble, this project lays the foundations creating the partition vendor, for the support treble.
CREDITS
@someone755 for the keycheck binary
@Zackptg5 for the V4A install script that inspired my version.
@Oki for the base script.
XDA:DevDB Information
[PARTITION][TREBLE] Project Treble for Samsung Galaxy Note 8 [SM-N950F][15.02.2019], Tool/Utility for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
DarioRetr
Source Code: https://forum.xda-developers.com/axon-7/development/tool-party-v0-1-vendor-partition-t3831517
Version Information
Status: Alpha
Current Stable Version: V1.0
Stable Release Date: 2019-02-26
Current Beta Version: V0.5
Beta Release Date: 2019-02-15
Created 2019-02-17
Last Updated 2019-02-17
oh my lord - it is happening. treble for the Note8 - just think of the possibilities :victory:
thank you unbelievably much:highfive:
WOAH dude! Finally its happening
edit: tried this and any combination i try i get a Error 2 error!
Any ideas? Or should i try this with a full wipe and try and flash it?
joluke said:
WOAH dude! Finally its happening
edit: tried this and any combination i try i get a Error 2 error!
Any ideas? Or should i try this with a full wipe and try and flash it?
Click to expand...
Click to collapse
Dont flash this yet. There's no rom compatible with this. Note that this is just a script to create partition.
v0ne said:
Dont flash this yet. There's no rom compatible with this. Note that this is just a script to create partition.
Click to expand...
Click to collapse
Ups
I'll keep it for the future then ^^
Guys, this script is currently recommended for use only you have developer, make the device compatible for Project Treble, but you need some developer of the scene, compatibilizzai kernel source for project treble, and give you the vendor.img and boot.img including a custom twrp, to be able to use a GSI and then project treble.
Furthermore, the operation of the script on all versions of Note 8 is not guaranteed.
Oh my god, here it is, but I hope that it doesnt end in the first build like everything else for note 8
Thanks devs but please dont quit now
This is insanely good work. This is so cool :laugh:
Deleted
I flashed this and got an error in TWRP.
Most likely because /dev/block/bootdevice doesn't exist on Note8, but this script is searching for that.
Shadow7107 said:
I flashed this and got an error in TWRP.
Most likely because /dev/block/bootdevice doesn't exist on Note8, but this script is searching for that.
Click to expand...
Click to collapse
What model do you have of Samsung Galaxy Note 8?
For advice and support, I suggest you join the Trebley - Making the future group!
https://t.me/joinchat/I5PCthNlYmrJ4YQY8xxXSg
Dirty Unicorns Android 9, PIE by Flintman for HP TouchpadClick HERE for How to Flash the ROM
________________________________________________________________
Work in progress, not workingBluethooth
Camera
Home button________________________________________________________________
Disclaimer: I am not a developer, just a regular user like YOU.
That have found a way to improve the Tablet and would like others to benefit by sharing the information.
I am not the creator of the ROM or Recovery mentioned.
All credits goes to the developer@flintman and the Dirty Unicorns Team.
________________________________________________________________
Nice Find Thanks!
Touchie Pad said:
Nice Find Thanks!
Click to expand...
Click to collapse
You are welcome!
The following does not work, installing only the ROM.
Camera
Bluetooth
Youtube plays very well
Very smooth
Microphone works.
Wifi works perfectly.
The only problem is that the internal storage is not accessible.
It can not even save screenshots, no access. ( it is fix on the 3-28-2019 version )
I dirty flashed the 13.x over 12.5x and did not do the open gapps, so I will have to sideload them I guess at some point since I cannot get to internal storage like you said.
It boots up, but lots of stuff does not work (like bluetooth). At least the March 2019 security updates are in place!
Thanks
I can't believe we now have Pie on the old work horse. Thank you so much. I wiped everything but internal storage and did a clean install with open pico gapps. I had previously installed the DU swap in the boot directory and booting with it goes to a boot loop. I went back to 8.1 and deleted the DU swap in the boot directory and did another clean install of 9. It came right up and the few apps I have installed work. I tried installing YouTube but the play store says this version is not compatible. It won't even show it as an option. There is no access to storage from either the files app or ES File Explorer. I even tried USB with Windows and android shades out the file transfer option. All my other Pie devices give you an option in setting to set up the SD as either removeable or internal memory. I am wondering if we need to reformat internal memory to get access. I hate to kill it since I have all my install files there as well as TP Toolbox. Any suggestions welcome.
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage. ( is all fixed on version 3-28-2019 )
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
HP_TOUCHPAD said:
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage.
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
Click to expand...
Click to collapse
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes. I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working. I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
johnbelloh said:
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes.
The partition sizes applied using the following:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
Will work with Pie, Q and any future release of Android.
The /system partition is set to 1.8G, which can accommodate a Super variant of the google open gapps.
I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working.
Is storage space not Memory or RAM. It will be about 500MB to 600MB extra of storage space not Memory, it does not affect performance.
I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
Click to expand...
Click to collapse
There is no SKZ kernel for Pie at the moment and it will not work with Pie 9 as it only works with 8.1.
The stock Kernel of Pie 9 is not optimize yet to use the swap partition, as soon as Pie is fix it will be available and the system will improve performance and stability as more RAM (Memory) will be available in Android. (Update Pie is completely optimize more than any other ROM
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
larrywilson said:
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
Click to expand...
Click to collapse
Thanks for the update ! The direct link now is updated to 03-28-2019 built.
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
johnbelloh said:
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
Click to expand...
Click to collapse
Android Pie is optimize and is swap enable from the core, all settings are set to be use with the swap partition.
Flintman did a marvelous job incorporating all the changes and making Pie available for the HP Touchpad with more improvement on its way that it could be the best ROM ever. I will update this guide soon.
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Steelskinz said:
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Click to expand...
Click to collapse
If you are using 8.1 now and enjoying your setup, then my recommendation is to keep using it that way until Pie which is 100% stable now with more features than 8.1, gets Bluetooth working and any other minor issues resolved. As of now Pie is working as Oreo. Pie is using the swap partition and fully optimized as 8.1 and 7.1.2. The only thing to do is to flash it just like any other ROM.
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
Thanks, Lister
Lister Of Smeg said:
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Yes Flintman still providing support and now has created the best ROM.
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
The swap partition must be created as in this guide:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
WebOS came with a swap partition and all the ROMS were install side by side with WebOS but never implemented the use of SWAP, Android 9 is the first ROM to completely take advantage of swap thanks to Flintman for applying all the changes. And all future version of Android for the HP Touchpad will have support for the swap partition.
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
Yes the partition that is created is the original from WebOS dev/store/swap.
In WebOS is a 400 MB
The new partition is 500 MB, it can be change to any size if the user wants to.
If you want to use any new ROM, 7.1.2 ,8.1 and 9 the /system partition must be 1400 MB, it can be resize using the ToolBox.
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
The /boot partition is a fix 32MB can not be change and there is no need for it to be larger.
Download the ToolBox from Here
Unzip the file rename TPToolbox-2015-01-08-v42.bin to uImage.ToolBox
Using TWRP Recovery mount /boot and using the TWRP File Manager copy uImage.ToolBox to /boot.
Using TWRP any boot uImage can be move from /boot to the SDCARD and then can be copy back.
There is no need for /boot to be larger as the boot files can easily be copy to it when need it to be use.
Think of it as a CD or USB disk that you insert into the PC to boot from, is the same concept. If you need to use the ToolBox make some space by removing a boot uImage and then copy the ToolBox in /boot.
Thanks, Lister
Click to expand...
Click to collapse
You are welcome!
Hi @HP_TOUCHPAD,
First of all, thank you for the very prompt and DETAILED reply, this is perfect and contains EXACTLY what I need to know. And apologies for the delay getting back to you, my brothers son has been in hospital last couple of days... So been a bit back and forth.
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition. Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
Thanks once again...
Lister
HP_TOUCHPAD said:
You are welcome!
Click to expand...
Click to collapse
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition.
Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
The ROMS Kernels available from my guide for Evervolv 7.1.2 and DU 8.1 are my changes to make use of swap with optimization.
Flintman integrated all the changes posted on my guide to the Kernel, Ramdisk and also to the ROM of Pie (9).
Android Pie (9) is the first ROM to completely take advantage of the swap partition thanks to Flintman for improving and making the extra changes.
Thanks once again...
Lister
Click to expand...
Click to collapse
You are welcome.
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Click to expand...
Click to collapse
The /boot partition is 32MB, It shows that WebOS is also installed. Before moving any files from /boot make sure to do a backup just in case if the wrong file gets removed. The ToolBox does not need to be in the /boot directory to be use . It can be loaded into the memory by placing the Tablet into Recovery Mode and from the PC with the novacom drivers install load it.
novacom boot mem:// <uImage.ToolBox
The ToolBox will be loaded into memory and use for anything need it, there is no need to keep it in the /boot.
The most important file to be in /boot uImage.moboot 63.KiB (boot manager)
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.