Database Users

[ROM][5.1.x][Unfficial][Pisces] MI3 TD CM-12.1/13.0/14.0 [2016-10-03]

Status in latest release:
Available
Dialing
Incoming Call
Hand free conversation
Phone conversation
Call recording
Single/Dual mic noise reduction
Vibration
NFC
Sensors
Auto brightness
Compass (seems buggy in some apps)
Charge only mode (Power down charging)
Power off alarm
Broken/Unavailable
App - FM
VPN/Shadowsocks? - need apps update for Android 5
Broken/Missing/WIP
Vibrate along with Music
Setting - Single/Dual mic mode
Since there'e isn't many ppl want this rom and updating this thread is hard, infomation in this thread is no longer being actively maintained, but rom files will keep being published in download links
XDA:DevDB Information
MI3TD, ROM for the Xiaomi Mi 3
Contributors
xuefer, xuefer
Source Code: https://github.com/MI3TD
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Current Beta Version: 2016-10-03
Beta Release Date: 2016-10-03
Created 2015-03-06
Last Updated 2016-10-05

Download links
Tools:
(Required) Recovery
English TWRP2 for MI3 TD: TWRP2.8-12.1-20150523-UNOFFICIAL-pisces.zip, flashable zip with img inside
Dual System fully supported, can flash/boot system-2
Dual Data co-existing (when enabled), allow system-1 / system-2 use different data, recovery must be used to switch system along with data
Flash using "fastboot flash recovery recovery.img"
Data Media supported, auto patch system (mount_ext4.sh) to support /data/media, which can be standalone or merged into data partition
Re-partition Internal Storage (use Advanced -> Partition SD Card), merge or split data/media
Download: @baidu, @androidfilehost (MD5: 5bd1176ccf0d2f2eb777a3df50612ab3)
new updates:
MI 3 TD CM 12.1/13.0 ROMs
MI3TD CM12.1/13.0/14.0-2016XXXX (CM: XXXX, Device: XXXX), latest random updates
Download: @baidu | @360 9f89 | @androidfilehost
MI3TD CM12.1-20150528 (CM: 0528, Device: 0528)
Download: @baidu | @androidfilehost | MD5: 136d1cada4b30223de2298d5d82ecd8b
MI3TD CM12.1-20150526 (CM: 0526, Device: 0526)
Download: @baidu | @androidfilehost | MD5: 3ebaefcf6975529033f097ae03d05b62
MI3TD CM12.1-20150519 (CM: 0519, Device: 0426)
Download: @baidu | @androidfilehost | MD5: 1ca1f2792a8960bb102c5fce4c56c131
MI3TD CM12.1-20150507 (CM: 0507, Device: 0426)
Download: @baidu | @androidfilehost | MD5: a370104c8d2e2b3f6b24f625baa669c1
MI3TD CM12.1-20150426 (CM: 0426, Device: 0426)
Download: @baidu | @androidfilehost | MD5: c65dabbdc0b0482860948bad533b92c9
MI3TD CM12.1-20150424 (CM: 0424, Device: 0424)
Download: @baidu | @androidfilehost | MD5: 89dca605e0922f4ae920123175d1de29
MI 3 TD CM 12.0 ROMs
MI3TD CM12.0-20150420 (CM: 0420, Device: 0420)
Download: @baidu| @androidfilehost | MD5: 64ccae192a8616307d7723e92b3bc5cf
MI3TD CM12.0-20150412 (CM: 0412, Device: 0412)
Download: @baidu | @androidfilehost | MD5: 64ccae192a8616307d7723e92b3bc5cf
MI3TD CM12.0-20150316 (CM: 0316, Device: 0316)
Download: @baidu | @androidfilehost | MD5: 155268021356ba018a63ff0cc67421bd
MI3TD CM12.0-20150304 (CM: 0304, Device: 0304)
Download: @baidu | @androidfilehost | MD5: 68a7618a4706887fb948933ba46364c8
Optional downloads:
(Optional) Minimal Gapps for 5.0.x: pa_gapps-modular-pico-5.0.1-2015xxxx-signed.zip
or Minimal Gapps for 5.1.x: pa_gapps-modular-pico-5.1-20150418-signed.zip
Downloads: @xda
(Optional) Xposed 3.0 module: xposed-sdk22-arm-*.zip
Downloads: @xda
or Xposed 3.0, Android 5.1: xposed-sdk21-arm-*.zip
Downloads: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
ChangeLog
[color=#ff0ff]2015-05-28[/color]
Fixed connectivity check by using g.cn as default check server
Updated CM to 05-28
[color=#ff0ff]2015-05-26[/color]
Optimized boot time (maybe hard to be noticed)
Updated kernel to 0522
Updated CM to 05-26 date
[color=#ff0ff]2015-04-26 ~ 2015-05-19[/color]
Updated CM to corresponding date
[color=#ff0ff]2015-04-24[/color]
Switch to CM-12.1
Updated CM to 20150424
Kernel updated to MI3TD_5.4.22 (3.4.35-g5971b39, Sat Apr 18 20:20:31 CST 2015)
[color=#ff0ff]2015-04-20[/color]
Added: Power off alarm (Both "Power Off" and "Power Off Charging" is supported)
Updated CM to 20150420
[color=#ff0ff]2015-04-12[/color]
Added: Support for System-2. Allow being installed to System-2 and boot from it.
Fixed: rework fix for recording issue
Added: U un-mount
Updated: libnfc*.so libtbb.so file to MIUI 5.3.20
Added: Power off alarm (Both "Power Off" and "Power Off Charging" is supported)
Fixed: Allow adb access to power off charging (only if authorized already)
Improved: Bigger charging icon
Added: Allow disabling APN
Added: Bluetooth A2DP sink (as client/speaker) (setprop persist.service.bt.a2dp.sink 1, restart bluetooth)
Fixed: Can't change USB Computer mode after selecting USB Charge Only
Changed: disabled Sms to Mms convertion
Added: Show 2G/3G after carrier name
Added: Vibration intensity setting
Improved: may reduce radio not initialized after boot
Updated CM to 20150412
2015-03-16
Warning: Only boot from 1st system as of now
Fixed: audio recording (which cashed video recording), this is a temp fix. may cause battery drain
Fixed: Bluetooth sharing
Fixed: volume key wake up
Fixed: variable button key light
Fixed: color settings battery/notification led
Added: hardware testing app
Fixed: charge only mode (power "off" charging), fix graph, fix led, fix percentage
Fixed: AudioFX FC
Improved: glove mode (in Settings -> Language & Input)
Improved: AMAPNetworkLocation (provided in MIUI rom), remove it if you wan't Gapps Network Location
Improved: charge only mode when connecting with computer (implemented by CM, MTP=off, adb=off, seems buggy, gray when clicked)
Improved: add dirac effect (not tested) from MIUI
Improved: compatible with datamedia mode (yet re-partition recovery script is not provided)
Improved: compatible with FAT32, NTFS, exFAT, ext4 USB disk
Improved: improved MIUI audio blob support for stability
Improved: disable wlbwservice which restart loop (may reduce battery drain)
Improved: vibrator was too weak, update to same as MIUI
2015-03-04
Warning: Only boot from 1st system as of now
Re-enable support non-PIC/non-PIE executable (Roll back some changes of AOSP/CM-12)
Fixes: Vibrator (was unsupported by CM-12)
Added: App to SD
Fixes: Phone (fixed fild)
Fixes: Audio (Updated MIUI API patch for CM-12)
Simplified steps to flash
fastboot flash recovery recovery.img (TWRP2 English)
fastboot reboot (while holding volume UP, to boot into TWRP2 recovery)
Switch system to "Current System: 1"
Select MI3 TD CM12 zip file from sdcard, flash
(Optionall) Flash Gapps
Simplified steps to return to stock rom
fastboot flash recovery images\recovery.img (the one from MIUI MI3TD flastboot package http://www.miui.com/shuaji-393.html)
fastboot flash boot+boot1 images\boot.img
fastboot flash system+system1 images\system.img
or follow the guide in http://www.miui.com/shuaji-393.html

The ROM is uploaded to baidu cloud storage @ china, if you have mirror the it to other country which is faster out of China, please send me the link for the thread
True Dual boot should be disabled because since MIUIv6 adds encryption to data is is not supported by this recovery hack
Please install to system 1, only
The recovery provided by my link is in Chinese menu, you may want to use English one. I don't have time to find English one for you

:good:
I have flashed it,the lollipop is sweet!

@xuefer Here is the link:
File is online: https://www.androidfilehost.com/?w=files&flid=27244

Bitti09 said:
@xuefer Here is the link:
File is online: https://www.androidfilehost.com/?w=files&flid=27244
Click to expand...
Click to collapse
Can you built some of these WIP feature into your CM 12.These are some great feature that makes a phone stand out.Also can you do anything about camera quality.Sony Z or z1 uses same sensor,they have great image quality.
Please include feature which will make our phone stand out.Thanks

can we use this rom for MI 3W...?

I'm working on some feature/bug fixes
No it won't work on anything else other than MI3 TD. Check MI3 W roms for MI3 W

ok thanks...

hi dear
i flashed on Mi 3 TD 64 GB
but its not working not coming up what can i do?
thanks

you need to disable the dual boot and install it on system 1

The bugs i found till now
maps google search not working fc
, camera video force close on saving
, sometimes in calls just turning call on background on call reply
, graphics glitch on performance when trying antutu i have some screen glitches
storage not shown as normal don't see sd internal storage in settings only system storage
- antutu score 37055 performance 26540 on balanced
root works perfectly

some screenshots with bugs and antutu
I've atached the antutu score and camera and google maps problem

ROM updated. some bug fixed

please update links
on baidu fails to download pleas put androidhost links or other sources that work well outside of china failed download every time
---------- Post added at 09:05 AM ---------- Previous post was at 08:52 AM ----------
when i reach the half of the download crashes for the first 5 min works great then jumps on low transfer then chrashes , that's strange on a gigabit connection use anything else for this but can't dowload it

Finaly managed to install it
every bugs that i reported are fixed i'll try to see if i'll find any more bugs , sorry for tte delay but i had to write the kk recovery again via adb because it was overwriten by the cyanogen one , for now everything works only one request do you know someone to translate the kk recovery it took a week for me to find the options i don't know chinese and the tdb was not a option in the clasic one so arangement differs a litle from the english version .
i'll test it for any more bugs i will atatch screenshots

draven32 said:
every bugs that i reported are fixed i'll try to see if i'll find any more bugs , sorry for tte delay but i had to write the kk recovery again via adb because it was overwriten by the cyanogen one , for now everything works only one request do you know someone to translate the kk recovery it took a week for me to find the options i don't know chinese and the tdb was not a option in the clasic one so arangement differs a litle from the english version .
i'll test it for any more bugs i will atatch screenshots
Click to expand...
Click to collapse
sorry, i don't have access to the source of this version of kk recovery

good job
after all the fixes and an antutu test i found a 400 points boost , maps and voice work now still i will have to test on a long term bases to see the battery stats, no bugs except you reported i mean fm radio ,
there is a bit of lag in call animations but is easaly fix with reducing animation to 0.5
by the way can you put the internal sd in storage i only see system memory and i need to go to file explorer to see how much storage i have

an ironical opinion about cm12 vs miui
for me at list it's more stable then miui v6 rom on miui v6 had some sim problems and found myself with no sim error mobile networks grayed out on cm12 never had that problem some small glitches but there were fixed ,
i mean this is ironical that a custom firmware works better then the original rom , if xuefer works the fm radio we will have a better rom than miui v6( i don't use that but i mean that is the only thing that is missing for me )
P.S : thanks xuefer for the fast support ,

FM app is not working for the lack of MIUI framework
SIM card may not work after a hot reboot, so make sure you can dial after boot (it's easier by checking carrier name, it seems different between working or now)
good to know most bug is fixed correctly. the animation is by CM or AOSP which i don't know, they should have tweaked it better i guess
the way MI3 TD partition the disk, emulating SD-card using a separated partition, is in-formal way and isn't supported by AOSP/CM
MIUI show it by hacking the framework code.
I could try to build a recovery with support for
true dual boot
English
datamedia (merged emulated-SD-card to data)
But It take some, and maybe donation. It seems not much non-China user is using MI3 TD. And a little (if not zero) of the China user like to donate

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S4 i9505 Stock to Android 11 R

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S4 i9505 Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S4 International i9505/jfltexx Any version to Android 11 / LineageOS 18
This detailed step-by-step guide helps you transform your Samsung Galaxy S4 i9505 to a powerful one with Android 11.
Make sure your phone is i9505 before going further : when you Power on phone, it is written Galaxy S4 i9505.
CHANGELOG
v7. Moved to Android 11 R, TWRP 3.6, updated pack
v6. Moved to Android 10 Q, TWRP 3.4, root with Magisk
v5. Moved to Android 9 Pie / Official Lineage OS 16, updated pack
v4. Moved to Android 8.1 Oreo
v3. Propose Android 8 or 9, latest Odin in pack + TWRP 3.2.3-0, tweaked OpenGapps download link
v2. Android 7.1, Google Play authentification, TWRP 3.2.1-0
v1. Android 6, pack v1
1) DOWNLOAD
- djibe Galaxy S4 i9505 pack: http://bit.ly/djibe-i9505-djibev2
(contains Samsung Odin 3.13.1 flash tool + Samsung USB drivers + recovery TWRP 3.6.0_9-0 + Magisk root).
### TWRP recovery is unified among all Galaxy S4 i95xx devices
Unzip files.
+ ROM [JDCTeam] Optimized LineageOS 18.1: https://forum.xda-developers.com/t/jdcteam-optimized-lineageos18-1-v6-0-27nov.4203927/
Download latest build here (v9 or later): https://drive.google.com/drive/folders/1a0xTxU1JIO6pxBC5JGB4QqvZsKyCaa_3
+ BitGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
+ a microSD card (FAT32 format)
+ Charge phone to 100%
Copy ROM, GApps, Magisk (optional) on the microSD card.
Insert it in phone.
1) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use an app like Backupyourmobile or SMS backup & Restore to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Download latest official updates.
Connect phone to Wi-Fi.
Go to Settings > More > About device > Software updates > Update now and confirm with OK.
Install updates if there are and repeat this operation after each update.
Remove Google Account:
Go to Settings > Accounts > Google > tap on account name. You are in Sync settings.
Tap on Menu button of phone (bottom left button) > Remove account. Confirm account removal in dialog.
3) FLASH TWRP RECOVERY
Shut down phone.
Boot in Download Mode : hold Home + Power + Volume- for 3 seconds and release.
Confirm with Volume+.
Connect phone in USB, wait for bootloader drivers installation in Windows.
Then launch Odin.exe (you unzipped) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT tickeded while F. Reset Time is ticked.
In Files > AP > select twrp-3.6.0_9-0-jflte.img.tar (from my pack)
### Warranty is now Void ###
Click Start.
When PASS! is written in Odin: disconnect phone
Hold Power to shutdown phone.
4) NANDROID BACKUP
Boot in Recovery Mode: Hold Home + Power + Volume+ for 4 seconds, release and wait a few seconds for TWRP recovery to boot.
TWRP will ask for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Backup, select all partitions (EFS MUST BE STORED TO SAVE phone's IMEI),
tap on Select Storage to set it to Micro SD card.
Swipe to backup.
5) WIPE DATA
Go to Wipe > Format Data, type yes and confirm with buttom right icon.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage, then Swipe to Wipe,
then back.
6) FLASH ROM, ROOT AND GAPPS
Go back to TWRP Home menu. Then tap on Install > choose Lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
(Optional) then Add more Zips > Magisk*.zip,
then Add more Zips > bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS (OPTIONAL)
Magisk grants you superuser privileges from boot. No extra activation needed.
Superuser access can be set from Magisk Manager app.
8) DARK MODE
As the screen is Super Amoled, Dark mode can save up battery to ~30%.
Go to Settings > Display. Switch Dark theme ON.
If you experience image flickering or screen bugs: Settings > Display > Smart Pixels
Switch Smart Pixels ON fixed my bugged display.
Developer options:
Go to Settings > About.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
Enjoy,
djibe
Thanks: JDC team, LineageOS team, TWRP team, OpenGapps team, @ripee, @Exodusnick, @0LDST4R, @AnnoDomini1993, @Buff99 and many others

New version : Google Play certification, Android 7.1, enhenced pack for easier flash.

Is Lineage OS 15 stable enough to recommend it in my tutorial ?

Hi can I move apps to SD card without apps2sd or link2sd please?

John D J said:
Hi can I move apps to SD card without apps2sd or link2sd please?
Click to expand...
Click to collapse
Hi, normally with Android 7.1, when you insert a SD card Android asks if you want to use the SDcard to extend internel memory (format is required)

Tutorial updated with latest sources available

Tutorial updated for Android 8.1

Tutorial updated for Android 9 Pie

Tutorial is still up to date. Enjoy

Move to Android 10 Q, it is awesome with looong battery life

Tutorial updated for Android 11

tutorial updated

updated

Aonly or A/B

Treble Check tell me Aonly and Treble Info tell me A/B. Which one must I choose?

PHH on his Android 10 AOSP GSI thread in his op says to only use this app to check https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

flash713 said:
PHH on his Android 10 AOSP GSI thread in his op says to only use this app to check https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
Click to expand...
Click to collapse
I know, and that is the question

[Acme said:
;82172543]I know, and that is the question
Click to expand...
Click to collapse
Duhhh on me. Haha! I would suggest asking this in device specific section here on xda but you can always download the a only image and the ab image and make a backup and flash one and see if it boots. If not then flash the other gsi that has the other partitioning. It won't hurts anything. It will either boot or it won't. No other users from your device forums use GSIs? You can always search here for your device name and model in some of the popular GSI threads and see what pops up. Have you ever had an ota? If so how did your device do the ota? AB devices will update via ota in background then just ask you to reboot to apply the update. Maybe search for "Treble GSI documentation (your device model) PHH experimental XDA" and click first two links that show up and see if there's anything documented about your device.
What is your device name and model?

I read phhusson wiki on GitHub and about my phone appears,
Samsung Galaxy S9 and S9 Plus (Exynos) starlte and star2lte ✓ A (A/B after updated to One UI 2.0 Beta 3) arm64
So I should choose "A" because I have never installed One UI 2.0 Beta 3, I have installed One UI 2.0 but not Beta 3. Isn't it???

[Acme said:
;82172973]I read phhusson wiki on GitHub and about my phone appears,
Samsung Galaxy S9 and S9 Plus (Exynos) starlte and star2lte ✓ A (A/B after updated to One UI 2.0 Beta 3) arm64
So I should choose "A" because I have never installed One UI 2.0 Beta 3, I have installed One UI 2.0 but not Beta 3. Isn't it???
Click to expand...
Click to collapse
Download termux or terminal emulator app on phone and type this in: getprop ro.build.ab_update (enter)
and see what it says afterwards. If it returns true your AB and if not your Aonly. I found that info here How to check if your Android device supports Seamless Updates
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/

flash713 said:
Download termux or terminal emulator app on phone and type this in: getprop ro.build.ab_update (enter)
and see what it says afterwards. If it returns true your AB and if not your Aonly. I found that info here How to check if your Android device supports Seamless Updates
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
Click to expand...
Click to collapse
Done!

[Acme said:
;82173721]Done!
Click to expand...
Click to collapse
Are you rooted? If so maybe type: su (then enter) then do the one liner and see what happens. How long have you had this device? Have you witnessed it catch an ota and if so did it say something like "please wait while update..." then it took a minute it three because AB devices don't make you wait at all. You just look at your phone one day and it says "reboot to apply update " or something like that and you reboot and when you boot back you're on a different version or whatever. I betcha it's a A Only 64 but like I said if you flash a GSI system.img that's the wrong partition for your device all that has ever happened to me is it will hang or do the constant bootloop and not boot. Then what I would do is just manually boot back to bootloader mode and boot recovery again or fastboot the GSI system image from my PC. These days phones are made so different. I would be out hunting for someone, anyone who has same device on the GSI rom threads. I did that once a few devices ago and after reading quite a bit of posts I finally learned from another person ...

flash713 said:
Are you rooted? If so maybe type: su (then enter) then do the one liner and see what happens. How long have you had this device? Have you witnessed it catch an ota and if so did it say something like "please wait while update..." then it took a minute it three because AB devices don't make you wait at all. You just look at your phone one day and it says "reboot to apply update " or something like that and you reboot and when you boot back you're on a different version or whatever. I betcha it's a A Only 64 but like I said if you flash a GSI system.img that's the wrong partition for your device all that has ever happened to me is it will hang or do the constant bootloop and not boot. Then what I would do is just manually boot back to bootloader mode and boot recovery again or fastboot the GSI system image from my PC. These days phones are made so different. I would be out hunting for someone, anyone who has same device on the GSI rom threads. I did that once a few devices ago and after reading quite a bit of posts I finally learned from another person ...
Click to expand...
Click to collapse
Not rooted, I was stock. Now I was able to flash TWRP and I try Aonly and A/B but none works. I'm afraid i am doing something wrong

@flash713
I have tried to flash Havoc OS and I found this file in my SD Card
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 8.1.0
ROM Build ID | OPM6.171019.030.K1.release-keys
ROM Version increment | dfb3e6c233
ROM SDK version | 27
ROM/Recovery modversion | Havoc-OS-20180926-starlte-Official
Device Recovery | to Havoc-OS ***************
Device Name | starlte
Device Model | SM-G960F
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 560
Install Type | Clean[Data Wiped]
Smart ART Pre-ODEX | false
Google Camera already installed | Clean
VRMode Compatible | true
Google Camera Compatible | true
New Camera API Compatible | true
Google Pixel Features | false
Current GApps Version | No GApps Installed
Installing GApps Zipfile | /external_sd/open_gapps-arm64-8.1-full-20200403.zip
Installing GApps Version | 20200403
Installing GApps Type | full
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[default]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[default]
Remove Stock/AOSP Gallery | false[default]
Remove Stock/AOSP Launcher | false[default]
Remove Stock/AOSP MMS App | false[default]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false
Ignore Google NFC Tag | false
Ignore Google WebView | false
Total System Size (KB) | 4384424
Used System Space (KB) | 1266780
Current Free Space (KB) | 3117644
Post Install Free Space (KB) | 2227260 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.
# Begin GApps <> ROM Duplicate File List
/system/etc/sysconfig/dialer_experience.xml
# End GApps <> ROM Duplicate File List
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 3117644 | 3117644
Remove | Existing GApps | + 4 | 3117648
Remove | Obsolete Files | + 0 | 3117648
Remove | calculatorstock | + 804 | 3118452
Remove | calendarstock | + 2476 | 3120928
Remove | clockstock | + 4712 | 3125640
Remove | exchangestock | + 0 | 3125640
Remove | extservicesstock | + 20 | 3125660
Remove | extsharedstock | + 12 | 3125672
Remove | packageinstallerstock | + 5972 | 3131644
Remove | provision | + 12 | 3131656
Remove | tagstock | + 364 | 3132020
Remove | wallpapersstock | + 3028 | 3135048
Install | Core | - 110668 | 3024380
Install | batteryusage | - 9780 | 3014600
Install | books | - 13552 | 3001048
Install | calculatorgoogle | - 2632 | 2998416
Install | calendargoogle | - 20700 | 2977716
Install | carrierservices | - 17124 | 2960592
Install | chrome | - 127276 | 2833316
Install | clockgoogle | - 5996 | 2827320
Install | cloudprint | - 3840 | 2823480
Install | dialerframework | - 12 | 2823468
Install | drive | - 40884 | 2782584
Install | exchangegoogle | - 480 | 2782104
Install | gmail | - 26372 | 2755732
Install | googletts | - 29320 | 2726412
Install | keep | - 15400 | 2711012
Install | maps | - 44208 | 2666804
Install | messenger | - 44352 | 2622452
Install | moviesvrmode | - 29336 | 2593116
Install | music | - 15192 | 2577924
Install | newsstand | - 15340 | 2562584
Install | packageinstallergoogle | - 5692 | 2556892
Install | photosvrmode | - 62324 | 2494568
Install | pixellauncher | - 2296 | 2492272
Install | playgames | - 20444 | 2471828
Install | search | - 123872 | 2347956
Install | speech | - 39128 | 2308828
Install | taggoogle | - 348 | 2308480
Install | talkback | - 12436 | 2296044
Install | wallpapers | - 2368 | 2293676
Install | youtube | - 57200 | 2236476
| Buffer Space | - 9216 | 2227260
------------------------------------------------------------------
Post Install Free Space | 2227260
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
Whas does "Device A/B-partitions | false" mean?
Is my phone A/B or not?

You're not AB that's what that says. False .. if it said true it would be that you are.

Then Treble Check was right and Treble Info not.
@flash73 Thank you very much for your help

I have a galaxy j600f, which had arm32 cpu with binder64 and had a only partitioning. But I found treble-64bit-vendor-for-j6.zip here on xda. And it allowed me to flash arm64 gsi for aonly and it worked.
But now I checked using both treble check and also terminal but it says my phone has a/b partitioning. Is this possible? Thanks

[Acme said:
;82187045]Then Treble Check was right and Treble Info not.
flash73 Thank you very much for your help
Click to expand...
Click to collapse
There is just one thing: After OneUI 2, it requires SAR GSIs and SAR GSIs are named... A/B (even if you are Aonly!). So Treble Info is right. Surprise.

I have the same doubt. In the Treble Check app says that my device is A only, but in the Treble Info app says A/B. Which one is correct? The device is the Doogee N20 PRO (6GB RAM / 128GB ROM). Has anyone installed GSI ROMs on this device?
{
"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"
}

smorer said:
I have the same doubt. In the Treble Check app says that my device is A only, but in the Treble Info app says A/B. Which one is correct? The device is the Doogee N20 PRO (6GB RAM / 128GB ROM). Has anyone installed GSI ROMs on this device?
Click to expand...
Click to collapse
Both are right. Read again:
"A-only system partiton"
"Use an A/B operating system"
So you have A-only but need to flash A/B GSIs.
That's because A/B GSIs are the same as A-only but with SAR. SAR was originally on A/B devices but now is on every Android 10, including A-only. Someone really should rename A-only and A/B GSIs to non-SAR and SAR.
Edit: As you see, both apps say you have System-as-root and A/B GSIs are for all system-as-root devices.

How
flash713 said:
Are you rooted? If so maybe type: su (then enter) then do the one liner and see what happens. How long have you had this device? Have you witnessed it catch an ota and if so did it say something like "please wait while update..." then it took a minute it three because AB devices don't make you wait at all. You just look at your phone one day and it says "reboot to apply update " or something like that and you reboot and when you boot back you're on a different version or whatever. I betcha it's a A Only 64 but like I said if you flash a GSI system.img that's the wrong partition for your device all that has ever happened to me is it will hang or do the constant bootloop and not boot. Then what I would do is just manually boot back to bootloader mode and boot recovery again or fastboot the GSI system image from my PC. These days phones are made so different. I would be out hunting for someone, anyone who has same device on the GSI rom threads. I did that once a few devices ago and after reading quite a bit of posts I finally learned from another person ...
Click to expand...
Click to collapse
How Do you fastboot a gsi from pc pls help am getting bootloops installing ab roms and my device supports seamless updates and has A/B partion

abdul5555 said:
How
How Do you fastboot a gsi from pc pls help am getting bootloops installing ab roms and my device supports seamless updates and has A/B partion
Click to expand...
Click to collapse
Looks like you have some searching and lots of reading to do. That's how all this works. Everything you or I ever wanted to know about this sort of thing is already here on xda. Search and read. You will find what you are looking for. Sometimes I can be overly helpful. It's best you do as we all do and put your questions in search and read up so you can better educate yourself about all this. Until you do this there is nothing that can be done. If you come thinking someone would just answer all your questions that you have without you ever even searching anything then you are most definitely in the wrong place.
Also this post you quoted was me giving someone else feedback. All you need to know is here somewhere and a search will reveal it. It's all part of the process.

[Acme] said:
Treble Check tell me Aonly and Treble Info tell me A/B. Which one must I choose?
Click to expand...
Click to collapse
Choose A/B note also arm64... and if theres no specific custom rom for your device choose somthing like a pixel experience gsi it works even withiuth gapps flash

[IIIII] CROSS - Custom ROM Scripted Setup

Nexus 7'13 CROSS - Custom ROM Scripted Setup (c)2020-2021 k23m
CROSS works on PC with Windows, or WinPE if you do not have Windows installed, or VirtualBox with a Windows guest.
Currently supported ROMs:
- Android 10 LineageOS 17.1
- Android 11 LineageOS 18.1
- Android 11 LineageOS 18.1-flox
Previously supported ROMs:
- Android 7 LineageOS 14.1
- Android 7 LineageOS 14.1-microG
- Android 10 LineageOS 17.1-flox
FEATURES
- automatic scan of developer's website for the latest ROM version
- automatic download of all required components
- automatic single-click installation
- optional components like root or special kernel
- all you have to do is select yes/no during the installation
- both flo and deb are supported
PREREQUISITES
- unlocked device
- installed N7 USB drivers
- original eMMC partition layout may be required
All of the above are ensured with RESTOCK - also a scripted tool, available here:
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
---------------------
lineage-install-2.bat
---------------------
This script installs and/or offers the following optional components:
- Android 10 LineageOS 17.1 UNOFFICIAL maintained by ripee https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-17-1-t4038425
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-max.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
---------------------
lineage-install-3.bat
---------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1 UNOFFICIAL maintained by followmsi https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-04-07.3569067/
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
NOTE: automatic scan of the developer's website is not possible.
Please download the ROM from: https://drive.google.com/drive/fold...HZThGTnM?resourcekey=0-0BunAmDBWluYPghT0Fs6CA
Save it in CROSS' folder and drag-and-drop it on lineage-install-3.bat to start the installation.
--------------------------
lineage-install-3-flox.bat
--------------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1-flox OFFICIAL maintained by npjohnson https://forum.xda-developers.com/t/...s-7-2013-wi-fi-repartition-only-flox.4255325/
- TWRP-flox (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip (flox compatible) by k23m (optional, no need if already flox-repartitioned)
- root: Magisk (optional)
- GApps: pico unofficial by ipdev (optional)
------------------------
getlog.bat and relog.bat
------------------------
If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.
----------
fstrim.bat
----------
Improve performance of your eMMC.
---------------
repartition.bat
---------------
If sysrepart repartition is impossible due to TWRP or GPT issues, run the repartition.bat script.
SUPPORT
[FIX][EMMC] Nexus 7 2013 ⊕ bricked, dead, frozen or stuck ⊕
Quick Links if fastboot mode is not available, try Unbricking Guide if fastboot mode is available, do RESTOCK In this thread I would like to consolidate information about eMMC flash memory failures and remedies. When flash memory fails it...
forum.xda-developers.com
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
If you select the local file option, CROSS will scan the data folder and offer the newest found file for installation. If nothing is found, you can type/paste a specific file name to install. You can drop anything you like to the data folder - CROSS is now a basic universal ROM installer.
SAMPLE OUTPUT
Code:
Nexus 7'13 LineageOS 17.1 Install v1.3 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]:
--2020-05-15 06:17:53-- https://lineageos.wickenberg.nu/flo/
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'tmp1'
tmp1 [ <=> ] 6.32K --.-KB/s in 0.001s
2020-05-15 06:17:57 (5.33 MB/s) - 'tmp1' saved [6473]
Found for download: lineage-17.1-20200515-UNOFFICIAL-flo.zip
Use local TWRP file? (no if unsure) [y/n]:
Press any key to continue . . .
Downloading installation files.
--2020-05-15 06:19:02-- https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img
Resolving dl.twrp.me... 45.249.91.154
Connecting to dl.twrp.me|45.249.91.154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9271296 (8.8M) [application/octet-stream]
Saving to: 'twrp-3.3.1-0-flo.img'
twrp-3.3.1-0-flo.img 100%[=================================================>] 8.84M 945KB/s in 11s
2020-05-15 06:19:15 (788 KB/s) - 'twrp-3.3.1-0-flo.img' saved [9271296/9271296]
--2020-05-15 06:19:15-- https://lineageos.wickenberg.nu/flo/lineage-17.1-20200515-UNOFFICIAL-flo.zip
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 413523888 (394M) [application/zip]
Saving to: 'lineage-17.1-20200515-UNOFFICIAL-flo.zip'
lineage-17.1-20200515-UNOFFIC 100%[=================================================>] 394.37M 2.71MB/s in 3m 17s
2020-05-15 06:22:34 (2.01 MB/s) - 'lineage-17.1-20200515-UNOFFICIAL-flo.zip' saved [413523888/413523888]
--2020-05-15 06:22:34-- https://jaist.dl.sourceforge.net/project/opengapps/arm/20200515/open_gapps-arm-10.0-pico-202005
15.zip
Resolving jaist.dl.sourceforge.net... 150.65.7.130
Connecting to jaist.dl.sourceforge.net|150.65.7.130|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 101519489 (97M) [application/octet-stream]
Saving to: 'open_gapps-arm-10.0-pico-20200515.zip'
open_gapps-arm-10.0-pico-2020 100%[=================================================>] 96.82M 3.25MB/s in 36s
2020-05-15 06:23:11 (2.73 MB/s) - 'open_gapps-arm-10.0-pico-20200515.zip' saved [101519489/101519489]
--2020-05-15 06:23:11-- https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Resolving github.com... 52.64.108.95
Connecting to github.com|52.64.108.95|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f19-3a5b8341b6e2?
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-
Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a13162209f0fff91
&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filename%3DMagisk-v20
.4.zip&response-content-type=application%2Foctet-stream [following]
--2020-05-15 06:23:11-- https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f1
9-3a5b8341b6e2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4
_request&X-Amz-Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a
13162209f0fff91&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filena
me%3DMagisk-v20.4.zip&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... 52.216.134.219
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|52.216.134.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5942417 (5.7M) [application/octet-stream]
Saving to: 'Magisk-v20.4.zip'
Magisk-v20.4.zip 100%[=================================================>] 5.67M 2.30MB/s in 2.5s
2020-05-15 06:23:15 (2.30 MB/s) - 'Magisk-v20.4.zip' saved [5942417/5942417]
--2020-05-15 06:23:15-- https://forum.xda-developers.com/attachment.php?attachmentid=4480528
Resolving forum.xda-developers.com... 104.18.19.88, 104.18.18.88
Connecting to forum.xda-developers.com|104.18.19.88|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594 [following]
--2020-05-15 06:23:16-- https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594
Resolving dl.xda-cdn.com... 104.27.191.76, 104.27.190.76
Connecting to dl.xda-cdn.com|104.27.191.76|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 782958 (765K) [application/zip]
Saving to: 'sysrepart.zip'
sysrepart.zip 100%[=================================================>] 764.61K 591KB/s in 1.3s
2020-05-15 06:23:20 (591 KB/s) - 'sysrepart.zip' saved [782958/782958]
Press any key to continue . . .
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
Verify...
Lock status...
Flash TWRP? [y/n]: y
sending 'recovery' (9054 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.516s]
finished. total time: 0.812s
1. on N7 select "Recovery mode" with volume button
2. on N7 press power button to boot Recovery
3. when you see TWRP main menu press any key to continue
Wait...
*
Installing...
*****
Repartition? (no if already repartitioned) [y/n]: y
Transferring: 782958/782958 (100%)
2575 KB/s (782958 bytes in 0.296s)
***
Wait...
Installing zip file '/sdcard/sysrepart.zip'
Checking for Digest file...
###############################
# k23m Nexus 7'13 Repartition #
###############################
Creating log and gpt backup
Removing partitions
Creating new partitions
Formatting new partitions
###############################
Operation completed. Copy backup gpt and log files from internal storage to PC before rebooting.
###############################
Done processing script file
***
...REBOOTING
When you see TWRP main menu press any key to continue...
*****
Proceed only if you really see TWRP main menu
Press any key to continue . . .
Do dirty flash? (no if unsure) [y/n]: n
Wiping data without wiping /data/media ...
Done.
Formatting Cache using make_ext4fs...
Done processing script file
Formatting System using make_ext4fs...
Done processing script file
Wiping Cache & Dalvik...
-- Dalvik Cache Directories Wipe Complete!
Done processing script file
Formatting cache using make_ext4fs...
Done processing script file
***
Transferring: 413523888/413523888 (100%)
3649 KB/s (413523888 bytes in 110.640s)
***
Wait...
Installing zip file '/sdcard/lineage-17.1-20200515-UNOFFICIAL-flo.zip'
Checking for Digest file...
Warning: No file_contextsTarget: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keysPatching system image unconditio
nally...script succeeded: result was [1.000000]Done processing script file
Install root? [y/n]: y
Transferring: 5942417/5942417 (100%)
3868 KB/s (5942417 bytes in 1.500s)
***
Wait...
Installing zip file '/sdcard/Magisk-v20.4.zip'
Checking for Digest file...
***********************
Magisk 20.4 Installer
***********************
- Mounting /system
- Device is system-as-root
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.tzdata
- System-as-root, keep dm/avb-verity
- Target image: /dev/block/mmcblk0p14
- Device platform: arm
- Constructing environment
- Adding addon.d survival script
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Done processing script file
Install GApps? [y/n]: y
Transferring: 101519489/101519489 (100%)
3623 KB/s (101519489 bytes in 27.359s)
***
Wait...
Installing zip file '/sdcard/open_gapps-arm-10.0-pico-20200515.zip'
Checking for Digest file...
##############################
_____ _____ ___ ____
/ _ \ | __ \ / _ \ | _ \
| / \ || |__) | |_| || | \ \
| | | || ___/| __/ | | | |
| \ / || | \ |__ | | | |
\_/ \_/ |_| \___| |_| |_|
___ _ ___ ___ ___
/ __| /_\ | _ \ _ \/ __|
| (_ |/ _ \| _/ _/\__ \
\___/_/ \_\_| |_| |___/
##############################
Open GApps pico 10.0 - 20200515
- Mounting partitions
- Gathering device & ROM information
- Performing system space calculations
- Removing existing/obsolete Apps
- Installing core GApps
- Installing swypelibs
- Installing calsync
- Installing googletts
- Installing packageinstallergoogle
- Miscellaneous tasks
- Copying Log to /sdcard
- Installation complete!
- Unmounting partitions
Done processing script file
***
Done.
Press any key to continue . . .
SUPPORT - http://bit.ly/2C35sLZ
Press any key to exit...
_____________________________________________________
REPARTITION
sysrepart.zip - 1.1GB system, data is not wiped
sysrepart-max.zip - 1.3GB system, data is not wiped, automatically downloaded by LOS 17.1 script
sysrepart-flox.zip - 1.5GB system, data is wiped, 'vendor' partition is added, automatically downloaded by LOS 17.1-flox script
sysrepart-ultimate.zip - 4GB system, data is wiped, 'vendor' partition is added, 'recovery' is enlarged to 64MB in-place and your current TWRP continues to function, flox compatible, automatically downloaded by LOS 18.1-flox script. For N7-16GB try sysrepart-ultimate-2.zip
sysrepart-stock.zip - data is wiped, original partitions are restored
reboot immediately after repartition!
sysrepart-ultimate/stock work on any previous repartitions
sysrepart/max/flox work reliably only on original partitions
to install GApps larger than pico/nano you need sysrepart-ultimate
sysrepart-ultimate supports custom, oversized TWRP builds
To recover from other repartition attempts, simply install sysrepart-ultimate if you intend to use LOS17+ or sysrepart-stock if you have other plans. If direct sysrepart installation is impossible due to TWRP or GPT issues, run the repartition.bat script. On rare occasions you may have to run RESTOCK and "Restore original partitions" with it.
_____________________________________________________
UPDATE version 2.5 changes:
- update components' URLs
- update relog.bat
- remove installation scripts of no longer available ROMs
- add update.bat cleanup script (run it once)
- add repartition.bat script for repartition-only
- add lineage-install-3.bat script
Download CROSS2.zip and unzip it then download cross-update-XXX.zip and unzip it to the CROSS folder, overwrite existing files.
Also check the very latest interim updates in this post https://forum.xda-developers.com/t/iiiii-cross-custom-rom-scripted-setup.4092215/post-87622749
____________________________________________________
NOTE - most of the attached files are meant for direct script download. Except for CROSS and its updates do not download them manually unless you know what you are doing.

Hi, thank you very much for this useful tool.
I wonder whether your script could be updated to support dirty flash also. Now it seems to always make a clean flash. But it is not very convenient to set up the device after each security update.
I am not very experienced in making batch files but I was thinking about adjusting your script like follows. From:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="Red"]echo.
echo Installing...
call:wait 5
adb shell twrp wipe /data[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
To:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="red"]echo.
set /p FLASHTYPE=Do you want to make clean flash or dirty flash? Clean flash will erase all data (except the files in the internal storage) [clean/dirty]: || set FLASHTYPE=null
echo Installing...
call:wait 5
if /i %FLASHTYPE%==dirty (
echo Skipping wiping data...
echo Performing dirty flash...
goto dirty)
if /i %FLASHTYPE%==clean (
adb shell twrp wipe /data
)
:dirty[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
Any comment on this? Would this worked correctly?

prorokrak said:
....Any comment on this? Would this worked correctly?
Click to expand...
Click to collapse
Thanks for the suggestion. This code can be abbreviated, same as the other optional items:
Code:
set /p ANS=Do dirty flash? (no if unsure) [y/n]: || set ANS=n
if /i !ANS!==n (
adb shell twrp wipe /data
)
I added it to the v1.2 update.

I just gave this script a try. This is quite slick and saves a bunch of time! Thanks for this. :good:

CROSS 2 release
CROSS version 2.0
- new log script
- new fstrim script
- updated components' URLs
- removed LOS microG as it is no longer available
Both LineageOS 14.1 and LineageOS 17.1 install flawlessly. There may be temporary download issues. If so, retry later. LOS17 server errors...
Code:
Resolving lineageos.wickenberg.nu... 83.209.185.118
Connecting to lineageos.wickenberg.nu|83.209.185.118|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-10-11 10:13:40 ERROR 500: Internal Server Error.
:highfive:

Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?

jelles01 said:
Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?
Click to expand...
Click to collapse
Hi again, first copy eg "lineage-17.1-20201009-UNOFFICIAL-flo.zip" to "CROSS\data" folder, then answer [y] to the question...
Code:
Nexus 7'13 LineageOS 17.1 Install v2.0 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]: y
Found local file: lineage-17.1-20201009-UNOFFICIAL-flo.zip
As you can see it is found automatically without entering a file name. If nothing is found, you could type any file name but the file must be located in the data folder.

It has worked! The install and setup was buttery smooth, thank you so much for this tool. Amazing!

A little help.
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1?
Thanks in advance!:highfive:

GeekyTanuj said:
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1? Thanks in advance!:highfive:
Click to expand...
Click to collapse
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:

You are a lifesaver!
k23m said:
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:
Click to expand...
Click to collapse
Thank you so much for developing this, RESTOCK as well as stock MM debloat script. it literally saved hours and hours of hassle that one has to face while getting to different versions of android! Running 10 with latest updates. feels so good!

kernel Configuration.
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:

GeekyTanuj said:
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:
Click to expand...
Click to collapse
For video and games LOS17 seems optimal, check these benchmarks.
Personally I use LOS14 without Gapps and with EX kernel including a modification to the battery life extender. I lowered max battery charge to 4.00V which is equivalent to 75% (under)charge resulting in 8x increase of battery life. Furthermore, the mod allows for constant external power connection and no battery overcharging nor overheating/swelling. I edited "buildconfig.sh" in EX zip:
Code:
replace
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4200" >> $CONFIGFILE
with
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4000" >> $CONFIGFILE
:good:

You gave my Nexus 7 (2013) a new lease on life! Woo-hoo!
I was running a years-old version of the vanilla stock FW and it was soooo slow. Somebody in some comment section somewhere mentioned RESTOCK & CROSS, so I tried out RESTOCK2 and it worked flawlessly.
Then I tried installing 17.1 via CROSS2 without repartitioning (as I believed RESTOCK did that). I got an error that I did not save, hoping it wasn't a big deal. I got stuck on the Google loading screen, so I ran CROSS again. I was going to try 14.1, but wasn't given the option again (bonus? 17.1 looks beautiful and it didn't make me redownload anything, which was smart coding on your part).
I think I should have run the logging programs when I first saw errors, because I'm afraid they were cleared by the reinstallation. I did send what I could after running the loggers post-successful installation, just in case.
Now, 17.1 is working so smoothly with a quick Netflix sideload (no GApps here, used APKMirror + the APKMirror Installer) - which certainly is only working thanks to Magisk. How long did it take me to figure out how to put app icons on the homescreen (swipe up, of course!) I don't think I want to reveal
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!

iforget said:
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!
Click to expand...
Click to collapse
If the Lineage build is using followmsi's sources, then you do not need to change kernels.
You just need to activate DT2W.
See this post on how to activate using a kernel manager.
The thread with the ever changing name. xda thread - Link
If you want something simple, I use a magisk module that enables it on boot.
DT2W GitHub - Link
Cheers.
PS.
Sorry for a bit of OT.
PPS.
The Lineage 17.1 build is using followmsi's sources.

hi
I have issue with otg on my N7, i used cross2 without problems : i installed twrp, lineageos 14, root the nexus and installed elementalx and googleapp
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ?
it's a kernel issue?
any app works
thx

gibnexus said:
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ? it's a kernel issue?
Click to expand...
Click to collapse
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.

k23m said:
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.
Click to expand...
Click to collapse
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx

gibnexus said:
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx
Click to expand...
Click to collapse
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all

gibnexus said:
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all
Click to expand...
Click to collapse
I can assure you that straight LOS14+EX OTG works fine.
You must have enabled the "USB OTG + charge mode" option which is meant for car use or externally powered OTG devices. It is NOT NEEDED for normal, N7-powered OTG storage.

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S GT-I9000 Any version to Android 6

[GUIDE/TUTORIAL] Samsung Galaxy S GT-i9000 Any version to Android 6
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S (GT-I9000 galaxysmtd) stock to Android 6 Marshmallow
This detailed step-by-step guide helps you transform your Samsung Galaxy S I9000 to a more recent one with Android 6.
Make sure your phone is i9000 before going further: when you Power on phone, it is written Galaxy S.
and Go to Settings > About phone > Model number is GT-I9000.
### If Model number is not GT-I9000, quit this tutorial.
Check Android version: right below Model number, you have Firmware version.
If Android is 2.2 or below, follow this tutorial entirely.
If Android is 2.3.x, you can skip step 3)
Back to top of the same About phone menu: tap on System updates to check for an official update.
CHANGELOG OF TUTORIAL
v2. Minor improvements. Bought another i9000 to try whole tutorial again.
v1. Initial release
1) DOWNLOAD
### All you need to upgrade to Android 6 is in my pack. However, Android versions above 4.4 are very slow on Galaxy S (unusable for calls and messages)
### You can easily try Android 5.1.1 and 6.0.1 and come back to 4.4 though.
- djibe Galaxy S i9000 pack (803 MB) v1 : https://bit.ly/djibe-galaxys-pack
(contains Samsung USB drivers + Odin 1.83 + Pit file 512 + Android 2.3.6 GT_I9000_XWJW5_XXJW4_OXXJVC_Sbl + Root CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
+ lineage-11-20170406-UNOFFICIAL-galaxysmtd + omni-5.1.1-20160414-galaxysmtd-HOMEMADE + Full+Advance-6.0.1-20160919-galaxysmtd-Final).
Official LineageOS 11 thread: https://forum.xda-developers.com/t/rom-4-4-4-lineageos.3589037/
- ROM. Full Advance 6.0.1 for galaxysmtd (build 20160919). Included in my pack.
Recommended: Unofficial Lineage OS 11 for galaxysmtd (build 20170406). Included in my pack.
- OpenGApps ARM 6 pico: https://opengapps.org/?arch=arm&api=6.0&variant=pico
Recommended - OpenGApps ARM 4.4 pico: https://opengapps.org/?arch=arm&api=4.4&variant=pico
- Charge phone to 100%
2) DESIMLOCK/DEBRAND/UNLOCK i9000
First, we want to make sure phone is not locked.
On your phone, open the dialer (as if you wanted to call a phone number) and type these keys:
Code:
*#7465625#
Phone returns this message:
Network Lock
[ON]
Follow my tutorial here before going further: https://forum.xda-developers.com/galaxy-s-i9000/general/guide-tutorial-howto-unlock-debrand-t4053109
If Network Lock is [OFF]. Go to next chapter.
3) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4 (particularly in DCIM folder).
Make sure your Google Account is synchronised.
Use an app like Backupyourmobile or SMS Backup & Restore to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
4) FLASH LATEST STOCK ANDROID 2.3.6 GINGERBREAD
### This step is only required if your phone is blocked on Android 2.1 Eclair or 2.2 Froyo (no more recent official update).
If you are already on 2.3.x Gingerbread, move on to next chapter.
You will lose all the data stored on phone.
Shutdown phone.
Boot phone in Download mode: Hold buttons Power + Menu + Volume down until Droid logi is shown and release the buttons.
You see a Droid logo with "Downloading... Do not turn off Target!!!" message (video here if my explanation isn't clear:
)
On PC, launch Odin with Administrator privileges (you unziped it from my pack, in the Flash folder). Select Odin.exe > right click > Run as administrator
In Odin's main window, check all 3 checkboxes: Re-Partition, Auto Reboot, F. Reset Time. Leave other checkboxes unchecked.
### Select PDA, PHONE and CSC files from the GT_I9000_XWJW5_XXJW4_OXXJVC_Sbl folder of my pack.
In PIT > select s1_odin_20100512.pit file
PDA > select PDA_XWJW5_Sbl.tar.md5
PHONE > select PHONE_XXJW4.tar.md5
CSC > select CSC_OXXJVC.tar.md5
Connect phone to USB.
ID:COM state becomes yellow.
Click Start
### ID:COM is not yellow: Try another USB port and/or another USB cable. Or another PC.
### Let flash proceed, don't touch anything, flash will last for 2min30.
Let phone autorestart.
Skip Android setup.
###### At any time, if your phone isn't working properly (bricked, bootloop), you can start fresh from this step.
5) FLASH NEW KERNEL + CWM RECOVERY
### Join us here if you your phone was already Android 2.3.x Gingerbread
Go to Settings > Applications > Development > Switch USB debugging ON.
Power off phone. Unplug phone from USB (if it was).
Run Odin as Administrator.
In Odin main window, check ONLY F. Reset Time checkbox. All other checkboxes must be unchecked.
In PDA > select CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar
Boot phone in Download mode: Hold buttons Power + Menu + Volume- until Droid logo is shown.
Connect phone to USB.
When ID:COM is yellow, click Start.
Wait until PASS! message shows up in Odin.
Disconnect phone.
We now want to enter in ClockWorkMod Recovery v3:
Hold buttons Power + Menu + Volume down until phone is shut...
THEN immediately move finger from Volume down to Volume up while holding Power + Home until Samsung logo shows up and release 3 buttons.
### If Android starts to load, just keep pressed on Power + Home + Volume+ until phone restarts and Samsung logo starts showing again.
6) FORMAT PARTITIONS AND INSTALL ANDROID 4.4 KITKAT / LINEAGEOS 11
Navigation within CWM recovery:
- Volume up: move up selection
- Volume down: move down selection
- Home: confirm selection
- Power: back to previous menu
Use Volume down to select wipe data/factory reset and confirm with Home.
On next screen, use volume- to select Yes -- delete all user data. Confirm with Home
Then repeat the operation to wipe cache partition.
Finally, go to mounts and storage and format /system.
Now select "mount USB storage" (still in mounts and storage).
Connect to PC, Galaxy S is detected as USB drive.
From Windows explorer, copy all files from my ROMs folder + Google Apps zip on phone's internal memory.
Once finished, safely remove device from Windows, then unmount from phone and unplug phone from USB.
Go back to CWM home menu and navigate to > install zip from sdcard > choose zip from sdcard > lineage-11*.zip and confirm install
Phone flashes and reboots in CWM recovery 6.0.5.1
### You now use Power to confirm actions within CWM 6 recovery.
Chose Install zip and confirm with Power this time.
choose zip from /storage/sdcard0 and confirm with Power
Select lineage-11*.zip and confirm flash. Wait
When finished, go back to CWM main menu.
Install zip of OpenGapps Pico 4.4 as described above.
Then reboot system now, Cyanogenmod 11/Android 4.4 loads.
Skip Android setup (if you want Android > 4.4, even though not recommended for performance reasons).
7) INSTALL ANDROID 5.1 LOLLIPOP
Shutdown phone.
Restart to recovery
Repeat same steps to install omni-5.1.1*.zip (wipe data/factory reset + Install zip)
Wait during boot.
Power off phone again, back to recovery.
8) INSTALL ANDROID 6 MARSHMALLOW
Recovery is now TWRP 2.8.7.0.
Check Never show this screen during boot again and Swipe to Allow Modifications.
Go to Wipe > Advanced wipe and select Dalvik, Cache, Data and System partitions. Swipe to Wipe.
Now go to Install > select Full+Advance-6.0.1-20160919*.zip and Swipe to Confirm Flash.
It is very long. When finished, tap on Back icon (bottom right of screen).
Tap on open_gapps-arm-6.0-pico*.zip and Swipe to Confirm Flash
Wipe cache/dalvik > Reboot system
Setup Android 6.
Enjoy.
djibe
TODO:
LOS 14.1 https://forum.xda-developers.com/t/rom-final-7-1-2-unofficial-lineageos-14-1.3703447/
### Want to go back to Android 4.4 for fluid usage ?
Restart in Recovery mode.
Go to Wipe > Advanced Wipe.
Select Dalvik, cache, data and systems partitions. Swipe to wipe.
Go to Install > lineage-11*.zip and confirm flash. Wait. Reboot.
Thanks: Authors of LineageOS 11, OpenGApps, Omni ROM, Full Advance ROM, @Katayew

Hi, does it work? Am I the first here, where are the others?
---------- Post added at 07:27 PM ---------- Previous post was at 07:20 PM ----------
Why is it necessary to install Android 5 bevor Android 6 ?

Hi,
seems clear enough to have 0 reactions
Yes you have to move forward slowly and install versions on top.
I would stick to 4.4 though (for fluidity)

I tried this way, and it seems to work. What do You think about?
Basis
S1 Gingerbread 2.3.6 + CF-Root
on internal SDCard CM 13.zip
https://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rombeta-cyanogenmod-13-0-t3343471
Installation
CWM Recovery 3.0.0.5
• 1. install zip from sd card – don´t reboot
• 2. again install zip from sd card
=> TWRP 3.0.2-0 appears
Status Quo:
SDCard = vfat
Data = auto
Cache = yaffs2
System = ext4
....................................................................................the following steps maybe were wrong or unnecessary?
• Reboot to system
=> Installation starts
=> TWRP Menue appears
• Mount SDCard
• Installation CM 13
=> Failed to mount data
• wipe data ext2
=> stopped
• Reboot in Recovery
...............................................................................................................................................................................
• wipe data → Ext2 → failed
• wipe data → Repair file system => OK
• wipe data → Ext2 => OK
• wipe date → Ext4 => OK
....................................................................................the following steps maybe were wrong or unnecessary?
• wipe data → f2fs => OK
• Dalvik + cache WIPE
• Reboot System
=> TWRP Menue
• wipe format System f2fs => OK (ROM probably can´t install on f2fs)
.....................................................................................................................................................
• Mount SDCard, Data, Cache
• Instal CM 13.zip - without Verficiation and without Reboot => DONE - don´t wipe
• Install CM 13.zip => now SU is installing => DONE
• Reboot System
=> CM 13 starts ..................................................................... Antutu 5.7.1 7760
Reboot to TWRP
Status Quo:
data = f2fs
system = ext4
sdcard = vfat
cache = yaffs2
• wipe sdcard to f2fs = > OK
• cache to ext3 (unnecessary because changes automatically back to yaffs2)
• reboot to system
=> CM 13 starts ........................................................................................ Antutu 5.7.1 9500
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
i´m now trying Your Way. However would You like to give some Feedback? I have no experience in Android and i´am just trying like a monkey.
Thanks. Chris

Hi @k2-18b
k2-18b said:
I tried this way, and it seems to work. What do You think about?
Basis
S1 Gingerbread 2.3.6 + CF-Root
on internal SDCard CM 13.zip
https://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rombeta-cyanogenmod-13-0-t3343471
Installation
CWM Recovery 3.0.0.5
• 1. install zip from sd card – don´t reboot
• 2. again install zip from sd card
=> TWRP 3.0.2-0 appears
Status Quo:
SDCard = vfat
Data = auto
Cache = yaffs2
System = ext4
....................................................................................the following steps maybe were wrong or unnecessary?
• Reboot to system
=> Installation starts
=> TWRP Menue appears
• Mount SDCard
• Installation CM 13
=> Failed to mount data
• wipe data ext2
=> stopped
• Reboot in Recovery
...............................................................................................................................................................................
• wipe data → Ext2 → failed
• wipe data → Repair file system => OK
• wipe data → Ext2 => OK
• wipe date → Ext4 => OK
....................................................................................the following steps maybe were wrong or unnecessary?
• wipe data → f2fs => OK
• Dalvik + cache WIPE
• Reboot System
=> TWRP Menue
• wipe format System f2fs => OK (ROM probably can´t install on f2fs)
.....................................................................................................................................................
• Mount SDCard, Data, Cache
• Instal CM 13.zip - without Verficiation and without Reboot => DONE - don´t wipe
• Install CM 13.zip => now SU is installing => DONE
• Reboot System
=> CM 13 starts ..................................................................... Antutu 5.7.1 7760
Reboot to TWRP
Status Quo:
data = f2fs
system = ext4
sdcard = vfat
cache = yaffs2
• wipe sdcard to f2fs = > OK
• cache to ext3 (unnecessary because changes automatically back to yaffs2)
• reboot to system
=> CM 13 starts ........................................................................................ Antutu 5.7.1 9500
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
i´m now trying Your Way. However would You like to give some Feedback? I have no experience in Android and i´am just trying like a monkey.
Thanks. Chris
Click to expand...
Click to collapse
Hi Chris,
I bought another stock and simlocked SGS to test again.
Whole tutorial went on very easily.
Especially when you know that going above Android 4.4 is crazy.

Wonderful tutorial! Pulled out my old phone and it’s happily running 4.4!! Now if I could get Magisk to figure out how to work with this, then I would be overjoyed.

EirikrHinnRauthi said:
Wonderful tutorial! Pulled out my old phone and it’s happily running 4.4!! Now if I could get Magisk to figure out how to work with this, then I would be overjoyed.
Click to expand...
Click to collapse
Hi,
You may try to
Download Magisk https://github.com/topjohnwu/Magisk/releases
Rename .apk to .zip
Reboot to Recovery
Flash zip
Tell us if it worked

djibe89 said:
Hi,
You may try to
Download Magisk https://github.com/topjohnwu/Magisk/releases
Rename .apk to .zip
Reboot to Recovery
Flash zip
Tell us if it worked
Click to expand...
Click to collapse
djibe89 said:
Hi,
You may try to
Download Magisk https://github.com/topjohnwu/Magisk/releases
Rename .apk to .zip
Reboot to Recovery
Flash zip
Tell us if it worked
Click to expand...
Click to collapse
I already have the flushable .zip — here is the message I am getting (ignore the /data thing - that was resolved - message happens anyway)
Also here is a picture of what I get with SuperSU flushable from ChainFire in case that helps anyone figure out what’s up.

Yes I think the phone has a weird boot sequence and cannot be flashed like this. Sorry I don't have time to look into it.
Somewhere on XDA ?

That is actually very well explained. If, like me, you only have Linux and can't use Odin, you can extract zimage from CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar and use heimdall to flash:
heimdall flash --KERNEL ./zImage --no-reboot

can we install any newer custom ROM above android 7?

AlphaBravo said:
can we install any newer custom ROM above android 7?
Click to expand...
Click to collapse
You won't be able.
This is the end.
Farewell i9000