Database Users

My OPT Stuck in 1+ logo and not enter to TWRP and cannot get inside bootloader

Please help I can Open my OPT

Ahmed Shawky said:
Please help I can Open my OPT
Click to expand...
Click to collapse
Please I ned any help
My mobile not open

I can not Unlock the boatloader

Huh. There is no information on your post. What do you think XDA is? Can't help until you tell your situation.

Nobody can solve your problem until you explain what happened.
Sent from my ONE A2003 using Tapatalk

Please elaborate on what happened to your phone. Till then check these links out for a possible fix:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
http://forum.xda-developers.com/oneplus-2/general/guide-to-stock-t3341130
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

I have similar problem, so maybe not generating new threat...
I got OP2 from friend. He used Oxygen 2.x (don't know exactly) and decided to flash some custom ROM. And something went wrong
He brought me today his phone and:
- fastboot works,
- device is locked and impossible tu unlock (FAILED (remote: oem unlock is disabled))
- after 2 hours of work I got stock recovery working (using some Chinese Qualcomm recovery tool).
But: I can't unlock BL, I can't flash anything via fastboot (because ->locked), ADB doesn't work too (cant push any file to devices).
When turning on phone it's in bootloop, but I can enter fastboot or stock recovery.
I tried almost all solutions from her and OP forums, but everything false because of locked BL.
ANY ideas? My short knowledge ends here There is probably no any data in device (no system, userdata etc.).
I don't have USB-C pendrive / cable so I cant flash anything from stock recovery. If I'll get USB-C pendrive will it be possible to flash stock ROM with stock recovery?

Does it show up in fastboot devices?
Sent from my Nexus 7 using Tapatalk

Try first-aid for oneplus 2. It's worked for me twice before. It's on XDA but I don't have a link. Search for it. I'm pretty sure it'll work.

EggZenBeanz said:
Does it show up in fastboot devices?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, It shows. But not much possible to do because of locked BL.
McCullyCullen said:
Try first-aid for oneplus 2. It's worked for me twice before. It's on XDA but I don't have a link. Search for it. I'm pretty sure it'll work.
Click to expand...
Click to collapse
I tried but with no success. All this tools works flashing .img's from fastboot. It's useless for me...

Have you tried the fastboot oem unlock using the device id as part of the command string?
Sent from my ONE A2003 using Tapatalk

No. How to do this?

vonski said:
Yes, It shows. But not much possible to do because of locked BL.
I tried but with no success. All this tools works flashing .img's from fastboot. It's useless for me...
Click to expand...
Click to collapse
try this...... "fastboot -i 0x2a70 oem unlock-go"
worked for me

Thank, but :
C:\Android_sdk\sdk\platform-tools>fastboot -i 0x2a70 oem unlock-go
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.007s
Same...

It sounds like the ability to unlock the bootloader is disabled in developer options. I think, but I'm only guessing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONE A2003 using Tapatalk

Yes, but I can't boot to system (probably memory is empty- no data) and switch OEM Unlock.
I've got only fastboot and stock recovery.

do any of these help you? I guess you could say your phone is hard bricked due to not booting to OS and not having TWRP recovery?
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

I used this tutorial but I can't get device correctly installed as Qualcomm. I'll try on other pc.
Tapatalk @ OnePlus X

vonski said:
I have similar problem, so maybe not generating new threat...
I got OP2 from friend. He used Oxygen 2.x (don't know exactly) and decided to flash some custom ROM. And something went wrong
He brought me today his phone and:
- fastboot works,
- device is locked and impossible tu unlock (FAILED (remote: oem unlock is disabled))
- after 2 hours of work I got stock recovery working (using some Chinese Qualcomm recovery tool).
But: I can't unlock BL, I can't flash anything via fastboot (because ->locked), ADB doesn't work too (cant push any file to devices).
When turning on phone it's in bootloop, but I can enter fastboot or stock recovery.
I tried almost all solutions from her and OP forums, but everything false because of locked BL.
ANY ideas? My short knowledge ends here There is probably no any data in device (no system, userdata etc.).
I don't have USB-C pendrive / cable so I cant flash anything from stock recovery. If I'll get USB-C pendrive will it be possible to flash stock ROM with stock recovery?
Click to expand...
Click to collapse
Fastboot this, it will DELETE EVERYTHING(no exceptions) (maybe except firmware) and install seraph08's cm13.
https://s.basketbuild.com/devs/Seraph08/oneplus2/fastboot img files
or flash stock OOS2.x official via stock recovery(if MTP or ADB works in stock recovery)
No idea about USB OTG, try dont buy. Might work in TWRP, dont think itll work on stock
or try the soft brick recovery on his basketbuild or other various available threads
Edit: you said fastboot works and then you said it doesnt work, confirm.

I used other PC and other tool including system.bin and userdata.bin. And it finally worked. Unbricked

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.

How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.

Hmm....
Have you tried rebooting to fastboot using adb?

Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times

Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?

elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.

Dc unlocker needs cash and it doesn t always work.

I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.

3 button upgrade doesn't work either.

I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.

Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method

shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..

Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain

Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!

I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.

Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.

elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??

Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.

I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

P10 black screen bricked!!

I tried to flash a custom rom (MorfuZ) and after installation is complete, the phone reboot and stucked on black screen. I can't get to fastbook or recovery screen. The MultiTool software recognises the device. I tried flashing trough the ''Unbrick'' method and it seems the process is completed, but the phone won't boot. I tried to turn it up but even the screen is not turned on. I have no red or green led as the others threads says (yes I've read a lot of them). The only sign of life is that my PC detects it as "Fastboot2.0" and it's supposed that I flash cust, boot, system and recovery imgs but nothing happens at all. It sounds it's rebooting and the cmd also says that but there is no change. My phone is LATAM version (WAS-LX3). Already bootloader unlocked, installed TWRP and rooted (magisk). My laptop recognises the device the (prompts sounds when connected.)
I tried flashing boot, recovery, system from this .zip file Warsaw-L23_C605B172_Firmware_Panama_Bolivia_Peru_Chile_Colombia_Guatemala_El Salvador_Nicaragua_Honduras_Nonspecific_Android7.0_EMUI5.1_0501 but I couldn't find the CUST file to flash with Multitool software.
This is what I get after flash using MultiTool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Plaseas Help !!!

jics91 said:
I tried to flash a custom rom (MorfuZ) and after installation is complete, the phone reboot and stucked on black screen. I can't get to fastbook or recovery screen. The MultiTool software recognises the device. I tried flashing trough the ''Unbrick'' method and it seems the process is completed, but the phone won't boot. I tried to turn it up but even the screen is not turned on. I have no red or green led as the others threads says (yes I've read a lot of them). The only sign of life is that my PC detects it as "Fastboot2.0" and it's supposed that I flash cust, boot, system and recovery imgs but nothing happens at all. It sounds it's rebooting and the cmd also says that but there is no change. My phone is LATAM version (WAS-LX3). Already bootloader unlocked, installed TWRP and rooted (magisk). My laptop recognises the device the (prompts sounds when connected.)
I tried flashing boot, recovery, system from this .zip file Warsaw-L23_C605B172_Firmware_Panama_Bolivia_Peru_Chile_Colombia_Guatemala_El Salvador_Nicaragua_Honduras_Nonspecific_Android7.0_EMUI5.1_0501 but I couldn't find the CUST file to flash with Multitool software.
This is what I get after flash using MultiTool
Plaseas Help !!!
Click to expand...
Click to collapse
If You still have TWRP and if you are on Emui 8 use HWOTA8 method, otherwise if you are on Emui 5 use HWOTA7 to flash your build. As you have already unlocked bootloader the first step in script will be automatically skipped.
Its very easy just follow my video tutorial. Instruction for HWOTA7 is on Serbian but you have instruction on English and some things are logical just view video.
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Good luck!

Thanksfor the reply. My phone won't boot to recovery nor fastboot mode. I can't turn it on or off, the screen does not display anything, it just sounds when I plug it to the pc. No led light or boot logo

jics91 said:
Thanksfor the reply. My phone won't boot to recovery nor fastboot mode. I can't turn it on or off, the screen does not display anything, it just sounds when I plug it to the pc. No led light or boot logo
Click to expand...
Click to collapse
Yes I understand u must use DC phoenix and test point method after that Hcu client to restore Imei, seriall. Dc phoenix and Hcu client are about 20 usd credit for 3 days. But for test point u must open the cover and on board find test point, conect it, plug usb and run Dc phoenix to restore all partitions. Its not so easy but phone could be fixed.
Poslato sa WAS-LX1 uz pomoć Tapatoka

do u have the location of testpoint of this phone

abcrino50 said:
do u have the location of testpoint of this phone
Click to expand...
Click to collapse
Here it is
Sent from my WAS-LX1 using Tapatalk

it dosent work

p10 lite
Alexxxx1 said:
Here it isView attachment 4533946
Sent from my WAS-LX1 using Tapatalk
Click to expand...
Click to collapse
Alexx da li možeš da uradiš p10 lite bricked u Beogradu da ti nekako dostavim i koliko bi koštalo. Pozdrav >Milan

Question Help! Stuck in fastboot mode can't do anything

So i try to use the DSU Loader found in Developer Options to flash a GSI, but i forget to unlock the OEM and turn on the usb debug.
After installing a DSU and rebooting, the phone will attempt to boot the GSI but it shows "Your device is corrupt" and will no longer boot.
That said, the phone boot to fastboot mode automatically. But all the options under fastboot is not working, i can't get into the recovery mode and my laptop can't identify my phone when i connect to it.
Is there anyone know how i can fix it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/

misecia said:
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
Click to expand...
Click to collapse
Thanks mate
But you can do it even you haven't enable OEM unlock and USB debug before the phone get bricked?

-

i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??

xera3k said:
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
Click to expand...
Click to collapse
Do you have the latest android platform tools? Try different cables, different ports?

Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/

xera3k said:
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
Click to expand...
Click to collapse
Idk if its because of that but you have typo in that command, should be bootloader instead boodloader

What if have you tried to boot into another slot fastboot --active-slot

layz1319 said:
What if have you tried to boot into another slot fastboot --active-slot
Click to expand...
Click to collapse
What command would i use ?

xera3k said:
What command would i use ?
Click to expand...
Click to collapse
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best

layz1319 said:
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
Click to expand...
Click to collapse
I also am having this issue and tried what you suggested and got this.
Any ideas on how to fix?

Eventually I was able to change the active slot but sadly still looping.

yquitumadbro said:
View attachment 5677361
Eventually I was able to change the active slot but sadly still looping.
Click to expand...
Click to collapse
Try to change it again. I solved with that.

Good evening, I have the same problem after using the DSU Loader, the mobile is stuck like the screenshot in the first post above. I've tried everything but can't unlock anything. Can someone help me ?

If your PC isn't detecting your device while in Fastboot mode, you don't have the correct drivers installed. This may help.
Never try to install non-factory software on a locked bootloader!
Since you didn't enable OEM unlocking, it's unlikely that you'll be able to recover your device. Still, focus on the driver issue for now and we can go from there. Do you have ADB Platform Tools installed?

I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked

Dominicus.1 said:
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
View attachment 5681643
Click to expand...
Click to collapse
ADB commands do not work in fastboot.
fastboot devices should show the device when connected in fastboot mode.
Try fastboot flashing unlock to unlock the bootloader, which will make recovering your device much easier.

I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works

xera3k said:
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
Click to expand...
Click to collapse
U can't do anything if u r OEM tab is off and you soft bricked and not booting to system.
If unr able to boot in recovery using fastboot menu there do format data it will boot to system