Database Users

[UPDATED]Recover your dead X8/W8.

Hello there fellow X8/W8 users!
This post is intended to point your attention to the simple fact that there's a hardware imposed danger to hard brick your Xperia X8 and W8, applies to E15i/a and E16i/a, at the attempt to unlock the boot loader!
The phones affected by the problem are units being manufactured at, and after, 11W29!
To check if your device is affected by the problem follow this simple steps:
Turn off the phone and open it up
Take out the battery
Look at the sticker below
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
These phones ship with a revamped chipset configuration having the security hole the boot loader unlock uses effectively closed. This means that upon unlocking the boot loader your phone will end up as a hard brick - and you will have NO means to revive the phone yourselves. You either have to send it off to Sony for repair (recommended solution) or find a phone repair shop being able to resurrect shot devices!
The symptom you will experience when unlocking the boot loader on an affected device is like this:
The boot loader unlock will most likely go through fine
At restart the phone will show NO signs of life anymore.
NO LED, NO LCD output, NO vibration.
This is the point where you can not do anything anymore yourself to resurrect the device.
You have been warned, DO NOT TRY to unlock the boot loader on phones manufactured PAST 11W29!
But it has been seen that there are few devices with manufacturing code above 11W29 have also successfully unlocked their bootloader.
For example me,i have 11W34 and unlocked the bootloader just fine..
But let me remind you again that this was just a matter of luck.
You might not be so lucky...
Also if you have manufacturing code above 11W29 and are desperate to unlock your bootloader then there are paid methods for it as reported by few users who had successfully unlocked their bootloader with manufacturing date above 11W29.
Update (2012/02/23):
To clear up the "no means to resurrect the phone yourself": This is true unless you are a experienced electronics technician. If you own a JTAG box (RIFF Box, Medusa Box) you may attempt to resurrect the device through JTAG. It may also be possible to resurrect the device through UART flash by using a test pin connection. Google is your friend here to dig up the required informations.
As posted by baiclark: There's an option to unlock the boot loader on 11W29+ devices, though this involves some Software (setool2) where you need to buy credits to perform the unlock. This is an untested procedure. If you decide to jump the gun please report your experience.
Update: Home-Brew unbricking with Omnius
Forum member aze2learn posted a guide about how to unbrick your hard bricked W8/X8 by using a modified Nokia CA-42 cable and Omnius. Find his valuable contribution at this post.
/!\ Be warned that this requires basic electronics skills to make it happen. /!\

Unbrick your briked X8/W8 via flashtools
Hi all
I made this thread since some guys were having trouble unbricking their X8/W8 via FLASHTOOLS...
And let me make it clear that the following post wont help you if your phone has bricked in attempt to unlock your bootloader when your phones manufacturing code was above 11W29.
In such a case the only (period) solution is to send it off to SONY to have it repaired.
How to unbrick your Soft Bricked phone..
What do you need?
Flashtools.(thanks to androxyde and bin4ry)
X8 stock firmware.
Or from here.
Or here.
X8 drivers installed.
WinRar
Your X8/W8 phone
A USB cable
A PC
Relaxed mind..
Click to expand...
Click to collapse
Now lets begin.
1.First of all download and install Flashtools from the link provided above.
2.Download SE firmware in *.ftf file format and put it in Flashtool/firmwares folder.
3. Now, run the FlashTool and click the
{
"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"
}
Lighting bolt button to start flash.
4.Now click flashmode and choose Xperia X8 (E15i).
4.Now wait for a while till it says you to "remove your phone,press the back button and hold it and install the USB".
Do it and wait for the flashing proceedure to finish...
If everything works fine then CONGRATULATIONS!!!!!! you have successfully unbricked your phone and installed the 2.1.1.A.0.6 version with 015 baseband, fresh and stock!
If your phone doesnt boots up still, then you might have gone wrong somewhere in the flashing process..
So read the steps carefully and do it again..
[OPTIONAL STEP]
Guide for installing the required drivers for flashing, skip this if you have PC Companion installed and connected your phone in flash mode at least once!
If your phone is not recognized by Flashtool that means you don’t have the required drivers installed.
Open folder /Flashtool/drivers and install ggsetup-2.2.0.11
If after the above Flashtool still doesn’t recognize your phone, do the following:
From Flashtool/drivers folder extract the zip file XXX_ADB_driver which corresponds to your phone model
Open “Device manager” on the computer and find the device which is with an exclamation mark on it (do this with connected to the computer phone)
Right click on the device and choose Uptade driver
Choose to find the driver manually and browse to the folder where you’ve extracted the zip file.
That should install the required drivers on your computer.
Click to expand...
Click to collapse
Now as you have successfully unbricked your phone, the first thing you would possibly do is rooting your phone...
So here i show you how to Root your phone with flashtools..
1.Start Flashtool
2.Connect the device to the computer and wait until it's recognized
3.Click the icon with the "Padlock [the second in a row]
4.FT will start pushing files, wait till it finishes. Meanwhile the phone will reboot once.
5.When it's over Flashtool will notify "Root Access Allowed"
6.Open the application list on the phone and look for the app "Superuser".
7.If "Superuser" is there you have Rooted your device successfully.
Congrats!
That's it...........
If you found this thread useful don't forget to click the THANKS button for me...
Thanks to
Bin4ry and androxyde..(for flashtools)
crowds for the original guide..
Leajian for allowing me to use content from his guide.
BlackRabbit1703 for the mirror of firmware.
And all the people who liked my work...
See ya..

um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.

I have 11W33 and unlocked 2 times now without a problem ! and works fine

Realtbhuion said:
um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.
Click to expand...
Click to collapse
We also had a few phones in the 11W3x region that unlocked perfectly, but the hard bricks we observed so far all start at 11W29 - and newer.
The source from where we got the information about the hard brick danger is a post of the_laser on setool.net ...
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
Click to expand...
Click to collapse
As you can see the_laser referenced 11W26 as the "threshold" where our observation is that 11W29 is where the trouble really starts.
EDIT: See this thread for reference - post #62 and #63 where we summed up a few hard bricks. But that's just the tip of the iceberg, there have been way more.
You're of course free to dismiss the warning and do as you please, just don't come ranting about your hard brick - you've been warned.

My phone is 11W30 (I forgot to check this before unlock bootloader) but all works fine for me.

Mine was 11W37, and I said "was" 'cause I just bricked it.
So Im reading this thread too late lol
However, this situation only hurries things because I'm getting Xperia Ray soon. Now I have to get it sooner.
For now, I have a fa(i)lPhone, wich was a present from my dad. So no worries at all. But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it! If not, then I'll have a nice modern piece of decoration for my living room: a smartphone XD

x8-11w37 new phone HARD BRICK!
I was lucky ennough they replaced my bricked x8. . No unlocked bootloader for me.

El Brillantinas said:
Mine was 11W37, and I said "was" 'cause I just bricked it.
But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it!
Click to expand...
Click to collapse
To be precise - there is something that can be done, it's just not very easy.
On the one hand you can try to read up over at setool.net. The latest versions of SETool are able to resurrect shot W/X8's. However, you either need to know to which test-pins to you need to connect the cable from your computer or simply try to get one of the Qualcomm resurrection cables fitting the W/X8. Apart from that you need "credits" for SETool to actually perform the operation. This means you have to pry your W/X8 apart to gain access to the PCB - that's not exactly something everyone around here is able to do - and connect to the right pins to flash in UART mode.
On the other hand you can always try to find someone (private person / repair shop) having a RIFF Box to see if the phone can be resurrected by JTAG, though the way it sounds (the post I read on setool.net about UART resurrection) a JTAG restore seems to be impossible - but feel free to try.
If you can work out a working, and relatively simple to follow, solution to restore shot W/X8's be our guest to write up a post.

thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?

Can i unlock my bootloader?
My W8 code is 11W25 can i unlock my bootloader??

B.Jay said:
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
Click to expand...
Click to collapse
NarutoDroid said:
thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?
Click to expand...
Click to collapse
akhi24nick said:
My W8 code is 11W25 can i unlock my bootloader??
Click to expand...
Click to collapse
So ... 11W28 and 11W25 are below 11W29, right?
No guarantee given as there's always the chance that you may mess up, but it should be safe to try and unlock the boot loader.

Mine is 11W21 (uhm semms a old version or something like that...?), soon I'll try unlocking...
But it has a f..... sinaptic touchscreen, damn...

Hmmmm..... I got 11W34 and i can unlock my Droid

11W48
Hi there,
actually I was following guides in the manner google -> blogs -> direct links to oneclickroot/roms -> direct links to bootloader unlocker and...
Well, unfortunately 11W48 (pretty fresh, huh?) got hard bricked xD
I understand it's motherboard failure now and we can do NOTHING more than sending my new paperweight back to SE?
Also I'm looking forward to finding another way to unlock bootloader with new chips in case the one I get back won't be <11W29
Thanks in advance for your reply

Ahh i wish so much i had red this thread and didn't act too much excited about unlocking it.

10W48 ---> unlock with flashtool!

2010matej said:
10W48 ---> unlock with flashtool!
Click to expand...
Click to collapse
Man.... You are exceptional on EARTH.....
You unlocked bootloader with 11w48 making. You have battery backup beyond 6 days.
May be you can overclock your X8 upto 1Ghz and have Multitouch instead of dualtouch even its also possible that SE will make a firmware 4.0 only for you....
Really, you are an amazing guy...

that's very good to warn everyone here before attempting ^^

my is 11w06

LG G4 (all variants) Unlock and Root Discussion/News (ONLY)

Hoyo folks.
So I'm sure you've all seen the plethora of "Do we haz root?" "How 2 unlok?" "unlok guide here"(which doesn't work) ect. Here in this thread I will attempt to summarize the current status of Unlock, Custom Recovery, and Root for each model.
Some of our devs now have Devices in hand, THANK YOU TO ALL THAT HAVE DONATED! It REALLY helps the entire G4 community! Now we wait with baited breath. (No pressure guys)
So without Further ado, here is a list of the status of all devices.
CURRENT Unlock/Recovery/Root Status, in order of success:
H815 (Europe Open model ONLY) -
Unlocked? - YES (Via LG's Official Unlocker)
Custom Recovery? - YES (TWRP info)
Root? - YES (Root Info)
NOTE: LG's offcial unlocker is a PERMANENT change. You cannot Re-lock, if you wanted to send in for a warranty claim. If you aren't willing to do that, lets wait and see if the dev's efforts will pay off with a more friendly unlock (which it may or may not)
H815 (Asia) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (USA) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (France) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815TR (Turkey) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818P (Thailand) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818N -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H811 (T-Mobile) -
NO to all - and "adb reboot bootloader" doesn't work
H810 (AT&T) -
NO to all - and "adb reboot bootloader" doesn't work
LS991 (Sprint) -
NO to all - and "adb reboot bootloader" doesn't work
F500S -
NO to all - and "adb reboot bootloader" doesn't work
F500K -
NO to all - and "adb reboot bootloader" doesn't work
F500L -
NO to all - and "adb reboot bootloader" doesn't work
VS986 (Verizon) -
No to all - and "adb reboot bootloader" doesn't work, AND no "Enable OEM Unlock" in developer settings.

I suggest editing the thread title to be more concise/official since that is the intent of this thread:
Something like "LG G4 (all variants) Root Discussion/News"

After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!

For any one that ones the source code is available from LG.
T-Mobile
International
Both kernels are compile-able with a little finagling.
On Root:
From what I can see in the International code is there are the defprefs for all of the p1 versions, and it doesn't "Appear" to have ping pong patched.
I have heard "rumors" that jcase , autoprime and thecubed, are working on a root for the device, but I have not heard from either of them. They did just release pingping v6 which supports the M9, a 64-bit kernel, meaning they have made one that works with the 64-bit linux kernel. For any one curious about their progress you can always check them out on twitter. For those of you posting about root and such, you can always see if there is anything you can do to support them in their efforts.
Thanks for making the thread, I think this phone will be a fun one, and I do expect to see some great things happen.
Have a good day all!

H818P Thailand can use adb reboot boot loader

MicroMod777 said:
After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!
Click to expand...
Click to collapse
Thanks for confirming. Same behavior on my TMo G4.

Not as skilled as some but I do currently maintain the HTC One M8 for DirtyUnicorns.
I have my G4 pre-ordered from Verizon. It has shipped today and current tracking has it arriving Tuesday 6/2. If no one beats me to it, I will post at least the basics of how that variant functions in terms of adb and fastboot. Anything else needed I will gladly try to provide from the VZW variant.

Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Yes

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.

barcodelinux said:
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.
Click to expand...
Click to collapse
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
I know with the last LG I had, the Optimus L90, there was a LAF partition the you had to zero out to get to fastboot. Once that was done, you could:
Code:
fastboot oem unlock
Now this was on a T-Mobile device, and T-Mobile is known for not locking bootloaders. I don't remember having an unlock.bin file, but I could be mistaken.

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
Well we have 14 days to return it if LG doesn't give us what we need!

MicroMod777 said:
Well we have 14 days to return it if LG doesn't give us what we need!
Click to expand...
Click to collapse
That's true. I actually haven't purchased mine yet but I had high hopes for this device. Was going to be my first carrier-supplied phone. I guess I'll wait for the oneplus 2 if this doesn't get sorted out.

Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.

barcodelinux said:
Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.
Click to expand...
Click to collapse
You need to install the LG device drivers first

has anyone tried to get into the bootloader on linux? a couple phones i had, you had to use sudo, then type the absolute path to platform-tools, even if you open terminal within the sdk, I.E.,
sudo /home/username/SDK/platformtools/fastboot oem unlock " or adb reboot-bootloader"
sometimes had to use su, im sure you could do the same on windows.
anyway worth a shot.

H815 - International variant here with me can officially use adb reboot bootloader
fw: V.10A

So far i got this but after this pc won't recognize phone have to reboot
{
"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"
}
https://imageshack.us/i/exlSOF19j

Worked for me on my LG-H815... It's possible to check the status of the bootloder.
Mine says it's locked. Now there's an option to: "fastboot flash unlock unlock.bin"
But where is the unlock.bin file?

[Q] Bootloader Unlocked ?

my new S7 Edge (No Brand Europe) it show me OEM UNLOCK line under Developer Options Tab
I have turned on button and restarted device.
So, Can this device be Bootloader unlockable ?
{
"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"
}

wolfgart said:
my new S7 Edge (No Brand Europe) it show me OEM UNLOCK line under Developer Options Tab
I have turned on button and restarted device.
So, Can this device be Bootloader unlockable ?
Click to expand...
Click to collapse
Yes.
Oh, and thanks for making me excited before I read you weren't referring to a Vodafone branded model.

Beefheart said:
Yes.
Oh, and thanks for making me excited before I read you weren't referring to a Vodafone branded model.
Click to expand...
Click to collapse
YES? Sure ?
So, How to boot device in Fastboot mode to unlock bootloader ?

wolfgart said:
YES? Sure ?
So, How to boot device in Fastboot mode to unlock bootloader ?
Click to expand...
Click to collapse
You don't need to unlock it, that toggle being there means the bootloader isn't locked in the first place. Just untoggle it and you're good to go. Besides, I knew for a fact before I created this thread that the non-branded international model didn't have a locked bootloader. Samsung do not lock bootloaders, certain carriers when they order their phones ask Samsung to lock the bootloader for them before then applying bloat and carrier features. I'm just hoping at this point that Vodafone UK isn't one of them.

Beefheart said:
You don't need to unlock it, that toggle being there means the bootloader isn't locked in the first place. Just untoggle it and you're good to go. Besides, I knew for a fact before I created this thread that the non-branded international model didn't have a locked bootloader. Samsung do not lock bootloaders, certain carriers when they order their phones ask Samsung to lock the bootloader for them before then applying bloat and carrier features. I'm just hoping at this point that Vodafone UK isn't one of them.
Click to expand...
Click to collapse
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk

EDIT...............

Beefheart said:
Great. Not what I read. How do you find out the bootloader is unlocked then?
Click to expand...
Click to collapse
You try to flash a custom kernel using ODIN, if it boots, it's unlocked.
I would assume there is an indication of whether your device is locked or not in the rom download screen as well.
Beware that flashing a custom kernel on the device will trip the knox counter to 0x1, which on Snapdragon SOC is irreversible (a fuse is blown), it can be undone on the Exynos version (as the flag is stored in eMMC) if the Engineering/JIG firmware ever leaks (this happened a while back on the Note 3)

mathieulh said:
You try to flash a custom kernel using ODIN, if it boots, it's unlocked.
I would assume there is an indication of whether your device is locked or not in the rom download screen as well.
Beware that flashing a custom kernel on the device will trip the knox counter to 0x1, which on Snapdragon SOC is irreversible (a fuse is blown), it can be undone on the Exynos version (as the flag is stored in eMMC) if the Engineering/JIG firmware ever leaks (this happened a while back on the Note 3)
Click to expand...
Click to collapse
Here my screen on Download Mode :
Fap Lock is OFF

wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
That's FRP, which stands for Factory Reset Protection. This relates to the OEM Toggle option I talked about earlier in the thread. I was under the impression that, in order for that to be off when you get the phone, the bootloader is unlocked. But according to _Dennis_ that isn't the case.
I would really like an easy way of finding out if Vodafone have locked this bootloader without flashing a custom kernel, of which there are none at the moment anyway. If this thing is locked, I'm returning it so only have a small window to do so.

Been searching everywhere, but it seems the only way to tell this for sure is to flash a custom ROM\Root the phone and see if it works.
Going by past experience with Vodafone since the original S phone, it hasn't been locked, so it would be a shame if they have decided to start doing this!
---------- Post added at 11:04 AM ---------- Previous post was at 11:00 AM ----------
http://forum.vodafone.co.uk/t5/Samsung-Galaxy-S7-Edge/S7-Edge-Bootloader-Unlocked/m-p/2475021
Most latest posts on that thread indicate its unlikely to be locked, but we still need to wait and see.
We may even have to wait for root to become available before we can find out!

EDIT..............................

if its an international non carrier, sim free and purchased outright from samsung or anywhere else; then the boot-loader is unlocked or at the very least easily unlockable

_Dennis_ said:
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
I've since discovered your claim is completely wrong, it has nothing to do with selinux state, and it is related to the bootloader as I indicated. Read the following:-
http://android.wonderhowto.com/insp...ndroid-even-if-you-dont-plan-rooting-0167840/
Also, look at the description under the toggle.
However, I'm unsure if it does indicate the bootloader is unlocked at this time.

Beefheart said:
I've since discovered your claim is completely wrong, it has nothing to do with selinux state, and it is related to the bootloader as I indicated. Read the following:-
http://android.wonderhowto.com/insp...ndroid-even-if-you-dont-plan-rooting-0167840/
Also, look at the description under the toggle.
However, I'm unsure if it does indicate the bootloader is unlocked at this time.
Click to expand...
Click to collapse
Interesting. Ill see what mine says when I get home. Its strange I never had this on my other Samsung S devices, so it must be new.

My Verizon S7 Edge also has this toggle. I don't know if it actually unlocks the bootloader though.

Blart said:
My Verizon S7 Edge also has this toggle. I don't know if it actually unlocks the bootloader though.
Click to expand...
Click to collapse
Could you boot into your download mode and post a photo of the screen? I'd like to compare it to mine.

Beefheart said:
There is a way. Go into download mode, connect to PC and you can check via the fastboot command in a command prompt.
> fastboot devices (to check if the device is seen)
> fastboot oem device-info
Look for:-
Bootloader unlock allowed - Yes >> This means that your Bootloader is Locked
Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Click to expand...
Click to collapse
strange, i don't have fastboot commands works on Download mode.
I always use them with my LG G4
it seems fastboot commands are not allowed ...

My wife said the same when I run through the instructions at home over the phone, I thought it was simply my laptop and a driver error. But perhaps there is an issue with the fastboot command with the S7's bootloader.
I need to find out today if this thing is bootloader unlocked, so I can return it fast if it isn't.

wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
This download screen is identical to mine.

_Dennis_ said:
Wrong, that toggle is not bootloader unlock, nor is it an indication you can unlock your bootloader. It simply is a setting within android OS to allow you to use selinux permissive kernels. Even the AT&T S6 had it, and their bootloader is locked down tighter then a submarine.
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
The dumb thing about this is if you can't boot the phone you cant toggle that option, you can't unlock the bootloader to flash a stock rom.
wolfgart said:
Here my screen on Download Mode :
Fap Lock is OFF
Click to expand...
Click to collapse
Heh fap lock

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

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

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

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

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

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

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

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

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

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

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

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

[TOOL][MIDO] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi Redmi Note 4's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Is there any source code available? I don't see many people using something like this when there are device-specific alternatives that are open source as well.

JosVermeulen said:
Is there any source code available? I don't see many people using something like this when there are device-specific alternatives that are open source as well.
Click to expand...
Click to collapse
This tool is not open source and it is device-specific for all Official supported devices.
I don't know others alternatives and I'm not interested in knowing them.
If you want to use it, ok, if you don't want to use it, it's always ok just don't bother others users

Good Job
It will make things easier for our device

v1da said:
Good Job
It will make things easier for our device
Click to expand...
Click to collapse
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working

mauronofrio said:
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
Click to expand...
Click to collapse
Then this app is mostly useless...
Don't write all in one, including boooader unlock if it does not unlock bootloader. The only way to unlock a Xiaomi Bootloader is via the official app. So either remove bootloader unlock or all in one from the title because it is misleading.

greenys' said:
Then this app is mostly useless...
Don't write all in one, including boooader unlock if it does not unlock bootloader. The only way to unlock a Xiaomi Bootloader is via the official app. So either remove bootloader unlock or all in one from the title because it is misleading.
Click to expand...
Click to collapse
The name is that and will not be changed, this tool is not written only for xiaomi devices but also for others devices. Unfortunately Xiaomi devices needs to be unlocked through official method and this is why they have not been added until now. In all cases clicking on unlock you will be redirected to a good guide to unlock xiaomi devices.

mauronofrio said:
The name is that and will not be changed, this tool is not written only for xiaomi devices but also for others devices. Unfortunately Xiaomi devices needs to be unlocked through official method and this is why they have not been added until now. In all cases clicking on unlock you will be redirected to a good guide to unlock xiaomi devices.
Click to expand...
Click to collapse
Whatever it was designed for it does not work as intended with Xiaomi devices. So you should not have shared it with that title because it is not true. Without bootloader unlock you cannot do mainly anything and this app is not designed to unlock MI devices. It is my opinion that you shouldn't have shared it here under that name because it's very misleading. I've told you what you should do to make it not misunderstandable but you refuse to take my advice. See, whatever. You told your own opinion and I've told mine. Topic closed.

greenys' said:
Whatever it was designed for it does not work as intended with Xiaomi devices. So you should not have shared it with that title because it is not true. Without bootloader unlock you cannot do mainly anything and this app is not designed to unlock MI devices. It is my opinion that you shouldn't have shared it here under that name because it's very misleading. I've told you what you should do to make it not misunderstandable but you refuse to take my advice. See, whatever. You told your own opinion and I've told mine. Topic closed.
Click to expand...
Click to collapse
He'll just say "If you want to use it, ok, if you don't want to use it, it's always ok just don't bother others users." and ignore any valid remarks.

JosVermeulen said:
He'll just say "If you want to use it, ok, if you don't want to use it, it's always ok just don't bother others users." and ignore any valid remarks.
Click to expand...
Click to collapse
Again, i don't say what he said it's not true, i said that this is the name of the tool and that is the name of dedicated support threads. Unlock option is not available for xiaomi devices (except for Xiaomi Mi A1), in its place you will find the link to a guide to unlock the bootloader. Now if you want to tell me that a recovery on the tool is not working, or you want i add a new recovery to the list or you have problem with the tool, comment and i will try to help you, but do not keep saying unnecessary things.
Thanks and have a good day

mauronofrio said:
Again, i don't say what he said it's not true, i said that this is the name of the tool and that is the name of dedicated support threads. Unlock option is not available for xiaomi devices (except for Xiaomi Mi A1), in its place you will find the link to a guide to unlock the bootloader. Now if you want to tell me that a recovery on the tool is not working, or you want i add a new recovery to the list or you have problem with the tool, comment and i will try to help you, but do not keep saying unnecessary things.
Thanks and have a good day
Click to expand...
Click to collapse
Whatever floats your boat. You too have a good day.

ouch, i was here to unlock my 2nd mido in the fast way, well the app cant unlock bl

Very promising tool! Many thanks for your work Dev.

Can this tool flash stock images on the device with locked bootloader, or do I have to use edl?

mauronofrio said:
This is the Xiaomi Redmi Note 4's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
Click to expand...
Click to collapse
where is the download ?

miaoudak said:
where is the download ?
Click to expand...
Click to collapse
Are you kidding, right? Don't be a write-only user.. Read the post you've replied to and follow the links.. literally the first line of the quoted #1 post points to the original thread where the download links are available (one main and 3 alternatives)..

its execute from fastboot mode or edl sir...

has someone tried it and is it still working today?

Just DL this morning to test