Database Users

Back from Repair - Fastboot Flash Mode (Not Secure) and "ENGINEERING"

Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon

An Engineering Bootloader is supposed to be completely unlocked, even more so than regular "bootloader unlock" if the official Moto forums are to be believed, it cannot be changed to locked or unlocked (fails every time), but in the Moto G 3rd gen community here we have several users with an engineering bootloader status and they have very sporadic issues with ROMs. For example RR 5.7.2 works but 5.7.3 fails, CM13 older nightlies work but current ones fail, certain kernels work and others do not, it is very weird.
To my (limited) knowledge, this is the first Engineering bootloader seen on a X Style/Pure here, you are in uncharted waters so proceed with caution...

FYI... Due to the fact that several users have seen this in the Moto G community, and it's started showing up in the Moto X Pure community, I posted in the Lenovo forums for more information on this in this thread.
The response was quite clear from AlphaDog (Moto Sr Moderator):
The phones should not be showing Engineering. If you get a phone back this way, it was not flashed properly and needs to be reflashed - call customer service and make arrangements to have it reflashed.
Click to expand...
Click to collapse

If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).

aybarrap1 said:
If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).
Click to expand...
Click to collapse
Due to weird issues that Moto G have... I'm leaning towards #2, or both.
Sent from my Motorola XT1575 using XDA Labs

Thanks all for your responses. I'm very sorry for my late reply, gmail hid the subscription emails in some subfolder (=
So an indeed very weird issue. I can confirm that it is at least the original outer frame of my phone. I had one customized from Moto maker and it had some unique scratches So they probably f***** up installation / flash. I'll try to get back with that provider an see what they say about it.
The first response on my question WHY that is, and that I'm now unable to unlock my bootloader was:
"Why are you booting Fastboot instead of normal? And you loose warranty if you unlock!"
...which of course is neither an answer to one of my questions nor helpful in any way.

I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Sent from my XT1575 using XDA-Developers mobile app

black_valor said:
I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Click to expand...
Click to collapse
fastboot oem fb_mode_clear
Sent from my Motorola XT1575 using XDA Labs

hdyim said:
Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon
Click to expand...
Click to collapse
{
"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"
}
The two entries never gave me any problems I also have an engineering bootloader.
Sent from my XT1572 using XDA-Developers mobile app

[email protected] said:
The two entries never gave me any problems I also have an engineering bootloader.
Click to expand...
Click to collapse
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So then for me no need to worry.. Not planning to flash anything other then stock and as long it doesn't give any problems with rooting and flashing some mods I won't return it ...
Sent from my XT1572 using XDA-Developers mobile app

Editing "software can't be checked for corruption" message from unlocking bootloader?

Editing "software can't be checked for corruption" message from unlocking bootloader?
I have rooted, modded, etc. my OnePlus 5 but that required me to unlock my bootloader. When you do that, it causes an ugly message to appear for 5 seconds at boot. I want to keep this message so I have 5 seconds to go into Recovery, Fastboot, etc and so myself and others will be aware that the bootloader is unlocked. However, I could make a much better design, maybe even add a changing countdown number until boot.
However, I don't know how to change it.
Does anyone know how to edit the "software can't be checked for corruption" message?
{
"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'm surprised this hasn't been changed as a couple of other phones have had this removed months ago...
I have an Axon 7 and that was solved a few weeks after it came about. There are fewer devs there than working on the One+ phones and we still have this undesirable boot screen every time we boot up...

keeganjk said:
I have rooted, modded, etc. my OnePlus 5 but that required me to unlock my bootloader. When you do that, it causes an ugly message to appear for 5 seconds at boot. I want to keep this message so I have 5 seconds to go into Recovery, Fastboot, etc and so myself and others will be aware that the bootloader is unlocked. However, I could make a much better design, maybe even add a changing countdown number until boot.
However, I don't know how to change it.
Does anyone know how to edit the "software can't be checked for corruption" message?
Click to expand...
Click to collapse
I don't think u can change it. It's becoming more and more common on phones now. There are some able to change on phones but with OnePlus I don't think so.

the_rooter said:
I don't think u can change it. It's becoming more and more common on phones now. There are some able to change on phones but with OnePlus I don't think so.
Click to expand...
Click to collapse
Can't flash with fastboot out something?

keeganjk said:
Can't flash with fastboot out something?
Click to expand...
Click to collapse
Explain? Alittle

the_rooter said:
Explain? Alittle
Click to expand...
Click to collapse
IDK, that's why I'm asking.

keeganjk said:
IDK, that's why I'm asking.
Click to expand...
Click to collapse
The screen u see is telling u that the bootloader is unlocked and that with that showing u can flash twrp, roms and root the phone. U can't flash factory imsges unless the bootloader screen that u see is showing .

ultramag69 said:
I'm surprised this hasn't been changed as a couple of other phones have had this removed months ago...
I have an Axon 7 and that was solved a few weeks after it came about. There are fewer devs there than working on the One+ phones and we still have this undesirable boot screen every time we boot up...
Click to expand...
Click to collapse
I don't want to GET RID of it, I just want to EDIT the image.

keeganjk said:
I don't want to GET RID of it, I just want to EDIT the image.
Click to expand...
Click to collapse
I really don't think u can. It's built I believe right in the bootloader or aboot . Maybe someone with more knowledge can confirm. But I believe it's there the way it is.

the_rooter said:
I really don't think u can. It's built I believe right in the bootloader or aboot . Maybe someone with more knowledge can confirm. But I believe it's there the way it is.
Click to expand...
Click to collapse
Again, this HAS been removed from the Axon 7... It doesn't sit there for 5 minutes with a blank screen then boot, it boots up as per normal without displaying the Bootloader unlocked" screen...

ultramag69 said:
Again, this HAS been removed from the Axon 7... It doesn't sit there for 5 minutes with a blank screen then boot, it boots up as per normal without displaying the Bootloader unlocked" screen...
Click to expand...
Click to collapse
Completely different phone. Not possible with OnePlus.

Some phones have the image in a separate partition on the flash memory.
These are easy to hack (although Google has made it harder to do that recently, with checksums).
For others, the image is embedded in the bootloader. Hacking the bootloader is very risky as any mistake will end up with a brick.
OP5 is the latter.
You can change the OS boot picture. You can change the OnePlus logo that's displayed first. But not that warning. I even think the warning is mandated by the Android certification process.

Bricked phone. Being a massive dumbass

Hey. I've bricked my Huawei P10 lite, literally just for the sole reason alone that I'm an idiot. I was in the process of relocking/unrooting when I did a massive choke - I've relocked the bootloader and IMMEDIATELY closed the goddamn tab. I haven't written the code down anywhere. When I've rebooted my phone, I discovered I have exactly 0 ways of doing a wipe, since the TWRP was obviously gone.
Hitools returns that the phone cannot be recovered due to not being supported.
Recovery? There isn't one. eRecovery always returns "failed to get.." yatta yatta yatta, It's not working.
The only thing currently reacting to my commands is fastboot. And, being the mr. obvious, I cannot push files onto the phone through fastboot to restore it by the full package, which was pretty much my only option at this point.
There aren't any replacement motherboards available for the P10 lite on eBay or pretty much anywhere else I could think of.
If there exists any good soul that can tell me if this is in any imaginable way reversible without getting a cracked screen phone and swapping the motherboards, PLEASE, PLEASE, do tell me.
{
"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"
}
Thank you.

INB4 anyone asks - No, I don't have the numbers to generate the code again either. At least not the serial id, i think.

EvESpirit said:
INB4 anyone asks - No, I don't have the numbers to generate the code again either. At least not the serial id, i think.
Click to expand...
Click to collapse
Did u tryed to flash original firmware by the dload method?
You don need unlocked boatloader for that. I already save my p10 few times.

hdemary said:
Did u tryed to flash original firmware by the dload method?
You don need unlocked boatloader for that. I already save my p10 few times.
Click to expand...
Click to collapse
How can I flash the original firmware? I can't even flash a recovery. The bootloader is l o c k e d, and the only thing I can access is fastboot. How am I supposed to push the files into the phones in fastboot???

EvESpirit said:
How can I flash the original firmware? I can't even flash a recovery. The bootloader is l o c k e d, and the only thing I can access is fastboot. How am I supposed to push the files into the phones in fastboot???
Click to expand...
Click to collapse
Man if you can't even google dload method to find out how to return to stock you r screwed.
But anyways i will help you with that: http://lmgtfy.com/?q=huawei+p10+lite+dload+method

I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
MOD EDIT: Mind your language

EvESpirit said:
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
Click to expand...
Click to collapse
Man as your post title says, you really are a massive dumbass, if you at least try to help your self with the link i send you u will see that dload method dont need to boot into system, no need for recovery and no need for unlocked boatloader, only an sd card with a folder that have original firmware for your variant.
But as you rude keep your phone as a brick.
Regards!

EvESpirit said:
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
MOD EDIT: Mind your language
Click to expand...
Click to collapse
Mind your language my friend.
This is an official caution for you.
If you have any doubts, check the FORUM rules

EvESpirit said:
>mfw mods ignore somebody attacking someone first and call me out for using bad language+edit the comment, yet still leave the actual swear happen without deleting
OMEGALUL so relevant
@hdemary If you would kindly learn to read. For the third time I'm telling you that ThErE Is No Way For Me to PUSH the FILES to the PHONE. I do not have an unlocked bootloader nor a functioning recovery AND NO DEVICE to put them on. Also nice OP dodge, but I guess that's just them being unbiasedly biased.
Click to expand...
Click to collapse
My last post in this thread.
Why u ask for help in the first place if you won´t accept?
Have fun with your bricked device!
Best of the best Regards! :angel:

Well, seems this thread has run its course
Thread closed

Galaxy S8 SM-950F Stuck on Logo, FRP LOCK: On OEM Lock: On

Hello guys.
My friend was trying to inject TWRP from Odin to his S8. But as guessed it is failed and now the phone is stuck on Logo and doesn't boot. So, as you see from the title,frp and oem locks are in position "on". What should i do? Since FRP lock is on everything i tried on Odin failed as i expected.
{
"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'm currently desperate and need some advice how do i fix the phone. Since he doesn't have any backup phone i'm trying my best. Thanks already!

Arda A. said:
Hello guys.
My friend was trying to inject TWRP from Odin to his S8. But as guessed it is failed and now the phone is stuck on Logo and doesn't boot. So, as you see from the title,frp and oem locks are in position "on". What should i do? Since FRP lock is on everything i tried on Odin failed as i expected.
I'm currently desperate and need some advice how do i fix the phone. Since he doesn't have any backup phone i'm trying my best. Thanks already!
Click to expand...
Click to collapse
Dude first off did you activated oem unlock in developer settings (does this Samsung even have a unlocked bootloader) Since you messed up patching twrp to the recovery you need to reflash stock firmware run the setup wizard after its done go in developer settings and make sure oem unlock is activated or more important is the option even present?
(alright its thier I didn't see the F in your model number)
([emoji88]Chaos GSI[emoji88])

PoochyX said:
Dude first off did you activated oem unlock in developer settings (does this Samsung even have a unlocked bootloader) Since you messed up patching twrp to the recovery you need to reflash stock firmware run the setup wizard after its done go in developer settings and make sure oem unlock is activated or more important is the option even present?
(alright its thier I didn't see the F in your model number)
([emoji88]Chaos GSI[emoji88])
Click to expand...
Click to collapse
First of all, my friend did nothing about unlocking oem (you can see from the picture i uploaded, both oem and frp locks are active). He didn't even searched about it . I don't think the bootloader also unlocked. So its pretty messed up right now. I actually tried flashing both android 8 and 9 with different variations, odin always failed. If at least oem was unlocked i think i would do something but, i have no idea waht to do.

Arda A. said:
First of all, my friend did nothing about unlocking oem (you can see from the picture i uploaded, both oem and frp locks are active). He didn't even searched about it . I don't think the bootloader also unlocked. So its pretty messed up right now. I actually tried flashing both android 8 and 9 with different variations, odin always failed. If at least oem was unlocked i think i would do something but, i have no idea waht to do.
Click to expand...
Click to collapse
Is thier a android 10 option......
([emoji88]Chaos GSI[emoji88])

PoochyX said:
Is thier a android 10 option......
([emoji88]Chaos GSI[emoji88])
Click to expand...
Click to collapse
Galaxy S8 didn't get android 10 update unfortunately. I'm still thinking that the problem that causes failed flashes comes from probably the roms i have. But i'm downloading from samdb, when it is downloaded i'll try that and it will probably work i assume.

Arda A. said:
Galaxy S8 didn't get android 10 update unfortunately. I'm still thinking that the problem that causes failed flashes comes from probably the roms i have. But i'm downloading from samdb, when it is downloaded i'll try that and it will probably work i assume.
Click to expand...
Click to collapse
Alright let me know the progress your friend shouldn't tinker without the proper knowledge cause now that expensive phone just a piece of metal once he has twrrp installed he should be protected from this happening again cause then again twrp is a modders best friend
([emoji88]Chaos GSI[emoji88])

PoochyX said:
Alright let me know the progress your friend shouldn't tinker without the proper knowledge cause now that expensive phone just a piece of metal once he has twrrp installed he should be protected from this happening again cause then again twrp is a modders best friend
([emoji88]Chaos GSI[emoji88])
Click to expand...
Click to collapse
You are completely right sir. Personally, every phone i had for 5 years were all modded and i always do my search before doing anything. What he did was a really big mistake and he could've asked me. At least he took a lesson from happened to him :laugh:
I just took his phone to my home and connected to my pc, i flashed the stock rom without any problem. I decided to root his phone by myself. I don't think he should attempt to do this kind of critical operations alone . Thanks for the help!
I also have another question; he had a backup of his files and apps using Smart Switch. If i root his phone, i know kies and smart switch doesn't work with updating phones. But can it restore the backup on a rooted phone?

Arda A. said:
You are completely right sir. Personally, every phone i had for 5 years were all modded and i always do my search before doing anything. What he did was a really big mistake and he could've asked me. At least he took a lesson from happened to him [emoji23]
I just took his phone to my home and connected to my pc, i flashed the stock rom without any problem. I decided to root his phone by myself. I don't think he should attempt to do this kind of critical operations alone . Thanks for the help!
I also have another question; he had a backup of his files and apps using Smart Switch. If i root his phone, i know kies and smart switch doesn't work with updating phones. But can it restore the backup on a rooted phone?
Click to expand...
Click to collapse
I don't believe so... Hope he learned his lesson from this
([emoji88]Chaos GSI[emoji88])

[Resolved] [Brush in wrong XBL] 8pro black brick cannot enter 9008 mode

My mobile phone system is the o12c10 version, and then I downloaded the o12c11 version, but I found that the OTA channel is not displayed on the mobile phone, so I directly used fastbootd to brush into the playload. Bin file in FastBoot mode (not FastBoot mode, but FastBoot mode)
After that, I can't start the machine directly, can't enter any mode, and 9008 can't get in
Long press to enter 9008 or any other mode will not respond, and there will be no vibration feedback
When charging, the screen is also black and does not display
The computer interface didn't respond. I've tried line breaks, too
I tried the original cable, lightning cable and USB port
The driver also attempts to uninstall and reinstall the new driver
The computer device manager window still does not show any new devices
{
"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"
}
Then I got the remote consultation service. The second-line remote service learned about the situation and didn't solve it remotely. It suggested that I send it for repair, but the epidemic situation was blocked and I couldn't send it for repair
How to solve this situation
emergency​----------------
English is not my native language; please excuse typing errors.
2023/03/02to update：XDA post-88110375 comments
Solution：How to prevent and remedy the crash caused by wrong XBL

It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.

ppajdek said:
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
Click to expand...
Click to collapse
yeah, it's gone with the wind, motherboard replace is the only solution

nkhater said:
yeah, it's gone with the wind, motherboard replace is the only solution
Click to expand...
Click to collapse
Ok, I have to pay more attention to the next time I swipe the system, so as not to make such a mistake again, thank you

ppajdek said:
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
Click to expand...
Click to collapse
Thank you for letting me know what's wrong with me. It seems that I should pay more attention to this next time I swipe the system

小忧忧 said:
Ok, I have to pay more attention to the next time I swipe the system, so as not to make such a mistake again, thank you
Click to expand...
Click to collapse
What do you mean will pay more attention, this is catastrophic, there is no room for error, you make a mistake and your investment is gone. This is new to OnePlus, I have been using their phones from day one, never thought this will ever happen.

nkhater said:
What do you mean will pay more attention, this is catastrophic, there is no room for error, you make a mistake and your investment is gone. This is new to OnePlus, I have been using their phones from day one, never thought this will ever happen.
Click to expand...
Click to collapse
Maybe the translation quality of the translator I use is not so perfect.
I prefer to experience other third-party systems without adaptation, so I will brush GSI
Therefore, I will pay more attention to these problems in the process of system brushing in the future

I solved this problem, and the specific solutions for details have been updated to my blog (need to translate, my English level is not good)
link:How to prevent and remedy the crash caused by the wrong XBL

小忧忧 said:
I solved this problem, and the specific solutions for details have been updated to my blog (need to translate, my English level is not good)
link:How to prevent and remedy the crash caused by the wrong XBL
Click to expand...
Click to collapse
My browser wont load the pictures and if im rifht they would show me the "line" to enter.
According to the description above, we can buy an engineering cable to connect to your phone
Then use this line to perform the normal 9008 flashing operation to save your phone
Just to be sure, we can use an Engineering cable to unbrick our devices?

little follow up here, would that work ? i did the same thing years ago with a Lenovo ZUK Z2 Pro, taped aluminium inside the usb connections which i saw from youtube on how to do that, and it reviewed my dead phone into edl from where i could flash stock roms
would this also work on our oneplus 8 pro ?
i hope we can figure stuff out here, threw away my dev-usb cable years ago, would try making a new one

Please tell me if any of you have been able to revive our 8 pro with this cable? or similar

Winstarshl said:
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
Click to expand...
Click to collapse
Yes it works, read here.

xtcislove said:
My browser wont load the pictures and if im rifht they would show me the "line" to enter.
According to the description above, we can buy an engineering cable to connect to your phone
Then use this line to perform the normal 9008 flashing operation to save your phone
Just to be sure, we can use an Engineering cable to unbrick our devices?
Click to expand...
Click to collapse
ikram.senguen said:
little follow up here, would that work ? i did the same thing years ago with a Lenovo ZUK Z2 Pro, taped aluminium inside the usb connections which i saw from youtube on how to do that, and it reviewed my dead phone into edl from where i could flash stock roms
would this also work on our oneplus 8 pro ?
i hope we can figure stuff out here, threw away my dev-usb cable years ago, would try making a new one
Click to expand...
Click to collapse
Winstarshl said:
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
ppajdek said:
Yes it works, read here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sorry, due to some work and network problems, I can't follow up XDA's posts in time. Besides, my English is not good. I use Google Translate, so some abnormal sentences may appear in the text. Please forgive me
Many people have encountered the same problems as me, which are solved by using the project line mentioned in How to prevent and remediate the crash by wrong XBL
One of my friends couldn't buy a data line because of some factors. He tried to understand the method of data line short circuit, but the test failed to enter 9008. Other group friends also bought the short data line test mentioned in How to recover your device after flashing incorrect DDR xbl images, but failed to enter the final test. (It is also possible that the line used in this article is qualified? But I can't buy it in my region, so I can't test it)
It is worth noting that the 22K resistor is used in the product description of the engineering data line introduced in my article. I think that's the key
I tried to search the platforms you can buy in your country, but I didn't find the data line
However, I found pcb2.0. It has a lot of internal resistance. Its appearance is roughly as shown in the figure below. This may help you