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.

Accidentally wiped phone system OS using TWRP; how can I fix this?

I have basic to medium experience relating to rooting, fastboot, Odin, flashing, etc.
I accidentally wiped my phone's OS. My phone is a Samsung S5 Neo SM-903W with no root and no unlocked bootloader but with TWRP installed. My OS was Android 6.0.1
I tried downloading the stock firmware of Android 6 and flashing it using an SD card; TWRP said it was an invalid zip file and did not find an md5 ( even though it was the only file in the zip)
When I am in TWRP, my laptop recognizes me as "Samsung Mobile MTP Device" but when I am in download mode, my phone is not recognized at all. I think that I need to flash drivers on my phone, but I have no idea how to do so, and if so, how can I flash an "invalid zip file" onto my phone?
Please help me, or at least give me some advice.
Thanks (I'm an idiot for experimenting with advanced wipe )

MCMarsBoyee said:
I have basic to medium experience relating to rooting, fastboot, Odin, flashing, etc.
I accidentally wiped my phone's OS. My phone is a Samsung S5 Neo SM-903W with no root and no unlocked bootloader but with TWRP installed. My OS was Android 6.0.1
I tried downloading the stock firmware of Android 6 and flashing it using an SD card; TWRP said it was an invalid zip file and did not find an md5 ( even though it was the only file in the zip)
When I am in TWRP, my laptop recognizes me as "Samsung Mobile MTP Device" but when I am in download mode, my phone is not recognized at all. I think that I need to flash drivers on my phone, but I have no idea how to do so, and if so, how can I flash an "invalid zip file" onto my phone?
Please help me, or at least give me some advice.
Thanks (I'm an idiot for experimenting with advanced wipe [emoji14] )
Click to expand...
Click to collapse
The stock firmware cannot be flashed with TWRP. It is built to be flashed with Odin.
If there is a stock firmware that has been converted into a custom recovery flashable zip, you can flash that in TWRP, it has to be converted from the Odin flashable firmware though, it can't be the actual downloaded firmware, it isn't compatible with recovery. This is only if such a file is available or if you learn to convert the firmware yourself.
The easiest thing would be to get your device recognized with Odin while in download mode so you can flash the firmware, this should restore your device. Try installing the USB drivers for Samsung phones from here:
http://www.samsungusbdrivers.net/2016/12/samsung-galaxy-s5-neo-usb-driver-for.html?m=1
Flashing the stock firmware via Odin will also remove TWRP and replace it with stock recovery, you'll have to flash TWRP again.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

The thing is, I installed TWRP via Odin, so I know there was (or is) nothing wrong with the drivers on my laptop, but after the system wipe, my phone could only be recognized by Odin if it was charging through it or if I was at TWRP. (the 0:COM indicator was pink, not green) I will try the method you mentioned, but if I have any difficulties I will come back here.
Thanks.

MCMarsBoyee said:
The thing is, I installed TWRP via Odin, so I know there was (or is) nothing wrong with the drivers on my laptop, but after the system wipe, my phone could only be recognized by Odin if it was charging through it or if I was at TWRP. (the 0:COM indicator was pink, not green) I will try the method you mentioned, but if I have any difficulties I will come back here.
Thanks.
Click to expand...
Click to collapse
When you are in download mode, connect to PC then open device manager and see if it at least detects the device, even if it isn't recognizing it correctly. Does it show anything in device manager? What does it show?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of 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"
}
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!

MCMarsBoyee said:
I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!
Click to expand...
Click to collapse
Try installing Kies, it automatically installs Samsung drivers correctly.
But make sure kies is completely closed and not running in the background when using Odin, it interferes.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

MCMarsBoyee said:
I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!
Click to expand...
Click to collapse
Thank you! It works perfectly! Marking as solved.

MCMarsBoyee said:
Thank you! It works perfectly! Marking as solved.
Click to expand...
Click to collapse
Which parts of what I posted solved it for you? It will help others understand if they read this thread.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I think I killed my brand new phone

I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.

Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David

DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.

In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck

If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting

viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?

If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.

whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date

Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem

whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.

whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"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"
}

Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work

whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?

viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.

whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse

So it sounds dumb but try rebooting your computer and switching USB ports then trying again.

whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port

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

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.