Related
XFAB Phablet(DAPENG A9230+,PICOPAD 5 GEA) - 5" Android Mobile - Root, CWM and ROMS
Dear Friends,
Good day.
I have own this device, which is from NXG electronics Ltd, India. It is good and I enjoy it.
{
"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"
}
Device XFAB PHABLET (MODEL NO - E1808_V75_HJY1A6X_5647)
[*]Brand NXG Electronics Ltd, India
[*]CPU 1GHz Cortex A9 (ARM v7 processor rev 10)
[*]Hardware MT6575
[*]OS Android 4.0 Ice Cream Sandwich
[*]RAM : 512MB
[*]Internal Memory 4GB
[*]Expandable Memory MAX support upto 64GB Class 12 Micro SD Memory Card (TF-Card)
[*]Screen 5.2-inch Capacitive multi-touch screen (5 points), WVGA: 480 x 800, 16 Million Colors
[*]Network Dual SIM Dual Standby, supports WCDMA+EDGE or EDGE+EDGE
[*]2G： Yes (GSM:850/900/1800/1900 MHz)
[*]3G： Yes (2100 MHz)
[*]Built in Sim card Slot (Dual SIM)
[*] Supports GSM/GPRS/EDGE/WCDMA HSPA
[*]GPS Built In A-GPS, supports voice navigation
[*]Connection Bluetooth with EDR & A2DP
[*]Wi-Fi : IEEE 802.11 b/g/n, WiFi Hotspot functionality, Tethering & portable hotspot
[*][ Micro USB 2.0
[*]Camera Dual Camera
[*] Back 8MP with Auto focus and Flash LED
[*] Front 0.3 Mega pixel
[*]Sensor Gravity Sensor, Proximity Sensor, Light Sensor]
[*]Color Black
[*]Video Playback Video playback and recording, supported formats: 3GPP, MP4, 720P(1280 x 720)
[*]Video Formats AVI , MP4 , FLV , 3GP , MOV , ASF , MPEG , RMVB , etc.
[*]Audio MP3 , AAC , WAV , etc. / 3.5 mm Audio jack
[*]Size 147 × 86 × 9.7 mm
[*]Weight 165 g
Accessories
Battery : 2800mAh and 180 hours of standby time
(2*2800mAh) 1 Battery Free
Earphone / 3.5 mm Audio Jack
USB Cable
Charger
The following is the Company Website
http://www.nxgelectronics.in/xfab.html
I have attached the screenshots, which were taken from my Xfab.
Device is Very good.
I have used Some Roms from Russian Forum (forum.china-iphone.ru) and posted here.
Developers, Please help here for Custom ROMs
NXG ORIGINAL STOCK ROM here
http://www.nxglabs.in/nxgblog/?p=324
THE FOLLOWING, DO AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY FAILURE DUE TO MISTAKE. BUT WHILE DOING SAFELY, THERE WILL BE NO DEIVCE BRICK
ROOTING:
I rooted through Tpsparky Root. Thanks to Mr.SparkyM3 . I have attached the file for rooting to all friends.
First install the MTK 6575 driver in the system (PC).
Enable 'USB debugging' mode in mobile (settings - developer options)
connect mobile through USB cable to the PC
turn on file copy mode in mobile
Then simply click the bat file and proceed with instructions.
CLOCKWORK MOD RECOVERY
THANKS TO RUSSIAN developer - Mr.Arsenev.
I have attached the link to clockworkmod recovery. But, the file is complete Rom. So, you have to download complete Rom files.
Flash through Smartphone flash tool and Good guide is here - http://bm-smartphone-reviews.blogspot.in/2012/05/mt6575-flashing-tutorial.html
Remove the recovery file from the downloaded Rom files and replace the attached recovery file. I dont know to separetly to flash the recovery. If anybody know, Please help. So, while flashing only select 'Recovery' and follow the 'bm-smartphone' guide. Your downloaded Rom is not waste, because that is 23.07.2012 build. so you can use also that Rom. But anyway stock rom is best.
Link for 23.07.12 build - http://narod.ru/disk/60288821001.67...723_e1808_v75_hjy1a6x__Flashtool_4.0.zip.html
Lewa TWRP recovery - given by Mr.black_cappucino - http://forum.xda-developers.com/showpost.php?p=36880132&postcount=17
you can install as the same method as above (clockworkmod recovery).
or - through Mobileuncle tools.. but I didnt test through Mobileuncle tools. I have attached the mobile uncle tools apk
AXIOO TOUCH RECOVERY - V.2.3.2.3
Works well in Our mobile. It is designed for AXIOO Picopad 5 GEA (Same Our Mobile - Indonesian Brand name is that) by Mr. insane ranting
Thanks to the Expert. Tested by me. 100% working.
Link here - http://www.jfdesignnet.com/?p=2804
Flash through the flash tool, as same as previous methods.
CUSTOM ROM
CUSTOM ICS:
1. Ok.. ICS 4.0.6 (modified as 4.0.6) ,custom ROMs are here
http://forum.china-iphone.ru/viewtopic.php?p=659135#p659135
Use google translate in browser. Because page is in Russian.
It is made by Mr.Alexey arsenev, russian developer for Star N8000. He told that it will match exactly to Dapeng A9230+. So I tried, and it exactly matched.. All tweaks are good. Rom is Very fast. "Awesome Beats" in this Rom is Excellent.. No need to buy Beats headphones.. Medium quality earphones are enough.. So, if you want , try.
2. Mr. black_cappucino' s CUSTOM ICS ROM - http://forum.xda-developers.com/showpost.php?p=36899596&postcount=18
3. GIONEE GN868 ROM (Micromax A90) - Stock ROM works well. has little problems. but we can solve that.
Little problems - we can solve that.
a. no signal - copy 'modem.img' from your stock rom (\system\etc\firmware) into GN868's Rom - same folder and change permissions (rw-r--r--)
b. bluetooth, wifi crashing - copy 'mtk_stp_wmt.ko' from your stock rom (\system\lib\modules) into GN868's Rom - same folder and change permissions (rw-r--r--)
Use your's stock ICS boot.img in the downloaded ROM .
Flash through Recovery.
Done .. Rom will be perfect.
Specialities in this ROM - 1. ICS Onscreen keys. 2. stock launcher with themes..
Link - http://www.romzj.com/index.php?option=com_mobile&task=download&id=4144&from=rom
4. SAMSUNG STYLE ROM - LENOVO A750 - works good in our mobile.
Specialities - Samsung Style ROM, Sony Bravia Engine, Dual Sim dialer.. etc..
works well. wifi problem one thing. for this you copy 'mtk_stp_wmt.ko' from your stock rom (\system\lib\modules) into This Rom - same folder and change permissions (rw-r--r--)
link - http://dl.vmall.com/c0pyvnub9y
Use your stock ics 'boot.img' in the downloaded Rom and flash through recovery.
1. LEWA OS
Link - http://narod.ru/disk/63368595001.b7...2.10.26_v_i9220_mod3rus_orkyz(zp100).zip.html
Flash through Clockworkmod Recovery.
Actually this rom is for 'Haipai I9220' device and It is from Russian Developer.
Credits go to 'Mr.MrorkyZ' - Russian Developer.
1 bug - There is no analog tv.
1.a) - LEWA LATEST BUILD (I tested)
http://disk.yandex.com/public/?hash=iNuFH9XZGuKIDKQiB8/qA3mkmt/zZRlVlRU1jgZptfY=
CREDITS GOES TO MR. SASHAML (RUSSIAN DEVELOPER - forum.china-iphone.ru)
No bugs for me... But there is no analog tv.
I have attached new LEWA BOOT IMAGE (zip file- you have to unzip) made by Mr. Vetal-ok , Russian Developer through my Request. All credits go to him. So replace the lewa boot image in the downloaded Lewa ROM.. means.. you have to unzip the file and replace the boot image, then again you have to make a zip for flashing through recovery..
2. MIUI
MIUI V4 works good in Our device.Only one problem (for me) - There is no analog TV. Firmware is from Haipai i9220 (Russian) forum.
Thanks to Mr.Cepexa and Mr.back37 , Russian Developers for their modified MIUI boot image for Our device.
Thanks to Mr.SashaML, Russian Developer for his MIUI firmware
Firmware Link - http://files.mail.ru/K0QEMD
1. Flash the firmware through clockworkmod Recovery.
2. Flash the 'attached 'dapeng A9230+ MIUI boot image' through clockworkmod recovery.
2.a) MIUI latest build here
http://files.china-iphone.ru/68rus_MIUI_10.12.12_i9220_e1809c_v75_gq1008_9p017.zip
CREDITS GOES TO ISTOMIN36 (RUSSIAN DEVELOPER - forum.china-iphone.ru)
Sorry friends.. the old attached MIUI boot image has camera shot problem.
So dont use. I have attached the new miui boot image .. Use that.
This New boot image also created by Mr.Vetal-ok, Russian developer (forum.china-iphone.ru)
After flashing the downloaded MIUI Rom file, flash the MIUI boot zip file through recovery.
Help please, Any Developer to port the original rom
Hellow Any Developer
Please help. I successfully rooted the device.
But I softbricked my device due to my simple mistake. While using ROM Toolbox lite, I tried to change the font.
I have no problem, while changing the fonts (downloaded through ROM toolbox}, I successfully changed the fonts.
But Yesterday night, I changed the font from local folder of device , Afterthat the device is not booting..Only Android logo.....
So I have to reflash the fimware... Any developer having firmware of this device..... please help..
In service center (chennai, India), also still Firmware not available...
I have seen the firmware topic in the following Russian website.
http://forum.china-iphone.ru/viewtopic.php?f=46&t=20476
But I cant understand clearly, because of unknown language (even using Google translator also)
So, please any Russian mates or Developers or Any Developer , please help.. Because I have no standby mobile..
Thanks.
Please send a mail to NXG - Pune (i am sure they will help you)
Dear Ramsuresh
Please send a mail to NXG-Pune and make a call to them, they will definetly send you firmware link & guide you
By the way
have tried factory reset from Recovery Mode...?
Regards
Arumugam
ramsuresh4 said:
Hellow Any Developer
Please help. I successfully rooted the device.
But I softbricked my device due to my simple mistake. While using ROM Toolbox lite, I tried to change the font.
I have no problem, while changing the fonts (downloaded through ROM toolbox}, I successfully changed the fonts.
But Yesterday night, I changed the font from local folder of device , Afterthat the device is not booting..Only Android logo.....
So I have to reflash the fimware... Any developer having firmware of this device..... please help..
In service center (chennai, India), also still Firmware not available...
I have seen the firmware topic in the following Russian website.
http://forum.china-iphone.ru/viewtopic.php?f=46&t=20476
But I cant understand clearly, because of unknown language (even using Google translator also)
So, please any Russian mates or Developers or Any Developer , please help.. Because I have no standby mobile..
Thanks.
Click to expand...
Click to collapse
I solved my problem myself
UParumugam said:
Dear Ramsuresh
Please send a mail to NXG-Pune and make a call to them, they will definetly send you firmware link & guide you
By the way
have tried factory reset from Recovery Mode...?
Regards
Arumugam
Click to expand...
Click to collapse
Dear friends,
I solved my problem myself. I got firmware from Russian friends and flashed successfully before 2 days. My only little issue is back camera gives inverted shots. I am searching for rear camera driver. Other than everything is well.
After sending mail to NXG , they sent firmware after 4 days. But that firmware gives error (flash scatter file is invalid) and I cant flash the NXG firmware.
hi.just wanna ask..can this recovery.img used in dapeng i9877?
thehaikal said:
hi.just wanna ask..can this recovery.img used in dapeng i9877?
Click to expand...
Click to collapse
hi，This is for Dapeng A9230 ±. I am not sure that this is for your device. Make a nandroid backup of your Rom , Then you can test this recovery.
Sent from my Dapeng A9230± using xda app-developers app
Hit Thanks
Rooting file - 26 downloads, recovery image - 21 downloads.
no one hitting thanks ?
there is an original factory firmware from russia forum come with flashtool, will upload link if anyone need it..
Send from my GT-N7000 using xda premium
e1808_v75_hjy1a6x (build -20120723) on my device with processor speed 1200Mhz..
e1808_v75_hjy1a6x_5647 (build -20120905) run 1001Mhz on my device..
Now using e1808_v75_jbl2_20120807 from N8000 on my device with 1200Mhz speed (kernel & driver remain e1808_v75_hjy1a6x_20120723)
ramsuresh brother, bout the miui rom. can this rom make a video call?
Sorry. There is no video call option presently in the Miui rom for this device. Maybe near future It may come.
Sent from my Dapeng A9230+ using xda app-developers app
Sorry for Very late reply. The above posted Roms are from Russian forum (forum.china-iphone.ru) only.
Sent from my Dapeng A9230+ using xda app-developers app
black_cappucino said:
ramsuresh brother, bout the miui rom. can this rom make a video call?
Click to expand...
Click to collapse
Sorry. There is no video call option presently in the Miui rom for this device. Maybe near future It may come.
Sent from my Dapeng A9230+ using xda app-developers app
alanccs said:
there is an original factory firmware from russia forum come with flashtool, will upload link if anyone need it..
Send from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry for Very late reply. The above posted Roms are from Russian forum (forum.china-iphone.ru) only.
Sent from my Dapeng A9230+ using xda app-developers app
People are simply downloading the files. No thanking mind. Only two persons have thanked me here. I am not a developer. But i have worked hard for this device..
thx for replying broth. maybe another trick for 3g video call? i think to add ics dialer or samsung dialer or something. not yet test, still wanna know your opinion broth.
Lewa TWRP Ported from stok fw
try this twrp broth. full touch. i use this twrp for 2 weeks, no problem, all function normal.
uma_DROID v1.0
uma_DROID v1.0
Custom ROM for Axioo PicoPad 5 (Indonesia)
[ Also Work for DAPENG A9230 - we have same machine]
HI guys, i made this custom rom just for fun. this is for Axioo PicoPad 5 GEA ( Indonesia). Actually have same machine with Dapeng a9230, so maybe you can install it to your device ( Im sure you can). Because i found the rusian stock rom for dapeng, and flash it to my GEA, and work like charm with no single problem on my GEA till now, thats why im sure you can install it to dapeng.
Thats it guys. Please read the information and the how to before you flash this rom. I have no responsibility if you brick your device because flash this rom to your device. Flash and Mod with your own RISK...!!!
- Lewa TWRP & Patch for 2GB System storage/500MB Internal sdcard included.
Code:
[CENTER]uma_DROID 1.0
ROM :
- 20120723_e1808_v75_hjy1a6x fw based
- Stock Axioo boot animation found inside axioo picopad 5 gea on facebook group
- 200dpi
- build.prob tweaked into Samsung galaxy tab 2, so you can install all apps inside market
- Moded Play store for density modifier, so you can change your lcd density to any value you want but you can install all apps inside market
- X-peria Launcher ported (my fav launcher ever)
- Jelly Bean Camera & Gallery found inside axioo picopad 5 gea on facebook group
- Keyboard : android keyboard (ics), X-peria keyboard & Samsung Keypad.
- No Live wallpaper, home screen tips
- No apps like facebook, ym, twitter, etc
- font changed to alex
- battery and wireless icon changed
- usb storage android logo changed to red devil android
- Sonny bravia engine tweak enabled
- better gps configuration for Indonesia
- init.d tweaks for : fast internet browsing, improved battery life, touchscreen more responsiv, little bit kernel tweak, zipalign all apks every boot, improve speed for x-peria launcher.
- build.prob tweaks for : better picture quality, better recording quality, lock launcher to memory, battery life, kernel error check disabled, more more deeper sleep, 3g tweaks, no black screen after call, video streaming, hsupa enabled, android logger disabled, dns tweak from common linux use google dns, & many more.
- default 500mb system and 2gb internal sdcard (use 2gb system storage to get 2gb system storage & 500mb internal sdcard - *zip file included)
- Lewa TWRP included (if you want, flash recovery via spft first or you can install it via mobileuncle after flashing this rom)
how to :
PLEASE BACKUP FIRST. If you brick your gea, i have no responsibilty for that.
PLEASE BACKUP IMEI FIRST. unless you will traped on invalid imei problem.
- download the file, extract it.
if you want, you can flash "2gbsystorage.zip" via recovery to turn your system into 2gb and internal sdcard into 500mb before you flash the custom rom.
inside you will find an archive named "uma_DROID_v1.0.zip". copy it to your sdcard, boot into recovery, and please DONT FORGET TO WIPE DALVIK, CACHE, & WIPE your device unless you will traped inside bootloop.
done.
note : If you want your phone rooted, install the "2gbsystorage.zip" after you flash the ROM, or if you want to flash the "2gbsystorage.zip" before you flash the ROM, you can r00t your phone via rooting tools[/CENTER]
DOWNLOAD :
HERE...!!!
black_cappucino said:
uma_DROID v1.0
Custom ROM for Axioo PicoPad 5 (Indonesia)
[ Also Work for DAPENG A9230 - we have same machine]
HI guys, i make this custom rom just for fun. this is for Axioo PicoPad 5 GEA ( Indonesia). Actually have same machine with Dapeng a9230, so maybe you can install it to your device ( Im sure you can). Because i found the rusian stock rom for dapeng, and flash it to my GEA, and work like charm with no single problem on my GEA till now, thats why im sure you can install it to dapeng.
Thats it guys. Please read the information and the how to before you flash this rom. I have no responsibility if you brick your device because flash this rom to your device. Flash and Mod with your own RISK...!!!
- Lewa TWRP & Patch for 2GB System storage/500MB Internal sdcard included.
Code:
[CENTER]uma_DROID 1.0
ROM :
- 20120723_e1808_v75_hjy1a6x fw based
- Stock Axioo boot animation found inside axioo picopad 5 gea on facebook group
- 200dpi
- build.prob tweaked into Samsung galaxy tab 2, so you can install all apps inside market
- Moded Play store for density modifier, so you can change your lcd density to any value you want but you can install all apps inside market
- X-peria Launcher ported (my fav launcher ever)
- Jelly Bean Camera & Gallery found inside axioo picopad 5 gea on facebook group
- Keyboard : android keyboard (ics), X-peria keyboard & Samsung Keypad.
- No Live wallpaper, home screen tips
- No apps like facebook, ym, twitter, etc
- font changed to alex
- battery and wireless icon changed
- usb storage android logo changed to red devil android
- Sonny bravia engine tweak enabled
- better gps configuration for Indonesia
- init.d tweaks for : fast internet browsing, improved battery life, touchscreen more responsiv, little bit kernel tweak, zipalign all apks every boot, improve speed for x-peria launcher.
- build.prob tweaks for : better picture quality, better recording quality, lock launcher to memory, battery life, kernel error check disabled, more more deeper sleep, 3g tweaks, no black screen after call, video streaming, hsupa enabled, android logger disabled, dns tweak from common linux use google dns, & many more.
- default 500mb system and 2gb internal sdcard (use 2gb system storage to get 2gb system storage & 500mb internal sdcard - *zip file included)
- Lewa TWRP included (if you want, flash recovery via spft first or you can install it via mobileuncle after flashing this rom)
how to :
PLEASE BACKUP FIRST. If you brick your gea, i have no responsibilty for that.
PLEASE BACKUP IMEI FIRST. unless you will traped on invalid imei problem.
- download the file, extract it.
if you want, you can flash "2gbsystorage.zip" via recovery to turn your system into 2gb and internal sdcard into 500mb before you flash the custom rom.
inside you will find an archive named "uma_DROID_v1.0.zip". copy it to your sdcard, boot into recovery, and please DONT FORGET TO WIPE DALVIK, CACHE, & WIPE your device unless you will traped inside bootloop.
done.
note : If you want your phone rooted, install the "2gbsystorage.zip" after you flash the ROM, or if you want to flash the "2gbsystorage.zip" before you flash the ROM, you can r00t your phone via rooting tools[/CENTER]
DOWNLOAD :
HERE...!!!
Click to expand...
Click to collapse
wow,great rom dude,i want to try it..but can you tell me how to back up imei?just in case if i get imei invalid,and what is the lewa twrp??
sorry for my noob,i'm new on this thing..
@Galon123
dude, to back up your imei, your phone must be r00ted. open your root explorer or similiar, go to " /data/nvram/md/NVRAM/NVD_IMEI/ ". You will find a file named "MP0B_001", copy it to your sdcard or maybe pc/laptop for future use. So you can paste it into the same folder, and you get your imei back if in case you traped inside "Invalid Imei" problem.
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Galon123 said:
wow,great rom dude,i want to try it..but can you tell me how to back up imei?just in case if i get imei invalid,and what is the lewa twrp??
sorry for my noob,i'm new on this thing..
Click to expand...
Click to collapse
black_cappucino said:
@Galon123
dude, to back up your imei, your phone must be r00ted. open your root explorer or similiar, go to " /data/nvram/md/NVRAM/NVD_IMEI/ ". You will find a file named "MP0B_001", copy it to your sdcard or maybe pc/laptop for future use. So you can paste it into the same folder, and you get your imei back if in case you traped inside "Invalid Imei" problem.
Click to expand...
Click to collapse
double post sorry.
Lewa TWRP :
Lewa (TWRP) touch recovery is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface, no more volume rocker or power buttons to mash.
Features:
-Graphical touchscreen interface with buttons and drag-to-scroll!
-Compressed backups that can save you up to 50% disk space
-Ability to choose which partitions to back up and which to restore
-Custom names for backups, rename and delete backups inside recovery
-Install Zip from SD card or internal storage
-Integrated Terminal Emulator
-Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
-Easy one-button cache & dalvik cache clearing after an installation
-Recovery settings are saved to the sdcard and persist through reboots
-File Manager that allows you to move, copy, delete and rename files and change their permissions
-Battery percentage indicator and clock (set your timezone in settings!)
-Power Off option
-Ability to partition SD Card with EXT3 or EXT4
-ADB support
-Detailed logfile
note : copy/paste from here.
Here are a few scripts I wrote for my device to boost up its performance. Few of them are written without being specific to any device or version of OS. For these general scripts (not specific to any device), download links are given at this first OP. For scripts which are specific to Redmi 3s, links are given at second post. These redmi 3s specific scripts install certain modified files such as service.jar and framework-res.apk.
All possible care has been taken to make general scripts work on all devices. Since I could check only on a few devices I could have access to, there could be a remote chance of not working on some devices. As devices vary on many accounts like OS version, customisation, configuration and file structure, for any eventuality, I recommend to take back up before proceeding with flashing of these zips.
Since the scripts are zipped in flashable zips, custom recovery (preferably TWRP) is must on your devices.
Here are general scripts with brief explanations.
1. Busybox installer zip: For various tweaks and init.d scripts to work properly, busybox is inevitable. This script installs Stericsons Busybox v1.24.2. If you have already busybox installed, no need of flashing this. Further flashing on the installed busybox may not harm.
Download Link: http://www.mediafire.com/file/s45tpufcy42h107/BusyBox-v1.24.2-Stericson.zip
2. Boot_patcher zip: This zip adds mount flags such as noatime, nodiratime, commit=60, nobarrier, noaudot_da_alloc, etc in fstab in boot.img and removes DM-verity. These flags have proved to increase IO on file systems. Many tweaks, I have noticed, put init.d script to remount partitions with these flags. But this zip does it directly at mount points at boot level obviating the need of init.d scripts.
Note: This zip is observed to break root enabled by Magisk. No need to worry. Just flash once again Magisk zip after flashing this zip. However, there is no problem of broken root if same is enabled by supersu.zip by chainfire.
Download Link:
http://www.mediafire.com/file/wshva78c456z1ub/boot_patcher.zip
3. Universal_journal_disabler zip: This zip makes journaling off on ext4 for system, data and cache partitions provided the partitions have been mounted on ext4 fs (if mounted on f2fs, it won’t touch those partitions). Journaling is a special control measure introduced from ext3 onwards. Journaling keeps track of changes made before writing on fs. This is useful in the scenarios of sudden power off or closure/crash due to any reasons for later restoration of changes made. This is not necessary on devices like mobile. But by default it is on. Since Journaling involves overhead on cpu, disabling the same is observed to improve performance considerably.
Note: Please flash this zip placing it on external memory, not on internal memory. Flashing from internal memory will not switch off journaling on data partition. So to ensure disabling journaling on data (which is essential for noticeable improvement), flash this zip placing it on external memory (external SD card) only.
Download Link:
http://www.mediafire.com/file/fmij6tnt8aebtyj/Universal_journal_disabler.zip
4. Permissive_selinux zip: In nougat custom roms, especially for Redmi 3s, selinux is enforcing. Enforcing selinux is seen to come in the way of many root apps though root enabled. One important issue I noticed that scripts at init.d folder were not running at boot due to enforcing selinux. Thus, I have made a small script to make selinux permissive on every boot by default. It takes care of file/folders created by supersu and magisk zip and accordingly puts the ‘setenforce 0’ in the appropriate folder.
Note: zip found not compatible with Magisk version 14
Download Link:
http://www.mediafire.com/file/qkimoscmfpu8x8a/permissive_selinux.zip
5. Ad_blocker zip: Nothing special about it. It just replaces hosts file in /etc folder for ad blocking. Important thing is about permissions assigned (rw_ r__ ___) for reducing impact of reading the big hosts file.
Download Link: http://www.mediafire.com/file/i50pr16umzp7h9q/ad_blocker.zip
6. Build_prop_patcher zip: This one has taken hell out of my time and patience. Not that it does any special thing, it simply inserts some build properties to build.prop file. But I wanted to make it such that it would search the intended build properties in build.prop file and changes the values thereof. If properties not found, inserts them at the end of file.
It is customisable zip. You can unzip and modify buildprop file according to your requirements. Special feature is it won’t add properties if present already with intended values. So, it is useful particularly to those who frequently flash roms with the result of losing added build.prop on every flash. Just flash this after flashing rom and have all your desired build.prop instantly.
Download Link: http://www.mediafire.com/file/c208fq98mixu9vx/build_prop_patcher.zip
7. Init.d script installer zip: I have collected some init.d scripts which I felt very essential and to implement on every device I have. Like build_prop_patcher zip mentioned above, herein also you can unzip the file and add your scripts to init.d folder therein, and make a permanent zip to flash every time you change your roms.
Note: For the scripts to work placed in init.d folder, you device should have been rooted and init.d enabled.
Download Link: http://www.mediafire.com/file/ot51sid37sfr0m8/initd_script_installer.zip
Credits:
@jcadduono for having heavily relied on his kernel flasher zip
@skynet28 for the method of journal disabling
Redmi 3s specifc
Here are Redmi 3s specific zips
1. Mm_rr_service_frmwrk_patch zip: This is meant for marshmallow resurrection remix rom as the modified service.jar and framework-res.apk used here for installation are from marshmallow resurrection remix rom. However, I think these modified files work on any marshmallow los based custom rom for redmi 3s.
In service.jar file, oom (out of memory) values for different categories of apps have been modified as below. As mentioned here, these oom values have resulted in turnaround of functioning of apps.
App category - old values - new values
Home ---------- 6 ---------- 0
Visible ---------- 1 ---------- 3
Previous ---------- 7 ---------- 5
Heavy ---------- 4 --------- 4
Service --------- 5 ---------- 6
Backup ---------- 3 ---------- 7
In all the custom roms, adaptive brightness is problematic, screen brightness is erratic on slight change in ambient light. So, I decompiled framework-res.apk, and changed autobrightness array values and found adaptive brightness afterwards comfortable.
Download Link:
http://www.mediafire.com/file/7y40j1x8dxp0bla/mm_rr_service_frmwrk_patch.zip
2. nougat_aex_frmwork_patch zips: Here also, I have modified services.jar and framework-res.apk files of nougat AEX roms. In services.jar, oom values have been modified as stated above, and in framework-res.apk also, autobrightness array values have been changed for smooth adaptation of screen brightness to ambient light. Since the services.jar and framework-res.apks used here are from AEX roms, zips are for AEX roms only. For each version of AEX rom (so far two versions, 4.5 and 4.6) for Redmi 3s, there is a separate zip which is to be flashed depending upon the version of AEX rom installed on your device.
For AEX v4.5
Download Link: http://www.mediafire.com/file/lxgd42fmfljxavv/nougat_aex45_svc_frmwork_patch.zip
For AEX v4.6
Download Link: http://www.mediafire.com/file/5bhawu1o226qdh3/nougat_aex46_svc_frmwork_patch.zip
3. nougat_rr_frmwork-res_patcher: This is for nougat resurrection remix roms. It also does the same thing of patching resources.arsc file in framework-res.apk for smooth adjustment of screen light to the ambient light.
Download Link: http://www.mediafire.com/file/luf4kslvttxss2d/nougat_rr_framework-res_patcher.zip
4. nougat_rr_svc_patch: This zip is for nougat resurrection remix roms. This installs patched services.jar with modified oom values as mentioned above (for the first zip in this post) for smooth functioning of apps.
Download Link: http://www.mediafire.com/file/61h9dz77zpxxuj9/nougat_rr_svc_patch.zip
5. adaptive_brightness_for_Oreo.zip: This is for overlaying the correct values of adaptive brightness in framework_res.apk for Oreo roms. Here, overlay feature of Oreo rom is being used instead of replacing modified framework_res.apk as done in the cases of zips for marshmallow and nougat roms above.
Download Link:http://www.mediafire.com/file/n77hsdvg9jx6pkp/adaptive_brightness_overlay.zip/file
6. persist_patch zip: This is for those who have corrupted persist files causing light, proximate and magnetic sensors not working.
Download Link:
http://www.mediafire.com/file/rrshneruhkdn8on/persist_patch.zip
Good work bro
Will it affect battery backup?
basiljose007 said:
Good work bro
Will it affect battery backup?
Click to expand...
Click to collapse
Definitely
shankar_vl said:
Definately
Click to expand...
Click to collapse
I mean positively or negatively? I prefer battery backup over higher performance, so asking
basiljose007 said:
I mean positively or negatively? I prefer battery backup over higher performance, so asking
Click to expand...
Click to collapse
both positively
Don't know if i will ever use these. But your hard work definitely deservers a vote of thanks.
------------------------DISCLAIMER------------------------
Flash this Firmware with SP flash tool at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware,
There are 2 firmware builds at the bottom,
1st with google play store as an app store.
2nd with Aptiode store.
Choose which version you wish to select Google play version is labelled as GP & Aptiode store is labelled as AP.
______________________________________
This Samsung S7 themed Rom has been personally built by myslef with the base system of an R11 max chinaphone ive replaced almost everything.
DEVICE INFO
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
_____________________________________
REMOVED OR UPDATED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• updated Launcher for G930F Ui resemblance.
• Lightning Browser (looks like chrome)
• gallery V1.1 with photolocker
• Modded Camera FV-5
• JRD Secure container
• JRD plugger
• Updated music FX
• JRD media container
• Samsung Boot animation
• Samsunf Shut Animation
• G930F boot logo
• G930F icons and theme
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build edited to display device as SM-G930F
• Fingerprint updated
• Updated to Release Keys (was test keys)
• updates -res
• root set to function without the need for Su manager app binaries can run themselves.
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
• SU Binary pre installed to system, no need for root manager
• BUSY BOX binary pre installed to system, no applet's are preinstalled though
Plus alot more stuff i cannot remember as i never made a changelog this is listed as release software as i deem it stable enough for daily use but as the system is customised it should be treated as Beta software, any bugs please report them to me so they can be fixed.
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
This Rom for now must use the modified boot.img & external SD card should you wish to use either of these roms due to a mounting error somewhere, no app will install despite there being 70mb + on both builds /data partitions so i need to fix, all works perfect with the modified boot.img,
Partition your SD card as follows using Mini partition tool with 2 partitions in this exact order EXT 4 Cannot be first or you will face data decryption error until rectified.
•PRIMARY partition
- FAT32 label it data
•PRIMARY partition
- EXT4 label it mmcblk0p2
To flash with modified boot.img open the scatter file, click on the BOOTIMG file path & select the modified boot.img,
Insert the newly partitioned SD card into the device and flash the firmware using the instructions on how to flash below.
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
•Open SP flash tool
•select the scatter.file
•insert the modified boot.img into BOOTIMG path
•change flash method to download only
•click start
•Wait for it to complete the flash
•Disconnect & Reconnect the usb cord
•Wait for device to start charging
•Turn on & enjoy
DO NOT USE "format all + download" in SP flash tool unless you have a backup of your firmware and security partition or you WILL lose your imei.
_________________________________________
LINKS
GP Build https://drive.google.com/file/d/1gpGH1Wj_JQHFFroV12r1PcHsxeE5zbTV/view?usp=drivesdk
AP Build https://drive.google.com/file/d/1VhZmpZyA-z-N6phAn9nfBifL-Lk0pdWL/view?usp=drivesdk
SP Flash Tool https://spflashtool.com
Modified boot is located within the .zip all credits to luca Roggero for his modified boot.img
can't get it to load with modified boot
i partitioned it as directed on a 32gb card flashed modified boot and it wont load also theres a weird glitch on this rom where once your battery hits about 20% it just instantly drops to 0 also cant install a custom recovery with easy magic (any of them) do u know the code to unlock the bootloader?
thinkotherwize said:
i partitioned it as directed on a 32gb card flashed modified boot and it wont load also theres a weird glitch on this rom where once your battery hits about 20% it just instantly drops to 0 also cant install a custom recovery with easy magic (any of them) do u know the code to unlock the bootloader?
Click to expand...
Click to collapse
Sorry for the late reply ive been busy busy busy making android 6.0.1 for the R11 max its almost finished,
Righto lets get started and get you up and running with the modified boot.img
Firstly how did you partition the Sd card, what partitions were they formatted to exactly and in which order,
They must be formatted in this exact order ill include the info aswell
Label: DATA
Format: FAT32
Type: PRIMARY
Label: MMCBLK0P2 (use lower case letters)
Format EXT4
Type: PRIMARY
i use mini partition magic and it works beautiful,
If the system boots on your device also it means that the boot.img is compatible with the device,
Which means that the modified boot.img is also compatible with your device as the original untouched works and all thats been done to it is the mount points were changed to the ext4 partition on the sd card,
This is everything that was done modifications to files were as follows
mount ubifs ubi @ userdata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mount yaffs2 mtd @ userdata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mount ext4 / emmc @ usrata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mmcblk0p2 is the name of the 2nd EXT4 partition of the sd card, which must be second and not first
The sd card must have 2 partitions, the first FAT32, the second ext4, both primary
Try that and see if it works,
If it dosent boot past the power on logo message back here you may have another revision board as there are a few in which i have a boot.img for 2 of the R11 max boards so will get your phone working with whatever GB storage you set as your partition
Did you also make sure you have the NAND version of R11 MAX also as there is an R11 which is emmc and not nand ? There are 5 variations of the NAND R11 max and 3 or 4 variations of the R11
basic info on the R11 max 5 build versions
Storage type: NAND (typically hynix)
Flash Size: 512mb
DRam 478mb
Radio: 2G GSM
The only diffs for the ones above are the partition infos and the bull**** storage capacity,
Basic info on the R11, 4 build versions
Storage type: EMMC (unknown)
Flash size: 2.5GB
DRam: ( unknown )
Radio: 2G GSM & 3G UMTS
Let me know how you go and sorry for the late reply
Oh by the way what you think is a Glitch isnt actaully a glitch,
Theres nothing i can do about that unfortunately,
In the framework-res.apk battery stats are set in 15% increments to much work for me to fix on the status bar, go to settings then battery and turn your battery % on thats at least accurate
And in physical terms of the battery i hope you dont actually think there a 3000Mah battery,
They are actually cheap chinese lithium cells that produce only 1000Mah and dont last very long at all mine did the same thing around 20% if you know what your doing you can re cell the battery with a samsung cell or similar as long as you are very careful and dont put to much force on the pcb on top of the cell to much and desolder it properly you will have a working battery that actually lasts, i did it to mine but i run a phone repair shop, i dont advise you do it if you are inexperienced in that case find a replacement battery that is decent quality same same size and pin location and youll be sweet.
And about the custom recovery again nothing i can do about that ive built and not used any tools that dont work half the time with so many diff variations of custom recoveries ive made,
Ive packed them with twrp ramdisk and made all edits but they just refuse to boot and only flash white and reset,
The bootloader is pre unlocked as youll notice theres no OEM unlock,
However if you really wanna try yourself,
Connect to the phone via adb and use one if the commands below to get you into fastboot mode, thats as far as youll get though fastboot oem unlock hangs on waiting even though fastboot devices shows the device
Syntax:
adb reboot bootloader
adb reboot-bootloader
adb reboot fastboot
adb reboot-fastboot
Forget which one it is but you can try for yourself,
Ive been trying and trying to get a half decent recovery for the next 6.0 build its still stock but ive done alot of mods to recovery like enabling adb in recovery and redoing the default.prop within it also
guess i'll just hold out
well its working pretty good sans battery life, lol
are you compiling a real marshmallow build? because that will for sure solve the sdcard as internal issue and you can install gapps etc.... the playstore would work etc... it wasn't until marshmallow that google started letting you use your sd a internal, still an awesome job man i love this project, its a hobby of mine taking old bricked or soft bricked phones and trying to get them to optimal standards so far so good! keep me updated on the progress.
I definitely used minitool and followed your instructions to a tee i'm thinking 32gigs is too much for the boot.img i'm going to try and partition it smaller on the fat32 and see if it will boot then, how big do you reccomend i make the mmcblock0p2 partition? i made it 3 gigs could that be the issue? too big?
Hey mate sorry for late reply was finishing up another alcatel U5 custom recovery project,
Yeah battery life isnt the best, next build ive added scripts to optimise battery life, ram and a few other things,
With the build unfortunately i cant fit an entire 6.0 system on a 512mb flash nand it just cant be done unfortunately theres not enough space but im working on that for a later build so at the moment though next build will use SDK23 system components but it will also include mostly SDK20, SDK21 & SDK22 system components that ive managed to merge into it,
Either way the modified boot.img is neccessary regardless, Gapps and play store i can confirm does work perfectly fine on this next build and there will be roughly 50mb so a couple apps can be installed before getting the storage low warning,
Even it if were a proper dedicated 6.0 build though again it would still need the modified boot.img as even though the app has been placed on the sd card it still has to run through the main system at startup and a full memory at startup will not boot the phone so again modified boot.img is necessary,
Shouldnt matter what size you make the partitions either, these boards support up to 32GB TF cards so thats not a problem,
I have a 16GB i made 2 partitions as follows
Data 7.5GB FAT32 primary
mmcblk0p2 7.5GB EXT4 primary
In that exact order & spelt that exact way if it is still not working for you then it is purely a pilot error (being you) as i mentioned normal untouched boot.img packed in with the firmware works correct ?
That means the modified boot.img will work also they are identical apart from the fact that the internal storage has been mapped over to your SD cards mmcblk0p2 instead of your internal mmcblk0p2,
If it is still not working i want you to please take a backup of your firmware and then from that zip up the following into an archive upload it to google drive or whatever you use and post the link to it here so i can download it and have a look at it to see if there are any differences anywhere
RECOVERY
BOOTIMG
MT6572_Scatter_file.txt
I highly doubt there will be any difference as it already works on your PMT info if there were something wrong it wouldnt boot at all even with the untouched stock one,
The boot.img and recovery has been highly modified in the next build so if your facing any probs still ill need to sort it out and possibly make a second version to support it, hopefully not the case tho.
Attention all users of R11 max,
New build will be up in a week maximum, Google play is functional, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.
New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041
Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also
All R11 users please be aware that a new build will be uploaded today or tomorrow latest which is a full AOSP CyanogenMod 11 flashable zip,
I will link the thread here was built for hs_q6_mb
But should work on all other variants as long as you use your stock boot.img
New thread will be linked here one completed and rom is uploaded
New rom is up link is here
https://forum.xda-developers.com/android/development/rom-cyanogenmod11r11maxmt6572ubifs-t3920315
i don't know wither this fits here or in the guide section so i leave it for the moderators to decide to move this thread or not
with that being said
i wanted to share my experience on how easily you can boot to miui without converting your device using erfan gsi
Download :
1. Erfan miui 10 a/b gsi from here : https://mirrors.lolinet.com/firmware/gsi/MIUI-AB-9-20190413-ErfanGSI.img.7z
2 . Files in this thread : https://forum.xda-developers.com/mi...on-aio-gsi-thread-mi-a2-t3933356#post79601628
Instructions :
1. format both a and b completely ( Data , system , etc ) also format data completely from twrp ( there is option which let you format data and userdata together next to advance option)
2. Restore the android q backup but only vendors and boot DONT RESTORE SYSTEM
3. install your gsi as system image
4. install. DM-Verity & Forceencrypt Disabler
5 . install permissiver_v2
6. format data completely from twrp ( there is option which let you format data and userdata together next to advance option)
7. reboot system and enjoy
Known issues
stock camera doesn't work
sometimes the blur effect in the notifications shade will not work instead it would be completely transparent
disclaimer : i didn't make or port any of those files used in the thread i'm just sharing my experience
Google Camera works?
g.laterza9 said:
Google Camera works?
Click to expand...
Click to collapse
it should work if you enable api 2 by magisk
however i didn't try it yet
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1The first truly working script, original and unique in its logic for all devices with a SUPER partition
Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by LeeGarChat
{
"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"
}
Spoiler: Screenshots
Short description:
Converts EROFS, EXT4(RO), F2FS Super partition to RW
Description:
A simple utility to convert your Super partition to RW mode (Read/Write) As well as the expansion and distribution of free space for each section, depending on how much space is available in the original Super section.
You can flash both via:
1. TWRP: by using controls in the script: (Volume control (+) to switch, Volume control (-) to select) in this case, the new super RW is flashed directly.
2. Magisk module: in this case you will need to go to the terminal and enter RO2RW, and a new RW-super.img will be prepared in the internal memory, you can choose both image output for FASTBOOT and RECOVERY.
For these two modes, the creation of the original super as a backup is supported, the file will also be output to the internal memory as bak-super.img
Spoiler: FAQ
Do I need to format the data after installation?- No, it is not necessary in normal cases, this script does not affect encryption in the data section. But in some cases, it is necessary to do the date format, it is not yet clear how this is related, for example on Asus devices.
Why do I need this script, for what and why; why do I, need it?- When your system partitions have read-only mode (RO), then you cannot integrate modifications directly into the firmware, (such as Viper4Android) as well as manually edit/delete files from system partitions. This script converts it in the case of F2FS and EROFS to EXT4, or forcibly in the case of EXT4 enables the "Read/Write" (RW) mode, and also expands partitions as much as possible.
What are systems partitions?What are system partitions?
- These are the sections that are located in the main container "super" (the script is focused only on devices with super), it includes system, product, vendor, etc., when mounting the system, the structure looks like this:
System <--- In TWRP it is mounted as /system_root
, in the system itself it is mounted as
Code:
/ <--- The main mount point for system
├── /product <--- The main mount point for product
├── /vendor <--- The main mount point for vendor
|
├── /system <--- Here are the main system files
│ │
│ ├── /system/vendor <--- Additional mount point for vendor
│ │
│ ├── /system/product <--- Additional mount point for product
And by analogy with product and system, all other partitions, or other mount points. This can be viewed in the fstab file located in vendor/etc/
Some files cannot be edited at the root, or even if they can be edited without RW, those modifications won't stick, because these are temporary files responsible for the operation of the kernel and the entire linux system, in this case android. For example, proc, or sys, if you open a clean image, or mount a system image, you will see that these folders are empty, and files appear there only after the system is started.
Is ROOT required?- If you want to prepare a new super partition inside the system, then you need it, the firmware via TWRP does not need root.
How does the script work in Magisk?- You need to install the archive via Magisk manager as a module, the script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img, these files will be located in internal memory, after which you need to them to a PC if it is a fastboot image, or flash it via TWRP as super img if the images are for recovery.
What does S=40% SE=10% and so on mean?- This is the distribution of free space in the super between the partitions 'System=S' 'Product=P' 'System_ext=SE' 'Vendor=V' 'Other sections are there they are= OT'
- For example: The whole system occupies a conditional 4.7 GB. The super partition always has a fixed size in the memory block on the device, for example, take the example with PocoF3, it has 8.5GB there
Code:
Super size 8.5-GB
{1111111111,111111111111,111111111,11111,11111111,111111111111111,000000000000000}
System System_ext Product Odm Vendor Others if any Unused memory
2.2/2.2G 0.5/0.5G 0.8/0.8G 7/7M 1.2/1.2G 1/1GB 3.8~G
- As you can see, there is unused space for the second slot in the section (In 99.99% of cases it is not needed for users with root), and we can use this space for expansion of the partitions, and for system, 40% of this free space will be distributed. For system_ext 10%, for other partitions, if there are any, conditional 10% will be divided between all of them
RO2RW worked correctly, and the system started, but I can't delete or change files, what is the reason?- Perhaps you have some Magisk module installed that prevents you from doing this, for example OverlayFS.
Also, the reason may be that your device is of the MTK family, in some models there is a restriction at the kernel level for changing system partitions, and therefore mounting in RW, you will not even be able to reinstall magisk on such devices from the system
In this case, you open the way only to modding via TWRP
Also, you need to use the latest version of a normal file manager, these are the ones I recommend:
Solid Explorer File Manager
Solid Explorer File Manager - Apps on Google Play
Organize, protect and share your files in a dual pane layout.
play.google.com
Root Explorer
Root Explorer - Apps on Google Play
The ultimate file manager for rooted devices. The original and still the best.
play.google.com
MT manager
下载 | MT管理器
MT管理器官网
mt2.cn
RO2RW worked correctly, the system started, but in any section, for example vendor, there is little free space available, 2-10mb, can it be expanded somehow?In- That's how it will not be possible to expand a lot, this is due to the limitation of space in the super itself. System partitions occupy a certain amount of space in it, in response to "What does S=40% SE=10% and so on mean?" there is an example of how it works inside. So, perhaps your firmware weighs a lot, and there is simply not enough space in the super itself, you can fix it if you know what you are doing, you need to remove any garbage, applications from the system partitions.
"/" is system, including "/system/
"/vendor" is a vendor, including "/system/vendor", with the rest of the sections in the same way by analogy. Some partitions have a different mount point, this can be viewed in your fstab, it is located along the path /vendor/etc/*fstab*.
So, you first need to delete something from the system partitions, after which, according to the configuration in RO2RW (it is available in config.txt inside the archive, or in the first choice when installing where "max expansion"), distribute the size according to percentages or a fixed size, i.e. flash ro2rw again, or generate rw-super one more time.
Will RW disappear after the OTA software update?- Yes, in this case, after OTA, you need to boot into the system first, the process will take place, re-mark super for new data, after that you can make a new super through the system or through TWRP:
1. OTA installation
2. Reboot into the system
3. Preparing a new super, or rebooting in TWRP
4. Installing a new super via fastboot, or firmware the archive inside TWRP
How to flash a file via fastboot?- You need to move the finished file from the phone to the PC, throw RW-super.img into the folder with fastboot/adb, switch to fastboot mode on the phone, and enter the command in the console on the PC "fastboot flash super RW-super.img".
Read more about using fastboot in the branch of your device.
What are the differences between the first 4 options and the rest when first selected in the script?- The first four expand the sections based on the maximum size of the super, the rest expand on a fixed scale for each section, for example, it is more logical for OnePlus to choose one of the first 4, since there are a lot of sections, about 8, and it will be very large size to expand each by the same 200 MB.
I cannot delete or modify files from /system/app or from /product/app or from any other specific directory, but at the same time in this directory or I can create a file, and at the same time in the neighboring directory I can change files, the system is RW, how to fix it?- This happens due to the non-direct mounting of specific folders, it is called overlay filesystem, more about it here: https://wiki.archlinux.org/title/Overlay_filesystem
It specifically mounts any folder read-only. At the moment, you can delete or change or add to this directory only via TWRP, having previously flashed RO2RW by selecting the LiteRW option.
Or go to the terminal and write the commands:
Code:
su
magisk --path
The last command will show the path to the magisk directory, you will need to follow the path:
"The path that the magisk --path command displayed"/.magisk/mirror/
There will be partitions that Magisk mounts directly; by going to them, you will be able to change files without obstacles from OverlayFS.
I have a device with 32GB of memory, I do not know which option to choose so that the memory does not suffer?- The super section occupies a fixed size in the device's memory and has already been marked up by the manufacturer, i.e. even if the system takes up a conditional 2 GB, super still takes up all its conditional 6 GB in memory, I wrote above about how memory is distributed in super.
Why does the script at some point ask to delete some applications?- This means that the firmware weighs a lot, and after conversion to RW, it does not fit into super, my script suggests deleting some system applications, for example, in Chinese miui there are such stupid advertising things as TikTok, MiShop, etc. Applications are removed from temporary partitions that are being prepared for conversion to super, from the installed system you do not delete anything, well, if you only interrupt the process, after installing a new super, naturally the applications will disappear.
So why should I redistribute something, I didn't understand. I don't care how the system distributes its "empty space" there, they are still not used by me for files, because it's still a system partition. Just need RW super in the same form as it is. That's all. Is it possible somehow without distribution?- No, you can't, because it won't be original anyway, it won't affect user memory, it won't affect the OTA process if the firmware is pumping FullOTA, only the process of light (incremental) updates that weigh from 2mb to 800mb on average will be prohibited, and the process will not become faster. And if you don't care, then don't you care that there is free memory in the system partitions? in any case, you can fix it through the config as you need and give 1% for all partitions, or 10 or less MB for all partitions.
If all the tests turn out to be successful, I will start adding more features to the script, so I'm waiting for the tests, and also please fill out the Google form if RO2RW worked correctly or incorrectly, by doing this you help the development, as well as other people to understand how it works on their device and their ROM
Do not PM me about the script and help without permission, write to the support group
DOWNLOAD - SourceForge
TG Group
Telegram support chat for quick feedback
Donate only TG link https://t.me/mfpupdate/47
Credits:
- Thanks to the first link in a Google search for" e2fsck --help" link for clarification on disabling RO
- Many thanks to my own tests with the super section and the official Google utilits lpdump/lpmake/lpunpack as well as the --help menu for it
- Many thanks to the first Google search result for explaining tune2fs and resize2fs
- Thanks to the Magisk team for the BusyBox and bootctl binary
- Thanks to the kory-vadim with UKA for the make_ext4fs bibary, and thanks help menu make_ext4fs
- Thanks to SKKK for the erofs.unpack binary
- Thanks all test users
Please take the survey for more RO2RW statistics
Google Forms: Sign-in
Access Google Forms with a personal Google account or Google Workspace account (for business use).
docs.google.com
Also, the entire list from the survey will be available on this table
RO2RW Support list
Ответы на форму (1) Отметка времени,You Device name: Example "Poco F3",You Device Code: Example "Alioth",ROM: Example "ArrowOS Official 12.11.22",Was the installation successful?,Attach a log file. Located on the path /sdcard/NEO.LOGS/,A brief description of wishes or problems,Which version RO2R...
docs.google.com
Changelog:
Stable Beta 3.7.0.0:
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
- Fixed non-removable logs. (To delete old logs from versions 3.6.2.1 and below, go to the /data/media/0/NEO.LOGS directory and you can delete them, or in TWRP and delete them
- Changed configuration logic for RW_SIZE and RW_SIZE_MOD parameters
- Changed the logical chain of appearance of SELECT MENU when there was a request for mount2ext4 or continue without mounting
- The logic has been completely redesigned, when in case of unsuccessful mounting, all partitions were not mounted, now everything will be mounted, except for unsuccessful ones during installation, only EXT4 is affected
- Completely redesigned config.txt, a simple one will open it and be surprised
- Now added support for forced start of the script (FOR TWRP), just configure the config as you need, in case of any failure, the script will fall into an error, do not be afraid
- Added a parameter to the config to disable timeout for the volume keys, so that the script does not fall into an error when you do not press the button for a long time
Stable Beta 3.6.2.0:
- Added avbctl for arm32, thanks for providing binaries: brigudav and Bodya-Kolibass
Stable Beta 3.6.1.1:
- Fixed work in arm32
- fixed chcon
Stable Betav3.6.0.0
- Add with only arm32 linker devices support (Support arm32)
Stable Betav3.5
- Added support for OTG and MicroSD
- Added LiteRW for Recovery mode. Some firmware is enough LiteRW
- Added manual configurator inside the script during execution in a running system through the terminal
- Added display of main paths to directories
- Fixed work for encrypted date if it is not available
- Fixed work "check RW and free size"
- Improved LiteRW code compared to LiteRW 3.0
Stable Beta 3.4.2
- Added the ability to check for RW partitions, and for free space in them. Access is available in TWRP and Terminal via termux
- Added the ability to delete pre-delete system applications
- There is an opportunity to choose "Forced deactivation of verivication and verity, or prepare patched vbmeta for manual firmware
- Fixed the work of ignoring the mounting of partitions for checking in the case of ext4
- Fixed code optimization in half of the code, cut the code thanks to universal functions
- Fixed a bunch of issues
- Fixed work install.sh in TWRP, after separating from update-binary
- Fixed work config.txt
- Fixed bash shell operation
- Fixed the calculation of free space in the super section
- Still need Samsung testers for F2FS
Beta 3.3
- Added e2fsck,tune2fs,resize2fs binaries from termux libraries
- Added the ability to ignore additional checks for ext4 systems, because of which images will not be mounted, because of which it is possible to bypass one of the errors in the previous version. But in this case DFE will not be installed
- Another fix for working with F2FS images
- Added an additional method for cases when you need to mount system images to migrate files to a new image, if direct mounting fails, an image dump will be created and it will already be mounted
- Fixed English language in the script
- Added "SKIP" option for DFE, if you don't know what it is, then press SKIP
- Moved to the bash shell, taken from the termux library, now the sh shell built into recovery / android will not be used.
- Executable script is now separated from update-binary
- Other minor fixes
- now u can use commands: RO2RW,ro2rw
Stable Beta 3.2
- Fixed work for F2FS systems, for Samsung. But you need to do additional manipulations for this, for example, to flash a custom kernel according to tests with a Samsung user comes out exactly like this.
- Fixed the problem of detecting an active slot
- The output of files has become with an informative file name like super.sparse.fastboot.active.slot._a.img
- Also, no patches are applied inside the active system, now you need to flash the same vbmeta through the rrecovery, or fastboot, it will also be output as patched and original in the case of a backup
Stable Beta 3.1.1
- Fix modified fstab for F2FS
Stable beta 3.1
- Add dfe (legacy mode) as an additional option
- Fix 55 error and need 9+gb free space for all devices
- Many text inscriptions for users have been corrected and new ones have been added so that users do not swear and understand what is happening
Beta 3.0.4:
- A lot of fixes when converting images
- Fixed a problem when dm-verity sometimes did not turn off
Beta 3.0.3:
- Fixed installation in Magisk
Beta 3.0.2:
- Small fixes
Beta 3.0.1:
- Slightly tweaked the calculator, some problems may have been fixed
Beta 3.0
- Maybe fixed the issue for some OnePlus devices
- Maybe fixed issue for new Samsung devices
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to make a backup of the original super inside the custom recovery (TWRP,OFox)
- The methods for converting images from versions 2.8 and 2.9 are combined, and it seems to me that F2FS support has been added, in theory it should work, but testing is needed
Spoiler: Older
Beta 2.9
- The procedure for converting to EXT4.img has been redesigned, there is no longer a need to mount the file system, except in cases where you need to free memory (remove) any garbage from images
Beta 2.8
- Fixed counting and comparison of large numbers for some devices
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
t.me
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
look at the size how to fix it
t.me
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
t.me
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added check for free memory before creating RW-super.img. will loop until there is enough free space
- Added an inscription about updating the script for magisk, if there was an update, then you do not need to restart the system, otherwise it will be said that you need to restart the system
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to backup the original super partition, both in row for recovery and sparse for fastboot
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added extensive log file with output folder /storage/emulated/0/NEO.LOGS a.k.a /sdcard/NEO.LOGS
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta 2.7
- Fixed a critical issue when the script was interrupted halfway through and was restarted, in which case data from system partitions could be deleted
- Fix metadata read, moved to android-tools binary from termux pkg
Toni Moon in MFP, DFЕ, RO2RW, for Android 10+
Screenshot (20 nov 2022 23:19:06)
t.me
- Fix install for magisk with hide magisk app
Toni Moon in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Fix calculate size for fixed size like 200-250mb
Thequellu in MFP, DFЕ, RO2RW, for Android 10+
Not work 150,200,250 for me
t.me
- Fixed a bug of different binary files in ROM, moved to a single busybox
Beta 2.6
- Added mode for Magisk.
Spoiler: DEMO MAGISK
Your browser is not able to display this video.
- Fixed some bugs that I don't remember anymore
Beta2.5:
-Fix awk calculate for any device
Sergiocubano1 in MFP, DFЕ, RO2RW, for Android 10+
t.me
Sergiocubano1 in MFP, DFЕ, RO2RW, for Android 10+
t.me
-add config.txt and added option to expand partitions in % or size Mb
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta2.4:
-Fix problem with a-only devices or like system partition name when not sustem_a/_b
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
Like this https://t.me/PocoF3DFE/65768 ?
t.me
Beta2.3:
-fix problem when "need -(minus)xxxx Mb free size"
Cookies in MFP, DFЕ, RO2RW, for Android 10+
Why me got -3835
t.me
Beta2.2:
-Fix problem when partition have name main or same name
Ngô Túc Thanh in MFP, DFЕ, RO2RW, for Android 10+
t.me
Ngô Túc Thanh in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta2.1:
- Fix this problem with RW for partition into TWRP ( works )
bad habbit in MFP, DFЕ, RO2RW, for Android 10+
t.me
- nject a crutch for large ROMs to fix the problem ( works with later miui cn on poco f3 )
Deleted Account in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Maybe Fix for A-only devices with super partition ( need test )
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Inject binary for disable DM-verity
Beta2:
-first release for test
Changelog:
Beta 3.0
- Maybe fixed the issue for some OnePlus devices
- Maybe fixed issue for new Samsung devices
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to make a backup of the original super inside the custom recovery (TWRP,OFox)
- The methods for converting images from versions 2.8 and 2.9 are combined, and it seems to me that F2FS support has been added, in theory it should work, but testing is needed
Changelog:
Beta 3.0.4:
- A lot of fixes when converting images
- Fixed a problem when dm-verity sometimes did not turn off
Beta 3.0.3:
- Fixed installation in Magisk
Beta 3.0.2:
- Small fixes
Beta 3.0.1:
- Slightly tweaked the calculator, some problems may have been fixed
Just flash the zip in recovery?
TheGhost1951 said:
Just flash the zip in recovery?
Click to expand...
Click to collapse
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Techguy777 said:
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Click to expand...
Click to collapse
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
TheGhost1951 said:
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
Click to expand...
Click to collapse
I have been into xda now for about 6 or 7 years. I was edger to learn and even built 3 custom roms back in android 9. Every year or 2 now google makes changes that are huge changes and I still find myself having to learn things like day 1 at times. The new EROFS kernels and roms is brand new I have no idea how they work. F2FS is samsung and thats one of the reasons I was interested because I have a tab s8 plus. The problem is for this to work it makes a copy of your super partition your system. I was trying to figure all of that out and they get pissed you dont understand all of it already. Well I tried flashing it on poco f3 because I thought I was on a RO rom because of EROFS and it failed and I had 13gb of img files in a couple of folders. It requires a lot of free space and if people have there phone filled up and start flashing it will fill it all the way up depending on how big your system is compared to storage. That should be mentioned its not.
Techguy777 said:
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Click to expand...
Click to collapse
TheGhost1951 said:
Just flash the zip in recovery?
Click to expand...
Click to collapse
Techguy777 said:
I have been into xda now for about 6 or 7 years. I was edger to learn and even built 3 custom roms back in android 9. Every year or 2 now google makes changes that are huge changes and I still find myself having to learn things like day 1 at times. The new EROFS kernels and roms is brand new I have no idea how they work. F2FS is samsung and thats one of the reasons I was interested because I have a tab s8 plus. The problem is for this to work it makes a copy of your super partition your system. I was trying to figure all of that out and they get pissed you dont understand all of it already. Well I tried flashing it on poco f3 because I thought I was on a RO rom because of EROFS and it failed and I had 13gb of img files in a couple of folders. It requires a lot of free space and if people have there phone filled up and start flashing it will fill it all the way up depending on how big your system is compared to storage. That should be mentioned its not.
Click to expand...
Click to collapse
I have added a FAQ, if there are any more questions, I will expand the FAQ
TheGhost1951 said:
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
Click to expand...
Click to collapse
My script also does RW-Super.img, if you use it from the system. In any case, I started to do the design, because I started to do work on another forum. Now it is similar to that on 4 pda
LeeGarChat said:
My script also does RW-Super.img, if you use it from the system. In any case, I started to do the design, because I started to do work on another forum. Now it is similar to that on 4 pda
Click to expand...
Click to collapse
Not very clear " if you use it from the system". I have no clue what you are saying here.
TheGhost1951 said:
Not very clear " if you use it from the system". I have no clue what you are saying here.
Click to expand...
Click to collapse
If you use a script from Termux or another terminal in the running system (that is, not via TWRP), after installing as a Magisk module. I'll fix it now, I'm bad at English
Working
izsdeaman said:
View attachment 5781557Working
Click to expand...
Click to collapse
Need "mount -o rw,remount /parts"
LeeGarChat said:
Need "mount -o rw,remount /parts"
Click to expand...
Click to collapse
your script works perfectly, partitions are both readable and writable, i flashed another system.img after running the script so it doesn't have rw yet.
Update to Stable beta 3.1
- Add dfe (legacy mode) as an additional option
- Fix 55 error and need 9+gb free space for all devices
- Many text inscriptions for users have been corrected and new ones have been added so that users do not swear and understand what is happening
Stable Beta 3.1.1
- Fix modified fstab for F2FS
I have used your Script with TWRP at Xiaomi Redmi Note 10 Pro (#sweet) and it works perfectly, partitions are both readable and writable.
Many thx
I used your script with TWRP as well on OnePlus Pro 9 in combination with lebigmac's script because his script doesn't make all folders / files in the main root storage R/W. Your script helped make it possible.
My main concern: In TWRP, if I try to place any file I backed up from the system to a folder / file that is usually R/O, I get Error:1 in twrp for a simple copy and paste job. Any reason for this? Sorry I am not an expert in android file systems.
immortalwon said:
I used your script with TWRP as well on OnePlus Pro 9 in combination with lebigmac's script because his script doesn't make all folders / files in the main root storage R/W. Your script helped make it possible.
My main concern: In TWRP, if I try to place any file I backed up from the system to a folder / file that is usually R/O, I get Error:1 in twrp for a simple copy and paste job. Any reason for this? Sorry I am not an expert in android file systems.
Click to expand...
Click to collapse
Need after mount partitions "mount -o rw,remount /system_root" for system. "mount -o rw,remount /vendor" for vendor and etc partitions.
Go to advance menu, mount. Mount all parts.
Go to advance menu. Terminal and write this commands