Related
Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.
Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.
I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.
"fastboot reboot" worked perfectly for me!
Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings
Contact me in discord.
Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.
Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!
szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....
Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???
Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?
equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk
Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk
Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
First fastboot stucked
Second no partition found
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GM1911 using Tapatalk
You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.
redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10
hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.
redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.
hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.
redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.
Hey! long story short. My phone wont boot slot B (witch is the location my primary Os is installed.) it reboots itself immediately after booting and switches back to slot A where it starts to load H2 OS, but in the end it stucks at loading screen forever.
Full details here:
It started when i decided to update the OS to android 10. So first i wanted to update the TWRP (3.2.3-1 is the older one, and i needed to install: 3.3.1-2).
I downloaded the latest update, backed up the recovery (all of it, just in case).
Then, keep in mind, i by mistake installed the same installer as i already had! I by mistake installed the same 3.2.3-1 version, from an installer i had earlier when i rooted the phone in the past.
In theory, nothing could go wrong. But there you have it, it stuck on TWRP. i just could not boot to system.
so i decided to restore from TWRP backup. Now the problem only worsened!
First, not just that the system doesn't loads (apparently, it is installed in slot B), it is forcing to load to slot A, every time i boot the phone. And it loads H2 OS, well not really loads, because it is loading for 20 minutes now and nothing happens.
Second, slot A is "only for reading" and everything is encrypted, so i can pretty much can't do a thing there, including restoring from backup again.
Third, every time i try to switch to slot B, in the recovery it switches, but as soon as i reboot (doesn't matter if i reboot to recovery, fastboot or system) the phone just restarts immediately after boot, apparently switches back to slot A in background, and tries to load H2 OS again. an i know that because i try to go into recovery after that and i see it is in slot A once again.
Click to expand...
Click to collapse
please help me with it!:crying:
Thanks!
The issue might be that official TWRP does not support Android 10 yet. You probably needed unofficial mauronofrio twrp. However, I am not sure if there is a clean way out of this situation. Maybe if you flash the right twrp it will just boot?
What do you mean "everything is encrypted and I cannot do much there"? Data is encrypted with your password, isn't it?
[email protected] said:
The issue might be that official TWRP does not support Android 10 yet. You probably needed unofficial mauronofrio twrp. However, I am not sure if there is a clean way out of this situation. Maybe if you flash the right twrp it will just boot?
What do you mean "everything is encrypted and I cannot do much there"? Data is encrypted with your password, isn't it?
Click to expand...
Click to collapse
how to properly flash the twrp?
and for your question.
the thing is, it doesn't gives me a password. it automatically gets into here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fenixsword said:
how to properly flash the twrp?
and for your question.
the thing is, it doesn't gives me a password. it automatically gets into here:
Click to expand...
Click to collapse
If you click "Read Only" doesn't it ask you the password then? I swear I have done this today when recovering from a poor magisk module...
I am actually not sure if you want to keep it read only or not, but I think no matter which option you select it promts you for a password
EDIT: Sorry, got distracted by the picture and missed the question. I looked at some threads and the process of upgrading seems to be potentially complicated if you have Magisk. Read more here. And maybe here.
Maybe if you boot into bootloader, run "fastboot set_active a" and then "fastboot flash boot_a <recovery_filename>.img" and everything will just work. Maybe it won't. Replace "a" with "b" in both commands if you are trying to boot into b.
TWRP 3.3.1-17 Q Unofficial by mauronofrio
[email protected] said:
If you click "Read Only" doesn't it ask you the password then? I swear I have done this today when recovering from a poor magisk module...
I am actually not sure if you want to keep it read only or not, but I think no matter which option you select it promts you for a password
Click to expand...
Click to collapse
and yet again, it doesn't asks for pasword, and wvwry folder i look to restore, looks like this:
meaning it is encrypted.
is there a way to reinstall TWRP from PC using command prompt, using adb or something like that?
fenixsword said:
and yet again, it doesn't asks for pasword, and wvwry folder i look to restore, looks like this:
meaning it is encrypted.
is there a way to reinstall TWRP from PC using command prompt, using adb or something like that?
Click to expand...
Click to collapse
Hm, interesting.
IF YOUR DATA IS ON THE LINE, DO NOT LISTEN TO ME. I do not know how twrp backup/restore works. Maybe wait for someone more knowledgeable to come in if you are worried about the data. But if you are sure that everything is safe on your pc somewhere, feel free.
Yes, please see my edit. You can do it through fastboot. You can use the respective section here for inspiration.
Did you had the password block on phone?
Just answer me, do u know the decrypt data? Its the password which u use to unlock phone
whatsinside said:
Did you had the password block on phone?
Just answer me, do u know the decrypt data? Its the password which u use to unlock phone
Click to expand...
Click to collapse
i'll answer detailed.. At start, while TWRP was working and it could launch slot B (it's where my OS initially was installed), it asked me for the phones password.
After backing up TWRP and trying to update it, it failed to launch OS, so i tried to restore from backup.
After restoring, it just couldn't start slot B at all (OS nor recovery) and it switched to slot A.
in slot A though, it didn't asks me for password, and encrypted data right away.
Now at the moment,after trying to flash TWRP to both slots, slot A don't launch recovery, the phone seems like it's connected to PC and works but screen is black, and the problem with slot B stays the same (switches right away to slot A)
you really can help with that? :silly:
fenixsword said:
i'll answer detailed.. At start, while TWRP was working and it could launch slot B (it's where my OS initially was installed), it asked me for the phones password.
After backing up TWRP and trying to update it, it failed to launch OS, so i tried to restore from backup.
After restoring, it just couldn't start slot B at all (OS nor recovery) and it switched to slot A.
in slot A though, it didn't asks me for password, and encrypted data right away.
Now at the moment,after trying to flash TWRP to both slots, slot A don't launch recovery, the phone seems like it's connected to PC and works but screen is black, and the problem with slot B stays the same (switches right away to slot A)
you really can help with that? :silly:
Click to expand...
Click to collapse
Restore from twrp is broken. Everything on slot b is gone but your data is there. You must install the same oos version you had on slot b to fix slot b. Then you boot into and do first time setup. Reboot to twrp and restore data only.
Try to enter settings and terminal, and type "decrypt [password]" or "twrp decrypt [password]
MrSteelX said:
Restore from twrp is broken. Everything on slot b is gone but your data is there. You must install the same oos version you had on slot b to fix slot b. Then you boot into and do first time setup. Reboot to twrp and restore data only.
Click to expand...
Click to collapse
ok.. i get what i need to do.. is there a guide on how to do so properly, so i wont mess up things even more? lol
The easy way would be if you have otg cable to jump drive with stock oos, twrp, and root. If not, then adb in twrp is your friend.
MrSteelX said:
The easy way would be if you have otg cable to jump drive with stock oos, twrp, and root. If not, then adb in twrp is your friend.
Click to expand...
Click to collapse
so i do have OTG cable. But i need a more vivid explanation on how to install stock os on it. or how to use adb in TWRP, if TWRP doesn't load on any slot.
The pictures look like you still have twrp. From twrp, you install stock rom twrp. Reboot recovery. Root and boot into system. The jump drive is because it will not be encrypted in twrp.
MrSteelX said:
The pictures look like you still have twrp. From twrp, you install stock rom twrp. Reboot recovery. Root and boot into system. The jump drive is because it will not be encrypted in twrp.
Click to expand...
Click to collapse
that's the problem though.. TWRP is gone, that's what i tried to tell you
first i need a way to flash recovery, then to do what you are suggesting.
You put phone in fastboot mode. The fastboot boot twrp.Img
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 should help
MrSteelX said:
You put phone in fastboot mode. The fastboot boot twrp.Img
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 should help
Click to expand...
Click to collapse
ok, i'll try it and update with the results, Thanks!
do you think i will be able to recover all the data from the phone?
fenixsword said:
ok, i'll try it and update with the results, Thanks!
do you think i will be able to recover all the data from the phone?
Click to expand...
Click to collapse
maybe?
Global/US OnePlus 9 Unbricking Guide
Tested and used on a LE2115 variant device.
YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)
Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
Step 2: Download the MSM tool.
The proper MSM tool can be found here.
I'd recommend using Internet Download Manager to speed it up.
Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
Step 3: Install the right drivers. (If they aren't installed)
The proper drivers can be found here.
Use the readme.txt file in the driver zip, it'll explain how to do everything.
Step 4: Run the "MsmDownloadTool V4.0.exe"
Set the dropdown to "Others" and click next.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
Click on "Start" once your phone is detected.
Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!
Errors
If an error occurs, don't worry! See here for the potential errors and how to solve them.
Sahara Communication Failed
When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
Install this app.
When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
Go into settings, and enable Advanced Mode (this is req'd)
Go to the main page, and click download update.
When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
Congrats! You fixed it!
If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
akboy7015 said:
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
Click to expand...
Click to collapse
Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
panoramixmeister said:
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
Click to expand...
Click to collapse
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks
winterfoxx said:
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
Click to expand...
Click to collapse
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
So sad , I am in the same situation!
Did you figured it out ??
from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
Congrats! You fixed it!
panoramixmeister said:
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
Click to expand...
Click to collapse
Congrats! I'm glad I was able to help
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
Erm, try factory resetting it in twrp
winterfoxx said:
Erm, try factory resetting it in twrp
Click to expand...
Click to collapse
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me
the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
papad13 said:
So sad , I am in the same situation!
Did you figured it out ??
Click to expand...
Click to collapse
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
allenjthomsen said:
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
Click to expand...
Click to collapse
"a12" you talked aboit open beta? or we have official oxygen android 12? thx
iaio72 said:
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
Click to expand...
Click to collapse
Can you help finding the “param bin file global”
Please ?