hello I am currently in need of of some serious help right now I have a one plus 7 pro tmobile variant and I switched it into international with twrp and all that after that I started messing with the twrp settings and the phone wouldent boot up but would stay in fastboot mode luckily I could just switch to different slot I was on a now im on b but now I tried to remove twrp and tried to get the phone back to normal I think both slots are messed up both slot a and b wont boot the phone and the phone just keeps rebooting itself into fastboot mode I cant go into recovery and I cant go into anything but fastboot mode I locked the bootloader to see if it will do anything now its still in fastboot mode and I cant flash anything because the phone wont unlock its bootloader now I don't know what to do pls help it would be greatly appreciated
@AshAe
Being on slot B to leave fastboot mode try
Code:
fastboot devices
fastboot --set-active=a
to boot device to (normal) Android OS kept in slot A: wait for response OKAY before re-starting phone !!!
BTW:
TWRP once installed can never get uninstalled, unless you re-flash Stock ROM.
jwoegerbauer said:
@AshAe
Being on slot B to leave fastboot mode try
Code:
fastboot devices
fastboot --set-active=a
to boot device to (normal) Android OS kept in slot A: wait for response OKAY before re-starting phone !!!
BTW:
TWRP once installed can never get uninstalled, unless you re-flash Stock ROM.
Click to expand...
Click to collapse
slot a dosent work either
AshAe said:
slot a dosent work either
Click to expand...
Click to collapse
Because fastboot obviously is working, what means you can enter device's bootloader, run
Code:
fastboot devices
fastboot boot twrp.img
to get access to TWRP: from there re-flash phone with its Stock ROM
Note: It's NO GOOD IDEA to install TWRP on Android with A/B-ed partition system.
Related
Hey guys, I hope you know what to do.
I just got my oneplus 7 pro and I want to install a custom ROM, so my device state is unlocked now
but I tried to boot a twrp.img and got stuck at the fastboot mode. So I restarted the phone and then tried to switch to my inactive slot, which is slot a
because I'm already on slot b. Unfortunately no matter which android sdk I download, there is no set command for fastboot.
So I don't know how to follow the fastboot set-active=a line :/
Are there any solutions to this?
Alright, I somehow had to use the powershell commands as admin
So a change of slots wasn't even necessary!
I have a OnePlus One 7 pro GM 1915. It is sim and bootloader unlocked. Oem button was not greyed out but was not not rooted. I wanted it rooted so I accidentally deleted the partitions during the process. Now I'm stuck at fast boot screen none of the bricked options seems to work. I don't believe I have any recovery any system files or anything left on it anyone that knows a way please..
it's a it's the nebula 12 gig version dying to be using it
tbaybucs said:
I have a OnePlus One 7 pro GM 1915. It is sim and bootloader unlocked. Oem button was not greyed out but was not not rooted. I wanted it rooted so I accidentally deleted the partitions during the process. Now I'm stuck at fast boot screen none of the bricked options seems to work. I don't believe I have any recovery any system files or anything left on it anyone that knows a way please..
it's a it's the nebula 12 gig version dying to be using it
Click to expand...
Click to collapse
you have 3 options to choose from. 1. in fastboot mode just change to other slot "fastboot --set-active=a" or b. 2. in fastboot mode flash a fastboot rom like https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 3. the get me out of f***** mode msm tool here https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595. make a choose and remember, NEVER delete system, vender, and efs. that will lead to very bad times.
MrSteelX said:
you have 3 options to choose from. 1. in fastboot mode just change to other slot "fastboot --set-active=a" or b. 2. in fastboot mode flash a fastboot rom like https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 3. the get me out of f***** mode msm tool here https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595. make a choose and remember, NEVER delete system, vender, and efs. that will lead to very bad times.
Click to expand...
Click to collapse
i have tried and tried...i believe its the drivers they show android bootloader interface and kedacom usb device.
at this point ill pay to get my opo 7pro nebula 12 gig up and running its been months now
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
jungl1st said:
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
Click to expand...
Click to collapse
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
greenys' said:
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
Click to expand...
Click to collapse
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
jungl1st said:
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
Click to expand...
Click to collapse
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
indeeed, custom recovery is the turning point to recover almost anything ! given the point that one manages to install it in the first place
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
Hi, I actually managed to flash the recovery, how ever it seem not to properly overwrite the original recovery.
I mean, i can flash and boot in to TWRP, only once at a time, once I exit TWRP and reboot into recovery, I land into the Realme recovery again !!!!! dont know whats wrong
hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help
Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.
https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide
One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader
I've been using an Asus Rog Phone 5 for some time now and I really like it. Original WW version. Unlocked bootloader and installed magisk without major hurdles. I could carry over root by patching boot image in the inactive slot in case of a new firmware version.
I've just tried to upgrade from Magisk 23.0 to 24.1 and unfortunately it didn't installed itself into the boot image. I assumed I have to repatch the boot image using the new magisk and reflash. I extracted the boot image from the payload and patched it successfully in magisk app.
Now I have a problem accessing the phone in fastboot mode. I have no problem entering fastboot mode: first entering the bootloader and selecting fastboot mode. However I see no activity over the USB port and the phone is not recognized by the computer (either from windows or linux). If I boot into the system I can see the phone in adb mode. It responds and I can issue commands - for example boot the bootloader. But no signs of traffic in fastboot mode.
Am I missing something? How I may flash an image if I cannot access the phone in fastboot mode? Please let me know if you have any ideas how to solve this situation.
Thanks: Dw.
Don't enter Fastboot (Fastbootd) from the bootloader,Just boot into bootloader and try sending Fastboot commands from there. If you're connection & drivers are in good shape, you should be sorted...
use the side port to communicate with the phone in fastboot mode.
yurishouse said:
use the side port to communicate with the phone in fastboot mode.
Click to expand...
Click to collapse
I'm officially an idiot. Thanks for the heads up...
Andrologic said:
Don't enter Fastboot (Fastbootd) from the bootloader,Just boot into bootloader and try sending Fastboot commands from there. If you're connection & drivers are in good shape, you should be sorted...
Click to expand...
Click to collapse
I tried to use the wrong port - and I'm banging my head against the wall...