Database Info

[Q] Custom binary blocked by reactivation lock

I cant boot my phone it doesnt go further than the samsung logo, i can go into some sort of custom os mode but when i cancel thay it doesnt do anything. I tried booting into recovery but it doesnt work. This happened after i flashed thenzeroflte samsung galaxy s6 TWRP (primary download) onto a fodaphone netherlands normal s6.
UPDATE: THANKS! It worked, i used the wonderhowto unroot tutorial.

creeperlwd said:
I cant boot my phone it doesnt go further than the samsung logo, i can go into some sort of custom os mode but when i cancel thay it doesnt do anything. I tried booting into recovery but it doesnt work. This happened after i flashed thenzeroflte samsung galaxy s6 TWRP (primary download) onto a fodaphone netherlands normal s6.
Click to expand...
Click to collapse
If you can get into download mode (the custom OS) than you can simply flash the stock firmware and restart from there.
Sent from my SM-T805 using Tapatalk

creeperlwd said:
I cant boot my phone it doesnt go further than the samsung logo, i can go into some sort of custom os mode but when i cancel thay it doesnt do anything. I tried booting into recovery but it doesnt work. This happened after i flashed thenzeroflte samsung galaxy s6 TWRP (primary download) onto a fodaphone netherlands normal s6.
Click to expand...
Click to collapse
Open www.findmymobile.samsung.com log in with your samsung account and deactivate reactivation lock (or not if your phone is stolen) (if its stolen you can't you ANYTHING) and install Kies or SmartSwitch and re install the firmware(you cant flash this phone in ODIN because the reactivation lock)

How do i flash it exacly?
¿Will-it-Blend? said:
If you can get into download mode (the custom OS) than you can simply flash the stock firmware and restart from there.
Sent from my SM-T805 using Tapatalk
Click to expand...
Click to collapse
How do i do that, can you provide me a link to a step by step tutorial

I cant connect it to the pc
I installed the USB drivers and the KIES software, but it just doesnt connect. Help please

How do i connect it to the internet
kmiloxdxd said:
Open linkhere log in with your samsung account and deactivate reactivation lock (or not if your phone is stolen) (if its stolen you can't you ANYTHING) and install Kies or SmartSwitch and re install the firmware(you cant flash this phone in ODIN because the reactivation lock)
Click to expand...
Click to collapse
I diaabled that but it doesnt have a connection to the internet, so it is still on. How do i connect it to the internet?

creeperlwd said:
I diaabled that but it doesnt have a connection to the internet, so it is still on. How do i connect it to the internet?
Click to expand...
Click to collapse
You dont need to connect it to internet just connect your phone to Kies or SmartSwitch and select emergency firmware recovery and connect your device, if it doesnt work you can enter in recovery mode (up button, home button, power button) and select wipe data/factory reset.
Hit Thanks if i helped 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"
}

Any way to enable USB debugging if I can't access the OS?

Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?

Marhan93 said:
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Click to expand...
Click to collapse
Have you tried using the OTA instead of the factory image? That might give you a workaround to get it functioning again.
Sent from my Pixel 2 using Tapatalk

Have you tried changing your usb cable and the port its plugged into? Its stupidly simple, but has solved nuuuuuumerous problems I've had with manually flashing.
Other that that, I think you've covered a lot of bases. Are you sure you can't get into recovery mode tho? I was only able to get in by unplugging, full power off, then using power + vol dn for bootloader mode, then selecting recovery mode. You might be able to do some flashes from there.
Also, adb only works in the OS and maybe recovery mode. Fastboot only works in bootloader mode. I'm not exactly sure if fastboot needs to be authorized. Adb does though.

Oneplus 8 fastboot only

I have a t mobile variant that is sim unlocked and bootloader unlocked.
I wanted to convert to a Global version however it failed because I apparently had the wrong oem software.
I used all in one tool which worked great for everything else I needed but here is the problem; I can only boot into fastboot mode and crashdump mode. When using all in one tool I chose to wipe the device before installing the new software
I also cannot get into EDL Mode to use the Msmdownload tool even though the correct drivers are installed to use this tool.
Anyway out of this? Thanks...
Aslo; I have tried fastboot commands with no luck...

You need to msm using edl. If you are bl unlocked, flash a custom ROM to get booted and maybe try again using proper tool?
Also, try different USB ports, cables, etc. You should be able to boot into edl with hw keys and connect to msmtool

As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?

Gabriel51 said:
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Click to expand...
Click to collapse
Not sure if you got this fixed but boot into fastboot, the use "fastboot boot" to boot into AICP Recovery. Within recovery eanble ADB, then "adb reboot edl". EDL mode is just a black screen and your phone will exit it and try to boot after a few seconds if the drivers are not installed so its easy to miss. If your phone can boot into fastboot it can boot into EDL.

I do not see that feature listed? Phone would not boot into normal recovery, it went right back into fastboot.
{
"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"
}

Also if you had read through the posts you would know that I already sent it to 1+ for repair, they have had it a couple of days...

OnePlus repaired my device for nothing which is nice however It's now sim locked and at first try T-mobile says this device does not qualify for unlock!!! T-mobile also said they are looking into it because it was previously unlocked and it may take a week to get a reply.
I called OnePlus and their response was it's not our problem (more or less) I sent them a unlocked phone and they completely ignored my request to load the global software on this device, they did what they wanted to, they could have contacted me at any time..THANK YOU OnePlus.

OnePlus 8T+ 5G (TMO KB2007) stuck in EDL mode, how do I get SMT Download mode to work?

I messed up my phone badly, I can't even get Qualcomm CrashDump mode to appear, it's just stuck in EDL mode, how do I get SMT Download mode to work to fix it?

SharpnessXVSlayer said:
I messed up my phone badly, I can't even get Qualcomm CrashDump mode to appear, it's just stuck in EDL mode, how do I get SMT Download mode to work to fix it?
Click to expand...
Click to collapse
MSMDownloadTool

AnierinB said:
MSMDownloadTool
Click to expand...
Click to collapse
I already have the tool, but SMT Download mode won't start without info.
{
"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"
}

AnierinB said:
MSMDownloadTool
Click to expand...
Click to collapse
Can you help me?

SharpnessXVSlayer said:
Can you help me?
Click to expand...
Click to collapse
Just don't try to unlock SMT Download mode, it will wipe your IMEI and your Widevine certificate if you use it.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds).

You'll lose your imei

Rootk1t said:
Just don't try to unlock SMT Download mode, it will wipe your IMEI and your Widevine certificate if you use it.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds).
Click to expand...
Click to collapse
1. I have a backup of my EFS partition.
2. I don't have a target dropdown box in my MsmDownloadTool.
3. It doesn't boot at all, it goes straight to EDL mode.
Edit: I will try this though, so thanks for the help for now.

What the hek is going on?

I've got a Moto One 5G Ace that I picked up from eBay. It's an XT2113-2 according to the Recovery Mode 128/6. I guess the carrier was T-Mobile because the annoy screen always comes on when I boot. Fastboot lists it as
NK0T4M0308 fastboot
but when I try and write the recovery.img I get
fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) FAILED (Write to device failed (No such device))
When I try and use the Recovery and Smart Assistant(Windows) from Motorola
the IMEI doesn't match to the firmware
And it's stuck on Android 10, when I try and update from the phone it says it has the latest version of Android
When I try and run Rescue and Smart Assistant(RSA) and boot to the Recovery mode it soon drops and says it can't connect to the device
Mobile Assistant is installed by RSA but after RSA tries to detect the device in Recovery Mode but can't it can no longer detect the USB when it's attached. I need to reset the device so I can go through the entire process all over again.
Please help I don't know what's going on or how to fix it

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You have an engineering phone. It cannot be updated via regular ways.

RETIEF said:
You have an engineering phone. It cannot be updated via regular ways.
Click to expand...
Click to collapse
So what irregular ways can I employ then?

Send it to someone who has the tools to flash it. I don't know anyone but perhaps someone on the Telegram channel does.

Just in case anyone else comes across this problem too. The internal hardware is not the same as the model would indicate with the model number it's entirely different. So in other words, it's an entirely different phone, it can't be flashed to anything. It's like comparing apples to oranges they are in no way the same.

In Developer options, does it say "Bootloader is already unlocked" under OEM unlocking?
Does it still fail to load recovery if you run "fastboot boot recovery.img" so it says "Waiting for device...", then plug the phone in while holding down the volume and the phone is shut down? Even retail kiev can be really finicky in fastboot mode.
Really cool find in any case.

fddm said:
In Developer options, does it say "Bootloader is already unlocked" under OEM unlocking?
Does it still fail to load recovery if you run "fastboot boot recovery.img" so it says "Waiting for device...", then plug the phone in while holding down the volume and the phone is shut down? Even retail kiev can be really finicky in fastboot mode.
Really cool find in any case.
Click to expand...
Click to collapse
it would be cool if I could image it, but the internals don't match to what it actually is
but yes it does say the bootloader is already unlocked