Database Info

[MOD][S-OFF] AOSP Based ROM Custom MTD Partitions Nexus One - Easy Flash/Patch

This recovery & patch allow installation of AOSP based ROM (CyanogenMod/OpenDesire/DeFrost) with partition sizes set to match that of Nexus One.
No more need for Apps2SD hacks!
It is very easy to install, however requires security to be disabled on your device (S-OFF in FASTBOOT).
Steps to install:
1. Download AOSP Based ROM to your SD card.
2. Download nexified-boot-patch-v1.0.0-bravo.zip to your SD card.
3. Reboot in Fastboot
4. Fastboot flash recovery nexified-recovery-clockwork-2.5.0.7-bravo.img
5. Reboot into recovery
6. Wipe data/factory reset
7. Flash ROM
8. Flash nexified-boot-patch-v1.0.0-bravo.zip
9. Reboot & Enjoy
Both the recovery, and the boot patch, have kernel cmdline:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.
The patch also removes "dalvik.vm.dexopt-data-only=1" from build.prop which places dalvik-cache on the cache partition as per AOSP.
I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.
My current partitions are:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Warnings:
Do not flash radio via recovery, only via fastboot. You should not be flashing radio via recovery anyway, it is strongly discouraged.
Credits:
AlphaRev - for bringing S-OFF to HTC Desire
Firerat - for the original mtd patch which I learned a lot from.
Lbcoder - for the initial information on how to modify partitions via kernel commands, i learned a lot from him as well.
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Kali- for porting CM6 to Desire thanks a bunch
I am doing this to try and spark further interest in this, in the hopes that other developers may improve on it, as the default partition sizes on the desire are crap.
How to uninstall / set partitions back to normal:
Boot into Fastboot
Fastboot flash standard/unmodified clockwork recovery or amon_ra
Reboot into recovery
Wipe data/factory reset
Flash ROM & Reboot
Downloads:
nexified-recovery-clockwork-2.5.0.7-bravo.img
nexified-boot-patch-v1.0.0-bravo.zip

Should this work with OpenDesire 0.34,too?
And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?

nice work.....
back in a flash

xtcislove said:
Should this work with OpenDesire 0.34,too?
And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?
Click to expand...
Click to collapse
No, the partition sizes are passed as kernel parameters, so recovery & ROM must be patched to use the same parameters.

so what are the advantages of this?
i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?
thanks for your hard works

Well done!
Very brave of you to almost brick your device (twice?) and continue development nonetheless.
I don't need it, but many others will love this. Thanks a lot.

If I follow your procedure am I stuck on nightly-132, or once i've got the resized partitions can I continue to flash CM6 nighlites?

These kernel parameters:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Where exactly are they set? I assume it's somewhere inside the boot.img?

I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps?

great works on my Desire..Thanks daedelus82 and other persons...I see 197 Mb on available space..

Thank you very much daedelus, i was waiting for this since the day s-off was released
Could you upload a version of the stable CM6 too?

Great Work! I hope this becomes the norm, we need that /system space for apps.

Excellent! At last! Thank you very much!

aleksei87 said:
Thank you very much daedelus, i was waiting for this since the day s-off was released
Could you upload a version of the stable CM6 too?
Click to expand...
Click to collapse
Hello, yes I will patch CM6.0.2 stable as well. I have to go to work now but within a few hours. I will also try to answer other questions but have to run right now.

Please note, this WILL break 'fastboot flash' functionality.
But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.

marinierb said:
These kernel parameters:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Where exactly are they set? I assume it's somewhere inside the boot.img?
Click to expand...
Click to collapse
Yes, boot.img for ROM, and recovery.img for recovery
djind said:
I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps?
Click to expand...
Click to collapse
Sorry I have patched CM and Clockwork Recovery only.
ieftm said:
Please note, this WILL break 'fastboot flash' functionality.
But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
Click to expand...
Click to collapse
Only breaks fastboot flashing of system and/or userdata, as fastboot will flash it to different blocks than the kernel is using. All other partition locations/blocks are unmodified meaning flashing of recovery, boot, and radio will be fine.. Also if you flash userdata, system, and boot all at same time it will also work, as overwriting boot will remove the kernel cmdline.
Would love to see a HBOOT implementation of this that does not require kernel modifications.
cgrec92 said:
so what are the advantages of this?
i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?
thanks for your hard works
Click to expand...
Click to collapse
Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.
I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.
My current partitions are:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1

Thanks very much for this, I'll be flashing it shortly. I have two questions if you don't mind!
Why must radio be flashed using a different method?
Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.
Maybe something like 96 System, 64 Cache, and the rest for data? (just for the love of god make it a multiple of 16 or my OCD will break the universe)

Updated OP. Added CM6 stable v6.0.2
nawoa said:
Why must radio be flashed using a different method?
Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.
Maybe something like 96 System, 64 Cache, and the rest for data?
Click to expand...
Click to collapse
You can patch system and cache to whatever sizes you want, it really depends on your ROM. If you have less than 96MB in your system partition then partitioning it to 96MB should be fine. I normally like to leave a few MB spare for good measure. See below for description on flashing radio from a re-partitioned recovery.
ezterry said:
Same steps as the rom, just ensure you *never* flash *any* spl or radio for any reason from a re-partitioned recovery with a cache partition that does not match the spl's actual cache start location. Or you will be in the market for a jtag adapter to fix your brick.
Click to expand...
Click to collapse

ieftm said:
There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
Click to expand...
Click to collapse
Thx !! we are waiting for that ;-)

Hmm... Because of the radio flashing issue and because I use DT-A2SD anyway, I think I'm going to hold off on using this until there's the HBOOT solution you guys are talking about.
Crossing my fingers that all I need to do is install standard clockwork recovery then go to a standard CM build.

[NIGHTLY][ROM][GWK74] CyanogenMod 7 for vendor Bravo (HTC Desire GSM)

This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Device specific ChangeLog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!

cm7 is in a development stage and for the first installation i recommend to:
1) install rom
2) reboot, skip setup wizard and setup your access point
3) reboot recovery and install gapps
4) start and follow setup wizard, when requested select desired gapps to be downloaded from market
Battery drain issue:
Set wifi sleep policy to never
settings -> wireless & networks -> wifi settings
press menu -> advanced and set wifi sleep policy to Never
press menu -> save
RIL issue:
Switching RIL is cause of know network problem:
* Unable to make a network scan
* Data connection die on asleep (only for some carrier)
CM7 HBOOT by Alpharev | xda thread
Change partition table size 130/5/302 (system/cache/size)
Require nightly #18 or newer
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD Addon:
CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
Bootloop free: bind mount do not cause bootloop
Zero Maintenance: no maintenance required after ROM update
Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
By default only App will be moved on SD
Optionally Cache and Data can be moved to SD, but is not recommended (guide)
Require GB Nightly #7 or newer
It's recommended to set the install location to "Internal" under Settings -> CyanogenMod -> Application Settings -> Install location
Before install check if /sd-ext is mounted, "quick system info" under A2SD Storage should report Total and Free space, if it report "information not available" format sd-ext from recovery.
r3: improved installation process (i hope)
r2: added data2sd and cache2sd as options
r1: first release
General App2SD Q&A:
Q: A2SD is recommended?
A: Internal storage perform better than SD, install A2SD only when low disk space warning happen
Q: How to check if is working?
A: run:
adb shell
df -h | grep /dev/block/mmcblk0p2
output should be
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /sd-ext
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app-private
Q: I have installed a2sd addon but now i get low space warning again, why?
A: by default a2sd addon move only app, this is fine for most user but some user with more application have to move also cache and/or data.
Cache2SD can be enabled with
adb shell
/sd-ext/userinit.d/10cache2sdext-binds enable
Data2SD
adb shell
/sd-ext/userinit.d/11data2sdext-binds enable
reboot when prompted
HBOOT
All alpharev's hboot are compatible except the oxygen version
CM7 version is recommended ~270MB for app (stock 110MB, N1 195MB)
HowTo
Perform automatic backups of files in /system/ while (re-)flashing CyanogenMod
useful link
http://goo-inside.me/google-apps/
md5:
18ef81c567398a93183aff65a41a1565 cm7_legacy_a2sd_r3-signed.zip

murdock's semi official nightly replacement drugs
update 31.05.2011: buildbot is down due to hdd crash. might take a few more days to return - so here is an interims nightly for you:
mirror1: cm_bravo_full_teamdesire-20110601-1925.zip size: 84M (88037737 bytes)
mirror2: cm_bravo_full_teamdesire-20110601-1925.zip md5sum: 38591bab5df5d8f57e714f7888567bdb

Kali- said:
CyanogenMod is a free, community built distribution of Android 2.3 (Froyo) which greatly extends the capabilities of your phone.
Click to expand...
Click to collapse
You mean Gingerbread not Froyo - pedantic I know!
Great work though by the way - excellent ROM!

sykomaniac said:
You mean Gingerbread not Froyo - pedantic I know!
Great wrok though by the way excellent ROM!
Click to expand...
Click to collapse
C&P fail
10 char

andQlimax said:
I was waiting for this thread lol
Any Radio / RIL recommended?
Click to expand...
Click to collapse
no
any 5.x should work

Nice looking forward to follow this thread

Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.

Niiiceee, great work team !

rover.prince said:
Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.
Click to expand...
Click to collapse
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report

before someone ask
Oxygen HBOOT do not work, system is too small (cm7 require other 20mb)
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested

not sure if this is a market issue or titanium backup but my apps don't appear as installed on the market after a restore. btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.

Kali- said:
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested
Click to expand...
Click to collapse
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?

MrDevil said:
btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.
Click to expand...
Click to collapse
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review

Kali- said:
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report
Click to expand...
Click to collapse
I am using it personally, I have done the installation what I did.
1. Installed CM7.
2. Installed G.Apps
3. Started Phone, Installed All Apps
4. Restored Some Apps via Titanium Backup ==>Ended Up via Low Storage
5. Installed DT
6. Executed CacheSD
7. Phone Rebooted (Took Some Time to Boot)
Voilla I am happy.

cTrox said:
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?
Click to expand...
Click to collapse
we are working for something like 5MB or less
the problem is about download and market.
for sure tmp file are stored on cache and if file size is bigger then free space download fail, not sure if there are other issue

rover.prince said:
Voilla I am happy.
Click to expand...
Click to collapse
this is the most important thing

Kali- said:
this is the most important thing
Click to expand...
Click to collapse
Kali I Love U and CM Team. Great Work with all thumbs UP.

Kali- said:
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review
Click to expand...
Click to collapse
thanks for the info. looking forward to a rc.
will try to reflash later and restore apps with mybackup and see if it's a market or titanium issue.

How long will it take before CM7 is released in stable mod?
I'm getting tired of using Oxygen 2.0 and its bugs

[Rom]*DietGingerbread*v09.16.2011*Magic/Sapp*NR6.35.16.19*Sept16*

If you want a lean mean Gingerbread rom for your new radio sapphire here it is!
Mixed results on 6.35.10.18 radio, radio 6.35.16.19 recomended. Upgrade your radio here
The source was originally from aosp and ezterry, it's quite deverged from that now.
The kernel is my 2.6.34 kernel from my other thread with all new updated usb for Gingerbread use. (turns out my kernel was fine,it was the roms that needed modifying)
As battery life goes it's ok as far as I can tell, unplugged last night at 12 am, used phone till 3 am, sat on table till 7 am, used it at work all day, when I got home at 6 it was at 58% still.
Not working:
HD youtube (has never worked for me)
Working:
cam
camcorder
usb mount
adb
usb tether (native* (wireless _settings)) < lol. been looking at code to long
charging
3d gallery
gps
wifi
cpu/memory info in about phone
usb debugging notify disable (toggle in development)
toggle for any app to sd (in applications/development)
openvpn added to vpn network types
long press back application kill (toggle in applications/development)
key backlights
Mms with full settings options (git://github.com/CyanogenMod/android_packages_apps_Mms.git)
voice search (update on market)
sync works (twitter, facebook, gmail,ect...)
updated apn list
openvpn
incoming and in-call touch UI
H for hspa enabled
CM Phone.apk
Androidterm (from cm)
Tmobile theme chooser (git://github.com/tmobile/themes-platform-vendor-tmobile-apps-ThemeChooser.git)
Notification powerwidget (thanks to ezterry)
Built in overclocking
Bluetooth pan
I shouldn't have to say wipe, yes do it, wipe all. (If coming from another rom)
If coming from any other rom I would suggest booting to the bootloader(hold back while pressing power on) and using fastboot to 'fastboot erase system -w'
Install instructions
Flash from recovery.
flash the gapps if you want them
I hope this works as good for you as it does for me!
I'm looking into a few things mentioned in this thread and adding new functionality, what would you guys like to see?
Older roms at end of post in Archive.
I'm not making a separate rom for mtd anymore, I made both DietGB and CM7 compatable with Firerats mtd boot flash and market works.
You must use fastboot and erase system "fastboot erase system -w" if you are new to DietGB or have any install or rebooting problems before posting here If you use the new recovery I compiled from cm7 clockworkmod you can just format in recovery.
I have been using this release for many weeks now, testing and modifing code, recompiling, and I think I finally have the most stable 6355 kernel and rom available, I also along the way added a few things.
New Sept 21
No wipe update to fix video recording force close
DietGB-v09.21.2011-6355sapphire
New Sept 16
Now 2.3.5 (has been for a bit now but I didn't release anything)
Many kernel updates (hope camera is good for everyone now)
added built in overclocking (in diet gingerbread settings)
bluetooth pan
new recovery
gapps backup if no wipe
3 days now, no reboots, no fc's
files are at Androidspin now, no more multiupload
DietGB-v09.16.2011-6355sapphire
July 19
Latest updates
added Notification PowerWidget
new recovery
Diet-GB-sapphire6355-07192011
carz-clockworkmod-v4.0.0.5-recovery
gapps_mdpi_gb_20110613_S
wipe if you have any issues, I didn't this time
June 19
Latest Aosp updates, new kernel, faster than ever in my testing and everything works, I would suggest a clean install.
Diet-GB-6355-v06-19-2011-signed.zip
Here is a new recovery v4.0.0.2 clockworkmod Carz-Clockworkmod-4.0.0.2-recovery.zip
reflash gapps after gapps_mdpi_gb_20110307_S.zip
New may 09
OK, everything is updated now and everything is working again, (cam and wifi) not that you knew it broke, so far after 2 days it seems more responsive and faster, I use set cpu @614 and 245
I did not wipe and it worked fine but after I did a wipe to test and it seemed faster so I don't know, you decide, I'm looking into adding compcache and swap also.
Diet-GB-6355-v05-09-2011-1-signed (usb mount fixed)(lowmemkiller fixed)
Here is a new kernel to try out, it's exactly the same as the stock kernel but has the 10mb ramhack. 10mb ramhack
New may 02
Updated to 2.3.4_r1
new Phone.apk
new Mms.apk
new Browser.apk
Diet-GB-6355-v05-01-2011
Also I have made a new recovery for our 6.35 radio sapphire phones based on Clockworkmod 3.0.2.8 get it here
New april 27
Updated kernel, no wipe from v04-23-2011, added back cm7 Mms, working on Phone.apk update
Here is link to just the kernel and modules package to flash on any version GB-v04-27-2011-signed.zip
Rom Diet-GB-6355-v04-27-2011
If you use a custom MTD flash this after DGB-boot-v1.5.8-custom-MTD_S.zip
April 23
Diet-GB-6355-04-23-2011
Updated kernel
Updated Rom 2.3.3
You need to wipe even from my rom, sorry
Diet-GB-6355-04232011
for Custom MTD flash this, DGB-boot-v1.5.8-custom-MTD_S.zip after flashing rom
v0.22.03.2011
volume/vib/silent option added
Failing at adding galaxy s style power widget, still working on it.
No wipe if coming from my roms, re install gapps
Diet Gingerbread v0.22.03.2011
Diet Gingerbread v0.22.03.2011-MTD
v0.20.03.2011
Tmobile theme chooser (tmo) (Androidian theme included)
AndroidTerm (cm)
H enabled
Diet Gingerbread v0.20.03.2011 non MTD
Diet Gingerbread v0.20.03.2011-MTD
No wipe if coming from my roms, re-install gapps (link below)
v0.16.03.2011
Updated Phone.apk
in-call and incoming call touch UI
kernel below included 528/245 max 710
No wipe needed, if coming from roms below, reflash gapps
Diet gingerbread v0.16.03.2011 non MTD
Diet gingerbread v0.16.03.2011-MTD
v0.13.03.2011
This is almost 2.3.3 I had some issues with cam with a few updates.
Facebook sync is fixed I believe
Soundrecorder with launcher shortcut added (I changed default to amr from 3gpp recording, I can post the 3gpp version if you want it)
Diet Gingerbread v0.13.03.2011 not for custom MTD
Diet Gingerbread v0.13.03.2011 w/MTD
I wiped this time, you should be able to just upgrade though, reinstall gapps
Google apps
Google apps( minimal package, get the rest from the market)
Full google apps (go to market and see if there are updates)
New kernel
I see some of you want a 710 kernel, well I did it for you, I added min and max at boot so it boots at 528/245 default, use setcpu to set to whatever you like, you can also select several different governors.
Flash over any of the roms here. Remember it's 528 default, so if you set to high and you reboot or lockup it will boot at 528 next time, once you find a stable frequency check set at boot in setcpu.
710 Diet Gingerbread kernel
Stand alone kernels (can be flashed back and forth without wipe)
528mhz kernel (if you have force closing try this please) also best battery life!
576mhz kernel (stock in rom)
614mhz kernel
Alternate gps.config files
Euro GPS config (flash this if you are having GPS issues in Europe)
Asia GPS config (flash this if you are having GPS issues in Asia)
Mixed results on 6.35.10.18 radio, radio 6.35.16.19 recomended. Upgrade your radio here
Custom MTD:
first before anything run this either in term or using adb (only "df" in term)
Code:
adb shell df
you should get something like this
Code:
[email protected]:~/android/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98100 32 98068 0% /dev
tmpfs 98100 0 98100 0% /mnt/asec
tmpfs 98100 0 98100 0% /mnt/obb
/dev/block/mtdblock3 174080 106820 67260 61% /system
/dev/block/mtdblock5 169728 114684 55044 68% /data
/dev/block/mtdblock4 133120 2048 131072 2% /cache
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 2816 2816 0 100% /system/fonts
/dev/block/mmcblk0p2 468331 8226 435120 2% /sd-ext
/dev/block/vold/179:1
7216340 5608896 1607444 78% /mnt/sdcard
/dev/block/vold/179:1
7216340 5608896 1607444 78% /mnt/secure/asec
K0HNKCLLUN"]
look at "/dev/block/mtdblock3 174080 106820 67260 61% /system" and "/dev/block/mtdblock4 133120 2048 131072 2% /cache"
I used "mtd 108 3" in my mtdpartmap.txt
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
These instructions are from firerats thread (recommended reading material) modified a little for my use.
Install Instructions:
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
Download DGB-boot-v1.5.8-CustomMTD_S.zip
Create mtdpartmap.txt and put on /sdcard/ see configuration above or in Firerats thread < recomended
reboot to recovery
nandbackup
wipe cache + data
flash DGB-recovery-v1.5.8-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Flash Diet_GB_carz_v0.090-signed.zip
Flash gapps if you want them
Flash DGB-boot-v1.5.8-CustomMTD_S.zip
reboot
Click to expand...
Click to collapse
The above is what I did and I'm running fine right now,
Code:
[email protected]:~/android/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98100 32 98068 0% /dev
tmpfs 98100 0 98100 0% /mnt/asec
tmpfs 98100 0 98100 0% /mnt/obb
/dev/block/mtdblock3 110592 106824 3768 97% /system
/dev/block/mtdblock5 363264 113212 250052 31% /data
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 2816 2816 0 100% /system/fonts
/dev/block/mmcblk0p2 468331 8227 435119 2% /sd-ext
/dev/block/mmcblk0p2 468331 8227 435119 2% /cache
/dev/block/mtdblock4 3072 788 2284 26% /dev/cache
/dev/block/vold/179:1
7216340 5665644 1550696 79% /mnt/sdcard
/dev/block/vold/179:1
7216340 5665644 1550696 79% /mnt/secure/asec
55 > 250 on data
Thanks anyone who put effort into making Gingerbread for our old phone possible.
Archive:
v0.090
removed boot animation, push one to /system/media/ if you want one
now has custom MTD support (explained at bottom, scroll down) Thank you Firerat and Ibcoder
Dietgingerbread v0.090
coming from v0.081
I only wiped cache and data as explained below
If this is a first install wipe everything
v0.081
DietGingerbread v0.081
no wipe if coming from v0.03 up re-flash gapps
v0.080
no wipe if coming from v0.03 up re-flash gapps
DietGingerbread v0.080
Flash this to fix ext mount (also works on v0.070/1)
v0.071
no wipe if coming from v0.03 up re-flash gapps
DietGingerbread v0.071
v0.06
No wipe if coming from v0.03 up, flash gapps again.
DietGingerbread v0.06
v0.05
No wipe needed if you flash the full gapps after rom
DietGingerbread v0.05
v0.03
DietGingerbread v0.03
sorry you may need to wipe, I didn't but had to re install gapps after and everything else updated from the market on it's own.
v0.01
Gingerbread for sapphire 6355 (still v0.01 kernel, flash prefered kernel)

Wow, 6.35 radio Gingerbread ROM with working Cam actually happened. I thought that's impossible thing to do. Thanks OP for all hard work you put in this. Will test in next couple of days and report back. HTC Magic is still alive and kicking almost 2 years after being release.

Nice work carz !!!
You need to put a donate link.
I think you're the last dev dedicated to the 32a 6.35.

giant_rider said:
Nice work carz !!!
You need to put a donate link.
I think you're the last dev dedicated to the 32a 6.35.
Click to expand...
Click to collapse
I do have one, not sure it works, haha

If you post it, I will add it to my threads. I updated GB Cronos with your latest kernel. Hopefully I will have bug free USB.

carz, are you missing AudioPara4.csv?

giant_rider said:
carz, are you missing AudioPara4.csv?
Click to expand...
Click to collapse
not that I know of, it flashes when detecting 6.35 radio

its in system/etc/.audio it unzips as needed when installing the rom

I just noticed it gets extracted during execution of the any kernel script from ezterry.

I could have got rid of all that but its much easier to repo sync this way

great effort carz! 2 thumbs up for you. hehe...
anyway, does voice search worked with this rom?
one more thing, does button backlight glows in this rom? i mean, when we click/screen on because in Giant's cronos version doesnt worked (correct me if im wrong, sorry Giant im not to blame you, but i love to have it glows, if possible hee....)
anyway great job to both carz and giantrider...

I'm trying to see if I can pull some of your stuff out and flash over GB Cronos latest build.
Not sure why. At this point I should sleep. If it works I will end up with a faster GB Cronos, working USB (thx to you), but Youtube and Gmail will not work.

albert emmer said:
great effort carz! 2 thumbs up for you. hehe...
anyway, does voice search worked with this rom?
one more thing, does button backlight glows in this rom? i mean, when we click/screen on because in Giant's cronos version doesnt worked (correct me if im wrong, sorry Giant im not to blame you, but i love to have it glows, if possible hee....)
anyway great job to both carz and giantrider...
Click to expand...
Click to collapse
Sure they do

Just tested voice search. it worked fine.

No offense taken Albert....carz is actually compiling himself....I'm not
But thanks for the comment, I did not even notice the back light issue.

carz....maybe I should pack it in and we focus on one solid 32a 6.35 rom.....yours is currently the least buggy I think....if people confirm that then it only makes sense....

giant_rider said:
carz....maybe I should pack it in and we focus on one solid 32a 6.35 rom.....yours is currently the least buggy I think....if people confirm that then it only makes sense....
Click to expand...
Click to collapse
Hey I'm game, when you need something let me know.

Anyone flash it yet?

carz12 said:
Hey I'm game, when you need something let me know.
Click to expand...
Click to collapse
LOL, I meant I should retire my ports and focus on your build not the other way around
I guess we'll see what makes sense....

flashing now
just had to nandroid, change radio and spl, and hey-ho were going for a boot

[CWM v6.0.4.8] MI-ONE Plus [20-04-2013]

CWM v6.0.4.8 MI-ONE Plus
This recovery is the official CyanogenMod 11 recovery with the partition resize option.
Features:
Touch capable
install zip from sdcard or sideload into system1 or system2
backup system1 and system2 individual or together into one package
much choices of where you want to restore backups to
mount and format system1 or system2
fix permissions on system1 or system2
set bootmode to system1 or system2
automatically checks for install-recovery.sh on both systems and asks you if you want to delete them TrueDualBoot
Click to expand...
Click to collapse
TrueDualBoot notes:
Enabling or disabling TDB will completely wipe your data-partition. Once enabled your data partition will be VIRTUALLY split which means that both systems together can use the full space of the data-partition.
There are some things which will break TDB:
everything which removes CWM(like Xiaomi Updater App's live install)
ROM's which don't support mount_ext4.sh (I did not see any ROM without support yet)
Click to expand...
Click to collapse
Changelog:
Code:
2014-04-20:
- fix some bugs related to TDB
2014-04-11:
- update to CWM 6.0.4.8
- update with last changes from CyanogenMod 11
2013-07-21:
- update to CWM 6.0.3.3
- update with last changes from mirom
- add touch capabilities
2013-06-17:
- update with last changes from CyanogenMod
2013-05-24:
- update to CWM 6.0.3.2
2013-04-13:
- fix flashing modem1
2013-04-06:
- update kernel to fix boot on MIUI since 3.4.5
2013-03-24:
- update to CWM 6.0.3.0
- block access to recovery partition from android
look here for more information: https://github.com/M1cha/android_bootable_recovery/commit/333f6101e155ebe4e6eba577719fd13680e06c71
2013-03-09:
- introduce TrueDualBoot feature
- backup/restore boot1 because it was missing in first release(CHECK YOUR OLD BACKUPS!!)
- show existing images in advanced restore menu only and provide system-selection
- merge upstream commits(from cyanogenmod)
2013-02-22:
first release
Bugs:
You tell me
Download:
CWM 6.0.4.8
Sourcecode:
https://github.com/rtfpessoa/android_bootable_recovery
Donate:
I do this just for fun but if you like my work it would be great if you want to spend me a beer
Installation (ZIP):
Download latest recovery-***.zip
Copy the file to the root directory of your sdcard
Reboot into recovery and install the zip file
Final notes:
Please be aware that your phone has only ONE data-partition. If you have TrueDualBoot disabled that means:
You can't install AOSP and MIUI on one phone
If you wipe your data, the settings in both systems will be deleted
Furthermore you shouldn't use the feature of MIUI-Updater app which lets you install during running system. Otherwise you'll have to reinstall CWM after every update.

Is USB mount working on this recovery?

SetazeR said:
Is USB mount working on this recovery?
Click to expand...
Click to collapse
I think it's not. I will take a look.

I don't see an option to mount data2 as /data either. And font is larger than in m1cha's CWM 6.0.3.0
Sent from my Xiaomi Mi-One Plus via Tapatalk

SetazeR said:
I don't see an option to mount data2 as /data either. And font is larger than in m1cha's CWM 6.0.3.0
Sent from my Xiaomi Mi-One Plus via Tapatalk
Click to expand...
Click to collapse
The font must have been updated by M1cha on MI2. And the "data2" works this way.
You enable TDB under advanced menu. And there you choose to boot either rom1 our rom2.
To flash a rom you just need to choose if you want it to number 1 or number 2.
Since this device has two system and boot partitions M1cha found a way to have dual data, and that works since he mount the right data, 1 or 2. When booting.
Is your question answered?

After some idle time i just rebuilt the recovery with some awesome new features. enjoy

..

hi rtfpessoa
doing some research on M1S phone we found a diference betwen m1+/m1c1 and m1s partition table. its simple. M1S END block is a bit smaller than the other two models.
all partitions are the same except the last m1+ and m1 c1 ends at 488448 but M1S 477184
that makes the script to repartition /system fails and change nothing on M1S phones.
a possible workaround is create two separated menú structures, one for m1+ and m1 c1 and other for M1S
Or (i think this one is better) let the system fdisk default END block when executing the script. that need the send of a carriage return
example:
#!/sbin/sh
# This is the systempart script for MI-ONE PLUS.
# Do not use this on MI2 or other device.
/sbin/fdisk /dev/block/mmcblk0 <<EOF
d
20
d
19
d
18
d
17
d
16
d
15
n
20868
84867
n
84869
148868
n
148870
150149
n
150151
151174
n
151176
174215
n
174217
488448 <---------------------- change this for a carriage return (enter) keystroke
t
17
60
w
EOF
that makes the script compatble for any M1 submodel.
I'll try to compile a modification for myself but i think is a good modification to insert in yor CWM branch
best regards

ehrans said:
hi rtfpessoa
doing some research on M1S phone we found a diference betwen m1+/m1c1 and m1s partition table. its simple. M1S END block is a bit smaller than the other two models.
all partitions are the same except the last m1+ and m1 c1 ends at 488448 but M1S 477184
that makes the script to repartition /system fails and change nothing on M1S phones.
a possible workaround is create two separated menú structures, one for m1+ and m1 c1 and other for M1S
Or (i think this one is better) let the system fdisk default END block when executing the script. that need the send of a carriage return
example:
#!/sbin/sh
# This is the systempart script for MI-ONE PLUS.
# Do not use this on MI2 or other device.
/sbin/fdisk /dev/block/mmcblk0 <<EOF
d
20
d
19
d
18
d
17
d
16
d
15
n
20868
84867
n
84869
148868
n
148870
150149
n
150151
151174
n
151176
174215
n
174217
488448 <---------------------- change this for a carriage return (enter) keystroke
t
17
60
w
EOF
that makes the script compatble for any M1 submodel.
I'll try to compile a modification for myself but i think is a good modification to insert in yor CWM branch
best regards
Click to expand...
Click to collapse
Now i'm using http://www.github.com/mirom recovery because they have active development to M1, you can submit a pull request to them and when i have time i will update my english version and compile it.

--

New recovery in the OP
Updated from CM repos that now have True Dual Boot (not tested), it has the script to repartition the device.
There are two versions, one with TrueDualBoot + Partition resize and other with only partition resize.
EDIT: Updated recovery (bug fix)

rtfpessoa said:
New recovery in the OP
Updated from CM repos that now have True Dual Boot (not tested), it has the script to repartition the device.
There are two versions, one with TrueDualBoot + Partition resize and other with only partition resize.
EDIT: Updated recovery (bug fix)
Click to expand...
Click to collapse
nice.... wondering if i have the old cwm recovery with TDB and partition with huge size already will flashing this new recovery will mess that up

eilegz said:
nice.... wondering if i have the old cwm recovery with TDB and partition with huge size already will flashing this new recovery will mess that up
Click to expand...
Click to collapse
In fact i'm not sure about that, because m1cha did a full re-write of the code. And i did not tested the TDB in this recovery, so make sure you have a backup to change if this one is not doing the dualboot correctly.

New recovery, should address all the bug of TDB.

[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s

DESCRIPTION
Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download.
FEATURE
The following items may not be available for all versions, please use the latest build!
Click to expand...
Click to collapse
Build with user variant instead of userdebug (to reduce image size and improve performance).
CPU/GPU is overclocked with optimized voltage/bus-cci and 300 Hz/Jiffies kernel clock frequency. [16.0 +]
EAS (sched cpufreq governor from linux-3.18) CPU scheduler implemented. [16.0 +]
Full-weight NotoSansCJK fonts included (to display East Asian characters with more font weights).
High screen refresh-rate (75 Hz) support for Mi-4c with "Sharp-rsp61322 LCD" screen. [16.0 +]
Implement ZRAM with ZSTD crypto algorithm (KSM is used after 20210116) to improve I/O performance on devices with 2GB RAM. [16.0 +]
Linux kernel is built by clang-12 toolchains, with Polly + LTO + -Ofast optimization to get better performance. [17.1 +]
Pre-dex2oat with everything filter globally (sacrificing space and first-install time to improve efficiency).
Remove or disable unnecessary kernel configs and modules, also includes some other optimizations. [16.0 +]
Remove unnecessary apps/binaries/libraries/services from system. [16.0 +]
Signature spoofing support (ready for MicroG, including Chinese translations).
User-friendly controller for special features in Settings app (like CPU overclock, Edge gesture and Screen refresh rate). [17.1 +]
...
STATUS
Go to GitHub Issues for more details and give me feedback.
Click to expand...
Click to collapse
Working
Basic hardware
Baseband/SMS
Bluetooth
Camera/Flashlight
IR remote
Speaker/Microphone
Wi-Fi
Extras
Camera API2 (with patch) [17.1 +]
Edge gesture (in Settings > System > Buttons) [16.0 +]
Overclock control (in Settings > Battery > Battery saver and performance) [17.1 +]
Screen refresh rate (in Settings > Display) [17.1 +]
Not working
SELinux permissive [16.0 +]
VOLTE (won't fix because of no compatible IMS stacks) [16.0 +]
DOWNLOAD
GitHub Releases: https://github.com/BYZYB/android_device_xiaomi_libra/releases
Kernel/ROM: https://www.androidfilehost.com/?w=files&flid=287533
TWRP: https://www.androidfilehost.com/?fid=8889791610682882451
SOURCE
Device: BYZYB/android_device_xiaomi_libra
Forked from (16.0 +): android_device_xiaomi_libra + android_device_xiaomi_msm8994-common
Kernel: BYZYB/android_kernel_xiaomi_libra
Forked from: android_kernel_xiaomi_leo
Vendor: BYZYB/android_vendor_xiaomi_libra
Forked from (16.0 +): android_vendor_xiaomi_libra + android_vendor_xiaomi_msm8994-common
Custom changes: repo_17.diff + repo_18.diff
Thanks to all developers and users (Gah0 | Mortezadadgar | Xiaomi classic dev | ...) who contributed to Mi-4c/Mi-4s (including other devices shipped with MSM8992/8994 SOC) or gave me help!
Click to expand...
Click to collapse

TIPS
Here are some tips which may improve your experience or resolve some problems.
Basic quality assurance: I only have one smart phone (3+32GB Mi-4c ×1), so the ROMs here should at least satisfy my daily usage.
This project will be kept maintained even after I bought my new mobile phone (8+128GB Mi-Mix-2 ×1) in 2021. My Mi-4c is one of the most meaningful items of my own, it's not easy to leave it behind in the drawer and say goodbye. The new battery and rear cover (thanks to yipinghuang1991) will refresh this old device and make it usable again.
Even though the signal icon in status bar shows "No signal" at the first minute after boot, the device is still able to receive SMS and phone calls (so the device does have signal, but the system doesn't admit it at all).
If the free space in /system is not enough to install GAPPs, try to delete /system/fonts/NotoSansCJK.ttc to get about 100MB free space (If Chinese/Japanese/Korean is not your main language). Removing the prebuilt Webview packages (about 120MB) after installed another one is also a solution.
If you found random reboot on your device with overclock enabled (or just updated to lineage-17.1-20201216 and left overclock option unchanged), please disable this feature to see if this issue is resolved. Go to Settings > System > Battery > Battery saver and performance, enable then disable "High performance mode", and reboot your device. If you are using lineage-17.1-20210209 or newer, it's no need to do such steps after a clean install (as both persist.sys.cpu_overclock and persist.vendor.edge_touch_mode are default to false by default).
It's highly recommended to disable system logs to reduce resource consumption (for better performance and privacy), unless you're going to collect system logs. Go to Settings > System > Developer options, and set the value of "Logger buffer sizes" to off.
It's not recommended to use SELinux enforcing mode even if it's supported in some builds. Also, please consider the negative effect of I/O performance before enabling disk encryption, unless you really want to.
BUILD
As all source codes and custom changes in my LineageOS ROMs are open-source, you are permitted to build your own ROM or kernel (not only for LineageOS) with my sources for non-commercial purpose.
There are many documents about how to build custom Android ROMs in Linux/OSX, so I will not post these basic steps here to reduce redundancy. However, there are still some important things which may not be included in other documents. Here are some basic steps about what you should do (using lineage-18.1 as example), you can also take a reference to other tutorials.
Install necessary packages
There are a number of "necessary" packages listed in most tutorials, but not all of them are needed. Here are the packages you need to install manually on Ubuntu or Debian.
sudo apt install bc bison git gnupg make repo rsync unzip zip
Sync Android sources
You need to download and update your local repo with upstream sources regularly, in order to get new changes as soon as possible (just like other open-source projects).
Init repo to current directory: repo init -u https://github.com/LineageOS/android.git -b lineage-18.1 --depth=1
Sync all repos and prune unused branches: repo sync --prune
If nothing wrong happened, the LineageOS sources have been downloaded to your computer (about 100GB). Here are some commands which might be useful in the future.
Show all local changes of your repos: repo status or repo diff
Perform any operations to all repos: repo forall -c "xxx"
Setup local manifest
To sync your Android sources with upstream repos easily, it's recommended to create a local manifest in ./repo/local_manifests/. The local manifest should be a XML file like the following one, any filename is accepted (file: libra.xml).
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="BYZYB/android_device_xiaomi_libra" path="device/xiaomi/libra" remote="github" revision="lineage-18.1" />
<project name="BYZYB/android_kernel_xiaomi_libra" path="kernel/xiaomi/libra" remote="github" revision="master" />
<project name="BYZYB/android_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_xiaomi" path="hardware/xiaomi" remote="github" revision="lineage-18.1" />
</manifest>
Resolve build errors
Due to some hacks in my device configurations which are conflict with Android build rules, there might be some build errors if using all my repos directly. To resolve this issue, you need to modify project build/make/manually on your disk. After that, you should be able to prepare the necessary environment for Android build without errors.
Setup build namespace only: . build/envsetup.sh
Prepare build environment for Mi-4c with a specified build variant (xxx = eng/userdebug/user): . build/envsetup.sh && lunch lineage_libra-xxx
If you want to build the ROM in "user" build variant instead of the default "userdebug", more changes are needed to avoid build errors or potential bootloop. The following commands are some ways to build a full ROM.
Build full ROM in "user" variant: brunch lineage_libra-user
Build full ROM in "userdebug" variant: brunch lineage_libra-userdebug
Build full ROM with a specified number of threads (x ≤ physical CPU cores): lunch lineage_libra-xxx && make -jx
If you have lunch before, here is the simplest way: m
As git patch files are similar to git diff, you can always do these changes manually without using git am xxx.patch && git reset HEAD^ or other shell commands.
Kernel build toolchains
The kernel supports to be built with gcc-9+ or clang-10+. As Link-Time-Optimization (LTO) for Clang is enabled by default (config: CONFIG_LTO_CLANG), building the kernel with GCC directly will result in build errors. In conclusion, it's recommended to choose Clang as your toolchains for both faster build speed and better performance.
As VDSO compat is enabled (config: CONFIG_COMPAT_VDSO), both arm and arm64 toolchains are needed to build the kernel. Clang could handle different cross compile targets easily (thanks to LLVM), but GCC could not. Also, though the kernel sources are compiled by clang, they will be linked by LD (included in GCC toolchains -> Binutils) with LLVM plugins. In conclusion, if the ROM you are building provides legacy gcc-4.9 toolchains (like LineageOS based projects), it should be safe to go ahead without installing GCC toolchains or Binutils. Otherwise, you need to install both Binutils and Clang packages in your computer to avoid build problems.
If you are using Ubuntu or Debian on your computer, please install the following packages (choose one way).
Using prebuilt toolchains in Android repo (recommend): sudo apt install libc6-dev libgcc-12-dev
Using toolchaings in your distribution: sudo apt install clang llvm-dev
For ROMs without legacy gcc-4.9 toolchains: sudo apt install binutils-aarch64-linux-gnu binutils-arm-linux-gnueabihf
Then you should be able to build the kernel without modifying build configs.
Build kernel image only: make bootimage
Build recovery image only: make recoveryimage
Apply custom changes (optional)

This is great. Is signature spoofing enabled? If not, could it be? MicroG users would like it. Ty.
Edit: signature spoofing is enabled, but It seems LineageOS 17 locked my bootloader.
Edit2: LineageOS 17 do not support custom partition tables. After flashing, my 2.3gb "system" goes to 1.8gb and there's no space left for NanoDroid and other mods.

Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?

rostopira said:
Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?
Click to expand...
Click to collapse
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.

WJXXBSH said:
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.
Click to expand...
Click to collapse
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)

rostopira said:
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)
Click to expand...
Click to collapse
It seems you're using lineage-17.0 roms, which needs more free space than 16.0 (eg. the APEX image).
Deleting the fonts that you never used is surely a way to get more space. If you have installed "Android System Webview" (com.google.android.webview) from play store or other origins, removing the prebuilt one from "/system/product/app/webview" should be another possible solution (get another 100MB). However, make sure to choose the new webview package in "Developer settings" and prevent factory reset unless flashing the rom again, or it might result in problems.

Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks

elna.nitz said:
Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks
Click to expand...
Click to collapse
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.

WJXXBSH said:
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.
Click to expand...
Click to collapse
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here (twrp from lollipop - nougat bootloader) I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.

elna.nitz said:
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.
Click to expand...
Click to collapse
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!

WJXXBSH said:
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!
Click to expand...
Click to collapse
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?

elna.nitz said:
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?
Click to expand...
Click to collapse
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".

WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?

elna.nitz said:
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?
Click to expand...
Click to collapse
Yes, if you want to unlock your device. A Mi account is needed to do this, on the latest MIUI version (if stable version "10.1.1.0" doesn't work, the develop version of MIUI is needed).

WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?

elna.nitz said:
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?
Click to expand...
Click to collapse
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).

WJXXBSH said:
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).
Click to expand...
Click to collapse
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?

elna.nitz said:
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?
Click to expand...
Click to collapse
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "◻".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download

WJXXBSH said:
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download
Click to expand...
Click to collapse
Finally I installed Weeb Gapps magisk Moudle, and The majority are fine.
There are 2 problems:
1. The device feels very lag in the opening of the apps and in the transition between them.
2. After restart takes the device nearly 2 minutes to find a cellular network