Related
Don't forget to thank me and Radii it means a lot to us!
Click to expand...
Click to collapse
Upon discovering the reason people being given an error trying to flash OTAs in my TWRP recovery image I decided I would come up with a work around while I work out a way to fix it.
The following solution is group work between me and Radii.
If you came here just for OTA links then click HERE
Click below spoiler if you haven't installed TWRP on your device and you want to OTA update and then install TWRP.
First you need to download the version you would like, in theory you could backdate although this hasn't been tested and it may misbehave. For example the latest version as of 16/10/2015, build number cm-12.1-YOG4PAS38J.
On the spread sheet you will need two files, the fastboot and the signed. In the fastboot ZIP there is a file called recovery.img. Copy this to your android SDK platform tools folder. Now with the signed ZIP you either copy that to the same folder (platform-tools). Put your phone into fastboot mode and type.
Code:
fastboot -i 0x2b4c boot recovery.img
Or the name of the recovery if you renamed it.
Your phone will boot into Cyanogen OS Recovery. From there click Apply Update (Top option) and click ADB Sideload. Then type,
Code:
adb sideload cm-12.1-YOG4PAS38J-ham-signed.zip
Or whatever you renamed it to.
Reboot and you're done! Now you'll need to install TWRP to flash things like SuperSU and Xposed.
To install TWRP you need to download the latest TWRP image from HERE move that to platform-tools and type (with your phone in fastboot mode/bootloader mode of course)
Code:
fastboot -i 0x2b4c flash recovery "recovery.img"
Changing the name in the quotations to the name of the recovery and removing the quotes.
Click below spoiler if you have installed TWRP on your device and you want to OTA update and restore/preserve TWRP
Do the same as above, I have discovered it's impossible to preserve because Cyanogen will auto-write it's own recovery to the recovery parition.
Nerdy stuff
If you're wondering why you can't OTA without going through all this then it's because Cyanogen OS will do checks to see if the System has been r/w mounted. If so then it will stop all OTAs from installing. Simple when you think about it.
FAQ
Q: Why isn't TWRP still installed after installing the OTA? A: Because Cyanogen OS will write over the recovery partition with Cyanogen Recovery
Q: Will I lose all my data? A: Don't wipe and no, you can dirty flash to preserve data.
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
othe01 said:
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
Click to expand...
Click to collapse
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Breadcrust said:
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Why not? root is a normal option in CyanogenMod, why wouldn´t the "commercial" edition not support it? I see no reason they can´t add it to PrivacyGuard.
Here one of the forum admins said hes telling the team to add it -> http://community.cyngn.com/t/reques...-thethering-and-inbuilt-superuser-access/97/2
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
othe01 said:
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
Click to expand...
Click to collapse
I'll look into it at sunrise it currently 3:23AM here so can't do it now
P.s thanks for waking me :3
Sent from my Z1 using Tapatalk
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Titokhan said:
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Click to expand...
Click to collapse
sounded different here: [FLASHABLE ZIP] [CM12] Enable integrated superuser
But is prolly just a misunderstanding from my side.
How exactly does CyanogenOS check if System is modified and can´t we patch the check with an xposed module?
@othe01
He must used the signed zip to update. Regarding OTA faliure, I've discussed the issue here: http://forums.yuplaygod.com/index.php?threads/15124/
You need to registered in the forum to read, so I've uploaded a PDF of the same: https://drive.google.com/file/d/0B9zZIJPXbMsubkFBYmZ4eGtMQjQ/view?usp=sharing
I personally own OnePlus One & YU Yureka so already have a good experience with these things.
The whole procedure is clearly explained - no 'Xposed' module can bypass it. You can, in theory, deploy a file based OTA (I've already requested it through YU developers) instead of block based OTA or patch the update-binary to return always true (unmodified) value while checking the state of partitions.
:good:
@Titokhan I will post them later
Sent from my Z1 using Tapatalk
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
aaswar said:
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
Click to expand...
Click to collapse
Issue is noted method is in post
Sent from my Z1 using Tapatalk
@Breadcrust
cm-12.1-20150805-EXPERIMENTAL-YOG4PAP1CG-ham: http://forum.xda-developers.com/showpost.php?p=63390843&postcount=223
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
aaswar said:
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
Click to expand...
Click to collapse
re: above
if using cos recovery and sideload via abd or from file the full signed version , and your have root, it will work, root will be lost though.
fastboot zip has recovery signed doesn't. you need to flash recovery extracted from the fastboot zip and then flash the signed full zip using cos either using abd or sideload file onto system
I flash the rom, but when I insert CDMA SIM into slot one, there is no signal
and there is no option to choose band from the menu.
would you please instruct on how to get CMDA works?
@taitai
As you can see here, it is not an CDMA device.
As regards technical faults as well we're unable to help in most cases as ROMs are from Cyanogen and unedited.
Sent from my Z1 using Tapatalk
I have a chinese version of Z1 and it has CDMA capability
None of them do. They're the exactly the same under the hood.
Sent from my Z1 using Tapatalk
Welcome to this guide, where I will guide you through rooting, flashing custom roms, and more, on our little Umidigi One Max !
WARNING : I am not responsible for your phone breaking or exploding during the night under your pillow. Please advice. If you cannot boot anymore, keep reading, your phone is NOT dead.
OFFICIAL ROM (Android 8.1)
The Umidigi One Max comes with Android 8.1 Out of the Box. Manufacturer has no plan on having 9.0 on the phone. That's why we root then ! Let's get into it.
Rooting the phone without unlocking it, or installing TWRP
Everything you'll do on this phone will NOT require a bootloader unlock. Note that this method is only in case you don't want to have your data wiped, or don't have access to an SD card (thus you cannot flash .zip in TWRP, except for ADB Sideloads)
What you'll need
Download the latest ROM from Umidigi's website : https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
Choose the ".rar" file
"E" ROMs are for European versions. It doesn't really matter what you choose.
Download SP Flash Tool on the same thread you opened for the ROM. It's "SPFT" for short
Unzip both
Install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/releases/
Steps
IMAGE COURTESY OF bencebacsi @ Umidigi forums
In the unzipped ROM folder, find boot.img
Copy it to your phone storage using an USB cable or any other method
Open Magisk Manager, press install
Choose "patch boot image file"
{
"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"
}
Let magisk do it's job
Find the boot.img file you just copied
Copy the patched_boot.img back to your computer
Open SP Flash Tool
Open the "Download" tab
In "Scatter-loading file", press the folder icon and browse to the downloaded ROM folder. Choose the only file that shows up
Untick every box except for boot. There is a column called "Location" with a path, click on it to change to file.
Choose patched_boot.img
MAKE SURE YOU UNTICKED EVERYTHING EXCEPT BOOT
Click the "Download" button
Turn off your phone (not reboot) and connect is via USB
wait for the flash to succeed. Once done, unplug, boot, voila ! You got magisk !
Credits to topjohnwu for Magisk, what a great piece of work
Installing TWRP
Note that if you want to access the /data partition (internal storage), you'll have to wipe it ! If you do not need it, keep going, it won't wipe unless you want to.
What you'll need
Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html
Magisk.zip installer (NOT the manager) : https://github.com/topjohnwu/Magisk/releases/
SP Flash Tool : http://www.mediafire.com/file/wxlld9dfywk67jl/SP_Flash_Tool_v5.1916.rar/file
This method is shorter and requires less downloaded files.
Steps
Turn off your phone
Run SP Flash Tool
Load the scatter file (see pictures above) you downloaded from the latest ROM (see above as well)
Untick everything except recovery
Change path to recovery.img to be the TWRP image
Click "Download" and plug your phone
After it's done, unplug, and press Power + Vol Up
You'll see three options appearing. That's how you'll get to the recovery. Use Vol Up to scroll, and Vol Down to select. Choose Recovery Mode !
TWRP should boot by now
EXTRA STEP : Make /data readable. You will need to format data (YOU'LL LOSE ALL YOUR DATA) (Wipe > Format Data > Type "yes") and after that, flash this zip : https://androidfilehost.com/?fid=1322778262904004415
You can now proceed to flash zips, including Magisk.zip. If you made /data readable, you can send it to your internal storage. If not, use an SD CARD or ADB PUSH / SIDELOAD.
Returning to stock to fix issues / brick
Use SP Flash tool but instead of unticking everything, tick everything. Note that USERDATA, if ticked, will clear your data.
Ticking only certain partitions may work if you got issues with magisk or system mods and are still on Official ROM. Flashing boot and system will remove Magisk. If you are on custom ROM, you can flash their system again to fix issues as well. Make sure to choose the right system.img in SPFT !
OTHER ROMS
Installing GSI (Generic System Image) to get Android Pie 9.0
GSI takes advantage of Project Treble to create one system image that will work on most devices without issues due to a separate "vendor" partition. The One Max is Treble-compatible, but only up to 9.0 (No 10 Q for now)
This will allow you to get an AOSP experience, with it comes easy modding and theming, and less bugs, less chinese-spying (that's a thing apparently, but who cares really ? Not me to say the least)
GSI List
You can find a GSI List including bugs and download links in my other thread here : https://forum.xda-developers.com/android/development/gsi-gsi-experiments-t3941194
WARNING : DOWNLOAD GSIs WHICH ARE ARM64-AONLY AND NOT AB !
Installing a GSI
You will need TWRP Installed. Check above if it's not done yet. You'll also need the Magisk.zip, and I highly recommend you getting the disable-force-encryption zip
Start up by wiping /data in twrp (Wipe > Swipe the bar). It will not wipe the files in your internal storage (Music, Download, etc...). If you want to get access to /data in TWRP (which I highly recommend), you'll need to do a full format (Wipe > Format data > type yes).
Download a GSI (.img) and send it to your phone (Either using an SD Card, or adb push [file on computer] [destination folder]). Send Magisk and the disable-force-encryption zip at the same time.
Flash that system image using Install > Install Image > Browse to the .img file
Flash disable-force-encryption if you formatted /data (don't flash it if you didn't do that !)
Flash Magisk.zip
Reboot and profit !
Note that there might be some issues with the GSI you choose. Most GSI suffers issues regarding Wifi Tethering/Hotspot. Other than that, check for my thread for issues regarding GSIs.
Some GSI require installation of GAPPS (Google Apps). Download a GAPPS zip and flash it at : https://opengapps.org/ (Choose ARM64 and 9.0)
If Installation fails, saying that system size is too small, go to (Wipe > Advanced Format > Tick "System" > Repair or change file system > Resize File System) and try flashing again.
INTERESTING MODS FOR ALL ROMS
Magisk FDE.AI
A great system manager. Saves a ton of battery without a performance hit. You need magisk installed. XDA Thread : https://forum.xda-developers.com/apps/magisk/beta-feradroid-engine-v0-19-ultimate-t3284421
Fix SafetyNet not passing on custom ROMs/GSIs
SafetyNet will not pass by default on custom ROMs / GSIs.
Use Magisk Hide Prop Config : https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Run 'su' then 'props' in a terminal emulator. Edit Device fingerprint, choose Pick a certified fingerprint. I recommend using Xiaomi Redmi Note 7, as it changes the status-bar to be notch sized.
Note that you may need to do this next fix to make 'su' work :
Root request not working with Magisk
On some GSIs, root requests will not show up. You need to move some vendor files over to system.
Use TWRP's File Manager (Advanced > File Manager) or Adb shell to copy theses files :
Code:
/vendor/lib/libdirect-coredump.so
COPIED TO
Code:
/system/lib/libdirect-coredump.so
Code:
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
This will fix this issue until GSI / ROM creator fixes it in their ROM;
Enjoy your new phone ! Don't forget to say thanks to all the developers behind every project (not me ! I didn't do anything )
If you have any issues, feel free to ask questions !
See you on the other side
Downloaded phhusson's AOSP ROM
Extracted compressed image. Then...
Wiped Phone from TWRP w/ all three options Swipe, Formatted (Type "Yes"), and advanced wipe.
From TWRP went to:
Install > Install Image > Selected system-arm64-ab-gapp-su.img > Select Partition to flash image
From this screen it lists these partitions for selection:
-recovery
-nvram
-uboot
-boot
-logo
-tee
-System Image
I select System image. It starts flashing. After it has finished, I go to reboot, and that is when TWRP states "No OS installed".
Am I downloading the wrong image file?
*********************EDIT****************************
Nevermind. I downloaded system-arm64-aonly-gapps-su.img.xz and it boots fine with gapps included
Exactly, you downloaded A/B image, not A-only.
Using phhusson's AOSP ROM. I got the root requests show up. However the superuser app is blank. Nothing shows in the list.
Request for a video to install GSI
Hello
I'm using Umidigi One Max Android 8.1 and want to upgrade to 9.0 . Can you please make a YouTube video showing how to install the GSI version I'd gladly appreciate it.
Over the last month or so, I've tried multiple GSI ROMs, and stock. I've rooted stock, and everything runs nicely, I just can't stand the lack of features. Even rooted on stock, Google Pay still works. If I install a GSI ROM like Havok, root it, gpay will not work. Not sure why it works on stock rooted with magisk, but not with other ROMs.
I'm looking for a hacked stock rom for the one max that:
A.) Can be rooted.
B.) Can still run gpay.
C.) Has a advanced restart option to boot directly into recovery.
D.) Displays the battery in the status bar as a percentage rather a symbol, and a clock with seconds option.
If I had those options, I would stick with stock. I can accomplish all those options with Havoc GSI ROM, I just can't get NFC/gpay to work.
su
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
@ _cab13_
thanks for tutorial
some comments/questions
Image shows MT6739 in phone image and scatter file of mt6739
My phone is MT6363 and appears to agree with online specs site such as
https://www.gsmarena.com/_umidigi_one_max-9525.php
Am I looking at the wrong tutorial or umm have you grabbed images from another phone and forgot to say so?
w1lh3lm3d said:
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
Click to expand...
Click to collapse
You have to mount the folder system and vendor for reading and writing and you can copy it, this is in recovery mount
Very helpfull, thanks)
Has anyone tried dual SIM and SD hack on this phone? I cant get my to work. When I do the hack, phone does not see any sim cards nor SD card.
However if I put only two sims, or sim and SD everything works well.
It is almost like issue w Samsung but no warning message
can i use this process on umidigi one as well
q1. Can i use this process on umidigi one as well?
When i visit "Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html" and search on devices they don't have umidigi one or one pro only the one max option. Other than screen size all three are pretty much spec'd the same. The umidigi one just doesn't have wireless charging or nfc that one pro and one max have and one max has 6.3 waterdrop vs one/one pro 5.9 notch display but all 720x1520 9:19 aspect ratio configurations. I found a umidigi one and one pro twrp recovery image here _https://unofficialtwrp.com/umidigi-one-umidigi-one-pro-root-twrp-recovery/ so if i have that are all the other downloads for doing non-rooted device upgrade to 9 pie non-device specific downloads?
q2. Nice to see this process covers a way to get form 8.1 to 9 w/o rooting device. Having never done so i'm curious why other search hits cover steps that require rooting device if the upgrade can be achieved without doing that, any insights?
q3. Would you say the likelyhood of bricking my device, if trying to follow these instructions using umidigi one vs one max, very low? Trying to determine if i should first line up and have on hand backup phone to use if the chance of that happening is high.
does magisk install allow me to upgrade to android 9 pie?
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
myusrn said:
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
Click to expand...
Click to collapse
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
drkiro said:
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
Click to expand...
Click to collapse
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
myusrn said:
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
Click to expand...
Click to collapse
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
drkiro said:
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
Click to expand...
Click to collapse
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
myusrn said:
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
Click to expand...
Click to collapse
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
drkiro said:
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
myusrn said:
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
Click to expand...
Click to collapse
You can return, to the Originate flashing state, this image, https://community.umidigi.com/forum.php?mod=viewthread&tid=18692&extra=page=1 , can experiment with any image and return it to the original state, the pixel experience does not work with this phone, in Android Q the NFC does not work, and the videos in whastapp, do not work. Android 10 image comes without gapps, you have to flash them. If the twrp you can flash it through fastboot
[ROOT] Galaxy J810x Methods Magisk And Twrp
[ROOT Normaly]
1. Download Stock ROM 9.x or upgrade normaly
2. Start your ROM enter configuration, developer options and set Unlock by OEM
3. Download Odin 3.14 and drivers
4. Download Magisk and TWRP 3.3.0 and no-verity-opt-encrypt-6.1.zip
5. Install drivers for J7
6. Copy Magisk and no-verity-opt-encrypt-6.1.zip to SD Card
7. Enter in Stock Recovery and Factory reset
[Download MODE]
8. After this enter in download mode imediatly or your system encrypt
9. no start your stock rom or your system encrypt
10. Open Odin 3.14 flash Stock Bootloader and Modem Only If necessary
11. Flash TWRP with Odin or upgrade via img
12. Reboot imediatly in Recovery
13. Flash Magisk 20
14. Flash no-verity-opt-encrypt-6.1.zip
15. iNTALL your prefered Custom ROM
16. Install Magisk Manager 7.5
17. Press Thanks please
18. in this moment install Havoc or Lineage 17.1
[mAgisk mEthod]
You will need the stock Rom files from Sammobile for your phone model(BL, AP, CP, HOME CSC) and Odin on your PC.
1. Install Magisk manager on your phone.
2 Copy the AP file on your Download folder of your phone.
3 Open Magisk and tap Install Magisk then Select and patch a file. Go on Download folder and select the AP file to patch. After is done it will create a file in your Download folder named magisk_patched.tar. Copy this file back on your PC.
4 Run Odin and put your phone on Download mode. To get in Download mode shut your phone off, Hold pressed VOLUME UP + POWER, select Reboot to bootloader.
5 In Odin select BL, CP and Home_CSC from your stock ROM folder. In AP select the magisk_patched.tar file. Go on Optons and uncheck Auto Reboot. Hit START and let him finish. IMPORTANT, READ FIRST : After is done you have to restart the phone by pressing VOLUME DOWN + POWER and when the screen is black immediately press VOLUME UP + POWER. Dont let go until you are in Recovery mode, even if restarts.
5 select Wipe data/ factory reset and then Reboot system now. Might take a while to boot.
6 Set up your phone and install Magisk Manager again. It will ask you to complete the rooting will need to install few more files. Press OK.
WELL DONE. You have root now.
[RECOVERY][UNOFFICIAL]TWRP 3.3.1-0 Galaxy J8 J810M/F/FN/G/DS
https://forum.xda-developers.com/an...overy-twrp-3-3-1-0-galaxy-j8-j810m-f-t3962423
[Magisk 20.4] Primary option
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
[Manager 7.5.2]
https://www.apkmirror.com/apk/topjohnwu/magisk-manager/magisk-manager-7-5-2-1e2de1bb-release/
[no-verity-opt-encrypt-6.1.zip]
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
[Official]
Magisk Official Post
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[RMM State Fix] Miracle box
https://forum.xda-developers.com/ga...-rmm-fix-oreo-8-1-oem-unlock-fix-dez-t3877764
The Secret Of My Seccess is Jesus
Since you mentioned custom ROMs in the first guide, have you found any that are compatible with the J8? If so, could you link them?
Edit: Found a port of LineageOS 16 (Android 9.0) by the developer Bad Guy. However I couldn't get TWRP to flash it as it always resulted in error 7, despite modifying the file to remove the assert section. The no-verity-opt-encrypt-6.1.zip would not flash either due to error 1.
Someonerandom said:
Since you mentioned custom ROMs in the first guide, have you found any that are compatible with the J8? If so, could you link them?
Edit: Found a port of LineageOS 16 (Android 9.0) by the developer Bad Guy. However I couldn't get TWRP to flash it as it always resulted in error 7, despite modifying the file to remove the assert section. The no-verity-opt-encrypt-6.1.zip would not flash either due to error 1.
Click to expand...
Click to collapse
Hello my friend
technically j8 has a native treble and means that any treble ROM can be installed on the j8 with a custom kernel
If You have time test this ROM
https://forum.xda-developers.com/ga...om-crdroid-6-3-android-q-10-0-galaxy-t4048917
You need Kernel Android 10
Remember backup your files
Unlock oem and USB debugg
hacker812c said:
Hello my friend
technically j8 has a native treble and means that any treble ROM can be installed on the j8 with a custom kernel
If You have time test this ROM
https://forum.xda-developers.com/ga...om-crdroid-6-3-android-q-10-0-galaxy-t4048917
You need Kernel Android 10
Remember backup your files
Unlock oem and USB debugg
Click to expand...
Click to collapse
I have taken a look at your ROM, however I don't think it would work.
The ROM is ARM64, and the Galaxy J8 is an ARM device with a 64-bit binder. This means that the ROM needs to have that architecture to work.
It also requires Spaget X which is built for Exynos, and the J8 is a Snapdragon device.
And on another note, do you happen to know the fix for error 1 on the disable forced encryption zip?
Someonerandom said:
I have taken a look at your ROM, however I don't think it would work.
The ROM is ARM64, and the Galaxy J8 is an ARM device with a 64-bit binder. This means that the ROM needs to have that architecture to work.
It also requires Spaget X which is built for Exynos, and the J8 is a Snapdragon device.
And on another note, do you happen to know the fix for error 1 on the disable forced encryption zip?
Click to expand...
Click to collapse
Yes
If j8 use custom kernel 10
You install any release treble
I have release arm and arm64
Can i do that with android 8?
J810F android 8 or 10 working ???
Install OneUI 2.0 or 3.1 without a PC
You only need zarchiver on your phone
1. Download your firmware from Samfw or Samfrew. (It doesn't need to be exact but it should be for your model)
2. Extract the AP section
3. Extract boot.img.lz4, system.img.lz4 and vendor.img.lz4
4. Extract boot.img, system.img and vendor.img
5. Boot into TWRP and backup
6. Wipe data, system & vendor
7. Install boot.img, system.img and vendor.img
8. Install dmverity and reboot to recovery
9. Reboot to system
To make your new ROM run silky smooth you can
1. Install a custom kernel.
If you installed a 2.0 ROM you need a Q kernel.
If you installed a 3.1 ROM you need an R kernel.
2. Install my debloater or my wizzROM-creator
wizzROM Creator
wizzROM Creator module v4 Thermal for all Samsung a-series phones OneUI 2.0 will become QwizzROM OneUI 3.1 will become RwizzROM OneUI 4.0 will become SwizzROM Debloated ROM with Extras Fixed apps in system/product Extras: Battery charge limit...
forum.xda-developers.com
I am not responsible for a bricked phone or an alien invasion.
@physwizz
I'm using Q boot loader and I have successfully used this method to install R and P firmware.
The only issue with P is that it doesn't see my 256gb sd card
I'am searching for my A205FDDS9BTI1 and cannot find android 11 (R). Do you have any other recommendations website sir? @physwizz
Astreinz said:
I'am searching for my A205FDDS9BTI1 and cannot find android 11 (R). Do you have any other recommendations website sir? @physwizz
Click to expand...
Click to collapse
Samfw or samfrew
physwizz said:
Samfw or samfrew
Click to expand...
Click to collapse
Is twrp 3.3/3.4/3.5 working in android 11?
Astreinz said:
Is twrp 3.3/3.4/3.5 working in android 11?
Click to expand...
Click to collapse
Use 3.5
So, I want to install Lineage OS instead of Android 10 Go Edition on my Doogee X95, but I can't find any TWRP build for the Doogee X95, so the thing is: How can i do to install Lineage OS on Doogee X95 ? Can anyone help me please ?
The Dogee X95 is a low-end phone, hence Android 10 GO got pre-installed what IMO is absolutely correct.
Of course you can try to flash LOS via ADB Sideload method.
Read
Generic system images | Android Open Source Project
source.android.com
Use this GSI arm64 A-only
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Unlock bootloader first
Ok i'll check that right now
Ok so i checked for ADB Sideload, but it seems like i need TWRP, and there is no TWRP build for the Doogee X95, so i think i'll try to use the Lineage OS GSI image, and i'll see how can i install it
LR7875, there is a problem with the GSI you told me to use, it's an ARM64; and when i install Droid Hardware Info, it say that i'm using an ARMv7 (armeabi-v7a, armeabi) CPU, same for Treble Check that's saying that i use a 32-bit ARM CPU, but if i check on google the Doogee X95 it says that, it is, indeed, a 64-bit ARM CPU, but the thing is why is it saying that i use a 32bit ARM if it is a 64bit ARM ? Is it safe to use the ARM64 A-Only GSI ?
DidierSardine said:
Ok so i checked for ADB Sideload, but it seems like i need TWRP, and there is no TWRP build for the Doogee X95, so i think i'll try to use the Lineage OS GSI image, and i'll see how can i install it
Click to expand...
Click to collapse
ADB Sideload is a mode bootloader boots into to allow to flash ROMs located on computer: has really nothing to do with TWRP.
Code:
adb devices
adb reboot sideload
adb sideload <ROM-ZIP>
ARMV7 CPU is 32-bit CPU. Hence you can only flash ROMs what are compiled for ARMV7 CPUs.
Ok i'll try to flash the A-only ARM 32bit rom of Lineage OS using sideload, i hope it will works
Hum i just remembered the Lineage OS is a .xz Archive containing the .img, what should i do ?
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img (extracted .img file)
or
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img.xz (archive)
Sorry, you need to flash arm (32) GSIs, not 64
DidierSardine said:
Hum i just remembered the Lineage OS is a .xz Archive containing the .img, what should i do ?
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img (extracted .img file)
or
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img.xz (archive)
Click to expand...
Click to collapse
Flash the extracted .IMG file.
jwoegerbauer said:
ADB Sideload is a mode bootloader boots into to allow to flash ROMs located on computer: has really nothing to do with TWRP.
Code:
adb devices
adb reboot sideload
adb sideload <ROM-ZIP>
Click to expand...
Click to collapse
As far as I have concerned it is impossible to ADB sideload a custom ROM via stock recovery.
Also a GSI is a system image, which is impossible to ADB sideload because you cannot dump it into a zip. For ADB sideloadable zips the zip always contains a META-INF file which vertified the ROM.
Hence it is only flashable in fastboot.
The original poster also needs a vbmeta.img from stock rom and flash it in fastboot with a special command, to disable boot vertification (even if bootloader unlocked you still need to disable vertification)
Because you quoted me: WTF? Has nothing whatsoever to do with what I said.
jwoegerbauer said:
Because you quoted me: WTF? Has nothing whatsoever to do with what I said.
Click to expand...
Click to collapse
I mean how can he ADB sideload without twrp
@DidierSardine
If your phone is Project Treble enabled ( should be - but verify this ) then take note that TWRP isn't needed at all to flash a GSI ROM.
How-to in detail is described here:
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
Ok, so, i don't flash it using adb sideload, but using fastboot (as described in the link you sent), but the thing is, in the Flash GSI without TWRP section, there is that line:
fastboot -u flash system name_of_system.img
but the thing is: I have to put in the Lineage OS GSI .img file (lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img) or the system.img file, because i don't have the system.img file of Lineage OS, and i don't know how can i get it. So i have to put "lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img" instead of "name_of_system.img"
like this:
fastboot -u flash system lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img
?
Yes, if it's a 32-bit image
Ok thanks, i'll try this right now
I've a problem, when i do
fastboot erase system
i get this error: FAILED (remote: 'not allowed in locked state')
but the thing is: my bootloader is unlocked, so why is it happening ?