There have been multiple reports of people bricking their devices after flashing a GSI with the DSU Loader found in Developer Options. In fact, I was probably the first guy to brick my N200 by installing a DSU to it. After installing a DSU and rebooting, the phone will attempt to boot the GSI and then show a Qualcomm CrashDump screen. After forcing the device to reboot, the phone will show a screen that says "Your device is corrupt" and will no longer boot. Although it is possible to boot into Fastboot mode, the phone will refuse to boot to recovery, and many Fastboot commands do not work since the bootloader is locked. Since there are no MSM tools available yet and the remote service team at OP support doesn't have the ROM files for this phone, your only option at this point would be to request a repair from OnePlus under warranty.
While it may be possible to use the DSU Loader on the N200 without bricking after unlocking the bootloader as shown in this thread, I still would recommend against it until unbrick tools are released.
Yes, if you attempt to use the DSU loader without unlocking the bootloader first, it appears it will fail verified boot since the GSI image is not signed on OnePlus.
Can you still boot into fastboot mode (hold vol down while booting)? You can try switching the active slot to a or b and see if it will boot that way.
Code:
fastboot --set-active=b
Also, if you can boot into recovery, try the "Erase everything" option.
EnumC said:
Can you still boot into fastboot mode (hold vol down while booting)? You can try switching the active slot to a or b and see if it will boot that way.
Code:
fastboot --set-active=b
Also, if you can boot into recovery, try the "Erase everything" option.
Click to expand...
Click to collapse
You can still boot into fastboot by holding the volume up+down buttons while booting. However the bootloader won't let you switch the active slot if the bootloader is locked.
Even if you select Recovery mode in fastboot mode, the phone will still display the device is corrupt error and refuse to boot into recovery.
lzgmc said:
There have been multiple reports of people bricking their devices after flashing a GSI with the DSU Loader found in Developer Options. In fact, I was probably the first guy to brick my N200 by installing a DSU to it. After installing a DSU and rebooting, the phone will attempt to boot the GSI and then show a Qualcomm CrashDump screen. After forcing the device to reboot, the phone will show a screen that says "Your device is corrupt" and will no longer boot. Although it is possible to boot into Fastboot mode, the phone will refuse to boot to recovery, and many Fastboot commands do not work since the bootloader is locked. Since there are no MSM tools available yet and the remote service team at OP support doesn't have the ROM files for this phone, your only option at this point would be to request a repair from OnePlus under warranty.
While it may be possible to use the DSU Loader on the N200 without bricking after unlocking the bootloader as shown in this thread, I still would recommend against it until unbrick tools are released.
Click to expand...
Click to collapse
While I'm guilty of Bricking my phone by doing exactly what you describe .. there's a little confusion on ... t-mobile locked phones and the ones bought unlocked from 1+ or Amazon....any difference in how to fix those 2.. I'm on a phone bought directly from 1+
Ethanvio said:
While I'm guilty of Bricking my phone by doing exactly what you describe .. there's a little confusion on ... t-mobile locked phones and the ones bought unlocked from 1+ or Amazon....any difference in how to fix those 2.. I'm on a phone bought directly from 1+
Click to expand...
Click to collapse
I'll answer my own question .. it don't matter .. I also tried switching from b to a but it won't allow it as it is locked
Ethanvio said:
I'll answer my own question .. it don't matter .. I also tried switching from b to a but it won't allow it as it is locked
Click to expand...
Click to collapse
Did you by any chance enable OEM unlock in the developer setting before it bricked? If you haven't tried already, what happens when you try to unlock the bootloader in fastboot?
EnumC said:
Did you by any chance enable OEM unlock in the developer setting before it bricked? If you haven't tried already, what happens when you try to unlock the bootloader in fastboot?
Click to expand...
Click to collapse
Won't allow it because it's locked .. so you can't unlock the bootloader. Hopefully oneplus will release the rom soon or there's a work around this
EnumC said:
Did you by any chance enable OEM unlock in the developer setting before it bricked? If you haven't tried already, what happens when you try to unlock the bootloader in fastboot?
Click to expand...
Click to collapse
No I did not unlock the oem in developer before all this
DSU runs fine once you are bootloader unlocked. I can confirm this myself.
There's a common sense
Flashing anything modified, even from stock, requires unlocked bootloader
BTW, I have mine rooted with patched kernel after bootloader unlocked
I wish I saw this post two weeks ago.
sahack said:
I wish I saw this post two weeks ago.
Click to expand...
Click to collapse
me too , even tho i knew of this place i went ahead blindly and did it ... now my phone is bricked and waiting for package from oneplus so i can send it for repairs .. i wish the rom was available .. this is a very easy fix
sahack said:
I wish I saw this post two weeks ago.
Click to expand...
Click to collapse
Dimitrimem said:
me too , even tho i knew of this place i went ahead blindly and did it ... now my phone is bricked and waiting for package from oneplus so i can send it for repairs .. i wish the rom was available .. this is a very easy fix
Click to expand...
Click to collapse
This thread is a whole 1 day old, so don't feel bad about missing it weeks ago.
I believe there's a stock ROM here:
Rooting Stock Firmware W/ Magisk
Once you have your bootloader unlocked (See edale1's post), you can get started! Disclaimer: * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...)...
forum.xda-developers.com
But I also believe you need your bootloader to already be unlocked to actually fix it. Not sure though.
edale1 said:
This thread is a whole 1 day old, so don't feel bad about missing it weeks ago.
I believe there's a stock ROM here:
Rooting Stock Firmware W/ Magisk
Once you have your bootloader unlocked (See edale1's post), you can get started! Disclaimer: * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...)...
forum.xda-developers.com
But I also believe you need your bootloader to already be unlocked to actually fix it. Not sure though.
Click to expand...
Click to collapse
at this point the rom wont be enough huh! .. the downlooad tool is also a must to fix the lock on the bootloader ...
i guess its worth saying this is for the fully paid one from the oneplus website here in US
so yeah i did exactly this and i just got the 1+ nord n200 5g ive tried everything including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
ThatNiggaDurk666 said:
so yeah i did exactly this and i just got the 1+ nord n200 5g ive tried everything including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
Click to expand...
Click to collapse
Have the T-Mobile or Metro variant? See this thread:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Have the unlocked variant? You're screwed. Contact OnePlus for a repair.
Posted possible answer Here
lzgmc said:
There have been multiple reports of people bricking their devices after flashing a GSI with the DSU Loader found in Developer Options. In fact, I was probably the first guy to brick my N200 by installing a DSU to it. After installing a DSU and rebooting, the phone will attempt to boot the GSI and then show a Qualcomm CrashDump screen. After forcing the device to reboot, the phone will show a screen that says "Your device is corrupt" and will no longer boot. Although it is possible to boot into Fastboot mode, the phone will refuse to boot to recovery, and many Fastboot commands do not work since the bootloader is locked. Since there are no MSM tools available yet and the remote service team at OP support doesn't have the ROM files for this phone, your only option at this point would be to request a repair from OnePlus under warranty.
While it may be possible to use the DSU Loader on the N200 without bricking after unlocking the bootloader as shown in this thread, I still would recommend against it until unbrick tools are released.
Click to expand...
Click to collapse
If you have a spare phone lying around, try flashing a GSI to see what custom ROM developers are up to these days. Since installing a GSI only requires Even with installing TWRP recovery, it only worked after I had successfully installed magisk on the device by flashing the magisk patched boot.
I just wanted to let you all know. If this happens to you, you CAN use the MSM recovery tool. I found the T-Mobile variants' EDL firmware in the OnePlus community repositories. Let me know if you need them, as I will upload them to a thread with a step by step recovery guide if needed. I had bricked my device by trying the GSI image through DSU Loader, but was successfully able to recover the device with the MSM tool
Related
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).
Hello sir,
I recently flashed a custom rom using twrp and successfully done, but then i thought to re-lock bootloader,
So, i did that using command
"fastboot flash oem lock"
and my device get bricked, it said the system has been destroyed
And screen get stuck in fastboot
I tried again flash twrp but nothing happened,
I also tried to flash by MiFlash tool but nothing happened,
Pls solve my problem
That's not a soft brick. That's a truly proper bricked device.
To relock a bootloader you must be 100% pure stock with no modifications whatsoever.
You can't relock a bootloader if you have a custom ROM installed.
The fact you locked the bootloader now opens up a lot of issues for you and the only way to recover is flashing in edl mode with a verified mi account.
In other words your going to have to look for someone with a verified account and give them remote access to your pc and probably have to pay them to get your device up and going again.
If you have a service centre near where you are you can try there but a person with a verified account is what you need.
Also you can't ask anyone here for it because paid services are against forum rules.
Always read up on stuff before attempting anything on your device.
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.
Ok , lemme cover my bases here... OnePlus 10t, Android 12, T Mobile. .
I have usb debugging on, oem unlock on, and device appears in ADB ... Newest platform tools, updated drivers.... When I run 'adb reboot bootloader', the phone shuts off, then I see 'fastboot mode' for like half a second , and it goes off and boots up normal. I can enter fastbootd .. but regular fastboot causes instant reboot! Can ANYONE help me with what I need to do? You can't unlock bootloader in fastbootd... So I need help figuring out how to make it NOT kick out of fastboot when I enter the command. (Usb 2.0)
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
I haven't heard about this before, is it a T-Mobile only thing? That seems really bad for oppo to do that...
Hurt Copain said:
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
Click to expand...
Click to collapse
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
beatbreakee said:
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
Click to expand...
Click to collapse
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
maamdroid said:
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
Click to expand...
Click to collapse
thank you ... i was waiting for the response from someone who had been in contact with them. I will mail them right away.