*Download all necessary files*
Magisk v15.0 or newest available
Download ElementalX kernel @ elementalx.org
Download latest Magisk Manager from official xda thread
Download TWRP for Moto G4 (Athene)
from twrp.me
Unlock bootloader (Go to Motorola's official site)
Check Unknown Sources in Android settings under security tab.
Download and install ADB & Fastboot on your PC
Boot into fastboot by holding down vol down and power.
Once you see Android robot with text at the bottom, on your computer in cmd type "fastboot boot TWRP image path" ex: fastboot boot D:/TWRPimages/twrp.athene.img
Once phone boots to TWRP, TWRP will ask to make modifications to system. Keep read only. (Note: if is asks to install, always say no.) Next go to backup, and make backup. (Just backup what is selected by default: system, data, and most importantly, boot.img) Note: make sure to tell it to backup to SD, and make sure the SD card is formatted as portable, not adoptable. Note: you might need mount the card under Mount tab first before being able to select it.
Next, go to mount, and uncheck "keep system read only", and swipe to allow modifications. Go to install, and flash ElementalX, and set it up in the following screen. As we already have the turbopower charger, you don't need to enable USB fast charging.
Wipe dalvik cache, and flash Magisk. Then, wipe dalvik again, and power off.
Boot into Android to make sure everything works. Install Magisk app if it didn't appear in your apps drawer from the .apk you downloaded earlier.
Hope this helps! Good luck!
Note: If you would like to flash TWRP instead, use "fastboot flash recovery TWRP.img" instead of fastboot boot.
Thank you for this tutorial! Is it required to install the ElementalX kernel?
Romano2K said:
Thank you for this tutorial! Is it required to install the ElementalX kernel?
Click to expand...
Click to collapse
It appears to be. I tried it without ElementalX first and got to the point of installing Magisk then rebooting before my G4 went to brick with the flashing light. Same behavior occurred when installed SuperSU. After installing ElementalX everything worked fine.
To supplement this guide, here are a few more links and notes of what I did.
Links
The December 2017 Nougat ROM from here
G4 compatible Shreps TWRP from here
Current Magisk here
ElementalX for G4 is here
If needed, install Platform Tools and Android File Transfer
Steps
Install the ROM using these commands (on Mac):
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery ./twrp-3.1.1-athene_shreps.img
./fastboot flash dsp adspso.bin
./fastboot flash oem oem.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash modem NON-HLOS.bin
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash fsg fsg.mbn
./fastboot erase cache
./fastboot erase userdata
./fastboot erase customize
./fastboot erase clogo
Click to expand...
Click to collapse
After running commands, restart bootloader w/o rebooting
Go into recovery w/o rebooting
Reboot
After booting into the OS, turn on Developer Mode (tap About / Build Number 8 times)
Go to Developer Options and turn on OEM unlocking and USB debugging
Copy Magisk and ElementX kernel to / using Android File Transfer (if AFT doesn't connect select USB config, change to charging then back to MTP to enable file transfer)
Reboot into Recovery, then Install Magisk and ElementX from TWRP
Performed on an G4 XT-1625, resulted was a rooted Nougat.
@Sanras, I followed your instructions and they went great on a republic wireless xt1625, thank you! But your post just says to boot into twrp, which means if I ever want to use twrp I have to connect my computer. Is there a special way to flash twrp instead of just booting to it? Because I tried flashing twrp but the phone wouldn't boot afterward. So I had to flash the stock rom and redo everything. Let me know and thanks!
supermaxkato said:
@Sanras, I followed your instructions and they went great on a republic wireless xt1625, thank you! But your post just says to boot into twrp, which means if I ever want to use twrp I have to connect my computer. Is there a special way to flash twrp instead of just booting to it? Because I tried flashing twrp but the phone wouldn't boot afterward. So I had to flash the stock rom and redo everything. Let me know and thanks!
Click to expand...
Click to collapse
You should be able to flash TWRP. That's actually the most used method. I simply recommended booting and not flashing because it is easier to revert to stock for an update. However, you should be able to flash TWRP if you want with "fastboot flash recovery D:/TWRPimages/twrp.athene.img"
(Replace last part with image path on your computer)
Thanks Sanras,
Great guide, worked for me with no problems.
Anyone know how to approach security updates after rooting via this method?
Currently on Dec17 looking to update to Apr18 security patch just don't want to brick device.
Thanks in advance. :good:
Thanks. Sanras.
I got my phone bricked after restore my stock rom and try to install magisk to it. This solved my case also.
I just have to pay attention that just installing the kernel after try the magisk is not enough. Like you said:
* Install ElementalX kernel; wipe caches
* then install Magisk (again), and wipe caches again
Is this safe for Qualcomm variants like the Boost Mobile version?
chuman72486 said:
Is this safe for Qualcomm variants like the Boost Mobile version?
Click to expand...
Click to collapse
Yes, my own G4 is a Snapdragon 617 (unlocked US Variant) XT-1625
SD Card Configured Adoptable
Sanras said:
*Download all necessary files*
Magisk v15.0 or newest available
Download ElementalX kernel @ elementalx.org
Download latest Magisk Manager from official xda thread
Download TWRP for Moto G4 (Athene)
from twrp.me
Unlock bootloader (Go to Motorola's official site)
Check Unknown Sources in Android settings under security tab.
Download and install ADB & Fastboot on your PC
Boot into fastboot by holding down vol down and power.
Once you see Android robot with text at the bottom, on your computer in cmd type "fastboot boot TWRP image path" ex: fastboot boot D:/TWRPimages/twrp.athene.img
Once phone boots to TWRP, TWRP will ask to make modifications to system. Keep read only. (Note: if is asks to install, always say no.) Next go to backup, and make backup. (Just backup what is selected by default: system, data, and most importantly, boot.img) Note: make sure to tell it to backup to SD, and make sure the SD card is formatted as portable, not adoptable. Note: you might need mount the card under Mount tab first before being able to select it.
Next, go to mount, and uncheck "keep system read only", and swipe to allow modifications. Go to install, and flash ElementalX, and set it up in the following screen. As we already have the turbopower charger, you don't need to enable USB fast charging.
Wipe dalvik cache, and flash Magisk. Then, wipe dalvik again, and power off.
Boot into Android to make sure everything works. Install Magisk app if it didn't appear in your apps drawer from the .apk you downloaded earlier.
Hope this helps! Good luck!
Note: If you would like to flash TWRP instead, use "fastboot flash recovery TWRP.img" instead of fastboot boot.
Click to expand...
Click to collapse
My Moto G4 has an SD card formatted adoptable. Is there a work around in step 6 to accommodate an adoptable SD card?
Thanks
rwruck said:
My Moto G4 has an SD card formatted adoptable. Is there a work around in step 6 to accommodate an adoptable SD card?
Thanks
Click to expand...
Click to collapse
Sure. Instead of making a backup to the card, backup to internal storage. Then, before doing anything else, on your pc copy the files from the newly created TWRP folder on your internal storage. These are your backups. You can then proceed with the rest of the steps. Honestly, the backup isn't even necessary, it's just good to have in case something goes wrong.
Hi
I know it's a bit old now, but I'm unable to root my Nougat XT1641
I already have the whole stuff :
- BL unlocked ;
- TWRP installed ;
- all backups done.
But everytime I try to flash ElementalX/Magisk, it fails and ends in a bootloop.
Can someone have an advice to help me ?
Well, I used this : https://topjohnwu.github.io/Magisk/install.html#patching-images
Patching my boot.img did the trick !
Related
How can I lock the phone back after unlocking bootloader, rooting, installing Xposed?
Wipe installed custom ROM (System+data+cache+dalvik).
**Internal storage optional (You may have to flash TWRP again though).
Install MIUI recovery ROM pack through TWRP. Run MIUI initial setup. Reboot to fastboot and flash stock recovery, you can find stock recovery in MIUI forums. After that check for successful flash and successful system boot. Only then run the fastboot command to lock the bootloader :
fastboot oem lock
**Do not lock with TWRP. You'll hard brick your phone
***After flashing MIUI in TWRP flash lazyflasher or your device will be stuck
If you don't understand the complications in this method please ignore it, am sure there are some easier ways using MiFlash. Check MIUI forum for relocking and recovering to MIUI. If you wanna come back to the world of custom ROMs and Mods XDA is the place.
ArK96 said:
Wipe installed custom ROM (System+data+cache+dalvik).
**Internal storage optional (You may have to flash TWRP again though).
Install MIUI recovery ROM pack through TWRP. Run MIUI initial setup. Reboot to fastboot and flash stock recovery, you can find stock recovery in MIUI forums. After that check for successful flash and successful system boot. Only then run the fastboot command to lock the bootloader :
fastboot oem lock
**Do not lock with TWRP. You'll hard brick your phone.
Click to expand...
Click to collapse
Thank You
BTW If you have the time could you write this more in steps like for a noob. If not it still kicks a$$ and thanks for reply
First you need to get rid of your current ROM and it's data. For that boot into TWRP and select wipe, in the list of partitions displayed select :
•System
•Data
•Cache
•Dalvikand confirm wipe. This step removes the ROM and data associated with it. Now the only thing you can access is TWRP and fastboot.
Also during wipe you can also select to wipe Internal Storage partition but after you do this you may lose TWRP also at the next boot. Now your phone can only boot into fastboot mode. So if you did wipe your internal storage also flash TWRP again from fastboot. If you ask how..:
•Download TWRP recovery from here
•Copy the downloaded file to any folder on your PC.
•Install ADB and fastboot drivers on your PC if you haven't.
•Reboot phone into fastboot mode(Power + Volume down) and connect to PC.
•Go to folder where your placed the TWRP image file.
•Open command prompt in that folder (Shift+right click mouse, open command window here)
•Type the following commands without the quotes :
" fastboot flash recovery twrp-3.2.1-0-mido.IMG "
•Now try rebooting into TWRP (Power + Volume Up). If you followed the steps right you should be able to.Remember this step is only if you decide to wipe internal storage also else it is completely not necessary.
OK now that you are left with a phone that only has TWRP we need a ROM to boot into, in your case you want a MIUI ROM. Download latest stable MIUI recovery ROM pack from MIUI website or just google if your having trouble finding it. For MIUI ROMs to successfully boot on a custom recovery you need to flash an additional zip called lazyflasher else your phone will be stuck at the MI logo. I'll attach the zip below. Okay so now since you have the required files copy them to your phone's internal storage.
Boot into TWRP and install the MIUI ROM zip first and the Lazyflasher zip after that. Reboot into system and phone should enter MIUI initial setup in some minutes(be patient MIUI initial boot can be long). Finish the setup.
Now you need to flash the latest stock recovery of your phone. I don't have it with me now so a simple google search will do the work. The procedure for flashing the recovery is the same as flashing TWRP which I have mentioned above. The only change you have do in the fastboot command line is the file name of your stock recovery.
After flashing check for successful boot, only then proceed with the relocking procedure as follows:
•Boot phone into fastboot mode
•Connect to PC
•Open Command prompt
•Type this fastboot command without the quotes :
" fastboot oem lock"•Once done reboot your phone.
Now you must have a relocked phone.
**Never relock your phone with any custom mods like custom recovery, custom ROM or even a MIUI which is rooted. Also be on 100% stock configuration before relocking device. Failing to do so will result in a hard brick.
***ATTACHED FILES ARE NOT MY WORK. CREDITS GO TO THEIR RESPECTIVE CREATORS.
Hi, I'm having some issues trying to install the newest update of A10.
I was on A9 with unlocked bootloader, root and twrp of recovery.
I first tried to install the .rar image via recovery but I couldn't find in the memory, but I already wiped system vendor and data.
So when I rebooted to try if the file was there or not, there was no recovery anymore.
Now I'm trying to flash the newest rom via fastboot but through the flash_all.bat it gives me fastboot tz_a error, so I'm trying to install a recovery through fastboot using this guide https://forum.xda-developers.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603 but of course it doesn't work and when I reboot it doesn't enter the recovery but always in fastboot (even tho I press the + button).
What should I do now? Is there anyway to erase everything and install a clean OS from 0 just from fastboot? (Without the flash_all or miflash because it doesn't work)
P.S. I don't care about the data, I've done a backup of all my important files before
Thanks for the help
Sapper Morton said:
First, you have to understand what you did. You wiped your system and vendor image, and didn't installed a newer one afterwards, you didn't wiped your recovery (it's inside boot partition).
Further, .rar files will not be flashed through TWRP, .zip must be used instead, with proper format, there must be a compatible flash script inside.
You can't access your recovery, just because you wiped system; inside your bootloader there's a component responsible to manage the slots, bootctl and by default if it detects a corrupted or invalid system partition, it will always boot onto bootloader mode.
As for the tz_a error, you must unlock critical partitions flashing, just because, tz is a critical partition, thus, run in Fastboot:
Code:
fastboot flashing unlock_critical
If you want to know your current state, use:
Code:
fastboot oem device-info
Your current slot is blocked by bootctl, but this doesn't mean your inactive is too, so, use:
Code:
fastboot set_active other
And reboot into TWRP again, that is, if you do have it installed in your inactive slot.
Fastboot/ADB and other tools, you will find it in here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
If you want to restore using recovery firmware, please do the favor, and read the post below:
https://forum.xda-developers.com/showpost.php?p=82595733&postcount=379
Click to expand...
Click to collapse
Thanks for the help but I managed to get into the recovery and install the rom via fastboot, the thing I was missing was a recovery working for Android10 (even though I remember recovery doesn't have nothing to do witg the installed OS), so I managed to install the recovery and root, and everything went fine after a few tries between various guides. Probably my partitions now are all messed up, but if I boot normally it goes into system (slot A), if I boot into recovery it goes into twrp and also works fastboot. Probably I also installed the OS on slot b, but I don't care as long the first partition works well
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205
I'll add some links to other threads that helped make this but I've found the root/custom rom process is the same for all
You don't need TWRP and if you're able to install it you won't get far as the system partition is hidden
try to make sure it comes with gapps preinstalled as you won't be able to install it after
*lineage will work but doesn't come with gapps preinstalled for example
Pre requisite: flash the latest rom using spflash tool
Steps:
1. Pick a rom here https://forum.xda-developers.com/project-treble
From the two devices I've had it looks like it must be an AB rom
I went with this as it is pre rooted
2. Back up your data & Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
3. Enter fastboot either with adb or power on while holding volume up
4. Fastboot reboot to enter fastbootd
5. fastboot erase system
6. Your system partition is likely too small so delete it
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
7. fastboot flash system (gsi file here)
And you're good to go
As of right now you can install the magisk app but it won't do much. Tried using the app last night as it got root from the other app but the patched boot image caused a bootloop and I had to reflash stock boot.
It looks like this is a thing with this brand and magisk at the moment not sure why
sources
https://forum.xda-developers.com/android/help/umidigi-power-3-android-10-t4044531
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-umidigi-t4169405
orions_Cat said:
I'll add some links to other threads that helped make this but I've found the root/custom rom process is the same for all
You don't need TWRP and if you're able to install it you won't get far as the system partition is hidden
try to make sure it comes with gapps preinstalled as you won't be able to install it after
*lineage will work but doesn't come with gapps preinstalled for example
Pre requisite: flash the latest rom using spflash tool
Steps:
1. Pick a rom here https://forum.xda-developers.com/project-treble
From the two devices I've had it looks like it must be an AB rom
I went with this as it is pre rooted
2. Back up your data & Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
3. Enter fastboot either with adb or power on while holding volume up
4. Fastboot reboot to enter fastbootd
5. fastboot erase system
6. Your system partition is likely too small so delete it
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
7. fastboot flash system (gsi file here)
And you're good to go
As of right now you can install the magisk app but it won't do much. Tried using the app last night as it got root from the other app but the patched boot image caused a bootloop and I had to reflash stock boot.
It looks like this is a thing with this brand and magisk at the moment not sure why
sources
https://forum.xda-developers.com/android/help/umidigi-power-3-android-10-t4044531
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-umidigi-t4169405
Click to expand...
Click to collapse
Hi, when I try to erase the system with fastboot it fails and says that the partition table doesn't exist. How can I solve that? thanks
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
DragonPitbull said:
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
Click to expand...
Click to collapse
Cool This helps already a lot.
i unlocked the Bootloader properly, but then i got a partition error. I assume i´ve an error in the command line. The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
beinfo said:
The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
Click to expand...
Click to collapse
Try but REMENBER I am not responsible for any errors. Bootloader should unlocked by adb-fastboot!!
Spoiler: Instructions
1. You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options: reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
2. Device in fastboot
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
vbmeta file from stock ROM or pulled from device
3.
Code:
fastboot -w
4.
Code:
fastboot reboot fastboot
(you MUST be at the FASTBOOTD menu now. If not, you will not be able to flash the GSI successfully)
5.
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
6.
Code:
fastboot delete-logical-partition product
- deletes the product partition, allowing a larger system partition
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
6A. fastboot resize-logical-partition product 509344768
6B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
7.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
8.
Code:
fastboot -w
for confirm great & fast start GSI
9.
Code:
fastboot reboot bootloader
9A.
Code:
fastboot erase userdata
for confirm and boot clean
10. Reboot to system
Code:
fastboot reboot
Enjoy
I also have an N20 Pro which I received Dec 2020. Had some trouble setting it up. I got the OEM ROM from Doogee customer support and was able to extract the boot image and patch it with Magisk. I then burned it with the SP Flash tool. It wouldn't boot until I burned a special vbmeta.img to turn off encryption. Now it's working fine.
Sorry this doesn't help you with TWRP but I think most people looking for TWRP are really looking to root their phone.
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
Okay so what ive seen is that you should avoid flashing custom roms via adb fastboot especially with our doogee phones, and also there are many incompatiable roms so what you will need is to unlock bootloader and do the whole twrp install thing adn also install magisk
before hand install treble info from google playstore and take down the information "arm64 a/b" and search for roms with that information to install custom os/rom/gsi properly. GSI versions are more preferred if your phone supports treblle
if your twrp keeps getting wiped after reboot open file :mount your system and connect to pc via usbcable (mtp if not showing disable mtp and re- enable it )
now got to where build.prop is saved there will be a file called recovery from boot.p , copy the file to pc , open with notepad, remove everything , save and copy back to phone (overwrite)
then go ahead and install magisk
make sure your magisk is working install edxposed, riru core , and busybox ndk get the apps you need for them (edxposed manager...) and then instal and activate a module which you can test if its working(if framework is active in edxposed manager and the module working correctly then you can go ahead and
Install custom os through twrp
follow these instructions ( https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/ ) with your custom rom (corvus, havoc, lineage...
(the g-apps didnt flash for me (error code 64) but i just rebooted and everything was working fine (including gapps but camera sucked (doogee's rear camera setup was just terrible))
https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/
** i can confirm follow instructions properly and it should work (i used this pixel experience on my doogee n20 make sure you unzip the .xz file and youre flashing a .img file
**also make sure its the gsi file (