Related
Hi,
Nice to be here after so much years of reading !
My LG G3s (d722) was fine with Cyanogenmod 13 and encryption enabled. I've made a Titanium backup for my apps (& cie...) on the SD card, and reboot in TWRP 3.0.2-0, enter my password to mount storage, and I've wiped all partitions exept the SD card.
Then I've flashed the CM14 zip file, and get these error in the process :
"could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4 mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Unkown error 200 unmount of /data failed; no such volume"
"Failed to mount '/data' (No such device)"
Since then :
- if I reboot into recovery, TWRP doesn't ask me the password to decryp the partition
- if I reboot in CyanogenMod ask me the password, but the tells me :
Decryption unsuccessful
The password you entered is correct but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.Then it reboot into TWRP
Any ideas ?
How could I mount ext4 partition in TWRP ? Or restore stock recovery ?
Thanks a lot for your advices
resolving !
Hi myself and everyone from another time,
I've resolved this mess by :
- installing LG drivers
- downloading kitkat stock-rom D72210d_00.kdz
- open LG Flash Tool 2014 and load D72210d_00.kdz, and start a CSE Flash
Then stard android 4, root it... etc
Best
Info from FASTBOOT;
Product Name: msm8996
Variant: MTP UFS
Bootloader version: -
Baseband version: -
Serial Number: <omitted from here>
Secure Boot: Enabled
Device State: unlocked
Hi,
I have ALWAYS had a lot of problems flashing both custom (Lineage 14.1) and official ROMs (Oxygen OS).
If I calculate the md5-checksum of lineage-14.1-20171102-nightly-oneplus3-signed.zip after its been downloaded I get this:
a42a838309e0b75f54a032d1e1722c74 which matches the official checksum here:
https://www.lineageoslog.com/14.1/oneplus3
The same goes for OnePlus3Oxygen_16_OTA_036_all_1710262329_97651662219b4e6b.zip downloaded from here:
oxygenos.oneplus.net.s3.amazonaws.com/OnePlus3Oxygen_16_OTA_036_all_1710262329_97651662219b4e6b.zip
which matches this checksum: 1cd78fd180ead7908b0c1127c7e385b3
But after I've transfered either Lineage or Oxygen to my phone I get different checksums each time I transfer them using "adb push".
This makes it really hard to update / install custom ROMs and I've tried two different USB-cables and different USB-ports on my computer.
The checksum should match even if I transfer the file to my phone, thats the whole idea of a (file)checksum = to validate file integrity.
My example:
Using TWRP 3.1.1-2
Using lineage-14.1-20171102-nightly-oneplus3-signed.zip
Host: Ubuntu 17.04 (Had 16.04 earlier, same problem, even tried with Windows, same problem)
Android Debug Bridge version 1.0.36
Revision 1:7.0.0+r33-2
* Reboot into recovery
* Allow for modifications for partition "system"
* Wipe (data, cache, dalvik; also tried wiping all partitions, no change)
* "adb push" to "/sdcard/"
* adb shell > cd /sdcard/ > md5sum lineage-14.1-20171102-nightly-oneplus3-signed.zip = 44851d667c8b13f18f054e6e4ce41ecb = NOT the correct checksum
* Tried installing lineage together with OpenGApps & AddOnSU and I always get different results. Normally it just stops at a "random" point in the process, this time it went all the way but it does notc continue installing the other zips. I can't however find any errors in the "/tmp/recovery.log", see paste here:
https://pastebin.com/JX13qUNc
Ok lets redo it:
Now its unable to mount system
https://pastebin.com/JtiEzZMc
Ok so the "system" partition is:
Code:
/system | /dev/block/sde20 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
which explains why it won't mount it...
* Wipe > Advanced Wipe > Selected all > Success except for OTG-USB
* Transfer the files using adb-push
* This time we get this checksum (on the phone): 10207fc1cbb1dc2c6b29c63dcff6d3c2
* Stalls around 20% with this error:
Code:
minzip: zlib inflate call failed (zerr=-3)
full log here:
https://pastebin.com/zgSXnq1d
So the times I've got it working has simply been a roll of the dice by doing multiple transfers and hoping one completes the installation.
Would really love some feedback and help, am I missing something really basic or is it actually behaving weird?
Best Regards and thanks for reading so long / TheSwede86
Update:
Tried the official android platform tools from Google here:
https://developer.android.com/studio/releases/platform-tools.html
Code:
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Behaves the same...
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
flash_all_except_storage.bat = flash_all_except_data_storage.bat
I have a few questions about this method of yours.
1) I downloaded the fastboot rom from this thread but I can't find the payload.bin mentioned in the first method. Did I download the right thing? All I can see are *.img files and system.img is there too. Can I flash that one?
2) I have both TWRP and magisk installed currently. Will I lose them if I follow your method? How should I go if I wanted to keep them?
3) Of course you advice us to make a backup beforehand. Can you tell me or link me a guide about how to backup and restore properly with the new A/B partion in the way?
I'm sorry for asking this much, but all the guides I'm following are either confusing or with conflicting info.
Thank you for the help, I just can't wrap my head around this dual partion thing :s
SirAugustin said:
I have a few questions about this method of yours.
1) I downloaded the fastboot rom from this thread but I can't find the payload.bin mentioned in the first method. Did I download the right thing? All I can see are *.img files and system.img is there too. Can I flash that one?
2) I have both TWRP and magisk installed currently. Will I lose them if I follow your method? How should I go if I wanted to keep them?
3) Of course you advice us to make a backup beforehand. Can you tell me or link me a guide about how to backup and restore properly with the new A/B partion in the way?
I'm sorry for asking this much, but all the guides I'm following are either confusing or with conflicting info.
Thank you for the help, I just can't wrap my head around this dual partion thing :s
Click to expand...
Click to collapse
1. Fastboot ROM can be used straight away (Option #2).
2. Well, the point of this guide is to restore phone to stock images, so you can install OTA update. TWRP can't be kept. You can flash Magisk without TWRP though.
3. Titanium backup pro is my #1 backup tool for years, except very few exceptions it can backup and restore all apps and their settings. Data partition is only one, so you might have luck using TWRP backup - I haven't tried it.
Thank you kindly for all the info. These days I will try the method you described. ?
_mysiak_ said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
Click to expand...
Click to collapse
I tried method 1, OTA installation still shows Error message
What next?
oseraphaels said:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
If you are running custom kernel, flash the stock boot.img to boot partition as well.
oseraphaels said:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Frank.G said:
If you are running custom kernel, flash the stock boot.img to boot partition as well.
Click to expand...
Click to collapse
I have stock boot img running, still ota install failed
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
_mysiak_ said:
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Click to expand...
Click to collapse
I fastboot flash_all.bat , I think this should mount all ROM segments, including system partitions
I fast boot flashed the latest ROM v11.0.15 and it works perfectly.
_mysiak_ said:
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Click to expand...
Click to collapse
I can't find any apps that may be mounting system partition.
Is there a way to find out?
oseraphaels said:
I can't find any apps that may be mounting system partition.
Is there a way to find out?
Click to expand...
Click to collapse
Yes, compare the last mount timestamp and Magisk log. You will see which app used root access at that time.
oseraphaels said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
sda12 is system_a, sda13 is system_b
Example of untouched system:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
Flash ota ROM in recovery
Rajendran Rasa said:
Flash ota ROM in recovery
Click to expand...
Click to collapse
Thank you very much
I fastboot flashed the latest ROM and my device works perfectly
Hi,
I have similar issue. My current version is V11.0.1.0.QFQEUXM. The system update show can't install update.
I get the stock version of V11.0.1.0.QFQEUXM fastboot room, and get the system.img. Then I flash it into my current active slot - b. After reboot, I still get can't install update.
The specific error is W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2020-05-15 10:30:34.000 UTC.
The remount is cause by TWRP.
Is there other suggestion?
Flash ota ROM in recovery
Click to expand...
Click to collapse
Tried to sideload V11.0.2.0.QFQEUXM OTA.zip, but error also.
Thanks.
JackVoo said:
Hi,
I have similar issue. My current version is V11.0.1.0.QFQEUXM. The system update show can't install update.
I get the stock version of V11.0.1.0.QFQEUXM fastboot room, and get the system.img. Then I flash it into my current active slot - b. After reboot, I still get can't install update.
The specific error is W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2020-05-15 10:30:34.000 UTC.
The remount is cause by TWRP.
Is there other suggestion?
Tried to sideload V11.0.2.0.QFQEUXM OTA.zip, but error also.
Thanks.
Click to expand...
Click to collapse
You've found the culprit already.. Do NOT use TWRP to flash images, it must be done via fastboot.
_mysiak_ said:
You've found the culprit already.. Do NOT use TWRP to flash images, it must be done via fastboot.
Click to expand...
Click to collapse
Hi, the remount is at 15-May. Which I try to fix this issue.
I use fastboot to flash the system.img, but it still mentioned about "remount R/W".
After that, I boot into stock recovery and sideload the OTA.zip, still fail
Thanks
JackVoo said:
Hi, the remount is at 15-May. Which I try to fix this issue.
I use fastboot to flash the system.img, but it still mentioned about "remount R/W".
After that, I boot into stock recovery and sideload the OTA.zip, still fail
Thanks
Click to expand...
Click to collapse
You probably forgot to flash something (or used incorrect image). Just download the latest fastboot image, switch to slot A and flash it all (except storage).
Try flashing with V11.0.1.0.QFQEUXM boot.img and system.img at slot A and B, still couldn't update.
Will try to flash all with the V11.0.2.0.QFQEUXM.
Update status:
I finally solve this issue.
I flash the new fastboot ROM into slot A, my current active is slot B.
Thanks for help.
help please
doing these steps will erase my data like factory reset?
if yes, then how can i install ota without losinig any data
_mysiak_ said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
Click to expand...
Click to collapse
Thanks for the post.
When i ran flash system.img is says partition unknown!
Hey folks! I unlocked my FireTV stick and was able to install TWRP following the amazing guide by @k4y0z (https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/).
I can boot into TWRP just OK.
I am using adb shell to issue TWRP commands. (I don't have an OTG cable with power input).
I began by flashing stock ROMs by @0815hoffi from here (https://forum.xda-developers.com/t/...-7-ota-zip-launcher-replacement-root.4155489/).
Then I tried installing pre-rooted images by @rbox (https://forum.xda-developers.com/t/fire-tv-stick-2-tank-prerooted-stock-images-5-2-7-3_r1.3912271/) along with magisk.
Here are the general steps I followed while flashing these images :
1. wiping everything. I suspect my first issue here :
Code:
$ adb shell
$ twrp wipe cache
$ twrp wipe data
$ twrp wipe dalvik
$ twrp wipe /system
~ # twrp wipe cache
Formatting Cache using make_ext4fs...
Failed to mount '/cache' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # twrp wipe /system
Formatting System using make_ext4fs...
Failed to mount '/system' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # mount /cache
mount: mounting /dev/block/mmcblk0p12 on /cache failed: No such device
Click to expand...
Click to collapse
~ # stat /dev/block/mmcblk0p12
File: '/dev/block/mmcblk0p12'
Size: 0 Blocks: 0 IO Block: 4096 block special file
Device: ch/12d Inode: 5332 Links: 1 Device type: b3,c
Access: (0600/brw-------) Uid: ( 0/ root) Gid: ( 0/ root)
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Access: 2010-01-01 00:17:58.000000000
Modify: 2010-01-01 00:17:57.000000000
Change: 2010-01-01 00:17:57.000000000
Click to expand...
Click to collapse
2. push images to /sdcard
Code:
$ adb push update-kindle-full_tank-288.6.6.4_user_664657620.bin /sdcard/firm.zip
update-kindle-full_tank-288.6.6.4_user... 6.1 MB/s (532252995 bytes in 83.009s)
3. Install image
adb shell
~ # twrp install /sdcard/firm.zip
Installing zip file '/sdcard/firm.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
[amonet] Remove boot patch...
[amonet] OK
Patching system image unconditionally...
Copying preloader_prod.img to boot partition 0 for secure device...
script succeeded: result was [][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
Click to expand...
Click to collapse
4. `adb shell reboot`
They all install just OK. But in all cases, every time I do `reboot` in `adb shell` after `adb install` commands, it boots and gets stuck on 'fireTV Stick' logo.
At first I thought maybe it takes time to boot for first time, but I let it go for as long as half an hour and still no good.
I tried wiping cache and dalvik before rebooting too, no avail (had same could not mount /cache prompt).
I am pretty sure I am doing something stupid, I'd really appreciate any help. I'll be happy if I get it back to a working state, I do not really need root. This all started because the stick went into bootloop outta nowhere. My initial finding pointed at a failed update, see :
https://twitter.com/i/web/status/1393963756426698756
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
0815hoffi said:
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks @0815hoffi , that's actually the very first image I tried with from your thread.
Looking back, I think there's something wrong with my partitions.
If I see logs of other people from these threads, it says
script succeeded: result was [ALL DONE][amonet] Install boot patch...
Click to expand...
Click to collapse
Whereas for me, it says
script succeeded: result was [][amonet] Install boot patch...
Click to expand...
Click to collapse
This may mean that my flash is not successful, right? It's same everytime I flash.
I wonder, is there a way to bring everything to a clean state?
Given your expertise in amonet, @k4y0z from the thread and this comment, do you have a suspicion of what could be going wrong?
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
saurabhshri said:
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
Click to expand...
Click to collapse
Usually when this corrupted partitions happen you may try the command:
fastboot format userdata
followed by :
adb shell
(to call twrp#)
Then :
twrp wipe data
twrp wipe system
twrp wipe cache
twrp wipe dalvik
Then adb push the rom, gapps/magisk to /sdcard
twrp install nameofyourrom.zip
twrp install gappsxx.zip
Let it boot once and go back and update magisk via recovery.
(adb reboot recovery once permissions set or use powermenu little vic apk for quickness)
Another method I found which works good with fireos is :
When faced with corrupted/encrypted partition issues and/or unable to mount/format data issues
goto advanced wipe
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Then push rom and any other zips etc to /sdcard and install in usual way.
Good you got it working
Regards
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
Bertonumber1 said:
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Click to expand...
Click to collapse
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
saurabhshri said:
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
Click to expand...
Click to collapse
Ah I see, I'm sure the twrp can be commanded to repair change file systems. However, you are correct it is much easier via otg mouse or keyboard.
Regards
I have tested 2 GSI's so far, phh's AOSP and AndyYan's LineageOS 19.1.
Everything works so far except:
MTP file transfer
Fingerprint reader
File encryption (GSIs don't boot if you dont disable encryption)
So, if you wanna install one, here's what I did:
Install Prove N's Unofficial TWRP and follow his guide. DONT INSTALL MAGISK, IT HAS THE IMEI PROBLEM AND ITS NOT TESTED WITH GSIs
Download your preferred GSI, I recommend lineage-19.1-20220320-UNOFFICIAL-arm64_bvS.img.xz, comes without GAPPS (Use bgS if you want em).
Extract it and rename the .img file to system.img
(Optional) Download this vendor.img, I made a treble overlay and added it to the image. The rom should be more stable and power management should be fixed with that. I still have to push the changes to github.
Download ChonDoe_Flasher.zip, it's a tool to flash dynamic partitions. It checks your storage for system.img and vendor.img.
Get a microSD card, and copy to the root of it the ChonDoe_Flasher.zip, system.img and vendor.img.
Boot to TWRP, and install the ChonDoe zip, wait till it finishes flashing.
Reboot to TWRP again, so it can mount the vendor partition again, go to the terminal and type multidisabler, so we remove encryption.
Format data, internal storage and reboot, you should be ready to go.
Settings in PHH Treble Settings
Go to Samsung features and check "Enable extended brightness range" and "Enable access to all cameras".
Go to Misc features and check "Use alternate way to detect headsets"
To get the display working at 90hzs go to "Force FPS" and check the option.
On camera check "Expose Aux cameras" and "Force Enable Camera2API HAL3" (In theory you should get better photos with that but I didn't go outside today lol)
For the lack of MTP file transfer, I'm using ADB instead of MTP with this tool for uploading and getting files from internal storage: Python ADB File Explorer. Suprisingly it's faster than MTP for some reason...
I know MTP can be fixed changing the kernel driver, I have compiled the kernel from @Prove N. , he had some USB fixes, but I don't know how to pack it for Samsung, It could be nice to have it for GSIs. If anyone wants to help me with these small issues it would be awesome.
Report bugs, workarounds and fixes here in this thread, let's try to make this phone usable!
I've recently bought this phone and installed LineageOS straight away. I used my alternative method without TWRP, by repacking super.img using my script, which I've modified to support SM-A325F. Too bad the fingerprint sensor does not work. Can anyone confirm it does not work regardless of on which Android version a GSI is based on?
I already have TWRP on my A32 and have Magisk. Followed the guide, unfortunately phone didn't boot up. Instead it reboots to recovery. The hereunder error appears while flashing.
Code:
PARTITIONS FLASHER
| Released at 2021, January 10
| Developed by ChonDoe
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/busybox-arm
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/e2fsck
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/installer.sh
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/resize2fs
ENVIRONMENT SETUP
| Unmount System
umount: can't unmount /system: Invalid argument
umount: can't unmount /system_root: Invalid argument
umount: can't unmount /system_ext: No such file or directory
umount: can't unmount /product: Invalid argument
umount: can't unmount /vendor: Invalid argument
| Detecting Partition Layout
| Dynamic partition detected
| System Block: /dev/block/dm-0
| Product Block: /dev/block/dm-2
| Vendor Block: /dev/block/dm-1
FLASHING SYSTEM IMAGE
Invalid sparse file format at header magic
Failed to read sparse file
703357+0 records in
703357+0 records out
2880950272 bytes (2.7GB) copied, 34.579540 seconds, 79.5MB/s
| System flashed as raw image
| Attempt to Resize Partition
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
/: 7386/7744 files (12.1% non-contiguous), 684040/692238 blocks
resize2fs 1.45.6 (20-Mar-2020)
Resizing the filesystem on /dev/block/dm-0 to 1217099 (4k) blocks.
The filesystem on /dev/block/dm-0 is now 1217099 (4k) blocks long.
| Done
FLASHING PRODUCT IMAGE
| Cant find product.img
FLASHING VENDOR IMAGE
| Vendor flashed as sparse image
| Attempt to Resize Partition
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Padding at end of inode bitmap is not set. Fix? yes
/dev/block/dm-1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/dm-1: 1140/41760 files (0.0% non-contiguous), 124955/166988 blocks
resize2fs 1.45.6 (20-Mar-2020)
Resizing the filesystem on /dev/block/dm-1 to 185664 (4k) blocks.
The filesystem on /dev/block/dm-1 is now 185664 (4k) blocks long.
| Done
I:TWFunc::Set_Brightness: Setting brightness control to 5
| Enjoy
I:Updater process ended with RC=0
I:Install took 59 second(s).
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p14 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p18 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p8 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p11 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p4 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p15 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0boot0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p5 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p7 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p13 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p10 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p12 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p9 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p6 for flashing: (null)
Updating partition details...
I:checking for twrp app
I:Data backup size is 0MB, free: 108145MB.
...done
I:Set page: 'flash_done'
I:TWFunc::Set_Brightness: Setting brightness control to 200
I:operation_end - status=0
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 200
I:Set overlay: ''
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
uluruman said:
I've recently bought this phone and installed LineageOS straight away. I used my alternative method without TWRP, by repacking super.img using my script, which I've modified to support SM-A325F. Too bad the fingerprint sensor does not work. Can anyone confirm it does not work regardless of on which Android version a GSI is based on?
Click to expand...
Click to collapse
upload firmware plz
jasurshoir said:
upload firmware plz
Click to expand...
Click to collapse
Ok, I'll try not to mess it all up this time...
Here is the link to download: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}. That is super.img I've created using my script, it is packed into a tar archive and zipped to reduce the size for file sharing. It is specifically for SM-A325F, based on the NPB (Nepal/Butan) version of the firmware and contains LiR v3.16. After unzipping it is ready to be flashed using Odin into the AP slot over the stock NPB firmware. That means, you have to download and flash it first, then flash the super.img. After each flashing go straight into the Recovery mode and do factory reset, only then boot the system.
But that's not all, additionally you have to extract and flash optics.img from your regional firmware. Here is how to do it. Changing optics.img to your regional one is not compulsory but with the Nepalese/Butanese one you'll only have a few major cellular providers working. You can do it at any time after flashing the system, it does not require factory reset.
I have chosen the NPB stock firmware as the basis because after analyzing contents of other regional firmware I've found that it is probably the most non-bloated and privacy-respecting of all (the worst were Russian and European).
uluruman said:
Ok, I'll try not to mess it all up this time...
Here is the link to download: .... That is super.img I've created using my script, it is packed into a tar archive and zipped to reduce the size for file sharing. It is specifically for SM-A325F, based on the NPB (Nepal/Butan) version of the firmware and contains LiR v3.16. After unzipping it is ready to be flashed using Odin into the AP slot over the stock NPB firmware. That means, you have to download and flash it first, then flash the super.img. After each flashing go straight into the Recovery mode and do factory reset, only then boot the system.
But that's not all, additionally you have to extract and flash optics.img from your regional firmware. Here is how to do it. Changing optics.img to your regional one is not compulsory but with the Nepalese/Butanese one you'll only have a few major cellular providers working. You can do it at any time after flashing the system, it does not require factory reset.
I have chosen the NPB stock firmware as the basis because after analyzing contents of other regional firmware I've found that it is probably the most non-bloated and privacy-respecting of all (the worst were Russian and European).
Click to expand...
Click to collapse
all good please create one ui firmware
jasurshoir said:
all good please create one ui firmware
Click to expand...
Click to collapse
Do you really need it? First, OneUI is not to be trusted as it's proprietary and not fully open-source, second, the only GSI version of it I can find (repacked by erfanoabdi) is very old (2019).
uluruman said:
Do you really need it? First, OneUI is not to be trusted as it's proprietary and not fully open-source, second, the only GSI version of it I can find (repacked by erfanoabdi) is very old (2019).
Click to expand...
Click to collapse
Yes, I really need this one, I saw on the Internet nippon gsi one oh 4.0 downloaded installed but did not start
add please play servise
my log after install nippon gsi one ui 4.0 keep reboot
jasurshoir said:
Yes, I really need this one, I saw on the Internet nippon gsi one oh 4.0 downloaded installed but did not start
add please play servise
Click to expand...
Click to collapse
Ok, here it is: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
It's the same Nippon GSI you mentioned, I've just repacked it into super.img. I don't know whether it's gonna work or not. Sometimes the system is just incompatible with the phone hardware or the kernel. All I can do is to repack it all, analyzing logs or tweaking the kernel is currently beyond my abilities.
Here is also the version of LiR with GApps (Google Play, etc.): {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
I've also updated my script, besides other improvements now it supports GZ-packed GSI images.
P.S.: I really don't recommend using any of the Google services. Don't let corporations gather your usage data. You bought the phone and from now on it should be all yours, with all of its data, like a PC in the good old days. You own your device, and nobody has the right to stick their nose into how you use your phone, gather any statistics and push you any ads. You always have a choice to turn down privacy-unfriendly stuff, the price of that "inconvenience" is actually ridiculous. From my point of view, there is simply no point in using non-stock systems if they are still littered with the privacy-unfriendly bloatware.
uluruman said:
Ok, here it is: ...
It's the same Nippon GSI you mentioned, I've just repacked it into super.img. I don't know whether it's gonna work or not. Sometimes the system is just incompatible with the phone hardware or the kernel. All I can do is to repack it all, analyzing logs or tweaking the kernel is currently beyond my abilities.
Here is also the version of LiR with GApps (Google Play, etc.): ...
I've also updated my script, besides other improvements now it supports GZ-packed GSI images.
P.S.: I really don't recommend using any of the Google services. Don't let corporations gather your usage data. You bought the phone and from now on it should be all yours, with all of its data, like a PC in the good old days. You own your device, and nobody has the right to stick their nose into how you use your phone, gather any statistics and push you any ads. You always have a choice to turn down privacy-unfriendly stuff, the price of that "inconvenience" is actually ridiculous. From my point of view, there is simply no point in using non-stock systems if they are still littered with the privacy-unfriendly bloatware.
Click to expand...
Click to collapse
thank you one ui not working play market worked youre new lineage firmware
does it also work with the PixelExpierence GSI?
Franzyy said:
does it also work with the PixelExpierence GSI?
Click to expand...
Click to collapse
Probably. Try it: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
uluruman said:
Probably. Try it: ...
Click to expand...
Click to collapse
I have a question. Is this file linked above different than the PixelExpirence GSI from GitHub? Because the file is about 1GB larger than the "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz" from https://github.com/ponces/treble_build_pe/releases?page=1
Franzyy said:
I have a question. Is this file linked above different than the PixelExpirence GSI from GitHub? Because the file is about 1GB larger than the "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz" from https://github.com/ponces/treble_build_pe/releases?page=1
Click to expand...
Click to collapse
It is different, although based on it. It is the full Super partition, while "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img" is only the System dynamic sub-partition within it. Besides System there are also Vendor, Product and ODM dynamic partitions included (taken directly from the NPB U2 stock firmware). Basically that's all the work my script is doing: repacking all the dynamic partitions inside super.img altogether, after which it contains another GSI but is still directly flashable with Odin.
There is an alternative way of installing a GSI, although it is far less straightforward. See this and this post. The latter deals with dynamic partitions, without which you cannot flash a GSI.
uluruman said:
It is different, although based on it. It is the full Super partition, while "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img" is only the System dynamic sub-partition within it. Besides System there are also Vendor, Product and ODM dynamic partitions included (taken directly from the NPB U2 stock firmware). Basically that's all the work my script is doing: repacking all the dynamic partitions inside super.img altogether, after which it contains another GSI but is still directly flashable with Odin.
Click to expand...
Click to collapse
Ok thx for explaining it
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Franzyy said:
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Click to expand...
Click to collapse
Open "Phh Treble Settings" from the settings, then "Misc features" and check "Use alternative way to detect headsets" in the Audio section.
Franzyy said:
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Click to expand...
Click to collapse
how it works PE? I saw it is still in beta, does it works with 2 sim? thank you