Related
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Alexenferman is not responsible for any damages or bricks made to your device. Please do some research if you have any concerns about rooting, its features and downsides. You are choosing to make these modifications, you should blame yourself for any mistakes you make.
Rooting may require a factory reset, please backup your data. Rooting will void your device warrany. By rooting your device, you will not be able to install OTA updates on your phone.
US carrier specific devices such as Verizon and Sprint might not be bootloader unlockable, therefore, not rootable.[/B]
You will need:
Platform Tools (Download from here)
Motorola Drivers
Windows or Linux PC
Bootloader Unlocked Moto E 2020
Your phone must be bootloader unlocked. Rooting your phone and not unlocking the bootloader will result in a soft brick.
Download the latest Magisk Manager APK from Github: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.0/MagiskManager-v8.0.0.apk
Install the APK file. Make sure to enable "Unknown Sources" in the Settings app
Patching the boot image
To retrieve the boot image in order to patch it, you will need to download the stock ROM for your specific variant.
Download the ROM from your variant from here: https://mirrors.lolinet.com/firmware/moto/ginna/official/
To check which region is your device, go to Settings > About Phone > Software Channel.
After downloading, open the ROM zip file with an archive manager.
Extract the boot.img file only.
Transfer the boot.img file on your phone.
On your phone, open the Magisk app.
Select "Install" > "Install" > "Select and Patch a File"
Locate the boot image in the internal storage on your phone. Select the boot.img file.
Transfer the magisk_patched.img file on your computer.
Rooting the device
Boot the device into fastboot mode by holding the [Volume Down] and [Power] buttons.
Connect your phone to your PC.
On your PC, open a fastboot console window.
Type:
Code:
fastboot devices
Your phone serial number should be displayed along with the word "fastboot" or "device" in the console.
Now, type the following commands:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Replace patched_boot.img with the path to your boot image we patched previously.
To reboot the device, type:
Code:
fastboot reboot
Once the device rebooted, open the Magisk app.
If you see the "Magisk is installed" message, you have successfully rooted your device!
You are done!
To view instructions with images, follow these instructions: https://www.alexenferman.com/articles/MotoE2020/root-moto-e-2020-magisk
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Hypercore said:
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Click to expand...
Click to collapse
Me neither, can anyone provide a TWRP for ginna?
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Hypercore said:
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Click to expand...
Click to collapse
Confirmed working. Tyvm!
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
dragonfire0501 said:
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
Click to expand...
Click to collapse
Ranthalion75 said:
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
Click to expand...
Click to collapse
I have one too and I've tried to unlock the bootloader however Motorola's website says the bootloader for this phone is not unlockable. It seems like this is what's preventing me from being able to install a different firmware like the stock one or root the device.
I do not know if there is any sort of workaround for this
For some reason on a Moto E, after rescuing using the Moto rescue assistant and then using
you guys can also use OFox Recovery and swipe magisk to root
Thank you. I used this guide to root my Moto E
QPGS30.82-135-2_Root.img
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
i can't get this to work at all, i cannot find a matching stock firmware being qpg30.82-135, there's no extra S and nothing else after the 135, got this phone from my motorola insiders rewards and now it's bootlooping after trying the 135-2 patched image
Has anyone been able to root and hopefully install a custom recovery on the lastest update? Mine is QPGS30.82-135-14, and so far I've only been able to get orangefox to boot but couldn't get it to decrypt my storage or install magisk. I tried twrp first, but to no avail, touch screen still doesn't work on it, so now I'm asking on a few different threads for this phone lol. Any help would be great!
Do you know of an updated method to get it to flash correctly? I was able to boot into ofox, but couldn't get it to properly flash. Ended up stuck on a screen that said my phone was unlocked and couldn't be trusted and that it'll reboot in 5 seconds. I don't know much about ofox either, been using twrp for years lol, it looks too different. Anyhow, any help would be appreciate much!
ace120ms said:
you guys can also use OFox Recovery and swipe magisk to root
Click to expand...
Click to collapse
You have to fastboot boot it anyway I don't have this phone anymore so idk
bouyakasha said:
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
Click to expand...
Click to collapse
I have the same problem with QPGS30.82-135-9. I can't get it to boot after Magisk patched boot image.
Hello Friends,
Android 12L Section
Android 12L has finally been released for Duo 1 and the update makes this device what it should have been from the beginning (again...). But root is always nice.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 12L stock boot img patched with magisk 25.2, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you want to go the payload dumper yourself and make your own boot.img, see below.
Install Magisk Manager 25.2 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
Android 11 Section
Android 11 has finally been released for Duo 1 and the update makes this device what it should have been from the beginning. But root is always nice.
Luckily Android 11 has made rooting a bit easier as well.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 11 stock boot img patched with magisk 23, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you want to go the payload dumper yourself and make your own boot.img, see below.
Install Magisk Manager 23 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
Extraction of payload.bin from OTA.
If you want to extract the boot.img yourself and patch it yourself, download the payload.bin extractor from here. Acquire the OTA either via recovery images or capturing the OTA URL during an update (link).
Use the payload dumper to get the boot.img, install Magisk on your device and transfer the boot.img to it to patch that stock boot.img using Magisk. After that, you will have your own patched boot.img.
Proceed with step number 4.
A huge thank you to @NTchrist and @Perseu5 for pathfinding this all and their amazing guides, give those guys some thanks and kudos please!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Android 11 OTA Link & zip File, .img Files (Unlocked)
Hey friends! These are only for the unlocked Surface Duo. I am sorry At&t users. Here is the OTA link for Android 11: https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip Link to the OTA.zip...
forum.xda-developers.com
Personally I've always been hesitant to provide pre-patched images. People just spam your inbox if it's not up to date five minutes after release. Also, people don't learn about what they're actually doing. I'd never be a developer today if I were just handed all the things I wanted to have and I suspect that'd be true of many of the best developers on this forum. That said, If there's a demand I'll make an updated full guide. Let me know in the comments on my original thread if you guys want that.
NTchrist said:
Personally I've always been hesitant to provide pre-patched images. People just spam your inbox if it's not up to date five minutes after release. Also, people don't learn about what they're actually doing. I'd never be a developer today if I were just handed all the things I wanted to have and I suspect that'd be true of many of the best developers on this forum. That said, If there's a demand I'll make an updated full guide. Let me know in the comments on my original thread if you guys want that.
Click to expand...
Click to collapse
I fully agree with you. I did magisk_patching for old nexus's, oneplus 6t, and a couple of the pixels and I actually didn't get that much spam. But go a ton of spam for system UI tweaks, twrp and such how-tos I posted.
The primary reason I provided a pre-patched one here is because I had a ton of issues getting payload dumper to work on my fresh windows 11. And this was just easier.
Finally a much more streamlined process, and it works perfectly. That back & forth patching each month was getting too hairy. Not too mention how much faster this device is now which has me into it all over again. This has all been worth it so far in my opinion based off of usage today. no random app crashes anymore , much better UI and control panel across the board, Hell it even sounds louder. I'm really happy with this update and root so far.
OK so I've got the AT&T variant (that I use as a secondary device with no SIM) that I've successfully flashed Android 11 onto using the filiphsandstorm script. I haven't reset the phone. Android 11 works fine so far like this. Unfortunately though I'm hanging on the boot screen when I fastboot the patched boot image. If I patch the boot image with an earlier version of Magisk it double boots and returns to the stock image. If I patch the boot image with the latest version of Magisk I get the boot hang. Obviously this could just be AT&T incompatibility but does anyone have any ideas? Has anyone with an AT&T device successfully rooted on Android 11?
-
delfuhd said:
OK so I've got the AT&T variant (that I use as a secondary device with no SIM) that I've successfully flashed Android 11 onto using the filiphsandstorm script. I haven't reset the phone. Android 11 works fine so far like this. Unfortunately though I'm hanging on the boot screen when I fastboot the patched boot image. If I patch the boot image with an earlier version of Magisk it double boots and returns to the stock image. If I patch the boot image with the latest version of Magisk I get the boot hang. Obviously this could just be AT&T incompatibility but does anyone have any ideas? Has anyone with an AT&T device successfully rooted on Android 11?
Click to expand...
Click to collapse
Dumb question on my part but are you booting the patched image or trying to flash it in bootloader?
Just making sure we are on the same page.
eqbirvin said:
Dumb question on my part but are you booting the patched image or trying to flash it in bootloader?
Click to expand...
Click to collapse
No problem. Not flashing, just trying to boot. From
adb reboot bootloader
I'm executing:
fastboot boot patchedboot.img
Trying to flash to the boot partition just gives me an error anyway.
Also, just to be clear, I've tried it with your patched image as well as a boot image that I extracted from payload.bin. Both same results.
EDIT: OK I bit the bullet and did a factory reset through recovery. I wanted to avoid this as it's a pain setting the device up again. However, this solved the problem. I was able to complete the steps above and successfully gained root permanently. Thank you for your help!
eqbirvin said:
Hello Friends,
Android 11 has finally been released for Duo 1 and the update makes this device what it should have been from the beginning. But root is always nice.
Luckily Android 11 has made rooting a bit easier as well.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 11 stock boot img patched with magisk 23, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you do not want to use my pre-patched boot that is understandable but at this time I am not providing a how-to on extracting the boot from the OTA. You can use the pre-existing root guide by @NTchrist and @Perseu5 to at least extract the stock boot and then patch it yourself, just make sure you use Magisk 23.
Install Magisk Manager 23 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
If there is enough demand, I will do a walk thought on extracting the stock boot and patching it because I understand some don't like to trust downloaded boots.
A huge thank you to @NTchrist and @Perseu5 for pathfinding this all and their amazing guides, give those guys some thanks and kudos please!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Android 11 OTA Link & zip File, .img Files (Unlocked)
Hey friends! These are only for the unlocked Surface Duo. I am sorry At&t users. Here is the OTA link for Android 11: https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip Link to the OTA.zip...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for providing the patched boot and for the guide (although in my case I know the steps). You save me a lot of work. Excellent.
I got the AT&T version. I just booted the patched image from OP and it works. (i was having trouble patching the AT&T image. probably was my fault because i was using magisk v.24.1 rather than v.23)
Any one get a system update notification?
Quick question:
Can we use the generic boot image to get TWRP working on the Surface Duo?
eqbirvin said:
Any one get a system update notification?
Click to expand...
Click to collapse
Yes , a 565MB file !
How do we update and keep root?
diejuse said:
How do we update and keep root?
Click to expand...
Click to collapse
1st post ( thanks to NTchrist )
==== UPDATE WHILE ROOTED ==== Section
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
pvillasuso said:
1st post ( thanks to NTchrist )
==== UPDATE WHILE ROOTED ==== Section
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Click to expand...
Click to collapse
This is actually no longer necessary on A11 in most cases. You can do the magisk "install to inactive slot" workflow here to ota and retain root
tl/dr:
magisk > restore images (do not reboot)
do ota (do not reboot)
magisk > install to inactive slot
reboot
done
NTchrist said:
This is actually no longer necessary on A11 in most cases. You can do the magisk "install to inactive slot" workflow here to ota and retain root
tl/dr:
magisk > restore images (do not reboot)
do ota (do not reboot)
magisk > install to inactive slot
reboot
done
Click to expand...
Click to collapse
Thanks, just did it with today's latest 2022.113.26 OTA !
Super easy
pvillasuso said:
Thanks, just did it with today's latest 2022.113.26 OTA !
Super easy
Click to expand...
Click to collapse
Updated to the latest , 2022.115.10 OTA
pvillasuso said:
Updated to the latest , 2022.115.10 OTA
Click to expand...
Click to collapse
Updated to the latest , 2022.215.137 OTA
pvillasuso said:
Updated to the latest , 2022.215.137 OTA
Click to expand...
Click to collapse
Same process as before?
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
jcp2 said:
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot
jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?
Use PixelFlasher and the latest full update.
AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.
jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk
I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.
@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.
I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .
Android flash tool is by far the easiest way to go for sure. Happy you got it fixed
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".