So I have decided to create a Thread to share with you- all the Custom ROM GSI that I have tried till now. First off, let's begin with Pixel Experience. It has managed to retain the same smooth UI and user experience. Furthermore, it actually comes with a Dark Mode and not that dark grey hue that our device has to offer. Apart from that, there are few other features as well. However, since we are already running an Android One device, you wouldn't find much difference. With that said, check out the screenshots to experience this ROM in detail
How to Flash GSI ROM on Moto One Action
There are two methods for that, the fastboot command method and the TWRP Recovery method. I will be discussing the latter because via the fastboot commands Bootloader wouldn't even allow formatting the system for some strange reasons SO here is what needs to be done (and yes I won't be responsible for your bricked devices, if that happens :silly
Notes:
Download the Pixel Experience GSI ROM. A huge thanks to turbolukex5 for this GSI ROM.
Do remember to always download an ARM64 CPU architecture ROM with AB partition for Moto One Action.
Transfer this ROM to SDCard. Although we won't be formatting Internal Storage, yet it is always advisable to keep it in external storage like SD Card or Pendrive.
Steps to Follow:
Boot to TWRP and go to Wipe > Dalvik, Data and System.
Head over to SD Card and tap on Install Image (the bottom right button on your recovery).
Now flash the GSI ROM.
Once it gets flashed (2-3mins at max), go to Reboot and tap Recovery. You will get a message that NO OS is installed. IGNORE it and proceed with the reboot. You should NOT reboot to the system otherwise bootloop is guaranteed from my end
Reason for bootloop: WIth A/B partition devices like ours, there is no separate recovery partition. It is handled by the boot partition itself (that is why we boot the recovery rather than actually flashing itself). Now we will have to refresh the boot [partiton and for that, you will have to reboot the TWRP recovery. If you don't do so, system won't be able to recognize the boot partition (personal experience: tried many times and ended up in bootloop each time ).
Once you reboot to recovery, again head over to Reboot > System. This time you won't notice the NO OS message. The first time the device might reboot once or twice, that is completely normal.
That's it. Enjoy the New Pixel Experience on your Moto One Action
Next Up: Flashing the HavocOS GSI ROM.
Thank for sharing. Which gsi do you recommend? I mean based on stability and battery life. Also what camera app are you using?
I was waiting for something like this to appear! I've had many problems flashing GSIs I kinda just gave up LOL.
How can you install it with fastboot? And what can be done for the statusbar to accomodate the camera cutout?
mymagicmyhero said:
Thank for sharing. Which gsi do you recommend? I mean based on stability and battery life. Also what camera app are you using?
Click to expand...
Click to collapse
On stability and battery life, Pixel is the go-to ROM. I am saying this from my previous experience of using custom ROMs. I have tried many custom ROMs and Pixel always took the first position in battery life and stability. The main reason for that could be attributed to the fact that it is a trimmed down ROM with just the basic functionalities.
As far as camera goes, I tried a bunch of GCams but unfortunately have to give up on all as none of them worked. There is a GCam channel on the Telegram for Action/Vision and there are a lot of discussions going on and Gcams being shared over there. Check it out.
nztcs said:
I was waiting for something like this to appear! I've had many problems flashing GSIs I kinda just gave up LOL.
How can you install it with fastboot? And what can be done for the statusbar to accomodate the camera cutout?
Click to expand...
Click to collapse
Here are the commands needed for that. But if a GSI have a separate GApps package, then I don't think you could flash it via fastboot commands. This is because GApps comes in .ZIP format and these types of files can't be flashed via fastboot (correct me if I'm wrong).
adb reboot bootloader // reboot to fastboot
fastboot flash vbmeta vbmeta.img //if the GSI ROM has a vbmeta file. Official Android builds provided by Google (Android 10,11) do come with this file.
fastboot erase system
fastboot flash system system.img //replace system.img with the name of the GSI ROM
fastboot -w //factory reset
fastboot reboot //reboot to system
Regarding the camera cutout, I don't use these GSI ROMs for more than a few hours. So haven't yet thought about it. If you want you could change the cutout style from Developer Options and see if it works.
binary**# said:
On stability and battery life, Pixel is the go-to ROM. I am saying this from my previous experience of using custom ROMs. I have tried many custom ROMs and Pixel always took the first position in battery life and stability. The main reason for that could be attributed to the fact that it is a trimmed down ROM with just the basic functionalities.
As far as camera goes, I tried a bunch of GCams but unfortunately have to give up on all as none of them worked. There is a GCam channel on the Telegram for Action/Vision and there are a lot of discussions going on and Gcams being shared over there. Check it out.
Click to expand...
Click to collapse
About the gCam I also tried several, but this one seems most stable and functional. And with good quality in my opinion (at least not worse from the Moto's stock one: GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk
Try it out. I've downloaded it from the group you mentioned.
Havoc os gsi rom
Well, the ROM is famous for providing tons of customizations and this GSI build doesn't disappoint either. You will be getting all the customizations functionality that is present in the custom ROM. However, there still exist some network issues which forbid making calls and sending messages. I have reached the halfway mark for finding the fix, and soon as I am able to find out the entire fix, I will update the guide. In the meantime check out the screenshots and the steps to install.
Notes:
Download both the ROM and Gapps. They both should be AB and ARM64. Thanks to turbolukex5 for the ROM and Gapps. GApps are near about 1GB whereas the ROM is around 500MB . But don't even think of skipping the Gapps, you will definitely get a bootloop (tried and tested).
STEPS:
Boot to TWRP and wipe Dalvik, Data, and System
Flash the GSI ROM in the system partition
Reboot to recovery
Flash Gapps in the system partition
Reboot to Recovery > System
Partial Calling Workaround:
After booting, first off turn off Aeroplane Mode and then type in *#*#4636#*#* --> Phone Information --> Enable the Mobile Radio Power. You will get the Network signal, unfortunately, this doesn't do much good. As soon as I get it working, will update this post
binary**# said:
Well, the ROM is famous for providing tons of customizations and this GSI build doesn't disappoint either. You will be getting all the customizations functionality that is present in the custom ROM. However, there still exist some network issues which forbid making calls and sending messages. I have reached the halfway mark for finding the fix, and soon as I am able to find out the entire fix, I will update the guide. In the meantime check out the screenshots and the steps to install.
Notes:
Download both the ROM and Gapps. They both should be AB and ARM64. Thanks to turbolukex5 for the ROM and Gapps. GApps are near about 1GB whereas the ROM is around 500MB . But don't even think of skipping the Gapps, you will definitely get a bootloop (tried and tested).
STEPS:
Boot to TWRP and wipe Dalvik, Data, and System
Reboot to recovery
Reboot to Recovery > System
Partial Calling Workaround:
After booting, first off turn off Aeroplane Mode and then type in *#*#4636#*#* --> Phone Information --> Enable the Mobile Radio Power. You will get the Network signal, unfortunately, this doesn't do much good. As soon as I get it working, will update this post
Click to expand...
Click to collapse
Any progress?
binary**# said:
Here are the commands needed for that. But if a GSI have a separate GApps package, then I don't think you could flash it via fastboot commands. This is because GApps comes in .ZIP format and these types of files can't be flashed via fastboot (correct me if I'm wrong).
adb reboot bootloader // reboot to fastboot
fastboot flash vbmeta vbmeta.img //if the GSI ROM has a vbmeta file. Official Android builds provided by Google (Android 10,11) do come with this file.
fastboot erase system
fastboot flash system system.img //replace system.img with the name of the GSI ROM
fastboot -w //factory reset
fastboot reboot //reboot to system
Regarding the camera cutout, I don't use these GSI ROMs for more than a few hours. So haven't yet thought about it. If you want you could change the cutout style from Developer Options and see if it works.
Click to expand...
Click to collapse
is there a possibility to add a custom screen cutout for the moto one action? since none of the cutout option fit our screen? or the move the position of the clock?
Thank you for your guide! I've installed Lineage 17 GSI on my phone this way & it is working perfectly (phone, NFC, camera, cellular internet)!
Update
mymagicmyhero: Someone suggested me a few adb root commands which might fix the calling issue on HavoCOS. I tried the same but unfortunately, it didn't do any good. The carrier's internet strangely works pretty well, its just the call that's creating issues. I even flashed the stock modem file onto Havoc, but still no luck. It's all messed up on professional front, so can't give in more time to it, but will still try to see if something works out.
Emmarelia: There's one magisk module that you could try out for the said process to work. Once you flash the GSI ROM, flash the phh's magisk file from TWRP (not the regular one, that isn't supported in GSI builds) . Then flash the None Display Cutout magisk module. And do share the results!
Hey binary, I just wanted to say thanks for the posts you've made in the one action forums, it really gave me a place to start from.
Just picked up a -4 variant a couple weeks ago in Canada on sale.
I've had many phones with varying degrees of custom ROM support and this phone is in a really weird place, open as all hell but nothing..
I used to build ROMs for i9100, d2can/d2att, mako, (ZTE) tulip, herolte, and m8ul. I havent looked into building for troika yet, with all the quarantine going on I have other priorities, but it's in my plans.
Have you tried building anything for troika yet?
I haven't found a ExtendedUI GSI that works but I've been running the Evo X GSI by Luke and all is well. Signal seems a bit weaker but it works fine.
Status bar is the right height out of the box.
I set the custom carrier in the rom to a few invisible characters, set it to the left side and made the carrier label size larger so it gives me a blank space where the camera is.
While it might not have true notch support in full screen apps, using the phone in portrait mode doing day to day tasks works like a charm.
I'm going to run this rom for a while but when I flash a new GSI I'll post the results here. If anybody has success with a particular ExUI GSI please let me know.
natetokes said:
I haven't found a ExtendedUI GSI that works but I've been running the Evo X GSI by Luke and all is well. Signal seems a bit weaker but it works fine.
Status bar is the right height out of the box.
I set the custom carrier in the rom to a few invisible characters, set it to the left side and made the carrier label size larger so it gives me a blank space where the camera is.
While it might not have true notch support in full screen apps, using the phone in portrait mode doing day to day tasks works like a charm.
I'm going to run this rom for a while but when I flash a new GSI I'll post the results here. If anybody has success with a particular ExUI GSI please let me know.
Click to expand...
Click to collapse
Could you please provide a link to the gsi?
mymagicmyhero said:
Could you please provide a link to the gsi?
Click to expand...
Click to collapse
https://sourceforge.net/projects/ex...-4.1.69-20200329-GSI-ARM64-AB.img.xz/download
i had some issues getting the bluetooth connected in my car but otherwise evox was a good gsi. might go back to it after im done testing the new android 10 update for -4
binary**# said:
So I have decided to create a Thread to share with you- all the Custom ROM GSI that I have tried till now. First off, let's begin with Pixel Experience. It has managed to retain the same smooth UI and user experience. Furthermore, it actually comes with a Dark Mode and not that dark grey hue that our device has to offer. Apart from that, there are few other features as well. However, since we are already running an Android One device, you wouldn't find much difference. With that said, check out the screenshots to experience this ROM in detail
How to Flash GSI ROM on Moto One Action
There are two methods for that, the fastboot command method and the TWRP Recovery method. I will be discussing the latter because via the fastboot commands Bootloader wouldn't even allow formatting the system for some strange reasons SO here is what needs to be done (and yes I won't be responsible for your bricked devices, if that happens :silly
Notes:
Download the Pixel Experience GSI ROM. A huge thanks to turbolukex5 for this GSI ROM.
Do remember to always download an ARM64 CPU architecture ROM with AB partition for Moto One Action.
Transfer this ROM to SDCard. Although we won't be formatting Internal Storage, yet it is always advisable to keep it in external storage like SD Card or Pendrive.
Steps to Follow:
Boot to TWRP and go to Wipe > Dalvik, Data and System.
Head over to SD Card and tap on Install Image (the bottom right button on your recovery).
Now flash the GSI ROM.
Once it gets flashed (2-3mins at max), go to Reboot and tap Recovery. You will get a message that NO OS is installed. IGNORE it and proceed with the reboot. You should NOT reboot to the system otherwise bootloop is guaranteed from my end
Reason for bootloop: WIth A/B partition devices like ours, there is no separate recovery partition. It is handled by the boot partition itself (that is why we boot the recovery rather than actually flashing itself). Now we will have to refresh the boot [partiton and for that, you will have to reboot the TWRP recovery. If you don't do so, system won't be able to recognize the boot partition (personal experience: tried many times and ended up in bootloop each time ).
Once you reboot to recovery, again head over to Reboot > System. This time you won't notice the NO OS message. The first time the device might reboot once or twice, that is completely normal.
That's it. Enjoy the New Pixel Experience on your Moto One Action
Next Up: Flashing the HavocOS GSI ROM.
Click to expand...
Click to collapse
I boot to recovery first but still show me no system installed no matter what I do..
areq1987 said:
I boot to recovery first but still show me no system installed no matter what I do..
Click to expand...
Click to collapse
Don't quote the whole op.
No problems here.
Wipe, flash GSI image as system, reboot to recovery, reboot to system.
Which GSI ROM are you trying to run?
natetokes said:
Don't quote the whole op.
No problems here.
Wipe, flash GSI image as system, reboot to recovery, reboot to system.
Which GSI ROM are you trying to run?
Click to expand...
Click to collapse
From the topic- Pixel experience. Shows no os installed even when i first boot to recovery after install.
Wysłane z mojego motorola one action przy użyciu Tapatalka
areq1987 said:
From the topic- Pixel experience. Shows no os installed even when i first boot to recovery after install.
Wysłane z mojego motorola one action przy użyciu Tapatalka
Click to expand...
Click to collapse
Are you booting to recovery after a shutdown or pressing reboot to recovery in TWRP?
natetokes said:
Are you booting to recovery after a shutdown or pressing reboot to recovery in TWRP?
Click to expand...
Click to collapse
Pressing reboot to recovery in twrp kole manual says.
Wysłane z mojego motorola one action przy użyciu Tapatalka
Related
I've tried flashing the phone to TWRP, and it sticks...
but when I flash LineageOS 16, it says no space... so I erase the system partition...
flash again and add Opengapps for pie 64bit version...
and it just boots to a lineage recovery page...
I haven't tried other roms, because I just basically want lineageOS, minimal gapps, and google camera basically
I have tried 3 times already, but this A and B partitions got me all worked up... do I have to flash A then do it all again for B partition?
I've had the phone for a week now, I'm staying on Stock Pie at the moment, because I turned off a bunch of stuff and battery drain in quite minimal at least... and I'm quite happy actually...
but I wanna test around roms to see what the community has created for this device.
SaberJ2X said:
I've tried flashing the phone to TWRP, and it sticks...
but when I flash LineageOS 16, it says no space... so I erase the system partition...
flash again and add Opengapps for pie 64bit version...
and it just boots to a lineage recovery page...
I haven't tried other roms, because I just basically want lineageOS, minimal gapps, and google camera basically
I have tried 3 times already, but this A and B partitions got me all worked up... do I have to flash A then do it all again for B partition?
I've had the phone for a week now, I'm staying on Stock Pie at the moment, because I turned off a bunch of stuff and battery drain in quite minimal at least... and I'm quite happy actually...
but I wanna test around roms to see what the community has created for this device.
Click to expand...
Click to collapse
If still in a quandary here goes ...
Flash per instructions for ROM you're going to use (see ROM OP instructions).
Here is a very basic rundown as compiled from various instructions from ROM's within XDA
1. Make sure you are on the correct vendor for the ROM you want
2. Download the ROM and Gapps
3. Pay attention to what slot stock bootloader is in (A or B) within bootloader window
4. Boot into TWRP Recovery
Remember that TWRP flashes to both slots, the Rom flashes to opposite slot you're in. Try to flash ROM and Gapps
onto same slot original bootloader appears as (in Reboot Menu)
5. Wipe as instructed within ROM instructions -- (clean/dirty?)
6. Flash the ROM (noting slot)
7. Flash TWRP Install Script (Don't forget, this is important to do!)
8. Reboot Recovery (note slot)
Gapps will flash to current boot slot so check and confirm that you are in the slot you want. If not, switch to it and
reboot the recovery again (you can check in Reboot Menu)
9. Flash Gapps
10. Reboot and Setup Device
If rooting, Magisk can be installed after first boot
If needed, with adb you can run this command to swap to A or B "fastboot --set-active=a (or b)"
Hope this helps, remember ... Flash per instructions for ROM you're going to use (see ROM OP instructions).
This TWRP recovery is compiled from source & not official yet
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Are there any decent ROMs yet for this phone? LineageOS would be fantastic.
@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.
I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692
_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse
kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse
kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.
kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?
dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".
I got my phone yesterday, and I can't flash custom roms. My phone gets stuck on the boot screen (the animation is working as expected) for over thirty minutes, then I give up. I am/was rooted on the latest stock image. In the Download folder, I put the ROM (I have tried with crDroid and Bliss), twrp.zip, nano gapps, and Magisk. I flash the ROM and TWRP and reboot into recovery. Whenever I do this, I no longer have a Downloads folder or files. So, not knowing what to do, I sideload gapps and Magisk and reboot system. Then, I inevitably get stuck on the boot screen animation. What am I doing wrong?
Hello have you try to format data before or after flash custom rom? Some rom don’t work if not do.
Are you familiar with A/B slot partitions and their related behaviors? It's markedly different from single slot systems.
c3drik 67 said:
Hello have you try to format data before or after flash custom rom? Some rom don’t work if not do.
Click to expand...
Click to collapse
I tried this. Unfortunately, no luck.
Dungeon47 said:
Are you familiar with A/B slot partitions and their related behaviors? It's markedly different from single slot systems.
Click to expand...
Click to collapse
I am not familiar with A/B slot partitions. I followed a guide step-by-step, so I wasn't too concerned about my ignorance. Should I be doing something special? Thanks.
Kama45 said:
I tried this. Unfortunately, no luck.
I am not familiar with A/B slot partitions. I followed a guide step-by-step, so I wasn't too concerned about my ignorance. Should I be doing something special? Thanks.
Click to expand...
Click to collapse
Yes. A lot. Get very familiar with how A/B slots work. It changes many things about the whole flashing process. Trying to do things the same way as before leads to exactly what you're experiencing.
Kama45 said:
I got my phone yesterday, and I can't flash custom roms. My phone gets stuck on the boot screen (the animation is working as expected) for over thirty minutes, then I give up. I am/was rooted on the latest stock image. In the Download folder, I put the ROM (I have tried with crDroid and Bliss), twrp.zip, nano gapps, and Magisk. I flash the ROM and TWRP and reboot into recovery. Whenever I do this, I no longer have a Downloads folder or files. So, not knowing what to do, I sideload gapps and Magisk and reboot system. Then, I inevitably get stuck on the boot screen animation. What am I doing wrong?
Click to expand...
Click to collapse
Same thing happened to me, I had to forced the phone off (Volume + and Power) without plug-in the USB after is off I went into EDL mode (Volume +- together and Power) then immediately plug in to your ready PC with msm already ready to go.
You might have to try it a few times...
That's what I did a while back.
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
format data when switching to different roms
JohnnyMwanza said:
format data when switching to different roms
Click to expand...
Click to collapse
Now if i format my data, will i be able to boot back to my current rom, evo x? (Sorry, but im a noob)
Backup your data and then oxygen os via fastboot....this worked for me.
MAX TEN said:
Backup your data and then oxygen os via fastboot....this worked for me.
Click to expand...
Click to collapse
You mean, boot to "twrp.img" and then flash oos?
Anmol45 said:
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
Click to expand...
Click to collapse
That's actually your internal storage still encrypted, this is a common issue, my recommendation is to try to boot normally after flashing the zips with adb sideload, if your internal storage is still intact then there you go, otherwise reboot to twrp and format internal storage.
Anmol45 said:
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
Click to expand...
Click to collapse
Always remove your phone password when changing rom...and always keep backup on your pc or hard drive or somewhere else...and avoid going from one security patch to another... especially when going from new security update to an old one...but mainly remove your password...imo that should help avoiding the data encryption and file corruption
So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.
I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.
To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.
cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking
DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.