Develop Bugs

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!

Need Help For switching rom from china to global

hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11

guys please help me i m frustrated tried every available method on internet downloaded tons of file.

aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?

SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.

aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?

subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.

i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>

aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.

aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.

SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.

drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked

aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.

SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image

i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.

aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.

drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you

aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system

aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.

drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.

aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools

Question Stock Moto G30 stuck at bootscreen after reboot / How to rescue data

Hi dear community,
I have a new Moto G30 which is now does not boot and keeps getting stuck at bootscreen where the logo is, even after trying to boot for hours. This happened after a reboot where nothing special happened before. I have not installed any custom ROM, and have no idea why this is happening. There is no SD card in it, battery can not be taken out. I tried booting from stock recovery in all possible ways, nothing worked. Tried leaving it shut off for half a day.
Support say the only option is factory reset. However I need to get the data to my laptop before resetting. Is there a way to use Rescue and Smart Assistant for this? I can not boot the phone and can only boot in recovery. Or could I install TWRP or something via ADB sideload would allow me to then use ADB pull or something to get the photos, but TWRP is not yet available for G30?
Thank you!

cricket62 said:
Hi dear community,
I have a new Moto G30 which is now does not boot and keeps getting stuck at bootscreen where the logo is, even after trying to boot for hours. This happened after a reboot where nothing special happened before. I have not installed any custom ROM, and have no idea why this is happening. There is no SD card in it, battery can not be taken out. I tried booting from stock recovery in all possible ways, nothing worked. Tried leaving it shut off for half a day.
Support say the only option is factory reset. However I need to get the data to my laptop before resetting. Is there a way to use Rescue and Smart Assistant for this? I can not boot the phone and can only boot in recovery. Or could I install TWRP or something via ADB sideload would allow me to then use ADB pull or something to get the photos, but TWRP is not yet available for G30?
Thank you!
Click to expand...
Click to collapse
Did you enable adb debugging, in dev options before bootloop?

Did you enable adb debugging, in dev options before bootloop?
Click to expand...
Click to collapse
Hi unfortunately not, I only enabled "developer mode" but didnt think to enable ADB debugging as I was just getting to know the new phone and stock Android 11.

cricket62 said:
Hi unfortunately not, I only enabled developer mode but didnt think to enable ADB debugging as I was just getting to know the new phone and stock Android 11.
Click to expand...
Click to collapse
Is the Bootloader unlocked?

Use LMSA Rescue to download firmware.
You will see a screen that has the device's current firmware, and the firmware LMSA will download.
Make sure they are the same, you can post a screenshot of that if you are not sure.
Then use fastboot.exe to flash this
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then reboot the device.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
Is the Bootloader unlocked?
Click to expand...
Click to collapse
No, reason is since Lineage OS or TWRP are not yet build for G30 I wanted to keep the fully functional stock.
sd_shadow said:
Use LMSA Rescue to download firmware.
You will see a screen that has the device's current firmware, and the firmware LMSA will download.
Make sure they are the same, you can post a screenshot of that if you are not sure.
Then use fastboot.exe to flash this
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then reboot the device.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks so much!! I will try that and write results when I get to it! Have a good healthy day!

Hi Just wanted to update: I still need to set up the USB redirect of the fastboot device to the Windows virtual machine. So may take a bit longer for me to get to it.

No bootable a/b slot

Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.

glossallalia said:
Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.
Click to expand...
Click to collapse
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers

Thank you! Yes I did follow the preinstall instruction and used copy-partitions-20210323_1922.zip several times. But obviously messed it up somehow.
I was missing some of the things you mentioned so I’ll work on that and thanks again!

sd_shadow said:
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers
Click to expand...
Click to collapse
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers

glossallalia said:
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers
Click to expand...
Click to collapse
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.

sd_shadow said:
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.
Click to expand...
Click to collapse
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!

glossallalia said:
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!
Click to expand...
Click to collapse
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.

sd_shadow said:
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.
Click to expand...
Click to collapse
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.

glossallalia said:
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.
Click to expand...
Click to collapse
what is the file name of lineage.zip?

sd_shadow said:
what is the file name of lineage.zip?
Click to expand...
Click to collapse
LineageOS17.1Modified.img.xz
I went to Motorola website and flashed the firmware to restore the phone to its original state. I'll try lineage again in future and thank you!

General Bootloop pixel 6 pro

I got bootloop pixel 6 pro
Pc recognize it
Only adb devices and adb fastboot cmd work
Other cmd not work.
Can anyone help me

And always blackscreen. Nothing show or display

Have you enabled USB debugging?
To enable USB debugging you need to enable Developer Options in your phone first. To do this: Go to Settings > About phone > Software info > and then tap the build number about 7 times.
Edit: I can see you have downloaded the Android SDK Platform-Tools on the desktop. Try to run the command under the correct path ( C:\Users\XXXX\Desktop\platform-tools_r33.0.2-windows\platform-tools>

RhapsodyK said:
Have you enabled USB debugging?
To enable USB debugging you need to enable Developer Options in your phone first. To do this: Go to Settings > About phone > Software info > and then tap the build number about 7 times.
Click to expand...
Click to collapse
How will he do this when he is in a boot loop?

CRXed said:
How will he do this when he is in a boot loop?
Click to expand...
Click to collapse
Indeed. I have definitely lost my mind.

Use android flashtool. You can't downgrade on official a13 and I think you have to flash it to both slots or use flashtool
Android Flash Tool
flash.android.com

CRXed said:
How will he do this when he is in a boot loop?
Click to expand...
Click to collapse
Yes i have bootloader unlock. But totally blackscreen now. Any button do not work.

If ADB and Fastboot still work (and since your bootloader is unlocked), then @fil3s suggestion to use the Android Flash Tool is the best option to try.

fil3s said:
Use android flashtool. You can't downgrade on official a13 and I think you have to flash it to both slots or use flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Pc not recognize phone.

Nordnord said:
Pc not recognize phone.
Click to expand...
Click to collapse
Guess I misunderstood. Do ADB and Fastboot still work, or don't they? If they don't, you might want to edit your OP.
Nordnord said:
Only adb devices and adb fastboot cmd work
Click to expand...
Click to collapse

Nordnord said:
Pc not recognize phone.
Click to expand...
Click to collapse
Do you have the latest drivers and Platform Tools installed? Try different cables and/or ports?

Here screenshot

Yes driver and platform toos installed. I tried different cable and port.
Abd/fastboot devices cmd works but next like adb reboot bootloader cmd not works.

Nordnord said:
Yes driver and platform toos installed. I tried different cable and port.
Abd/fastboot devices cmd works but next like adb reboot bootloader cmd not works.
Click to expand...
Click to collapse
Are you using A to C cable?

If fastboot devices works type
Code:
fastboot reboot bootloader
Or use adb sideload

Nordnord said:
I got bootloop pixel 6 pro
Pc recognize it
Only adb devices and adb fastboot cmd work
Other cmd not work.
Can anyone help me
Click to expand...
Click to collapse
What were you trying to do, and at what point did this happen?
Is your phone recognized as a Android device, or is it showing up as something else?
Does holding down the Power button + Volume Down do anything?

Lughnasadh said:
Are you using A to C cable?
Click to expand...
Click to collapse
Yep

V0latyle said:
What were you trying to do, and at what point did this happen?
Is your phone recognized as a Android device, or is it showing up as something else?
Does holding down the Power button + Volume Down do anything?
Click to expand...
Click to collapse
Button combination not work
Not enter fastboot mode or recovery mode

fil3s said:
If fastboot devices works type
Code:
fastboot reboot bootloader
Or use adb sideload
Click to expand...
Click to collapse
Fastboot devices works
Adb reboot bootloader cmd not works

Nordnord said:
Fastboot devices works
Adb reboot bootloader cmd not works
Click to expand...
Click to collapse
Fastboot reboot bootloader cmd not works