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.
Related
Hello, I'm still a noob trying to learn, so far with help of this forum I've learned to unlock and root my first android phone, now I'm trying to learn how to properly keep my device updated!
Can someone please give a little rundown to what are the correct steps to update OTA on a rooted twrp device?
I've been browsing the forums a lot but I seem to find a lot of different approaches, or too vague instructions.
It would be greatly appreciated if someone could help me out, step by step, and explain the steps with the commands I need to put in, if there are any.
Thank you
download the ota from here
place it on your phone
go to update on you phone then hit the cog and hit local update
let it up date
reboot to boot loader
fastboot twrp img again
then flash the installer
reboot recovery
then it will boot back in to recovery again
flash root
job done
Hello,
To save you having to fastboot boot TWRP, do the following:
Save the following files to your SDCard:
OTA.zip
Magisk.zip
TWRP.zip
Boot into TWRP
Flash OTA.zip first, then TWRP.zip straight after, then Magisk.zip straight after that, reboot.
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
Sorry yes, put the installer zip on the sdcard
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
i just download and install the OTA through system updates. Then boot to Trwp recovery and flash magisk . Profit
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide
to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You can flash the installer zip for TWRP through TWRP itself.
Doesn't installing OTA through system settings wipe TWRP? That's why I perform all my updates from TWRP directly.
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You have to do twrp/root again after updates. Unlock sticks, but twrp and root don't.
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Ajaykumar21066 said:
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Click to expand...
Click to collapse
It prob doesn't overwrite until u reboot so twrp may not have been overwritten on that partition yet, so would make sense, I need to try it out sometime
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Swatto is correct. The risk when using twrp is that you must reboot to recovery immediately after flashing the twrp installer zip, or you will boot to the old slot and things will be broken. Rebooting to recovery gets you onto the active, updated slot.
When you reboot to recovery and flash an OTA, you are flashing it to the other slot. The current slot is untouched, while the new active one is completely stock. The twrp installer zip flashes twrp to both slots.
This is the procedure to follow if you want to update via twrp. Personally, I prefer taking the OTA and reinstalling via fastboot just to make sure everything is clean.
lollyjay said:
I have personally tested the following with TWRP already installed and twrp-installer-enchilada-3.2.1-0.zip on your phone:
Download full (not incremental) OOS ROM to your phone and check MD5
Reboot to your installed TWRP
Install the OOS ROM
Do not reboot instead stay in TWRP
Install twrp-installer-enchilada-3.2.1-0.zip
Reboot Recovery
Wipe cache
Reboot System
Click to expand...
Click to collapse
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Thank you
DampDeceiver said:
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Click to expand...
Click to collapse
I have not tried that method as I want twrp, but that is the recommended approach.
I know things have changed with twrp, but it's not that hard once you get used to it. You just have to remember that your phone will switch active slots every time it gets an update or you flash an ota (for example, to go back to stock), so twrp, etc, have to be installed on the other slot before you boot to it. Once you get comfortable with that idea, the rest of it is pretty easy.
Well, I am glad to read this post. Its always interesting how things can be slightly different in every phone manufacturer's setup.
After my lady Huawei device (Honor 6x), I did not want to have to deal with their style of... Control over their devices.
And things seem much easier here, while also being a little confusing right now. I don't fully get the slot a/b stuff yet but it sounds like it's a system to ensure stability on the phone in cases where the newest update could install incorrectly the alternative slot has a backup to ensure the device will function.
Sorta sounds like the dual bios setup on some motherboards. It's good!
Right, so to summarise to ensure I got it right:
1) Downloaded large (1gb+) ota zip from one of these threads, official twrp recovery installing zip, new version of magisk recovery installing zip
2) in recovery install all 3 of those zips in that listed order
3) reboot to recovery again to ensure twrp is still installed
4) profit
Which twrp thread should I take the zip from? There are a few different threads. I shouldn't care about the fastboot version when I already have twrp installed, right?
Either way, it can be much easier than what I had to do on Huawei phones. (currently the easiest phone I used for customisation like this was Nexus 4, but gladly OP6 is getting pretty close to that same level).
Sent from my OnePlus 6 using XDA Labs
You're best off downloading from the official twrp site. If you already have it installed, no need to use the fastboot boot method. You should to reboot to recovery in between flashing twrp and magisk to be sure magisk gets installed on the active slot.
Swatto86 said:
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Click to expand...
Click to collapse
Question, more of a scenario really. So if I'm on slot A and have TWRP and Magisk installed, would it be alright to just do a local update and reboot, giving me a perfectly clean install in slot B? Does it work that way? Thanks!
I'm actually using a 6t, but worst case scenario I just use the MSM Download tool, still I wanna get the hang of these confusing A/B devices.
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.
Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.
Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?
Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.
Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.
I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do
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 .
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
UrAverageNerd said:
If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Hi there. I ran into similar problems when I was a Root noobie (which I still am). Try the All In One Tool that can be found in this forum. That will help you flash TWRP. It got me there when I was struggling to Flash TWRP.
redpoint73 said:
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Click to expand...
Click to collapse
Thanks for your help. Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching. I like using TWRP because it's convenient if I wan't to flash something else without a PC or Mac.:laugh:
UrAverageNerd said:
Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching.
Click to expand...
Click to collapse
Something wrong with the "main" download link (androidfilehost)?
UrAverageNerd said:
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Use adb & fastboot via powershell
Get the adb files in a folder
Copy the twrp.img to the adb folder and on phone /storage/emulated/0/
Get a copy of the twrp installer on your phone anywhere works
Open adb folder
Hold shift and right click a empty space
Open powershell & type
Adb boot bootloader
Fastboot boot twrp.img (you can drag and drop the file into powershell if your lazy like me)
Flash the twrp installer on your phone
Done?
Reboot and go back into recovery to see if it works
Tip for updates:
After you get the update
Flash via twrp
Then flash twrp (so you don't need your computer)
Flash magisk if you want superuser
Reboot
Reboot recovery
Flash magisk again (seems it takes two flashes)
None of the tools work for my devices anymore just powershell
All in one doesn't read my fastboot
Cmd has a remote error after attempting to boot it.
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Just noticed that the TWRP "guacomoleb" is the "unified" version that works with both the OnePlus 7 and the 7 Pro. Shouldn't make a difference whether you use the "unified" version or the 7 Pro specific TWRP.