Database Info

[Resolved] Installed TWRP on phone with a locked bootloader - now stuck in boot loop

I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.

if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk

EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.

i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk

I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done

EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.

Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks

Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!

IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?

mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.

Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.

Team MT's Huawei Multi-Tool – Works with Honor 10 !

Hey Folks,
I recently stumbled upon Team MT's quite useful Huawei Multi-Tool – but didn't find anything about it in the Honor 10 Forum although it's compatible!
First of all I have no connection to Team MT at all, so this thread is just about the usefulness of the Tool and what you and I might experience using it.
Also I'm not responsible for any damages/issues caused by this tool.
The tool might come in handy for people that are uncomfortable using cmd/terminal commands or get confused too easily.
Of course there are still a lot of things that could go wrong so if you're not sure what you're doing or what the consequences might be, just don't flash anything.
To use the Multi-Tool, you'll have to have your bootloader unlocked and the phone connected to your pc with adb installed.
When the tool shows you the (right) phone model in the lower right, you're good to go.
With the help of the Multi-Tool, you can
ROOT your Honor 10 with Magisk
flash TWRP
flash STOCK RECOVERY
unlock various small features
All with just a few clicks.
You can download it at Team MT's website:
http://pro-teammt.ru/huawei-multi-tool/
I for instance used it to flash the stock recovery after I had installed TWRP, so I could get regular OTA updates through the system again.
I'm curious to see if there are other people that have used the tool as well or what people that just heard of it now will use it for.

Is an unlocked bootloader required for the tool to root the phone and flash custom recovery?

leAndroid91 said:
Is an unlocked bootloader required for the tool to root the phone and flash custom recovery?
Click to expand...
Click to collapse
Yes , unlocked bootloader is required

Btw where did you get your stock recovery? Cause I don't see Any stock recovery out there for colal10 model. Btw thanks for the info, gotta check it out

fosterqaz11 said:
Btw where did you get your stock recovery? Cause I don't see Any stock recovery out there for colal10 model. Btw thanks for the info, gotta check it out
Click to expand...
Click to collapse
You can back up stock recovery after flashing magisk

miststudent2011 said:
You can back up stock recovery after flashing magisk
Click to expand...
Click to collapse
https://www.addictivetips.com/mobil...ecovery-and-system-partition-images/&hl=en-IN
Will this work since I will have to backup without using twrp.

fosterqaz11 said:
https://www.addictivetips.com/mobil...ecovery-and-system-partition-images/&hl=en-IN
Will this work since I will have to backup without using twrp.
Click to expand...
Click to collapse
The link you provided is broken.
You can find the procedure here.
https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3

miststudent2011 said:
The link you provided is broken.
You can find the procedure here.
https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3
Click to expand...
Click to collapse
Ty turn out it was almost the same info

fosterqaz11 said:
Btw where did you get your stock recovery? Cause I don't see Any stock recovery out there for colal10 model. Btw thanks for the info, gotta check it out
Click to expand...
Click to collapse
The Stock recovery just appeared inside the Multi-Tool, where I was able to download and flash it, I didn't download or back up anything beforehand.
Isn't there some dropdown menu where you can choose the recovery to flash?
I've been flashing it onto my COL-AL10 AND my L29, so it works either way.

vollkornbaguette said:
The Stock recovery just appeared inside the Multi-Tool, where I was able to download and flash it, I didn't download or back up anything beforehand.
Isn't there some dropdown menu where you can choose the recovery to flash?
I've been flashing it onto my COL-AL10 AND my L29, so it works either way.
Click to expand...
Click to collapse
I didn't install the app yet
I'm gonna wait for gpu turbo update then maybe root

Flashing from CN version to Global questions

Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!

Safari unzips after downloading. You can disable it in the settings I think.

TheArchangel123 said:
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Click to expand...
Click to collapse
Flash magisk 19 then install the magisk app

TheArchangel123 said:
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Click to expand...
Click to collapse
You do not need to root your device to flash it to the Global ROM. Unless you need root for something specific, I would suggest forgetting about TWRP and root and using fastboot to flash to the Global ROM. You can find the fastboot flashing guide, here. Click on fastboot, read the instructions, download the correct fastboot image for the Mi Mix 3, unzip it, boot your device into fastboot, connect it via USB to a Windows based machine, and run the flash_all.bat. The device will reboot when finished.

Thanks!
jcsww said:
You do not need to root your device to flash it to the Global ROM. Unless you need root for something specific, I would suggest forgetting about TWRP and root and using fastboot to flash to the Global ROM. You can find the fastboot flashing guide, "https://en.miui.com/a-232.html"]here. Click on fastboot, read the instructions, download the correct fastboot image for the Mi Mix 3, unzip it, boot your device into fastboot, connect it via USB to a Windows based machine, and run the flash_all.bat. The device will reboot when finished.
Click to expand...
Click to collapse
Ok thanks! Will definitly check it out. However i would like to get twrp working as well even just for the sake of it. But every time after i do the "reboot flash recovery rocovery.img" cmd it keeps booting into either the normal OS or into fastboot mode. Ive read about installing the force disable encryption zip file but how do i install that if i cant boot into twrp?

TheArchangel123 said:
Ok thanks! Will definitly check it out. However i would like to get twrp working as well even just for the sake of it. But every time after i do the "reboot flash recovery rocovery.img" cmd it keeps booting into either the normal OS or into fastboot mode. Ive read about installing the force disable encryption zip file but how do i install that if i cant boot into twrp?
Click to expand...
Click to collapse
Which TWRP are you flashing? When I was attempting to root my Chinese Mi Mix 3 running the GLobal Stable ROM, it was very hit and miss getting TWRP to stick. I couldn't get fastboot reboot-recovery to work for me so I had to power the device off after flashing TWRP and then hold Volume Up and Power until it vibrates again to get it into TWRP.
To root in that particular situation (Chinese device/Global ROM), you need to flash this region hiding thing right after you flash root. My device kept bootlooping so I gave up and used fastboot to debloat the ROM, which took a few minutes compared to the almost hour I spent on trying to get TWRP to stick and try to get the device rooted. This is one of my many gripes with Magisk root and how inferior it is to Chainfire's discontinued implementation.

Final stage!
Ok so my last post can be ignored as i was finally able to boot into twrp and also installed magisk so now my device is rooted.
I have now uploaded MIMIX3GLOBAL_V10.2.2.0 PEEMIXM into my phones directory.
Now before i install it thru twrp.... Do i need to wipe/erase/clean my phone first? Or can i just install it without doing so?
Many thanks in advance!

TheArchangel123 said:
Ok so my last post can be ignored as i was finally able to boot into twrp and also installed magisk so now my device is rooted.
I have now uploaded MIMIX3GLOBAL_V10.2.2.0 PEEMIXM into my phones directory.
Now before i install it thru twrp.... Do i need to wipe/erase/clean my phone first? Or can i just install it without doing so?
Many thanks in advance!
Click to expand...
Click to collapse
You can dirty flash it. It's just a minor update. The current beta will bring some new features though, once it is released in the next stable version.

jcsww said:
You can dirty flash it. It's just a minor update. The current beta will bring some new features though, once it is released in the next stable version.
Click to expand...
Click to collapse
Even though my current rom is the chinese version and i want to flash to a global version?
And how about if I flash to Mi Mix 3’s MIUI 10 Global Stable ROM based on Android 9 Pie (MIUI v10.0.11)??

TheArchangel123 said:
Even though my current rom is the chinese version and i want to flash to a global version?
And how about if I flash to Mi Mix 3’s MIUI 10 Global Stable ROM based on Android 9 Pie (MIUI v10.0.11)??
Click to expand...
Click to collapse
You can't dirty flash it...
Wipe in twrp
Install zip in twrp
format data in twrp
Reboot
If you want to root it you'll need the hardware origin magisk module that's somewhere in the mix 3 forums

Region, china?!
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????

TheArchangel123 said:
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
Click to expand...
Click to collapse
China has the most content, it's not a bad thing. All themes become available etc

Mackay53 said:
China has the most content, it's not a bad thing. All themes become available etc
Click to expand...
Click to collapse
ok fair enough. However I have a situation now... after installing the process goes into a loop after selection china as region. The last small message it gives is "find device quit unexpectedly" and then it loops for 5 minutes untill it boots into recovery mode. Here i can only choose boot system (which will go into the same loop again), wipe data, or connect to MIUI assistent...
What did i do wrong?? Did i flash the wrong rom?

TheArchangel123 said:
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
Click to expand...
Click to collapse
When cross-flashing, clean/factory reset is always the way to go. With TWRP though, there seems to be some sort of region options not changing issue. There are a few ways to work around it I personally never bothered with, but I have flashed two Chinese devices via fastboot with the Global Stable ROM and haven't ran into the region issue at all.

TheArchangel123 said:
ok fair enough. However I have a situation now... after installing the process goes into a loop after selection china as region. The last small message it gives is "find device quit unexpectedly" and then it loops for 5 minutes untill it boots into recovery mode. Here i can only choose boot system (which will go into the same loop again), wipe data, or connect to MIUI assistent...
What did i do wrong?? Did i flash the wrong rom?
Click to expand...
Click to collapse
Google miui region fix, download and flash and it should sort it

Mackay53 said:
Google miui region fix, download and flash and it should sort it
Click to expand...
Click to collapse
ok got the miui region fix. But how do i flash it... my phone wont boot into twrp anymore. Im also not sure how to get into fastboot either because it doesnt seem to connect if i type in the commands in cmd

TheArchangel123 said:
ok got the miui region fix. But how do i flash it... my phone wont boot into twrp anymore. Im also not sure how to get into fastboot either because it doesnt seem to connect if i type in the commands in cmd
Click to expand...
Click to collapse
Fastboot is the bootloader. Once you boot your device into the bootloader (Volume Down + Power), you can use ADB through the command prompt to flash TWRP or just flash the Global ROM properly. This thread on it is still very relevant and useful.

Got it!
jcsww said:
Fastboot is the bootloader. Once you boot your device into the bootloader (Volume Down + Power), you can use ADB through the command prompt to flash TWRP or just flash the Global ROM properly. This thread on it is still very relevant and useful.
Click to expand...
Click to collapse
Thanks guys, after a few long days ive finally succeeded to flash a global rom for the first time. Nxt step, try to get all my apps/data etc back. Hopefully i made a correct back up...

Unable to boot recovery after Android 10 Open Beta 1 OTA

Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!

seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.

HighOnLinux said:
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
Click to expand...
Click to collapse
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.

verbatim7 said:
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
Click to expand...
Click to collapse
Had read somewhere that flashing stock boot.img will help restore stock recovery.. Have you tried doing that

brashmadcap said:
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
Click to expand...
Click to collapse
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me.
Edit: this part down was meant for OP, sorry for confusion
so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal

HighOnLinux said:
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me. so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
Click to expand...
Click to collapse
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:

Use an older version of magisk and you won't lose twrp

verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
how did u get back the recovery?

LazerH said:
how did u get back the recovery?
Click to expand...
Click to collapse
As stated above - just downloaded the OTA Android 10 update file for the right device, installed it and didn't install magisk to inactive slot and I had it back. If I tried to install magisk to keep root I didn't have the recovery mode. My guest guess is that magisk still isn't fully compatible with the new Android 10 boot changes.

verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
To me having a stable phone is much more important than a heavily modified device that's unstable at any given time. I'd say use the msm tool, flash back to a fresh build of pie, download the full open beta 30 zip, after its done flashing, reboot twice to iron out any present issues, then unlock the bootloader, and then you should be good to go. If you want root, just fastboot boot into twrp and flash the latest magisk zip and you're good to go. At the end you should have root, an unlocked bootloader, all while on the open beta android 10 build, with access to the stock recovery

Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (

terrorblade23 said:
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
Click to expand...
Click to collapse
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot

Schnullifax said:
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Click to expand...
Click to collapse
thanks..this is what i was looking for ...the problem is that now i'm in a boot loop , the dots keep spinning 4ever...and i did factory reset it from recovery
up1: i managed to install on slot a (i guess) Twrp.. but the whole memory is empty and i cant place anything (firmware) with pc on phone
formated data from twrp (to some format ntfc4 or smth like that ) and installed back android q and is working .

Unresponsive touch screen in TWRP - how can install a ROM?

So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?

kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip

vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device

vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.

kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group

vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.

kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted

vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.

FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant

I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.

s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.

kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.

I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.

TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)

roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.

TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work

This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.