Related
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.
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.
Just a reminder for people who only read the oneplus 9 forum and not oneplus 9 pro one:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
I tested it and flashed it on my oneplus 9 LE2110 and it works.
Again, as i always have to write to people.
Be careful, only do something you can undo.
Before you "Flash Current TWRP" do a full BACKUP!
Does said recovery perform full back-ups of partitions and restore features ?
Edit
I booted it up . Decrypts perfectly. Backed up modem just to see for myself. Rebooted back onto system . Booted twrp again and it found saved partition to restore. This makes life so much easier. Time to go get a full system backup !! Cool
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
noname122414 said:
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
Click to expand...
Click to collapse
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Hi there, I have a question:
When you have a new device, would the following work:
1. Unlock bootloader
In fastboot mode:
2.
Code:
fastboot boot c:\twrp.img
In TWRP
3. Install TWRP
4. Install Magisk
5. Reboot - then you have Root, TWRP?
6. Upgrades can than be done in TWRP by installing the files and than intalling again TWRP and afterwards Magisk?
Best
Axel
It appears you are asking. If I am incorrect, my apologies. With the 6t (also a a/b OP device)
The process I always used was
1) reboot to bootloader
2) boot twrp.img
3) install twro zip
4) reboot recovery
5) upon TWRP reboot, install magisk
6) profit.
Anytime I tried to go ahead and install Magisk in the same round as installing TWRP, it would install to the opposite slot making me have to do the whole process over again. Ymmv
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
barguybrady said:
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
MrSteelX said:
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
Click to expand...
Click to collapse
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
barguybrady said:
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
Click to expand...
Click to collapse
You should start a separate thread for all that. Kinda want to keep on topic to make it less confusing for everyone
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
mattie_49 said:
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Click to expand...
Click to collapse
Just installed it - thanks OP.
Does anyone know if I can jdirtyflash the global rom 11.2.7.7 over the EU rom which is currently on 11.2.7.7 in twrp?
I was originally on global (le2110) but flashed EU via update. Now I want to go back to global.
applyscience said:
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
Click to expand...
Click to collapse
Full system everything. User data. ? Did it work
mattie_49 said:
Full system everything. User data. ? Did it work
Click to expand...
Click to collapse
i dont know i have been bricked for 5 days ever since i attempted the lineage release
applyscience said:
i dont know i have been bricked for 5 days ever since i attempted the lineage release
Click to expand...
Click to collapse
Just lineage no kernel no special cam?
mattie_49 said:
Just lineage no kernel no special cam?
Click to expand...
Click to collapse
nah. just lineage. pretty sure i deal with support again tomorrow. fun...
Need help...
I typed Fastboot boot twrp.img instead of fastboot flash boot twrp.img
And that was to boot_a
So then i tried fastboot flash boot_b twrp.img
It wont load the recovery now. Phone wont boot up unless i
fastboot boot patched11.2.7.7DA.img
I even try to install Magisk directly and it fails.
Can I get some help. Dont even wanna restart my phone.
Thank you
All Good Now..... I Figured It Out!
How to fix this
id avoid TWRP if on 11.2.8.8 already. it can boot from fastboot and even install itself as your recovery but it will not mount data. i tried the refresh sizes trick in backup and then the default_password for password to decrypt and nothing. pretty sure twrp mishaps are what bricked my phone last too . thankfully it still boots, just the recovry section is effected
ill try and flash the OTA zip tomorrow. sick of messing with it for now lol
Are we still avoiding twrp
Hello!
I tried the search function but my search-fu isn't strong today. I got a Vortex V22 phone from Standup Wireless. I must have been half asleep, because when i flashed what I assumed was the correct boot.img, I got stuck in a boot loop.
On further investigation, I had flashed the boot for another device called Vortex. I am having incredible difficulty in finding the right boot image. The info I have from the side of the box is:
Vortex V22 4G LTE
Color: Graphite Blue
ROM 32GB
RAM 3GB
OS Android 11
FCC ID 2ADLJ-V22
I deeply appreciate any and all help. Thanks so much!
i was trying to find a phone case for the phone what model number is yours ?
If you're still searching I can try to make a rom dump, I have this phone as well brand new untouched or registered.
I'd just need a tutorial on the proper way to dump and extract the files so I can upload the boot.img
_
I've never used it cause I put the StandUp Wireless sim in my T-Mo InSeeGo 5G HotSpot and prefer to use my Galaxy S8 with Keyboard Cover Case and Unihertz Titan Pocket
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
PicelBoi said:
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
Click to expand...
Click to collapse
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
In fastboot not fastboot d do
Fastboot flash unlocking
And it'll ask ya if u agree bs....
& Click yes.
Mtkclient unlocks bootloader as well
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
PicelBoi said:
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
Click to expand...
Click to collapse
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
mee too
defcondoc said:
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
Click to expand...
Click to collapse
Yea, will post it later this day! Do you need anything else like my super partition?
PicelBoi said:
Yea, will post it later this day!
Click to expand...
Click to collapse
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
PicelBoi said:
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
Click to expand...
Click to collapse
I was able to get a bunch of GSI's that work with it, including the phone you posted, but I was looking to get root and found a couple pre-rooted GSI's that work as well. Newer ones do work as well I has 13 rooted and working. However, I liked the Pixel ROMs the best and would prefer to install those instead and then root. So I need the firmware for that so I can patch a modified boot.img.
PicelBoi said:
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
Click to expand...
Click to collapse
Thank you. I understand and have a lot of experience with this. However, I still never understood why there is two Fastboot's.
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
atsalchenberg said:
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
Click to expand...
Click to collapse
Are you looking for a good GSI ROM?
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
But yes I am indeed looking for a good running a12 rom
atsalchenberg said:
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
Click to expand...
Click to collapse
I completely messed up one messing with partitions and it took many tries trying to get to was able to still get to the bootloader fastboot and then recovery to fastbootD. You should be able to get it booted into fastbootd and flash as it seems you can.
Try the one below. you should be able to find it with a google search. If you can't let me know and I will try to look and see where I downloaded it from as I cannot remember where I found it.
I've tried many GSI ROM's Some boot fully, some only boot to the boot screen and some won't boot at all.
I'm using 13 rooted LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
It is vanilla. I can't remember if there is a GAPPS version or not. But you can load it all after with magisk. But its rooted.
I still would like if picelboi could share the stock rom, so we can have a boot.img. I would like to try other ROM's that are not PRE-Rooted.
atsalchenberg said:
But yes I am indeed looking for a good running a12 rom
Click to expand...
Click to collapse
I can't remember which A12 I had working but I was looking for root and the one A12 that was prerooted I had issues with so I went to A13.
This is an A13. LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
There may be a newer version of it now.
Also, these phones seem have that internet connect issue with some GSI ROMS and this is one of them I think, they connect to wifi but they won't actually connect to internet, but there is a easy fix for it.
Hey y'all,
I'm switching back to Android after 3 years on iOS and I'm a bit stuck on some changes.
First off, battery life on OOS was terrible and they ended support for OP7Pro this year, with no more major (or even security updates) so I decided to get a custom ROM, and I got this Pixel Experience ROM from here. I'm stuck with a few things:
Trying to root it, looks like the procedure is as simple as patch the boot image in that link with Magisk and flash it from the bootloader via "fastboot flash boot patched.img" but every time I do that and reboot, I get the 1+ splash screen and then nothing, black screen. If I boot back in bootloader and flash the original boot image via "fastboot flash boot original.img" it boots again. Same happens if I just run "fastboot boot patched.img", completely black until I reboot. Does anyone know what could be going wrong here?
Is there any way to install TWRP and make a NAND backup with this ROM? I've been out of the game for a while and I'm confused about why there's no recovery partition but there's A and B partitions, and I keep reading that TWRP can't decrypt data or something like that (I'm pretty sure it could 3 years ago tho)
Thanks!
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
dragancla said:
boot image in that link
Click to expand...
Click to collapse
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
TheMystic said:
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
Click to expand...
Click to collapse
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
dragancla said:
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
Click to expand...
Click to collapse
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
billperrotta said:
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
Click to expand...
Click to collapse
I already have Pixel Experience installed, so my bootloader is unlocked. Has been since I bought the phone 3 years ago
TheMystic said:
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
Click to expand...
Click to collapse
Google yielded no results, decided to post here to see if anyone else ran into this, I'll try to extract it myself somehow.
Coming out of left field but maybe you need to return to stock with bootloader unlocked. Flash 12 ota then rewipe for PE to get 12 latest firmware? https://www.xda-developers.com/oneplus-7-7t-end-of-life-final-update/
used to flash otas through TWRP when I had a rooted op5T with an unlocked bootloader. So Sad, Oxygen was so good till this last crummy update. Now they are forcing my hand to return to custom roms since OP insists on abandoning Support for the best phone they ever made.
Nothing worked, so I fixed it by wiping the phone and starting from scratch. Guess something bugged out.
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
ill probably flash the ota back to twelve through twrp. then flash pixel experience recovery over that when I wipe and start over after the downgrade and bootloader unlock.
billperrotta said:
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
Click to expand...
Click to collapse
I was on latest stock (12) before I started doing this. Had my bootloader unlocked since Android 9. Since it's impossible to do anything without unlocking it, that's your first step. I posted the link to PE website in my first post. Didn't copy any partitions. I just installed it and rooted it with a few commands from terminal (with the phone connected):
adb reboot bootloader
fastboot flash boot BOOT.img
fastboot reboot recovery
-- on the phone: wipe data, select install from sideload --
adb sideload ROM.zip
adb reboot
-- on the phone: wait for it to boot, enable developer options --
adb install MAGISK.apk
adb push BOOT.img sdcard/Download
-- on the phone: patch the boot image with Magisk --
adb pull sdcard/Download/magisk_patched-25200_xxxxx.img
adb reboot bootloader
fastboot flash boot magisk_patched-25200_xxxxx.img
fastboot reboot
That's it, installed and rooted. Stop at step 6 if you don't want root.