Database Info

Galaxy Tab 2 7.0 p3100 bootloader question

I have read numerous threads on how to unlock the bootloader, however after the GTab2 7.0 p3100 is/was updated to JB 4.1.2 (VRBMI1), there is nothing i have found after a few days of looking and reading. Is this bootloader locked and no way to flash a custom ROM to it? Obviously, if this is a ridiculously dumb question, then I apologize in advance and the thread should be deleted. I just really would like to flash something really minimal to the 2 GTab2's that I have laying around to use them as home automation tablets in a couple of infrequently visited areas of my house. The stock ROM is really slow imho.
I do realize this is a very old tablet so it may be just too old to do anything with, regardless thanks very much for any help in this!

If you didn't buy it from a carrier and such, it's unlocked

Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?

To check if your bootloader is locked: install adb and fastboot to your computer as well as the proper drivers, boot your tab into download mode (power+volume down) and connect it to the computer with usb cable. Open a command prompt and type "fastboot devices" (without the quotes). If everything is right you will see your tab listed. Now for the check type "fastboot getvar unlocked" (again without the quotes). If the result is yes, your bootloader is unlocked.

Ok, so I already had adb/fastboot and odin 3 v 3.12 installed. Odin3 sees the device in both on and download states. adb doesnt see it at all in either mode. Windows 10 is my OS... Device manager see the tab unplug and plug in each time and I have used multiple USB ports as well. Any ideas? Chuck the tabs in the trash perhaps?

Trash is not a good idea It's probably a driver issue. Check that you have installed the adb/fastboot drivers, maybe there is an update to some driver you haven't done or seen yet. Also, try to install for your tab specifically the adb driver through the device manager (I don't know much about windows 10 so I can't tell you exactly how to do it, perhaps right-click on the tab or from some menu).
EDIT: Since odin works, try to install twrp with it. If it fails it's locked and you need fastboot to unlock it.

Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.

zulutron said:
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
Click to expand...
Click to collapse
"System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help."
are you really sure that you have a p3100?? it seems that you have a verizon varient of the tab 2. in this case dont flash p3100 stuff on your device. it will brick

Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?

zulutron said:
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
Click to expand...
Click to collapse
go to settings --- about the tablet. make a screenshot of this page and post it here.

Here it is. Thank for the help.
{
"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"
}
http://tinypic.com/r/2rzv3f8/9 <-- if the above doesnt work

zulutron said:
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
Click to expand...
Click to collapse
here you said that the tab is from verizon.
there is no rom available for your device.
i say it again
DONT FLASH P3100 STUFF ON THIS TAB !!
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
zulutron said:
Here it is. Thank for the help.
https://unsee.cc/tumezaso/ <-- if the above doesnt work
Click to expand...
Click to collapse
this is a sch-i705 and not a p3100. thats different devices

This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674

zulutron said:
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
Click to expand...
Click to collapse
look at the last 2 posts of the thread. all download links are dead since 1 year.
the best scenario for you. someone can help you out with the files. then you can install a damn old twrp recovery. with that you can backup your current system. nothing more.
there is no up to date twrp and no available rom for this device.
in this case unlocking the bootloader makes no sense, i think.

I appreciate the help for sure. I wont waste any more time on these tabs.

Samsung Galaxy S6 Edge Plus(SM-G928C) “Invalid Kernel Lenght” issue

Hi,
My S6 Edge Plus 32GB was functioning properly when i left it in a box for a while. After then, when i tried to boot it, it just showed a white screen and said “Could not do normal boot. Invalid Kernel Lenght!”. I tried to go to recovery mode yet it was not possible. Only i can do is to open download mode, but neither pc nor odin didn’t detect the phone at all. Plus, it was saying “FRP LOCK: on” I downloaded up to date Samsung Usb Drivers from the original source, but didn’t fix the issue either. Now I have a phone which i can not do any further action. What should i do friends?
(Battery was replaced with a replica one before. It opens up as i plug it and stays open without cable for a while then dies. Nothing changed other than original battery, and haven’t rooted before.)
Thank you!
{
"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"
}

Today it just showed up new alerts. I ordered a new cable and I will try to make odin to detect the phone. But then? I need help folks.

Emreturkmenoglu said:
Hi,
My S6 Edge Plus 32GB was functioning properly when i left it in a box for a while. After then, when i tried to boot it, it just showed a white screen and said “Could not do normal boot. Invalid Kernel Lenght!”. I tried to go to recovery mode yet it was not possible. Only i can do is to open download mode, but neither pc nor odin didn’t detect the phone at all. Plus, it was saying “FRP LOCK: on” I downloaded up to date Samsung Usb Drivers from the original source, but didn’t fix the issue either. Now I have a phone which i can not do any further action. What should i do friends?
(Battery was replaced with a replica one before. It opens up as i plug it and stays open without cable for a while then dies. Nothing changed other than original battery, and haven’t rooted before.)
Thank you!
View attachment 5306065View attachment 5306067
Click to expand...
Click to collapse
First of all I need to say: I'm no expert for your phone.
I just stumbled over this thread.
more to read for FRP:
OEM vs Bootloader lock.
The guide to unlocking the bootloader on the newer Samsung tablets seems to cause confunsion about what the OEM Enable switch does. First of all, the OEM switch has no direct bearing on the Bootloader lock. That switch has been around for quite...
forum.xda-developers.com
looking at your first photo from comment #1:
current binary: Custom
system status: official
sounds somewhat curious to me (but as I said: I'm no expert)
What *I* would suggest: "get the phone in a sane state"
1.
- read about "developer Mode"
- I'm unsure if debug mode is needed to flash stock or that the phone is seen by the PC
2.
- fix your PC, so that the phone is seen by PC
lastest USB Driver:
Android USB Driver for Windows | Samsung Developers
The world runs on you.
developer.samsung.com
if that doesn't work try to set up a *clean* windows VM with VBox
Oracle VM VirtualBox
www.virtualbox.org
don't forget to install "VM Virtual Extension Pack" so that USB (Guest <=> Host) is okay
3.
reset your phone *after* you deleted your google account on phone, see above "FRP"
WARNING: ALL DATA will be lost, if you have no backup (at google or somewhere else)
4.
flash lastest stock with ODIN
you need an Odin Version which corresponds to the stock Android Version
see:
Odin Device Compatibility List | Odin Android Version Compatibility
Check out what Odin version you should use! Here's a list of Odin device compatibility. Odin Android version compatibility with Nougat Oreo and Pie firmware
www.droidviews.com
and
Download Odin Tool for Samsung Devices (All Versions) | DroidViews
Download Odin Tool for Samsung Devices. Samsung Odin download is available for free for Windows PC. The Latest Odin version is Odin3_v3.14.1.
www.droidviews.com
last stock is Android 7, if I got it right:
Download Samsung Galaxy S6 edge+ SM-G928F firmware
Download the latest Samsung firmware for Galaxy S6 edge+ with model code SM-G928F. Check out our free download or super fast premium options.
www.sammobile.com
5.
do what you initial want to do ( custom Rom flash or what-so-ever) now on the clean state of the phone.
good luck

rw_on_xda said:
First of all I need to say: I'm no expert for your phone.
I just stumbled over this thread.
more to read for FRP:
OEM vs Bootloader lock.
The guide to unlocking the bootloader on the newer Samsung tablets seems to cause confunsion about what the OEM Enable switch does. First of all, the OEM switch has no direct bearing on the Bootloader lock. That switch has been around for quite...
forum.xda-developers.com
looking at your first photo:
Click to expand...
Click to collapse
Hi,
The issue is, i can not boot the phone. If i were able to do it, of course i would sign in to my Google account and remove the lock with the help of the guide you attached. So, there is an endless loop unfortunately.
Thank you.

Emreturkmenoglu said:
Hi,
The issue is, i can not boot the phone. If i were able to do it, of course i would sign in to my Google account and remove the lock with the help of the guide you attached. So, there is an endless loop unfortunately.
Thank you.
Click to expand...
Click to collapse
Okay, I missed that.
But you're able to boot to download mode.
if so, try to flash TWRP recovery and with that format the partitions and flash stock
don't know if that helps regarding FRP, but maybe for the boot problem

rw_on_xda said:
Okay, I missed that.
But you're able to boot to download mode.
if so, try to flash TWRP recovery and with that format the partitions and flash stock
don't know if that helps regarding FRP, but maybe for the boot problem
Click to expand...
Click to collapse
So here is the update
I got a new cable. Odin detected my phone. But it got stuck at system.img with stock firmware. I tried many other odin versions. I tried different USB ports. Nothing changed. It gets stuck at something and can’t fix unfortunately. It showed a partition error as well. I tried a 4part repair firmware with a pit file, didn’t work. I tried a pit file with official firmware, didn’t work. I tried a boot_recovery file, didn’t work. I tried to load TWRP, didn’t work.
Here are the list of options I tried:
1-Stock firmware
2-TWRP firmware
3-Pit files
4-Repair firmware
5-Boot_recovery file
Here are the list of stuck positions at trials(mixed):
1-System.img
2-Nand Write Start!!
3-There is no pit partition
4-Re-partition operation failed.
5- Complete(Write) operation failed.
I think I’ve seen every error code can ever be seen through odin
Smart Switch didn’t helped either. Detects the phone but don’t list it on emergency list.
So now, for me, I ran out of options… Odin variable tested. Cable is working properly. Pc is running properly.
From now on I don’t care if it dies, so don’t hesitate, it’s dead already for me, why not to try other things huh. Any further suggestions for me to give it a try?
By the way, a repairguy said it’s bricked and he might try to fix it with JTAG, yet if EMMC chip is dead there is nothing left he can do.

Emreturkmenoglu said:
So here is the update
I got a new cable. Odin detected my phone. But it got stuck at system.img with stock firmware. I tried many other odin versions. I tried different USB ports. Nothing changed. It gets stuck at something and can’t fix unfortunately. It showed a partition error as well. I tried a 4part repair firmware with a pit file, didn’t work. I tried a pit file with official firmware, didn’t work. I tried a boot_recovery file, didn’t work. I tried to load TWRP, didn’t work.
Here are the list of options I tried:
1-Stock firmware
2-TWRP firmware
3-Pit files
4-Repair firmware
5-Boot_recovery file
Here are the list of stuck positions at trials(mixed):
1-System.img
2-Nand Write Start!!
3-There is no pit partition
4-Re-partition operation failed.
5- Complete(Write) operation failed.
I think I’ve seen every error code can ever be seen through odin
Smart Switch didn’t helped either. Detects the phone but don’t list it on emergency list.
So now, for me, I ran out of options… Odin variable tested. Cable is working properly. Pc is running properly.
From now on I don’t care if it dies, so don’t hesitate, it’s dead already for me, why not to try other things huh. Any further suggestions for me to give it a try?
By the way, a repairguy said it’s bricked and he might try to fix it with JTAG, yet if EMMC chip is dead there is nothing left he can do.
Click to expand...
Click to collapse
disable FRP lock first

ineedroot69 said:
disable FRP lock first
Click to expand...
Click to collapse
How? I would love to disable it, but as I cannot even boot it, I can’t.

maybe fastboot might help (I haven't played with it enough though)
=> format, erase, flash ???
Fastboot (Tool)
www.droidwiki.org

Nokia 1.4 TA-1322 Help

Hello everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?

Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it

optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"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"
}

Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?

optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...

S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?

Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)

Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got

Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.

Question [Fixed] Issue with MSM tool on LE2110

EDIT: Solution here https://forum.xda-developers.com/t/fixed-issue-with-msm-tool-on-le2110.4452133/post-86963931
Hi everyone, after hours of internet searches and scratching my head trying different methods over and over, I've decided to post here asking for help since I'm totally lost.
First of all, I got a bricked Oneplus 9 LE2110 (chinese model) that I'm trying to restore to any semblance of operation.
I've followed this FizzyAps tutorial https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
I got the drivers installed and MDM recognizes the device.
{
"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 first weird behavior I have is that whenever every 10 seconds or so, the device disconnects from the computer, then automatically reconnects again (I get the windows sound of a new usb device plugged in and out, and also the device is removed from the device manager and MSM).
Anyway, whenever I try to flash the phone with the configuration above, I get one of the following errors:
The dreaded "Sahara Communication Failed" If I just follow the tutorial to the letter.
If I hold volume UP+DOWN pressed at all times after connecting the phone, the error I get is different;
As a last resort, I tried using the Lite Firehose checkbox, but then it MSM prompts that the image does not match the device:
I was unable to find an image for LE2110 anywhere on the internet, but according to reports from other forum posts, the firmware I'm using (lemonade_22_O.07_210412.ops) should work.
Anyway, if anyone has a OEM LE2110 image that can be shared, it would be helpful.
Can anyone help me fix this issue?
Worth mentioning that I've tried multiple different USB ports, but I'm not using the OEM cable since my computer does not have a USB-C port, and the cable which came with the phone is USB-C on both ends. I'm using a high quality USB 3.1 cable instead.
Windows firewall and antivirus are disabled while trying to flash the phone.
About booting into EDL, the phone does not give any cue, as I just get an unlit black screen at all times, even when the device is recognized as QDLoader9008. I tried powering it off first by holding power for 15 seconds and even let the battery dry for a month, but when trying again the results were the same.

Replying to myself to confirm that this zip fixes the issue with the default configuration:
ONE PLUS 9 EU MSM TOOL TESTED
This was a Untested MSM .OPS file for the EU Variant use at your own risk. This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof. This will fail verification when pressing...
forum.xda-developers.com
Anyone with LE2110 don't use FizzyApps tutorial or files, please use this link instead.

GryphusR said:
Replying to myself to confirm that this zip fixes the issue with the default configuration:
ONE PLUS 9 EU MSM TOOL TESTED
This was a Untested MSM .OPS file for the EU Variant use at your own risk. This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof. This will fail verification when pressing...
forum.xda-developers.com
Anyone with LE2110 don't use FizzyApps tutorial or files, please use this link instead.
Click to expand...
Click to collapse
Interesting. Sounds like the tool posted there may be a universal MSM like the Indian 9 Pro's then because it shouldn't have worked for your device either if it was a Chinese variant.

EtherealRemnant said:
Interesting. Sounds like the tool posted there may be a universal MSM like the Indian 9 Pro's then because it shouldn't have worked for your device either if it was a Chinese variant.
Click to expand...
Click to collapse
I was also surprised because I got the phone bricked on the first place by trying to flash an EU ROM instead than the Global ROM. But since another person with a LE2110 said it worked, I decided to give it a try and indeed it worked at the first attempt.
On the original FizzyApps thread, someone said that LE2110 also work, but for whatever reason it does not. Being a Chinese variant it would not surprise me if there are different "revisions" of LE2110 model number, and perhaps some are incompatible with older versions of the FW

GryphusR said:
EDIT: Solution here https://forum.xda-developers.com/t/fixed-issue-with-msm-tool-on-le2110.4452133/post-86963931
Hi everyone, after hours of internet searches and scratching my head trying different methods over and over, I've decided to post here asking for help since I'm totally lost.
First of all, I got a bricked Oneplus 9 LE2110 (chinese model) that I'm trying to restore to any semblance of operation.
I've followed this FizzyAps tutorial https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
I got the drivers installed and MDM recognizes the device.
View attachment 5626537
View attachment 5626541
The first weird behavior I have is that whenever every 10 seconds or so, the device disconnects from the computer, then automatically reconnects again (I get the windows sound of a new usb device plugged in and out, and also the device is removed from the device manager and MSM).
Anyway, whenever I try to flash the phone with the configuration above, I get one of the following errors:
The dreaded "Sahara Communication Failed" If I just follow the tutorial to the letter.
View attachment 5626547
If I hold volume UP+DOWN pressed at all times after connecting the phone, the error I get is different;
View attachment 5626549
As a last resort, I tried using the Lite Firehose checkbox, but then it MSM prompts that the image does not match the device:
View attachment 5626551
I was unable to find an image for LE2110 anywhere on the internet, but according to reports from other forum posts, the firmware I'm using (lemonade_22_O.07_210412.ops) should work.
Anyway, if anyone has a OEM LE2110 image that can be shared, it would be helpful.
Can anyone help me fix this issue?
Worth mentioning that I've tried multiple different USB ports, but I'm not using the OEM cable since my computer does not have a USB-C port, and the cable which came with the phone is USB-C on both ends. I'm using a high quality USB 3.1 cable instead.
Windows firewall and antivirus are disabled while trying to flash the phone.
About booting into EDL, the phone does not give any cue, as I just get an unlit black screen at all times, even when the device is recognized as QDLoader9008. I tried powering it off first by holding power for 15 seconds and even let the battery dry for a month, but when trying again the results were the same.
Click to expand...
Click to collapse

It meant to have a black screen in edl mode, I got driver from op remote flash team & MSM tool which worked on op9 & pro version of global. Mine a le2110 too . I still had bugs after flashing global so the remote team flashed it with Chinese ROM & I flashed it back to oxygen using fizzys ROM , works great now but after updating OTA it says my device is a le2115 OP said that's normal , here's link m8 https://mega.nz/folder/wTZRkKyA#q146JvIeKkD2B6qnIN9F2Q
I had problem with driver because I got AMD CPU, always use original cable when flashing , I keep one for that , it's a signed driver as well

It worked one month ago, but I played with my phone again and this MSM tool doesnt work now even with the same cable (now im trying different cables) in the same port i used last time
it fails at Firehose GetUfsInfo but if i continue holding volume+, it will get to FirehoseCheckRSP Failed Errno 258

Question Read Flash unbrick unlock bypass FRP & More

Hello Everyone.. here is the Instructions for OnePlus Nord CE 2-
Note:
backup Internal storage, contact message etc before process
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file.
1. Reading Firmware from Device
we download Require files USBDK Driver, Mediatek Driver & The Program
We Install both USBDK and Mediatek driver on our computer
disable windows defender and extract Program
Run Program
Select 'Firmware reader' Option and Mark The Full Firmware Option and Click 'Start Button'
{
"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"
}
turn Phone off, Press Volume up and down key and Insert USB
Reading Process Started. it will take around 15Min, once done we collect Firmware in Out Directory (it will Include nvram too)
unlocking bootloader:
there is a fastboot access issue on this device, you can try exploit method which is located Mediatek/service section...
bypass FRP lock:
From the very first Screen we Select FRP bypass Option and click 'START' Button
turn Phone off press volume up and down key and then insert usb
once done we disconnect device
Flashing Firmware:
we Go to Mediatek/Firmware Flashing Option
Select second Method 'write all partition' locate the firmware folder
click 'flash' button
turn phone off Press Volume up & down key and then inset usb
wait until success. done

Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?

trohn_javolta said:
Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?
Click to expand...
Click to collapse
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader

mark332 said:
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader
Click to expand...
Click to collapse
Turns out my work laptops antivirus instantly removed the .exe

Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.

trohn_javolta said:
Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.
Click to expand...
Click to collapse
The same story for me, the phone can't be put in preload or download mode or whatever they call it. I know one thing it is my last Oneplus phone if they're all going to be pain in the arse like this one. I guess it's back to my old 6t for another while then.

Accessing it by way of Recovery mode is also broken. To try it yourself, boot in to Recovery, connect your phone to your computer with usb-c cable. Multi-tap version number, it will eventually ask you if you want download mode and you click yes. It will attempt reboot into download mode, fail and then will `normal` boot phone.

trohn_javolta said:
Turns out my work laptops antivirus instantly removed the .exe
Click to expand...
Click to collapse
fixed a clean version + code available in public https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/

Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`

Quaicheist said:
Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`
Click to expand...
Click to collapse
connect in Proper way= install Latest usbdk and mtk driver, start process turn Phone off press volume up & down key and then Insert USB, once the Phone is detected release keys

Thanks for the info, though I have been doing that setup all along. I dual windoze and Linux. My windows is a custom minimal version of windows 10 with feck all on it. I upgraded this phone to stock 12 beta yesterday and ROM2Box for a wonder is happily doing a dump of that. It should be interesting when I downgrade to stock 11 and try to do a dump of that.

@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?

Quaicheist said:
@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?
Click to expand...
Click to collapse
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Hi @mark332, sorry I wasn't able to get to you sooner about this. Coredump was only possible with OxygenOS 12.1 beta, BROM was definitely locked down in 11. I succeeded with 12 but 'out' folder looks incomplete, files like ''preloader' which is in the beta package are missing from the dump. I don't think I would be able return to stock with ROM2box, maybe manually with fastboot commands.

Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.

Quaicheist said:
Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.
Click to expand...
Click to collapse
I'm just curious how did you downgrade?

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Brom is enabled on A11 I've reflashed my device recovery partition when i was stuck

ko_hi said:
I'm just curious how did you downgrade?
Click to expand...
Click to collapse
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581

Quaicheist said:
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581
Click to expand...
Click to collapse
I guess if BROM mode works, use the bypass method to flash back to A11.v

Ah you see, the fecking phone managed to rollback to 11 but the touch screen driver is broken I guess. Physical buttons work but touch is broken. So I have contacted Oneplus tech support so we'll see what response I get tomorrow.