Related
Introduction
This is a collection of Tools and Resources for Flashing Mi2(s)(c).
MiFlash4Linux
https://github.com/M1cha/aries-image-builder
Core Recovery Package for MiFlash
This is a small package to Recovery MI2 from any bricked state. It has the following advantages over the official ones from Xiaomi:
They don't flash any ROM, just the core system(bootloaders, modem and recovery)
They are small which means both Download and Installation are faster
It directly installs custom Bootloader and TWRP. That means you easily get your device back to a modded status.
Please follow the official MiFlash guidelines for installation with the following differences:
the DLOAD config is called rawprogram_core.xml
the fastboot script is called flash_core.bat(or flash_core.sh for linux)
there's a script called flash_partition_table_and_core which is a alternative to flash_core.bat/sh.
It can be used to change the partition table.
USE THIS WITH THE CUSTOM BOOTLOADER INSTALLED BY ONE OF THE CORE PACKAGES ONLY. Xiaomi's bootloader will format your whole MMC device. THIS WOULD ERASE YOUR EFS AND YOU CAN'T MAKE CALLS ANYMORE
Changing the partition table
There are multiple packages available:
separated: Xiaomi's original layout with a virtual internal sdcard
separated_single: same as separated but without Dualsystem and bigger system partitions
unified: Xiaomi's new layout with /data/media support
unified_single: same as unified but without Dualsystem and bigger system partitions
unified_single_xiaomi: Xiaomi's version of unified_single
SkiFire13 said:
aries_core_unified_single.zip -> only MIUI > 5.4.x or M1cha's CM12.1 or latest AOSP5 works (only they can see Internal Storage, that now is a virtual sd-card in /data/media/0)
aries_separated_single.zip -> other roms
Click to expand...
Click to collapse
Installation:
Backup all your data(including internal sdcard, and EFS just to be safe)
if you don't use the custom Bootloader yet, flash this package using flash_core.bat/sh first. See the big red warning above for more information
flash the package using flash_partition_table_and_core.bat/sh
boot into recovery(which is TWRP now), recreate the filesystems for all partitions(system,data,cache,sdcard to ext4) in the wipe menu and reinstall your ROM.
Version Information
Bootloader: https://github.com/M1cha/mi2_lk/commits/LA.AF.1.1-02810-8064.0
TWRP: v2.8.7.0
core partitions: aries_images_5.7.16_20150626.0000.4_5.0_cn_a63cddccfa.tgz
Download links for Mobile users:
aries_core_unified_single_xiaomi.zip
aries_core_unified_single.zip
aries_core_unified.zip
aries_core_separated_single.zip
aries_core_separated.zip
XDA:DevDB Information
Flashtools, Tool/Utility for the Xiaomi Mi 2
Contributors
m11kkaa
Source Code: https://github.com/M1cha/aries-image-builder
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2015-07-27
First (as always)
Sent from my A0001
the singleboot packages causes the latest version of CM12 to fail booting because of SELinux enforcing. I'll upload a fixed package asap.
everything has been fixed and is up again.
Pls download everything again(especially MiFlash4Linux if u use that).
i think i will wait util the release of GRUB4Android....
acastrocab said:
i think i will wait util the release of GRUB4Android....
Click to expand...
Click to collapse
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
m11kkaa said:
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
Click to expand...
Click to collapse
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
On the top of the page just followed by the title, there is a "Download" tab, you could find the miracle at there ;p
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
ancics said:
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
Click to expand...
Click to collapse
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Hey M1cha, thank you! Great job!
I have some issues about the procedure:
1. I am not sure if already had a custom bootloader, so first i'll flash the package flash_core.bat :
- turn on mi2s in fastboot mode
- plug usb, device should appear in miflash(the program should be configured as the photo?)
- and click flash
- reboot phone, enter in fastboot mode again and do the same procedure with flash_partition_table_and_core.bat
Is that right?
It's easy to recreate the ext4 filesystem in TWRP? always used CWM....
m11kkaa said:
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Click to expand...
Click to collapse
Oh that's why, I'll download it from a computer, thanks!
Sent from my MI 2S using XDA Free mobile app
@m11kkaa: thnx for the linux tools/scripts, it made my migration from CWM to single-system partition + new bootloader + TWRP easier.
BTW, I just wanted to migrate and keep my current CM11 for the time being. I had to fight a bit with restore from backup because I was not aware of the incompatibility between CWM and TWRP, luckily enough it eventually was sufficient to:
reformat system, data and cache in TWRP
flash the old CWM temporarily and restore boot, system and data
flash TWRP again and make new backups.
Proposal:
It would be good if you can change the heading style of "Installation" in the OP to be the same as e.g "Introduction", because now it looks like part of "Singleboot Partition Layout" section only. It is confusing IMHO.
In my case (i.e. flashing both flash_core.sh and then flash_partition_table_and_core.sh), I had to recreate ext4 FS not only on the system partition in TWRP, but also on the data partition (it could not be mounted and TWRP announced 0 MB size) and eventually also on the cache partition. This seems to contradict the info in OP, part "Singleboot Partition Layout", which mentions that data will be preserved.
@cogano thx for your feedback
it's weird that u had to recreate the filesystems because the positions of these partitions still are the same. I resized system1, modem1 and boot1 to 2KB and system, modem and boot to 2*oldsize-2KB. I checked the offsets and they still are the same.
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
cogano said:
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
Click to expand...
Click to collapse
thx "parted /dev/block/mmcblk0 p" will help to debug these things.
If you don't have a ROM/Recovery with parted you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
m11kkaa said:
you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
Click to expand...
Click to collapse
What a great feature!
superiyezi said:
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
Click to expand...
Click to collapse
There's a Download "card" on top.
What are the partitions sizes after flashing the singleboot partition layout?
TWRP3.2.30-Universal version uploaded
https://drive.google.com/open?id=16BueY8230PzL-5ngkMiNZGxpIYBoK4EL
TWRP3.2.20-Universal version uploaded
https://drive.google.com/open?id=1Qr35EfIy76c6lkQZaKBzRS_PuBhUfjMX
TWRP3.2.10-Universal version uploaded
Rebased on TWRP3.2.1-0
https://drive.google.com/open?id=1Tcc5pk-7MOz5IRwqgH-zfKj-t7pnSMi5
TWRP3.2.0-0-Universal version uploaded
Changelog:
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
Oreo ready..........
https://drive.google.com/open?id=1uJAc84Qgw4k1NW3W3BjcVtwc37y--xz8
TWRP3.1.1-0-Universal version uploaded
Changelog:
Uses 7.5.11 Android 5.02 kernel
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
https://drive.google.com/open?id=0BwdRTuyj12_yVWZqUnd6MEN0QVk
Note: This version saves to a folder named as the serial number of the device which is different to the previous version. Old backups will not work unless they are copied into the new folder.
TWRP3.0.2-2 has had a makeover also:
Rebased on 7.3.16 Kernel
Removed F2FS support to prevent "mishaps"
Added ability to backup & restore Preloader partition
https://drive.google.com/open?id=0BwdRTuyj12_yU19qQWNra1o3alk
Hi, great work. Can you make twrp 3.0 for our beloved xrmn2? It's has been released: http://www.xda-developers.com/twrp-3-0-0-has-arrived/
If you don't like the extensive partition listings in the original, I have altered the fstab files and repacked so you see only the necessary partitions for each function. Other than that, it is the same.
Now only one version with all the partitions you need and none that will get you into trouble
Thank you for sharing!
jajk said:
TWRP3.0 is here. All credit to Jeminni.
Unpacked, examined and tested to be fully functional and free from malware by me. This is totally unaltered - just mirrored here for convenience.
Click to expand...
Click to collapse
Hi, great work...thanks alot, just keep peaking !
Can we get informed by you what kind of malware plant in this, does it method by flashing any zip using it or by restore/backup process?
Anyway, u're whispering somethin' th
at we cant wait ur MM builds desperately...
@Adam Hui Maybe you misunderstood, I checked that there is no malware in the original by unpacking it and looking at the code. I also tested every function does not break the phone and works correctly. I am assuring other users that maybe cannot examine the contents that it is clean.
My modified version only rationalizes how partitions are presented in Recovery. Try the original and you will understand the need to alter the partitions displayed.
MIUI based on MM is in beta testing for ReNo2 already (I am not one of the beta testers)
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
jajk said:
[MENTION=4666525]
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
Click to expand...
Click to collapse
Hey man, pls washout that greyed info.
Do u mean there'll be a locked bootloader in miui MM ?
U should inform us if u knew it at first time !
Hi, Is there a MultiROM / dualboot feature included in this release?
Thank you to jemimi for the dev work and thank you in advance for any reply.
@MiSteven No dualboot in this one and I haven't seen one for our phone (not that I have been looking)
New version 3.0.0-3
jajk said:
New version 3.0.0-3
Click to expand...
Click to collapse
Is this update of jemmini's TWRP_3_ReNo2.zip from 4pda.ru?
@sanceliken2000 No it is original.
jajk said:
@sanceliken2000 No it is original.
Click to expand...
Click to collapse
Thanks for the answer. Could you please tell me if i could flash it directly with twrp 3 jemminis' in order not to do the procedure with fastboot?
@sanceliken2000 Just flash it in your existing TWRP (it is a flashable zip)
Interface look good, old backups need to be re-backup! Thx~
addro said:
Interface look good, old backups need to be re-backup! Thx~
Click to expand...
Click to collapse
If you have backup made by jemmini's TWRP3 it is not necessary to re-back. The new one understands that backup.
@faorekh It surely is. I look for compatible donors since we have no official build for our device.
The only thing that changes from previous TWRP backups is the folder name where it is stored. If needed, rename the old folder to /TWRP/BACKUPS/Redmi_Note_2 and TWRP will see it or just move the old backups into the new folder when it is created on first new backup.
There is the signature "Lenovo/full_aio_otfp/aio_otfp" inside recovery. Is this recovery port from recovery-twrp-3.0.0-3-k3.img of Lenovo K3 Note?
This version works great for my rmn2 prime.
Sent from my 2014817 using Tapatalk
I flashed this recovery yesterday through my twrp 2.8.7.
After updating to TWRP 3.0.0-3 I got messages like this:
Code:
This package is for "hermes" devices; this is a "".
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/external_sd/!Flash/twrp287.zip'[/COLOR]
After that I used the fix in this thread to make my old recovery flashable again. Now everything works fine again, but you may want to look into that, so others won't have to get similar headaches as me.
Little note: I spent 3 hours trying to make this work under OSX El Capitan, but it seems like OSX can't create flashable zips. I used a windows partition to zip the files and everything worked fine.
After considering the pros and cons of upgrading (mainly I would like to see if it fixes issues that I am experiencing with custom roms), I have decided that I would like to upgrade the firmware on my G4 to v29a. However, I would like to make a backup of my current firmware (I believe booloader and modem are the parts that cannot be backed up with TWRP), and I was wondering how I would back those up.
Also, should I need to restore these backups, how would I do it?
Thanks
ThePiGuy said:
After considering the pros and cons of upgrading (mainly I would like to see if it fixes issues that I am experiencing with custom roms), I have decided that I would like to upgrade the firmware on my G4 to v29a. However, I would like to make a backup of my current firmware (I believe booloader and modem are the parts that cannot be backed up with TWRP), and I was wondering how I would back those up.
Also, should I need to restore these backups, how would I do it?
Thanks
Click to expand...
Click to collapse
Latest unofficial TWRP backups bootloader and firmware (if you select it)
Nevertheless I ALWAYS recommend to do a backup with SALT at least once as this backups really EVERYTHING ( full mode can even backup your full internal storage which can NOT be done with TWRP) . A SALT backup is just a double protection as a full TWRP backup is usually all you need.
Restore in TWRP your TWRP backup and for SALT backup files you would use TWRP plus the dd command in an adb shell if needed (e.g. dd if=/sdcard/cust.image of=/dev/block/bootdevice/by-name/cust).
But again: restoring SALT backup files is for the worst case only.. But for that case it's good to have them..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Latest unofficial TWRP backups bootloader and firmware (if you select it)
Click to expand...
Click to collapse
Would you recommend latest Marshmallow or Nougat unofficial TWRP (I'm backing up Marshmallow but I would be restoring it from Nougat or Oreo)?
ThePiGuy said:
Would you recommend latest Marshmallow or Nougat unofficial TWRP (I'm backing up Marshmallow but I would be restoring it from Nougat or Oreo)?
Click to expand...
Click to collapse
If you do not encrypt just choose latest N one. Regardless of which ROM you currently use or will use in the future.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you do not encrypt just choose latest N one. Regardless of which ROM you currently use or will use in the future.
Click to expand...
Click to collapse
Ok thanks. I just booted into it and had a look at the backup - I can see bootloader, and I can also see Carrier. Is the Carrier option the modem that is referred to in the v29a update?
ThePiGuy said:
Ok thanks. I just booted into it and had a look at the backup - I can see bootloader, and I can also see Carrier. Is the Carrier option the modem that is referred to in the v29a update?
Click to expand...
Click to collapse
Nope. Firmware = Modem
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Nevertheless I ALWAYS recommend to do a backup with SALT at least once as this backups really EVERYTHING ( full mode can even backup your full internal storage which can NOT be done with TWRP) . A SALT backup is just a double protection as a full TWRP backup is usually all you need.
Restore in TWRP your TWRP backup and for SALT backup files you would use TWRP plus the dd command in an adb shell if needed (e.g. dd if=/sdcard/cust.image of=/dev/block/bootdevice/by-name/cust).
But again: restoring SALT backup files is for the worst case only.. But for that case it's good to have them.
Click to expand...
Click to collapse
I have just tried to do a backup with SALT, and it was working really well and then it froze on the System backup. Looking in the log, it appears there has been a timeout error. Could this have been because my Ubuntu VM locked whilst the backup was happening?
ThePiGuy said:
I have just tried to do a backup with SALT, and it was working really well and then it froze on the System backup. Looking in the log, it appears there has been a timeout error. Could this have been because my Ubuntu VM locked whilst the backup was happening?
Click to expand...
Click to collapse
Well there is one open issue in SALT atm: it does not warn you about too less disk space. The result is it freezes on backup if you have not 32 GB disk space available and choosen the full backup.
In VirtualBox you can setup shared folders which then can be auto mounted on FWUL (choose persistent folder and to auto mount in vbox settings)
Choose a folder with at least 32 GB free space and choose that one in SALT.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Well there is one open issue in SALT atm: it does not warn you about too less disk space. The result is it freezes on backup if you have not 32 GB disk space available and choosen the full backup.
In VirtualBox you can setup shared folders which then can be auto mounted on FWUL (choose persistent folder and to auto mount in vbox settings)
Choose a folder with at least 32 GB free space and choose that one in SALT.
Click to expand...
Click to collapse
My VM has 58GB free space at the moment. The python error in the log was a usb timeout error
ThePiGuy said:
My VM has 58GB free space at the moment. The python error in the log was a usb timeout error
Click to expand...
Click to collapse
What FWUL version? Persistent or forgetful? If forgetful the disk size is defined by the RAM. If persistent the max avail is 30 GB. So out of the box none of them can handle a full backup atm without modifications..
...or do you have mounted a 58 GB disk in vbox and store the backup there?
Some devices / firmwares got a timeout issue like you describe in big partitions. I adjusted the timeouts already and fixed it for the most ppl. If that happens go to advanced menu and grab the log. Use a pastebin service like hastebin or pastebin and share the link
Sent from my LG-H815 using XDA Labs
steadfasterX said:
What FWUL version? Persistent or forgetful? If forgetful the disk size is defined by the RAM. If persistent the max avail is 30 GB. So out of the box none of them can handle a full backup atm without modifications..
...or do you have mounted a 58 GB disk in vbox and store the backup there?
Some devices / firmwares got a timeout issue like you describe in big partitions. I adjusted the timeouts already and fixed it for the most ppl. If that happens go to advanced menu and grab the log. Use a pastebin service like hastebin or pastebin and share the link
Click to expand...
Click to collapse
I wasn't running it in FWUL - I already had a Ubuntu 16.04.3 LTS VM set up so I was backing up in there, and the allocated disk space for the VM had 58GB free. It only had 4GB RAM allocated though, so maybe this caused an issue. I can try again on a true Ubuntu machine to see if the VM was the issue
ThePiGuy said:
I wasn't running it in FWUL - I already had a Ubuntu 16.04.3 LTS VM set up so I was backing up in there, and the allocated disk space for the VM had 58GB free. It only had 4GB RAM allocated though, so maybe this caused an issue. I can try again on a true Ubuntu machine to see if the VM was the issue
Click to expand...
Click to collapse
Just use your Ubuntu one is fine!
The RAM is just interesting when we talk about FWUL forgetful.
So just do it again and when it happens again grab the log as mentioned above.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Just use your Ubuntu one is fine!
The RAM is just interesting when we talk about FWUL forgetful.
So just do it again and when it happens again grab the log as mentioned above.
Click to expand...
Click to collapse
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Just out of interest, looking at the files, I can see a modem file (and also modemst1 and modemst2 - If I use the modem backup, do I need to flash these as well?), but I can't see a bootloader file. Is it under a different name?
Finally, now that I have a backup, where would you recommend getting the v29a files and how would you recommend flashing them?
Thanks for all your help
ThePiGuy said:
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Click to expand...
Click to collapse
Having said that, I just got an md5 mismatch error on my userdata.bin. Is there any way to backup just that partition rather than the entire thing again?
ThePiGuy said:
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Just out of interest, looking at the files, I can see a modem file (and also modemst1 and modemst2 - If I use the modem backup, do I need to flash these as well?), but I can't see a bootloader file. Is it under a different name?
Finally, now that I have a backup, where would you recommend getting the v29a files and how would you recommend flashing them?
Thanks for all your help
Click to expand...
Click to collapse
Nope modemst1 and 2 are when you have issues with your imei. Nothing which you need to restore usually. Those are also get backuped by TWRP when you choose EFS.
Regarding the way to go to N? Well when you're unlocked and you have TWRP: flash the zip from @kessaras . If you flash the full ROM ensure that it does not contain the recovery image as it would overwrite TWRP. I would also remove the laf file from there to ensure SALT will continue to work (some ppl have issues on N laf).
ThePiGuy said:
Having said that, I just got an md5 mismatch error on my userdata.bin. Is there any way to backup just that partition rather than the entire thing again?
Click to expand...
Click to collapse
Was it really a mismatch so ERROR or a warning?
Yes but not in the GUI (yet):
Open a terminal
sudo -s
cd /root/programs/lglafng
sudo python3 partitions.py --dump YOURBACKUPFOLDER/userdata.bin userdata
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Nope modemst1 and 2 are when you have issues with your imei. Nothing which you need to restore usually. Those are also get backuped by TWRP when you choose EFS.
Regarding the way to go to N? Well when you're unlocked and you have TWRP: flash the zip from @kessaras . If you flash the full ROM ensure that it does not contain the recovery image as it would overwrite TWRP. I would also remove the laf file from there to ensure SALT will continue to work (some ppl have issues on N laf).
Click to expand...
Click to collapse
Ok thanks - I'll get going
steadfasterX said:
Was it really a mismatch so ERROR or a warning?
Click to expand...
Click to collapse
Unfortunately it was definitely an error. I reran the entire backup and I got the same error - "These files are corrupt (md5 mismatch): userdata.bin" under the errors tab after md5 verification
ThePiGuy said:
Ok thanks - I'll get going
Unfortunately it was definitely an error. I reran the entire backup and I got the same error - "These files are corrupt (md5 mismatch): userdata.bin" under the errors tab after md5 verification
Click to expand...
Click to collapse
Share the log
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Share the log
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I would but I made the mistake of closing and reopening SALT and it all got deleted. Would you like me to run a third backup to get the log again?
ThePiGuy said:
I would but I made the mistake of closing and reopening SALT and it all got deleted. Would you like me to run a third backup to get the log again?
Click to expand...
Click to collapse
If you don't mind.. Maybe it's an issue I can fix. Up to you.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you don't mind.. Maybe it's an issue I can fix. Up to you.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'll get it going
WARNING : I will not responsible for any damage and lost, USE IT AT YOUR OWN RISK.
EDIT : USE V2, V1 have a serious bug in restore.
Functions :
-- Backup specified block to image
-- Restore specified image to block
Principle :
This tool using the exploit of linux kernel (or you can use normal shell superuser, but I didn't test that yet),
and use dd command to dump the block, pull it out, then there have the image of that block.
Limit :
-- You can't backup image that bigger than your phone's free space.
-- This tool is only available for Windows.
How to use :
Download the zip below, then go read Readme.
Credit :
@nlra for possible root method
someone for "su98-memory-kallsyms" binary
Nice job!
It's awesome you made an easy tool for TA backup/restore. There are perhaps millions of devices still locked out there.
I haven't tested the tool since I don't have a windows machine, but this should surely make things a bit simpler to those who arrive now to the XZs party (such as myself).
I already got my TA backup (unlocked BL and relocked) but I'm sticking to stock for now because I can't find a way to have both camera support and stability. Surprisingly, the smoothest rom I found was built for a different device (XZ) lacking only camera support in the kernel.
Can I ask what rom did you end up using?
dinosaur99 said:
Nice job!
It's awesome you made an easy tool for TA backup/restore. There are perhaps millions of devices still locked out there.
I haven't tested the tool since I don't have a windows machine, but this should surely make things a bit simpler to those who arrive now to the XZs party (such as myself).
I already got my TA backup (unlocked BL and relocked) but I'm sticking to stock for now because I can't find a way to have both camera support and stability. Surprisingly, the smoothest rom I found was built for a different device (XZ) lacking only camera support in the kernel.
Can I ask what rom did you end up using?
Click to expand...
Click to collapse
I think there has no a rom which can use as daily for xperia xzs due to its short battery-life.
But if you have time to try different possibles, maybe you can flash android 11 aosp-based rom, maybe that works.
thank you, i have successfully backed up my ta
Hi everyone
I have created an python script to automate patching of the super partition in A/B devices
can be found here: (https://github.com/ChromiumOS-Guy/SuperPatcherGSI)
important to mention that both Windows / Linux versions only work for 64-bit,
I have attached how a full log of the SuperPatcherGSI script looks like when it successfully makes a patched super.img
also I'm a new user in the XDA forums so please tell me if this post needs to be moved to somewhere else,
feel free to ask any question I will try to answer to the best of my abilities
Enjoy and Thanks.
@ChromiumOS-Guy , you are great and your script works smoothly.
Just installed LineageOS 20 after having MIUI 13.
Somehow, after flashing, my phone lost the MAC address and bluetooth (IMEIs are fine).
Do you think it can be due to LineageOS or for the flashing process?
Welcome to XDA!
Hello good tool i like it but im getting error on repack could you help ?
snx413 said:
Hello good tool i like it but im getting error on repack could you help ?
Click to expand...
Click to collapse
I can try to
newboihere said:
@ChromiumOS-Guy , you are great and your script works smoothly.
Just installed LineageOS 20 after having MIUI 13.
Somehow, after flashing, my phone lost the MAC address and bluetooth (IMEIs are fine).
Do you think it can be due to LineageOS or for the flashing process?
Welcome to XDA!
Click to expand...
Click to collapse
Thanks!,
never happened to me though, try changing LineageOS to 19 had only bad things happen with 20 (my own experience though may not be the same)
if it still doesn't work maybe the firmware you flashed corrupted your nvdata ?
if this is the case you can use SP flash to take a backup of current nvram /nvdata / nvcfg / protect1 / protect2
and try to restore MAC address and bluetooth with SP writer or Modem Meta (don't forget engineering rom)
sorry for reply time i took a break from phone roming (working on making custom PCBs)
edit:
also know that fastbootb(fastboot dynamic) works for flashing dynamic images with phones with fastboot support, this tool is for phones without fastboot like Samsung with download mode ,though it should work all the same just letting you know (if Samsung do have fastboot then i don't know about it)