TWRP - Can't Mount, internal Storage 0MB - Huawei P10 Plus Questions & Answers

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

Related

[Problems & Questions] With Official 2.3 Update V2

Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.

Flashtools (MiFlash4Linux, Recovery from QDL/DLOAD, Partition resize)

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?

Corupted Data Partition

I have working TWRP (the one from the 18th) and the cyanogenmod build installed.
But somehow i managed to absurdly corrupt my data partition.
atm it shows as EXT4 partition in twrp and fastboot.
When i try to boot cm, i get "encryption failed" which is weird because EXT4 does not even support encryption on android. I think is still sees the F2FS partition.
When it tries to format via TWRP it automatically chooses F2FS
When i try to format F2FS i get tons of errors:
Unable to mount /data and find crypto footer.
Unable to recreate Data folder.
Unable to format data..
.....
process ended with signal 6.
Formatting /data with fastboot did not help,
format:f2fs trows errors
and formant:ext4 works but still does not boot. "Failed Encryption"
Question: ....Help?
sorry 4 grammar.
btw i got build form here:
bluesmoothie said:
I've found the problem !
That was the BOARD_SYSTEMIMAGE_PARTITION_SIZE set at a wrong value !
I've successfuly flashed build with this parameter corriged !
EDIT:It's uploading in my dropbox but keep in mind that not all works correctly.
EDIT:https://www.dropbox.com/sh/fhaq20kjn...PjPgoJHva?dl=0
Click to expand...
Click to collapse
nvm it was fault of the recovery the lineage os one fixed everything
Hey where did you find a lineage os for the nova/nova plus?
Rymcbc said:
Hey where did you find a lineage os for the nova/nova plus?
Click to expand...
Click to collapse
I also would like to have a copy of it.
Rymcbc said:
Hey where did you find a lineage os for the nova/nova plus?
Click to expand...
Click to collapse
Michiel0912 said:
I also would like to have a copy of it.
Click to expand...
Click to collapse
From here: https://twitter.com/Grarak/status/840002964718813186
Anyone know if it's been tried on the L03 variants?

[URGENT] Need help disabling the forced encryption stuff

Why the [URGENT] you might ask? Well, I just happen to leave to the other side of the world where I won't have access to a PC, so leaving without a propely working phone....well, you get the idea
The person whose post helps me get this sorted out and have properly disabled forceencryption and the likes will get a small donation via PayPal by me - promised!
Hi there,
since yesterday I'm the proud owner of an LG G6 H870.
The only problem I have with it: I can't disable forced encryption no matter what!
Theoretically that's fine, but I am really, really dependant on TWRP backups.
Here is a list of things I have already tried:
• Unlocked bootloader - Works fine
• Flashed TWRP 3.2.1 - Works fine
All of the following are supposed to disable forceencryption, but none of them works for me :crying::
• Flashed some various no-verity-opt-encrypt.zips - Don't work
• Did a full wipe and flashed westwood24's stock 8.0 rom - Doesn't work
• Flashed zefie's anti-root-removal tool - Doesn't work
• Flashed zefie's Melina Kernel - Doesn't work
I really don't know what else to try now and your help will be greatly appreciated!!!
You just have to format data. Not the usual "wipe", but the format option which you have to type "yes" to confirm.
Of course, you will need to make a backup on your external sd because everything on internal storage will get erased
blackhawk_LA said:
You just have to format data. Not the usual "wipe", but the format option which you have to type "yes" to confirm.
Of course, you will need to make a backup on your external sd because everything on internal storage will get erased
Click to expand...
Click to collapse
that i have done, but it turned out that i was using a wrong version of twrp. thank you though!
Closed, per user's request.

HELP! Recommendations for Samsung Galaxy Tab 10.1" SM-P580?

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.

Resources