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?
So I wanted to install Blackball's Genesis ROM on my AL00 P10+. Unlocked bootloader just fine, installed TWRP, which appeared to work OK as well. When I boot into TWRP though (and I tried various versions already); I can't do much. Internal Storage is not recognized, shown as 0MB (SD card storage is recognized though). I can't mount anything other than my SD card, Wiping anything just gives error messages about being unable to mount xyz. Backup screen shows me no partitions to back up.
Things I have already tried from searching other threads:
- fastboot format userdata (command not allowed)
- Set a PIN in settings (never being asked for it in TWRP as I supposedly should be)
- advanced Wipe, change file system (already all on ext4, no effect)
- Switch off any encryption (switched off TrustSpace with no effect, nothing else found)
Any hint on where else to look or how to facilitate debugging my issue would be much appreciated!
Did you tried to install the rom in twrp?
Did you format data in twrp so you can see the internal storage.
Before doing anything,do a backup in twrp at least for oeminfo.
No, I never get to the point of installing anything and I have nothing to select for backup. How would I go about formatting?
khaberz said:
So I wanted to install Blackball's Genesis ROM on my AL00 P10+. Unlocked bootloader just fine, installed TWRP, which appeared to work OK as well. When I boot into TWRP though (and I tried various versions already); I can't do much. Internal Storage is not recognized, shown as 0MB (SD card storage is recognized though). I can't mount anything other than my SD card, Wiping anything just gives error messages about being unable to mount xyz. Backup screen shows me no partitions to back up.
Things I have already tried from searching other threads:
- fastboot format userdata (command not allowed)
- Set a PIN in settings (never being asked for it in TWRP as I supposedly should be)
- advanced Wipe, change file system (already all on ext4, no effect)
- Switch off any encryption (switched off TrustSpace with no effect, nothing else found)
Any hint on where else to look or how to facilitate debugging my issue would be much appreciated!
Click to expand...
Click to collapse
use it
drive.google.com/open?id=0B-NCtYJ6s_GAUHI1QW1PS0EwUHRNdEhvckVHckVKcU9KNENR
nguyennc said:
use it
drive.google.com/open?id=0B-NCtYJ6s_GAUHI1QW1PS0EwUHRNdEhvckVHckVKcU9KNENR
Click to expand...
Click to collapse
Thank you so much - this resolved it. Much appreciated!
Now I am getting a lot of failed to mount /dev/block/platform/ff3b0000 - will research and check in the ROM thread on this.
Thanks again!
khaberz said:
Thank you so much - this resolved it. Much appreciated!
Now I am getting a lot of failed to mount /dev/block/platform/ff3b0000 - will research and check in the ROM thread on this.
Thanks again!
Click to expand...
Click to collapse
All ROM is not support for AL00.
You should convert AL00 to L29.
nguyennc said:
All ROM is not support for AL00.
You should convert AL00 to L29.
Click to expand...
Click to collapse
According to https://forum.xda-developers.com/p10-plus/development/rom-fromfuture-genesis-b150-t3617126 AL00 is supported with the right datafiles. Or am I missing something?
khaberz said:
According to https://forum.xda-developers.com/p10-plus/development/rom-fromfuture-genesis-b150-t3617126 AL00 is supported with the right datafiles. Or am I missing something?
Click to expand...
Click to collapse
I had tried everything. But partitions not compatible.
nguyennc said:
I had tried everything. But partitions not compatible.
Click to expand...
Click to collapse
I see...where did you get the L29 image?
khaberz said:
I see...where did you get the L29 image?
Click to expand...
Click to collapse
* You try. I hope you will succeed. But not ok for me.
1. https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
2. https://forum.xda-developers.com/p1...nvert-to-dualsim-huawei-p10-plus-vky-t3605071
* 100% success. I had buy 5 Credits and used 2. If you need, I will send free.
https://funkyhuawei.club/rebranding
nguyennc said:
* You try. I hope you will succeed. But not ok for me.
1. https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
2. https://forum.xda-developers.com/p1...nvert-to-dualsim-huawei-p10-plus-vky-t3605071
* 100% success. I had buy 5 Credits and used 2. If you need, I will send free.
https://funkyhuawei.club/rebranding
Click to expand...
Click to collapse
Thanks a lot! I have Blackball looking at the problem in the ROM thread now. If he can't resolve it, I'll do that. Thank you!
Just to wrap this up for now: I did rebrand to L29 via funkyhuawei, found a TWRP that could read my filesystems (from https://forum.xda-developers.com/p10/development/testers-twrp-t3585256 ). Now I get Error 7 installing any ROM. No idea why. I went back to original AL00.
Any attempts to just root the device have failed as well.
From some other threads, there is some indication that my EMMC storage causes problems with some TWRPs. Most devices purchased in Europe have UFS and are therefore not affected.
Right now, I am keeping my eyes out for a TWRP that may work with my device.
nguyennc said:
use it
drive.google.com/open?id=0B-NCtYJ6s_GAUHI1QW1PS0EwUHRNdEhvckVHckVKcU9KNENR
Click to expand...
Click to collapse
Is that reliable?
Problem solved through link:
https://forum.xda-developers.com/ga...-twrp-oreo-t3769254/post76036701#post76036701
i rooted my phone 1st time and now am really stuck. I had installed xxx rom and as it booted i got fc so i accidently wiped the whole rom and forgot that i dont have the external storage to flash the rom again. Now am stuck at twrp and it says no OS installed. Please help me how do i install the ROM again?
Download the full rom from here http://oxygenos.oneplus.net.s3.amaz...3_OTA_006_all_1801292021_96eade81793548e4.zip
And then put in internal storage via twrp on
And flash it via TWRP and you are back stock .
that is what the problem..how do i put on internal storage? while TWRP is on i can see the nothing no folders etc..and when i try to copy and paste the ROM..it nothing happens..or i cant even create a new folder.
ronak123456 said:
that is what the problem..how do i put on internal storage? while TWRP is on i can see the nothing no folders etc..and when i try to copy and paste the ROM..it nothing happens..or i cant even create a new folder.
Click to expand...
Click to collapse
Just format the data by going in additional format option and then type yes after that you would be able to transfer data from PC to phone .
Aarju said:
Just format the data by going in additional format option and then type yes after that you would be able to transfer data from PC to phone .
Click to expand...
Click to collapse
Thanks men you are a life saver
ronak123456 said:
Thanks men you are a life saver
Click to expand...
Click to collapse
Your welcome dude
I would suggest stick to the stock open beta 5 as it's a good optimised rom .
ronak123456 said:
Thanks men you are a life saver
Click to expand...
Click to collapse
stick with xXx and decrypted. Definitely the best ROM right now.
dladz said:
stick with xXx and decrypted. Definitely the best ROM right now.
Click to expand...
Click to collapse
Yes, it is good! But I m unable to use the K-klock as its giving me error! target application/overlay outdated or mismatched configuration selected. any idea?
ronak123456 said:
Yes, it is good! But I m unable to use the K-klock as its giving me error! target application/overlay outdated or mismatched configuration selected. any idea?
Click to expand...
Click to collapse
Nothing wrong with K-Manager, i'm using it now.
works perfectly
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
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
abagm said:
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
Click to expand...
Click to collapse
Thanks for the input. I have it upgraded to Android 11. Yhe unknown resources shouldn't matter AFAIK, in this case, as I am only trying to install via Play Store. I was trying to work with Magisk - I have it installed. I was going to try the ExSD module but I haven't been able to add it.
V0latyle said:
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
Click to expand...
Click to collapse
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
JR1979 said:
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
Click to expand...
Click to collapse
In theory, yes - because GSIs are meant to be used with the stock kernel, and the system image doesn't have to have any specific hardware support.
LineageOS is built from AOSP, with added tweaks and customizations. I used it for a while, but grew tired of the Magisk issues I was having (PHH builds have built in SuperSU) so I just went straight vanilla with GMS.
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
JR1979 said:
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
Click to expand...
Click to collapse
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
V0latyle said:
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
Click to expand...
Click to collapse
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
JR1979 said:
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
Click to expand...
Click to collapse
Don't worry about the No OS warning, I get the same thing on my Tab A after installing a GSI.
You formatted data, yes?
You did NOT wipe /boot or /product I hope?
Something I noticed with the LineageOS GSIs is that the securized ones bootlooped, and I had to flash one of the pre-rooted builds. Can you link the image you tried to flash?
As a test to ensure a GSI runs properly, download one of the Android Developer Preview GSIs and try installing that. Let me know how it goes.
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
JR1979 said:
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
Click to expand...
Click to collapse
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
JR1979 said:
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
Click to expand...
Click to collapse
And so I tried the system.img files from the 2 zip files that are in the Android 13 (stable) folder:
aosp_arm64-exp-TP1A.220624.014-8819323-996da050.zip
gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1.zip
Neither of these work. I still get the splash screen boot loop.
One thing I noticed is when I wipe system, it shows:
========================================
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system_root' (Invalid argument)
Formatting system using mke2fs...
Done.
Updating partition details...
...done
=========================================
It's almost tablet frisbee time.