** UPDATE 2016-09-28 ** Android 6.01 enables support for HW_Crypto in Snapdragon 800+ phones, which requires recompiled TWRP.
-----------------------------------------------------------
Hi, can anybody clarify whether TWRP is meant to be able to decrypt CM13 (Android 6.0.1) EXT4 partitions ?
According to TWRP 3.0.2.0 it should support encryption but this version was released a while ago.
When I enter my encryption pin in TWRP it gives a "password failed" error.
I finally got CM13 encryption all setup and now I find I cant do an upgrade because CM updater reboots to recovery which then cant decrypt to write the updates.
So if it DOESN'T support encryption, how the heck do people upgrade their encrypted CM installs ? Is there a better recovery than TWRP ?
Digian said:
Hi, can anybody clarify whether TWRP is meant to be able to decrypt CM13 (Android 6.0.1) EXT4 partitions ?
According to TWRP 3.0.2.0 it should support encryption but this version was released a while ago. I never tried it with an old Android 5 rom.
When I enter my encryption pin in TWRP it gives a "password failed" error.
I finally got CM13 encryption all setup and now I find I cant do an upgrade because CM updater reboots to recovery which then cant decrypt to write the updates.
So if it DOESN'T support encryption, how the heck do people upgrade their encrypted CM installs ? Is there a better recovery than TWRP ?
Click to expand...
Click to collapse
What phone are you using?
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
What phone are you using?
Click to expand...
Click to collapse
Galaxy s4 LTE-A (i9506) aka "ks01lte".
Ok so it turns out Snapdragon 800 phones have hardware encryption module which is not compiled in TWRP.
You can see my thread here for more info, if anyone can help re-compile TWRP for i9506 to add the required dependency for HW_CRYPTO, i will tip some $$
# HW CRYPTO - TWRP needs to be compiled with these flags (there may be other tweaks required, im not sure)
TARGET_HW_DISK_ENCRYPTION := true
TARGET_KEYMASTER_WAIT_FOR_QSEE := true
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
Note this problem affects many phones, snapdragon 800, 801, 808 and probably other CPUs with HW crypto.
Nexus 5 | MSM8974 Snapdragon 800 | hardware keystore
LG G4 & LG G4 H815 | MSM8992 Snapdragon 808 | can't find quickly
Sony Xperia Z3 Compact | MSM8974AC Snapdragon 801 | hardware keystore
Sony Z1 Compact | MSM8974 Snapdragon 800 | hardware keystore
Sony Xperia Z3 | MSM8974AC Snapdragon 801 | hardware keystore
1+1 | MSM8974AC Snapdragon 801 | hardware keystore
Galaxy s4 i9506 (msm8974) | Snapdragon 800 | hardware keystore
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
ABOUT
ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
Flashing GApps in recovery for vanilla build doesn't work, either use WeebGapps Magisk module or Lite Gapps
Hotspot
Be sure to include a log : check how to
FLASHING STEPS
•Make sure you are on 12.0.1.0 and above firmware to flash ROM.
•Reboot Recovery (Use the recovery on download section to flash ROM)
•Flash Rom
•Format data
•Reboot System
•Once you see Bootanimation, Hold the power button to force reboot (To avoid bootloop on first boot)
DOWNLOADS
Download Vanilla Build
Download GApps Build
Download RECOVERY
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Redmi-MT6768
Telegram: Channel | Group
CONTRIBUTORS
Communos
Firas
Reserved
wow pro god sir
rsyforreal said:
wow pro god sir
Click to expand...
Click to collapse
wow pro god sir
im doing all the recomendation but after install rom ,format data and reboot the phone boot into fastboot mode.
Ragod45 said:
im doing all the recomendation but after install rom ,format data and reboot the phone boot into fastboot mode.
Click to expand...
Click to collapse
I did! it booted fine, is there a gapps to install for this version?
Hmm... all I see is a neverending blue and white arrow symbol.
Ragod45 said:
is there a gapps to install for this version?
Click to expand...
Click to collapse
With the OpenGapps test builds for Android 11, or the NikGapps, the installer always complained about not enough space on the system partition, even though it was already the smallest package (pico/core).
Only the FlameGapps basic package installed without errors on my device, but since it doesn't boot, I can't tell you if it actually works.
Here's the log from the OpenGapps pico package:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | RQ1A.210205.004
ROM Version increment | eng.ebincr.20210225.160609
ROM SDK version | 30
ROM/Recovery modversion | v11.0
Device Recovery | TWRP 3.4.2b-1213-c4a6db32
Device Name | merlin
Device Model | M2003J15SC
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 440
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /external_sd/Download/open_gapps-arm64-11.0-pico-20210130-TEST.zip
Installing GApps Version | 20210130
Installing GApps Type | pico
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | false
Total System Size (KB) | 1186384
Used System Space (KB) | 971236
Current Free Space (KB) | 198764
Additional Space Required (KB) | 25676 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 198764 | 198764
Remove | Existing GApps | + 0 | 198764
Remove | Obsolete Files | + 56 | 198820
Remove | extservicesstock | + 0 | 198820
Remove | extsharedstock | + 52 | 198872
Remove | packageinstallerstock | + 3284 | 202156
Remove | provision | + 0 | 202156
Install | Core | - 174976 | 27180
Install | calsync | - 2556 | 24624
Install | dialerframework | - 32 | 24592
Install | googletts | - 37896 | -13304
Install | packageinstallergoogle | - 3156 | -16460
| Buffer Space | - 9216 | -25676
------------------------------------------------------------------
Additional Space Required | 25676
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
MyBrainIsAStrainer said:
Hmm... all I see is a neverending blue and white arrow symbol.
With the OpenGapps test builds for Android 11, or the NikGapps, the installer always complained about not enough space on the system partition, even though it was already the smallest package (pico/core).
Only the FlameGapps basic package installed without errors on my device, but since it doesn't boot, I can't tell you if it actually works.
Here's the log from the OpenGapps pico package:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | RQ1A.210205.004
ROM Version increment | eng.ebincr.20210225.160609
ROM SDK version | 30
ROM/Recovery modversion | v11.0
Device Recovery | TWRP 3.4.2b-1213-c4a6db32
Device Name | merlin
Device Model | M2003J15SC
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 440
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /external_sd/Download/open_gapps-arm64-11.0-pico-20210130-TEST.zip
Installing GApps Version | 20210130
Installing GApps Type | pico
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | false
Total System Size (KB) | 1186384
Used System Space (KB) | 971236
Current Free Space (KB) | 198764
Additional Space Required (KB) | 25676 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 198764 | 198764
Remove | Existing GApps | + 0 | 198764
Remove | Obsolete Files | + 56 | 198820
Remove | extservicesstock | + 0 | 198820
Remove | extsharedstock | + 52 | 198872
Remove | packageinstallerstock | + 3284 | 202156
Remove | provision | + 0 | 202156
Install | Core | - 174976 | 27180
Install | calsync | - 2556 | 24624
Install | dialerframework | - 32 | 24592
Install | googletts | - 37896 | -13304
Install | packageinstallergoogle | - 3156 | -16460
| Buffer Space | - 9216 | -25676
------------------------------------------------------------------
Additional Space Required | 25676
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
Click to expand...
Click to collapse
Due to dynamic partition, the system gets resized after you flash system and reboot, leaving no space for gapps, so flash gapps before first boot, or you could use Magisk module gapps, here's the link:
https://drive.google.com/uc?id=1JBeuXQsHXy-T5hFcxmRQFBwh5yRRnKf1&export=download
Also note that first boot is a bootloop, you need to force reboot after waiting a minute or so
Please let me know if you still have issues, I'll fix them in next build.
Hi, i just tried again, installed rom, installed magisk and booted sucessfully without bootloops.
FLAME,OPEN and NIK GAPPS wont work at all!
after the system booted, i updated magisk and installed magisk module gapps. after reboot, i tried to open the google store but got stuck on logo from the app and thats it. so ill be waiting for next build to see if we got some bug fixes. thanks for the hard work !
Ragod45 said:
Hi, i just tried again, installed rom, installed magisk and booted sucessfully without bootloops.
FLAME,OPEN and NIK GAPPS wont work at all!
after the system booted, i updated magisk and installed magisk module gapps. after reboot, i tried to open the google store but got stuck on logo from the app and thats it. so ill be waiting for next build to see if we got some bug fixes. thanks for the hard work !
Click to expand...
Click to collapse
I see, thanks for reporting, I'll fix this in next build, stay updated
Communos said:
so flash gapps before first boot
Click to expand...
Click to collapse
That is what I did. I installed ArrowOS with OpenGapps as an additional ZIP. ArrowOS installs fine, then the installer for OpenGapps says there isn't enough room on the system partition and exits with error code 70.
Only the FlameGapps install without error, but then the system won't start (endless ArrowOS logo).
or you could use Magisk module gapps, here's the link:
https://drive.google.com/uc?id=1JBeuXQsHXy-T5hFcxmRQFBwh5yRRnKf1&export=download
Click to expand...
Click to collapse
That one sort of works, but there seem to be a few stability issues. I often get the message that the Google Play services had repeatedly crashed. Play Store works fine for me, although I had to restart the app once.
All in all, it seems usable, but I'm not sure it's reliable.
Please let me know if you still have issues, I'll fix them in next build.
Click to expand...
Click to collapse
So far, I encountered only minor issues. Like some developer settings that are present in other ROMs but seem to be missing here:
I can't find an option to enable adb root access. Running 'adb root' anyway prints the error: "adbd cannot run as root in production builds".
There's also no option to enable the extended restart (where you can select if you want to boot into recovery, bootloader, or normal system). I also can't take a screenshot from the restart menu. Stuff like that isn't critical, but helpful for people like me who can't remember all the different key combos.
One weird problem I encountered is with Here WeGo (a navigation app from the Play Store that I like because you can use it offline). At first, it works fine. But when you then tell it to use the SD card for those offline maps (and not the precious internal memory), the apps freezes every time it tries to start. You have to uninstall and reinstall it to make it lose its settings and work again. I guess I can use it with the internal storage for now, but it does cost me ~1.5 GB that I could find other uses for. Again, I'm not sure if this is your build's fault, but it worked on every other ROM and phone I've tried so far. In case it's important: I get no permission request for the SD card when I switch the storage in the app.
And while I'm at it: Any idea why the internal storage is only 8 GB total? I bought the device with 64 GB. I understand that there's bound to be some overhead for A/B stuff, recovery, and whatnot, but I've lost almost an order of magnitude here. It seems odd. EDIT: Ok, I have reinstall ArrowOS, but this time, I formatted the partitions first in TWRP. Now I have the full storage available. Man, there are so many little thing to keep track of.
Obviously, I haven't had the time yet to put the ROM through all its paces, but so far, I'm pretty impressed with it. I have not run into any game-breakers so far. You did a good job.
MyBrainIsAStrainer said:
That is what I did. I installed ArrowOS with OpenGapps as an additional ZIP. ArrowOS installs fine, then the installer for OpenGapps says there isn't enough room on the system partition and exits with error code 70.
Only the FlameGapps install without error, but then the system won't start (endless ArrowOS logo).
That one sort of works, but there seem to be a few stability issues. I often get the message that the Google Play services had repeatedly crashed. Play Store works fine for me, although I had to restart the app once.
All in all, it seems usable, but I'm not sure it's reliable.
So far, I encountered only minor issues. Like some developer settings that are present in other ROMs but seem to be missing here:
I can't find an option to enable adb root access. Running 'adb root' anyway prints the error: "adbd cannot run as root in production builds".
There's also no option to enable the extended restart (where you can select if you want to boot into recovery, bootloader, or normal system). I also can't take a screenshot from the restart menu. Stuff like that isn't critical, but helpful for people like me who can't remember all the different key combos.
One weird problem I encountered is with Here WeGo (a navigation app from the Play Store that I like because you can use it offline). At first, it works fine. But when you then tell it to use the SD card for those offline maps (and not the precious internal memory), the apps freezes every time it tries to start. You have to uninstall and reinstall it to make it lose its settings and work again. I guess I can use it with the internal storage for now, but it does cost me ~1.5 GB that I could find other uses for. Again, I'm not sure if this is your build's fault, but it worked on every other ROM and phone I've tried so far. In case it's important: I get no permission request for the SD card when I switch the storage in the app.
And while I'm at it: Any idea why the internal storage is only 8 GB total? I bought the device with 64 GB. I understand that there's bound to be some overhead for A/B stuff, recovery, and whatnot, but I've lost almost an order of magnitude here. It seems odd.
Obviously, I haven't had the time yet to put the ROM through all its paces, but so far, I'm pretty impressed with it. I have not run into any game-breakers so far. You did a good job.
Click to expand...
Click to collapse
The 8gb storage issue is peculiar, No one complained about any issue like this in the telegram group.
For the WeGo navigation app, can you please record logs while it starts and freezes? Would make it easier to briefly look over the issue.
I'll look over everything you reported, and try to fix them.
Logs would be highly appreciated.
Communos said:
The 8gb storage issue is peculiar, No one complained about any issue like this in the telegram group.
Click to expand...
Click to collapse
Looks like your reply overlapped with my edit. I think I fixed it by reinstalling ArrowOS. But this time, I used the "Format Data" option in TWRP's wipe menu beforehand. That gave me the full storage.
For the WeGo navigation app, can you please record logs while it starts and freezes? Would make it easier to briefly look over the issue.
Click to expand...
Click to collapse
Attached is the 'adb logcat' output from changing the storage to the third restart attempt (this time, it didn't freeze but crashed). I hope it's what you wanted. I'm new at this. If you need something else, let me know.
I just noticed that encrypting the phone does not work. If you select it, the device enters into a reboot loop (blank screen -> Redmi logo -> blank screen -> Redmi logo -> ...).
I don't think I can give you a log, because at that stage, adbd isn't running yet. If there's a way to get any helpful info on that, let me know.
On miatoll (Redmi Note 9 Pro, exactly) the mic does not turn on during phone calls.
Before clean-flashing this rom I installed the most recent firmware
( fw_joyeuse_miui_JOYEUSEEEAGlobal_V12.0.2.0.QJZEUXM_53af718a4c_10.0.zip )
Another ROM (Fluid 1.2) does not have the problem, nor the stock ROM, so I know the hardware is good . . .
Any advice would be appreciated!
This rom build is NOT for Miatoll, Redmi Note 9 with HelioG85 does not come under Miatoll category.
fbachofner said:
On miatoll (Redmi Note 9 Pro, exactly) the mic does not turn on during phone calls.
Before clean-flashing this rom I installed the most recent firmware
( fw_joyeuse_miui_JOYEUSEEEAGlobal_V12.0.2.0.QJZEUXM_53af718a4c_10.0.zip )
Another ROM (Fluid 1.2) does not have the problem, nor the stock ROM, so I know the hardware is good . . .
Any advice would be appreciated!
Click to expand...
Click to collapse
Please reach out to your device maintainer and report the bugs to him/her.
geht dieses rom auf das merlinnfc gerät oder nicht.
Raymen03 said:
geht dieses rom auf das merlinnfc gerät oder nicht.
Click to expand...
Click to collapse
it works on nfc
New FINAL ArrowOS Update is up!
Download: arrow_merlin-gapps.zip
Changelogs:
- This build is a followup build of previous ArrowOS build.
- GApps Included
- Fixed few minor bugs
MyBrainIsAStrainer said:
That is what I did. I installed ArrowOS with OpenGapps as an additional ZIP. ArrowOS installs fine, then the installer for OpenGapps says there isn't enough room on the system partition and exits with error code 70.
Only the FlameGapps install without error, but then the system won't start (endless ArrowOS logo).
That one sort of works, but there seem to be a few stability issues. I often get the message that the Google Play services had repeatedly crashed. Play Store works fine for me, although I had to restart the app once.
All in all, it seems usable, but I'm not sure it's reliable.
So far, I encountered only minor issues. Like some developer settings that are present in other ROMs but seem to be missing here:
I can't find an option to enable adb root access. Running 'adb root' anyway prints the error: "adbd cannot run as root in production builds".
There's also no option to enable the extended restart (where you can select if you want to boot into recovery, bootloader, or normal system). I also can't take a screenshot from the restart menu. Stuff like that isn't critical, but helpful for people like me who can't remember all the different key combos.
One weird problem I encountered is with Here WeGo (a navigation app from the Play Store that I like because you can use it offline). At first, it works fine. But when you then tell it to use the SD card for those offline maps (and not the precious internal memory), the apps freezes every time it tries to start. You have to uninstall and reinstall it to make it lose its settings and work again. I guess I can use it with the internal storage for now, but it does cost me ~1.5 GB that I could find other uses for. Again, I'm not sure if this is your build's fault, but it worked on every other ROM and phone I've tried so far. In case it's important: I get no permission request for the SD card when I switch the storage in the app.
And while I'm at it: Any idea why the internal storage is only 8 GB total? I bought the device with 64 GB. I understand that there's bound to be some overhead for A/B stuff, recovery, and whatnot, but I've lost almost an order of magnitude here. It seems odd. EDIT: Ok, I have reinstall ArrowOS, but this time, I formatted the partitions first in TWRP. Now I have the full storage available. Man, there are so many little thing to keep track of.
Obviously, I haven't had the time yet to put the ROM through all its paces, but so far, I'm pretty impressed with it. I have not run into any game-breakers so far. You did a good job.
Click to expand...
Click to collapse
I tried the WeGo app on new build, seems like a source issue, I guess I can't fix it
Hi, I am trying to flash a system image in TWRP.
When i try flashing the system.img to the System Image partiton i get this error:
Code:
Size of image is larger than target device
How can i solve this error? I tried the resize partition option on the system partition but seems that it doesn't help.
The phone is a Huawei P Smart (FIG-LX1).
you could shrink the file. give more information about partition layout and the file you are trying to flash.
Code:
259 4 2367488 mmcblk0p52
aIecxs said:
you could shrink the file. give more information about partition layout and the file you are trying to flash.
Code:
259 4 2367488 mmcblk0p52
Click to expand...
Click to collapse
How do I shrink it? And how do i give you more info about the partiton? The file is a system image of a custom rom for my phone.
found your device meanwhile. this is information you could provide from beginning. spreading information over multiple threads is bad attitude
https://forum.xda-developers.com/t/...ei-p-smart-2018-fig-lx1.4535331/post-87922363
how about link to rom you're trying to flash? how big is the file size?
useless double posts
https://forum.xda-developers.com/t/...e-cannot-flash-images-to-file-systems.4535981
https://forum.xda-developers.com/t/...led-remote-sparse-flash-write-failure.4536295
aIecxs said:
found your device meanwhile. this is information you could provide from beginning. spreading information over multiple threads is bad attitude
https://forum.xda-developers.com/t/...ei-p-smart-2018-fig-lx1.4535331/post-87922363
how about link to rom you're trying to flash? how big is the file size?
useless double posts
https://forum.xda-developers.com/t/...e-cannot-flash-images-to-file-systems.4535981
https://forum.xda-developers.com/t/...led-remote-sparse-flash-write-failure.4536295
Click to expand...
Click to collapse
The ROM name is Kangvip, the image size is 3,153,712,956 bytes (3GB). I have downloaded it from here: https://mega.nz/file/QHZAHBbA#V4MaeY5BXMCQo3wOXVcRNcr8qckKsGRanqEdAG-Z41M
(i have got this link from a youtube video, i dont know if i can post the link of it)
well that's too large 700 mb in compressed state is probably even larger when unsparsed with simg2img. you can repartition emmc storage but that is dangerous. I strongly recommend not to try, because in case you brick you might lose fastboot
download partitioning tools here (attachments)
https://forum.xda-developers.com/t/3712171
Tutorial
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
aIecxs said:
well that's too large 700 mb in compressed state is probably even larger when unsparsed with simg2img. you can repartition emmc storage but that is dangerous. I strongly recommend not to try, because in case you brick you might lose fastboot
download partitioning tools here (attachments)
https://forum.xda-developers.com/t/3712171
Tutorial
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
Click to expand...
Click to collapse
But is that tool to do the repartition?
the "tool" is a binary called parted
in case you make any typo the device becomes unrecoverable immediately
do you really think that unknown obviously incompatible ROM is worth it wasting your Huawei P Smart?
aIecxs said:
the "tool" is a binary called parted
in case you make any typo the device becomes unrecoverable immediately
Click to expand...
Click to collapse
But you told me to not do that
aIecxs said:
the "tool" is a binary called parted
in case you make any typo the device becomes unrecoverable immediately
do you really think that unknown obviously incompatible ROM is worth it wasting your Huawei P Smart?
Click to expand...
Click to collapse
Yes i understand, i will try another ROM and tell you the result
this device support GSI A-only arm64
https://github.com/phhusson/treble_experimentations/wiki/Huawei-P-Smart
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019. If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank: LineageOS is a free, community built...
forum.xda-developers.com
try this
https://sourceforge.net/projects/an...1-20210808-UNOFFICIAL-treble_arm64_avS.img.xz
Code:
{arm|a64|arm64}_{a|b}{v|g}{N|S}-{vndklite|secure|personal}
| | | | |
| | | | vndklite: For VNDKLite devices,
| | | | or for read-writeable /system on regular devices
| | | | secure: Superuser removed and system props spoofed,
| | | | for better chances of passing SafetyNet
| | | | personal: With personal mods, for reference
| | | |
| | | N: No Superuser
| | | S: *Built* with PHH Superuser (app needed)
| | | (Z): *Built* with eremitein's Dynamic Superuser (not offered here)
| | |
| | v: Vanilla, i.e. no GAPPS
| | g: With regular GAPPS
| | o: With Android Go GAPPS
| | (f): With built-in MicroG and FLOSS replacements of GAPPS (not offered here)
| |
| a: "A-only", i.e. system-as-system (deprecated since Android 12)
| b: "AB", i.e. system-as-root
|
arm: ARM 32-bit (deprecated since Android 12)
a64: ARM 32-bit with 64-bit binder
arm64: ARM 64-bit
aIecxs said:
this device support GSI A-only arm64
https://github.com/phhusson/treble_experimentations/wiki/Huawei-P-Smart
Click to expand...
Click to collapse
Is it a ROM?
Unofficial LineageOS 17 GSI released for Project Treble compatible devices
You can now get LineageOS 17, based on Android 10, on any Project Treble compatible device thanks to this unofficial LineageOS 17 GSI release.
www.xda-developers.com
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
aIecxs said:
Unofficial LineageOS 17 GSI released for Project Treble compatible devices
You can now get LineageOS 17, based on Android 10, on any Project Treble compatible device thanks to this unofficial LineageOS 17 GSI release.
www.xda-developers.com
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
Click to expand...
Click to collapse
Yes i understand, I will try to flash them and tell you what happens.
don't forget full TWRP backup to PC
DSU Sideloader for gaining temporary/permanent root, testing GSI's or installing GSI's Semi-permanently, pulling boot image, AND making your backups
Hello, I just wanted to post this as an answer to many questions regarding not being able to use DSU to install a GSI for testing or gaining root. The DSU install in developer options is NOT what we are using for installing GSI's temporarily for...
forum.xda-developers.com
Huawei Partition Kit - Enlarge system partition
Huawei Partition Kit This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls...
forum.xda-developers.com