Can't boot to recovery after uninstalling SuperSU!!! - Lenovo ZUK Z2 (Plus) Questions & Answers

Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]

kunalvirk said:
Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]
Click to expand...
Click to collapse
Use magisk and hide root for tez app

visheshjain25 said:
Use magisk and hide root for tez app
Click to expand...
Click to collapse
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....

kunalvirk said:
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....
Click to expand...
Click to collapse
Can you access fastboot

selvarajrajkanna said:
Can you access fastboot
Click to expand...
Click to collapse
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks

kunalvirk said:
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks
Click to expand...
Click to collapse
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM

selvarajrajkanna said:
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM
Click to expand...
Click to collapse
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....

kunalvirk said:
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....
Click to expand...
Click to collapse
You can't access abd until your phone is booted into android

Weird, normal here.

selvarajrajkanna said:
You can't access abd until your phone is booted into android
Click to expand...
Click to collapse
So is there any other solution available that can get my phone to woking state.....:crying:

kunalvirk said:
So is there any other solution available that can get my phone to woking state.....:crying:
Click to expand...
Click to collapse
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily

selvarajrajkanna said:
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily
Click to expand...
Click to collapse
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......

kunalvirk said:
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......
Click to expand...
Click to collapse
Happy to help

Related

Problems rooting, adb etc.

Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.
Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"
Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question
Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?
Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641

Help I bricked my Oneplus 3

Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!

How to wipe android partitons while NO access to Fastboot? PLZ help

Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp
pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.

Stuck on bootloader

I cannot exit my bootloader. Even if I choose to reboot to TWRP it gets me back at the same selection screen. I tried the other options as well but they didn't seem to work. HELP!
AeonClaw said:
I cannot exit my bootloader. Even if I choose to reboot to TWRP it gets me back at the same selection screen. I tried the other options as well but they didn't seem to work. HELP!
Click to expand...
Click to collapse
Reflash the recovery using adb
satyen_ said:
Reflash the recovery using adb
Click to expand...
Click to collapse
My PC is not recognizing my device in cmd. When I type adb devices it's shows no device detected and I have even installed the zuk drivers.
Qfil?
AeonClaw said:
My PC is not recognizing my device in cmd. When I type adb devices it's shows no device detected and I have even installed the zuk drivers.
Click to expand...
Click to collapse
When you are in bootloader, you should use fastboot command instead of adb.
And first, try to flash TWRP using: fastboot flashing recovery "YOUR TWRP IMAGE". If it works, flash rom like normal.
If that doesn't work, use QPST.

OnePlus 7T boot error after Android F.15 update

Hello, I downloaded and installed android beta update https://gauss-componentotacostmanua...22/08/03/b5192ec34f094ad9bb76e5554cd69f89.zip from https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-open-beta-2/amp/ and since then the device is just booting in loops and not going ahead. I get the boot reason error as attached. The boot logo has also changed.
My device did not had developer module enabled nor had I backed up any data from my mobile before installing the update.
I desperately want to recover data from my phone before formatting it. Please assist. Thanks a lot.
kiranlalge said:
Hello, I downloaded and installed android beta update https://gauss-componentotacostmanua...22/08/03/b5192ec34f094ad9bb76e5554cd69f89.zip from https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-open-beta-2/amp/ and since then the device is just booting in loops and not going ahead. I get the boot reason error as attached. The boot logo has also changed.
My device did not had developer module enabled nor had I backed up any data from my mobile before installing the update.
I desperately want to recover data from my phone before formatting it. Please assist. Thanks a lot.
Click to expand...
Click to collapse
Try to reboot into recovery, then normal reboot.
Did that already. No luck :-(
kiranlalge said:
Did that already. No luck :-(
Click to expand...
Click to collapse
Data must be formatted to boot
HueyT said:
Data must be formatted to boot
Click to expand...
Click to collapse
Sorry I cannot afford to format the device as I'm desperate to recover the data.
Take phone to repair shop to download data via adb commands using laptop
Also try switching slots in fastboot mode: "fastboot set_active other" and then "fastboot reboot"
HueyT said:
Take phone to repair shop to download data via adb commands using laptop
Click to expand...
Click to collapse
I have ADB utilities on my laptop. I connect my device to my laptop via USB cable and then do "adb devices" on the command prompt. It shows no devices. Perhaps this happens because my device was not rooted? Is there any other way I can access files on my device using adb?
HueyT said:
Also try switching slots in fastboot mode: "fastboot set_active other" and then "fastboot reboot"
Click to expand...
Click to collapse
Please can you elaborate a little more on this? Where to switch slots? Can we connect over WhatsApp or a ZOOM call please?
kiranlalge said:
Please can you elaborate a little more on this? Where to switch slots? Can we connect over WhatsApp or a ZOOM call please?
Click to expand...
Click to collapse
Enable USB debugging in developer options
Spoiler
HueyT said:
Enable USB debugging in developer options
Click to expand...
Click to collapse
The device needs to be booted successfully to enable USB debugging. Booting is the fundamental problem. How can I enable USB debugging without booting the device?
The device needs to be booted successfully to see this screen. Booting is the fundamental problem. How can I enable USB debugging without booting the device?
Phone needs to be off. Try holding down vol. Down button, power button til it reboots into bootloader mode while plugged into usb-c to USB-a cable to laptop. Then type "fastboot devices" on laptop while changed into adb subdirectory with "command C:/ prompt"
HueyT said:
Phone needs to be off. Try holding down vol. Down button, power button til it reboots into bootloader mode while plugged into usb-c to USB-a cable to laptop. Then type "fastboot devices" on laptop while changed into adb subdirectory with "command C:/ prompt"
Click to expand...
Click to collapse
I appreciate you trying to help me promptly. Thank you.
I tried doing what you advised. The command did not show anything. Photos attached.
You need to unlock bootloader by using Superboy msmtool, but will lose all data
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
You shouldn't mess with oos12 with locked bootloader as it can lose data
You could try to manually flash each file using fastboot (fastboot devices must show a number so install correct OnePlus and adb drivers for windows 10) --use payload dumper to extract all files from payload.bin from Indian op7t rollback zip below. Just don't do "fastboot -w" as that will format your data
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
HueyT said:
You could try to manually flash each file using fastboot (fastboot devices must show a number so install correct OnePlus and adb drivers for windows 10) --use payload dumper to extract all files from payload.bin from Indian op7t rollback zip below. Just don't do "fastboot -w" as that will format your data
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
Click to expand...
Click to collapse
Thank you. I have just started downloading this file (2.6 GB) on my laptop. Yes I am very keen to save my data before formatting. Please can you guide on the next steps to do after the download completes?
I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
kiranlalge said:
Thank you. I have just started downloading this file (2.6 GB) on my laptop. Yes I am very keen to save my data before formatting. Please can you guide on the next steps to do after the download completes?
I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
Click to expand...
Click to collapse
Right OK so I have downloaded the ZIP package and have also managed to extract the payload.bin file. See file contents in the attached image.
Please can you guide on the next steps hereafter? I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
kiranlalge said:
Right OK so I have downloaded the ZIP package and have also managed to extract the payload.bin file. See file contents in the attached image.
Please can you guide on the next steps hereafter? I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
Click to expand...
Click to collapse
I think this is getting closer. I managed to install drivers as in the attached. Please take a look. 3 out of 4 have yellow triangles not sure if that means any issue. The 4th one appears only when I connect the device to laptop via a cable.
Only works on win10/11
HueyT said:
Only works on win10/11
Click to expand...
Click to collapse
OK. I still tried on Windows 7 and I got the attached. If I manage to change the slot from a to b using "https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/", then will I loose any data? Again, I'm very keen to retrieve my data.
kiranlalge said:
OK. I still tried on Windows 7 and I got the attached. If I manage to change the slot from a to b using "https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/", then will I loose any data? Again, I'm very keen to retrieve my data.
Click to expand...
Click to collapse
Yes, unlocking BL will wipe data
HueyT said:
Yes, unlocking BL will wipe data
Click to expand...
Click to collapse
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
kiranlalge said:
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
Click to expand...
Click to collapse
All you can do is keep repeating reboot to recovery, normal reboot, reboot to bootloader, reboot to recovery, normal reboot, while praying and hoping that your phone boots up.
kiranlalge said:
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
Click to expand...
Click to collapse
Does "fastboot devices" give you numbers and letters?
HueyT said:
Does "fastboot devices" give you numbers and letters?
Click to expand...
Click to collapse
Yes. It printed the serial no. of my device.

Categories

Resources