Database Develop

[Q] Can't figure anything out

So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.

EvoTheBoy said:
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
Click to expand...
Click to collapse
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.

Seanie280672 said:
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Click to expand...
Click to collapse
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?

EvoTheBoy said:
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
Click to expand...
Click to collapse
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968

For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)

Seanie280672 said:
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
Click to expand...
Click to collapse
EddyOS said:
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Click to expand...
Click to collapse
I keep getting this error :/ Idk if this helps but it says s-on and hboot is 1.54 and my OS is 5.11.1700.3
{
"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"
}

That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)

EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
It is weird. I googled it and came about people saying to downgrade (Which I have 0 knowledge of when it comes to HTC devices.. coming from LG as my device with experience). Idk. Thanks for the help hopefully someone can help me out about this.

The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss

EddyOS said:
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
Click to expand...
Click to collapse
Guess that isn't the problem :/ I triple checked to make sure I had the right fastboot and I kept getting the same error.

EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
I've never seen that.. It's very odd.

graffixnyc said:
I've never seen that.. It's very odd.
Click to expand...
Click to collapse
I read online about it and saw some say to call google and they could help fix the problem cause it is a problem within the actual device. I called them and they didn't help lol. Anyways, my device is still under warranty and has the purple camera tint problem so I will try to send it in and hopefully get a new model back.
OT: if anyone has had this error before please say how you fixed it thanks

UPDATE: After some googling I found out that after 4.4.2 fastboot oem unlock does not work anymore with this devices (I am on 5.0.1)

Cannot unlock bootloader

I cant unlock my bootloader im running android 6.0.1 help plz!!!
When i type fastboot OEM unlock on cmd nothing happens on mobile and on cmd it just says finished and shows time taken

http://forum.xda-developers.com/sitesearch.php?q=unlock bootloader nexus 6

istperson said:
http://forum.xda-developers.com/sitesearch.php?q=unlock bootloader nexus 6
Click to expand...
Click to collapse
When i type fastboot OEM unlock on cmd nothing happens on mobile and on cmd it just says finished and shows time taken

What is the status when you boot into Fastboot mode?
I installed the MMB29K image and it was unlocked already.I never bothered to check the status,thinking I was having an issue.Maybe it is done already.

abeer04 said:
When i type fastboot OEM unlock on cmd nothing happens on mobile and on cmd it just says finished and shows time taken
Click to expand...
Click to collapse
1. Is Allow OEM Unlocking enabled in Developer settings?
2. Is your Android SDK up to date?
3. Is your phone recognized by your computer?
4. What does adb devices say?
5. When you reboot to bootloader what does fastboot devices say?
6. Did you try fastboot flashing unlock instead?

istperson said:
1. Is Allow OEM Unlocking enabled in Developer settings?
2. Is your Android SDK up to date?
3. Is your phone recognized by your computer?
4. What does adb devices say?
5. When you reboot to bootloader what does fastboot devices say?
6. Did you try fastboot flashing unlock instead?
Click to expand...
Click to collapse
1 OEM unlocking is enabled.
2 idk how to check i just downloaded them from website.
3 yes it is recognized by the computer.
4 adb devices shows nothing attached.
5 fastboot devices command shows the device serial number and fastboot written after to tab spaces.
6 idk about fastboot flashing unlock.

abeer04 said:
1 OEM unlocking is enabled.
2 idk how to check i just downloaded them from website.
3 yes it is recognized by the computer.
4 adb devices shows nothing attached.
5 fastboot devices command shows the device serial number and fastboot written after to tab spaces.
6 idk about fastboot flashing unlock.
Click to expand...
Click to collapse
Well then, read the sticky about adb a fastboot. Then you'll see that adb works in booted up and TWRP mode, and fastboot works in bootloader mode. Get the latest SDK tools from Google, it's also in the sticky. If everything's in place then try again everything I wrote, and paste here all output, and we'll try to help if it still doesn't work.

istperson said:
Well then, read the sticky about adb a fastboot. Then you'll see that adb works in booted up and TWRP mode, and fastboot works in bootloader mode. Get the latest SDK tools from Google, it's also in the sticky. If everything's in place then try again everything I wrote, and paste here all output, and we'll try to help if it still doesn't work.
Click to expand...
Click to collapse
can u give me a clean step by step procedure with links plz

abeer04 said:
can u give me a clean step by step procedure with links plz
Click to expand...
Click to collapse
My advice is that you really, really should read the sticky post. If you've read it, and something is still not clear, I'm more than happy answer any specific question:
http://forum.xda-developers.com/showpost.php?p=59785843&postcount=2

istperson said:
My advice is that you really, really should read the sticky post. If you've read it, and something is still not clear, I'm more than happy answer any specific question:
http://forum.xda-developers.com/showpost.php?p=59785843&postcount=2
Click to expand...
Click to collapse
when I try to unlock from toolkit it says encrypted.

abeer04 said:
when I try to unlock from toolkit it says encrypted.
Click to expand...
Click to collapse
Toolkit? What toolkit?
If you have read this (http://forum.xda-developers.com/showpost.php?p=59785843&postcount=2), as I suggested you should, then it clearly says, only use toolkits after you actually know what they do.

abeer04 said:
when I try to unlock from toolkit it says encrypted.
Click to expand...
Click to collapse
I can't figure it out either. I've been reading and searching for the past several hours. I made a thread and another user suggested I read the stickies. I read them and followed the rabbit further down the hole but I am not any further than when I posted a few hours ago.
My understanding is that you have to have to wipe your device entirely and flash another, previous, version of Android or an updated Kernel that allows encryption to be by-passed so that you can unlock the phone. What I don't understand is how to do that if you're already encrypted, how can you flash either if you're still locked? I can't flash or change kernels until I am unlocked but I cannot unlock my device until I flash a kernel or another version.

If you use sdk and tell us what the prompts say it may be more useful. Traditionally encryption isn't an issue for unlocking. Typically you check oem unlock then go into fastboot and type fastboot oem unlock.
It will either unlock or issue a command prompt. It's anyone's guess what is happening.

ghostofdavid said:
I can't figure it out either. I've been reading and searching for the past several hours. I made a thread and another user suggested I read the stickies. I read them and followed the rabbit further down the hole but I am not any further than when I posted a few hours ago.
My understanding is that you have to have to wipe your device entirely and flash another, previous, version of Android or an updated Kernel that allows encryption to be by-passed so that you can unlock the phone. What I don't understand is how to do that if you're already encrypted, how can you flash either if you're still locked? I can't flash or change kernels until I am unlocked but I cannot unlock my device until I flash a kernel or another version.
Click to expand...
Click to collapse
No, no, no. Encryption has nothing to do with unlocking. I'm sure there's a misunderstanding of the situation here. But until we see what was typed in the command line, and what the error message was, nobody can help you people.

istperson said:
No, no, no. Encryption has nothing to do with unlocking. I'm sure there's a misunderstanding of the situation here. But until we see what was typed in the command line, and what the error message was, nobody can help you people.
Click to expand...
Click to collapse
I get this error on nexus root toolkit by Wugfresh.
{
"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://prntscr.com/9pwad8

mikeprius said:
If you use sdk and tell us what the prompts say it may be more useful. Traditionally encryption isn't an issue for unlocking. Typically you check oem unlock then go into fastboot and type fastboot oem unlock.
It will either unlock or issue a command prompt. It's anyone's guess what is happening.
Click to expand...
Click to collapse
I get this and nothing happens on the mobile.
http://prntscr.com/9pwc4d

I can also teamviewer and skype if possible from your side.

abeer04 said:
I get this error on nexus root toolkit by Wugfresh.
http://prntscr.com/9pwad8
Click to expand...
Click to collapse
ok today I tried the latest version of the toolkit released today or yesterday night I think it doesnt show the error.it starts unlocking process normally but after doing everything the bootloader is not unlocked :V. The toolkit just gives commands and same as sdk it doesnt do anything.
http://prntscr.com/9pwgy8
as we can see in the live log it tries to unlock but nothing happenes.

and this is how my bootloader looks like just in-case xD
http://prntscr.com/9pwk7b

You've got and engineering device, you don't have to unlock it. Just start flashing.
And I'm really sorry you didn't take the time to look for the answers instead of insisting on pushing buttons on a tool.

Was told the VerizonDroid Turbo was rooted and needed to be unrooted.........plz help

did a lil research on google by what I was told........downloaded RSD Lite. When I went to look for phone info, noticed that there was NO IMEI info! No MIN, PRL Version, MEID,ICCID, IMEI, IMEI SV Unkown......No IP Address, No Wifi MAC Address or Bluetooth info...................there is a serial number tho. I can turn it on and play with it; it will go into bootloader or fastboot mode or what ever its called. From what ive read it came with kitkat version, it has lollipop installed. Is there anything I can do?

I'm thinking all that stuff should populate once you install a SIM card and put it on the network. If you really want a rooted phone, do it now with sunshine and unlock your bootloader. Otherwise, after you update to the latest marshmallow version, you will be forever hosed and not able to root at all. If the bootloader of states it is already unlocked, it's likely that sunshine has already been used.
A phone can't simply be unrooted to bet an update. The update will see the ROM is not pure stock, and fail. RSD can put a phone right, but can wipe the data. If rooted, why not put TWRP on, flash a stock rom in TWRP, saving data, reflash stock recovery in ADB, take update, TWRP back on, back up pure new-stock, mess with ROM. Little involved? Sure. More so than re-doing all your apps and settings? HELL NO!
Sent from my XT1254 using Tapatalk

cannon8694 said:
did a lil research on google by what I was told........downloaded RSD Lite. When I went to look for phone info, noticed that there was NO IMEI info! No MIN, PRL Version, MEID,ICCID, IMEI, IMEI SV Unkown......No IP Address, No Wifi MAC Address or Bluetooth info...................there is a serial number tho. I can turn it on and play with it; it will go into bootloader or fastboot mode or what ever its called. From what ive read it came with kitkat version, it has lollipop installed. Is there anything I can do?
Click to expand...
Click to collapse
Bootloader unlocked or nah? TWRP installed or nah?

cannon8694 said:
Was told the VerizonDroid Turbo was rooted and needed to be unrooted.........plz help
Click to expand...
Click to collapse
Who told you it was rooted?
Who told you it "needed" to be unrooted? Your post is very confusing.
I won't have a phone that is not rooted. All my phones WILL be rooted. Rooted means you are the "admin", you are the real owner.
In bootloader mode, what does the "status code" say? O, 3 ? What number do you see?

ChazzMatt said:
Who told you it was rooted?
Who told you it "needed" to be unrooted? Your post is very confusing.
I won't have a phone that is not rooted. All my phones WILL be rooted. Rooted means you are the "admin", you are the real owner.
In bootloader mode, what does the "status code" say? O, 3 ? What number do you see?
Click to expand...
Click to collapse
i just want the phone to work! would prefer it to be rooted, never had a rooted phone! status code = 0

TheSt33v said:
Bootloader unlocked or nah? TWRP installed or nah?
Click to expand...
Click to collapse
New to this........wtf is TWRP?

Okay, if status code is 0, that means your bootloader is locked. As long as you haven't taken all the over the air updates, you can still unlock it (and then root it). Follow this guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684

cannon8694 said:
i just want the phone to work! would prefer it to be rooted, never had a rooted phone! status code = 0
Click to expand...
Click to collapse
TheSt33v said:
Okay, if status code is 0, that means your bootloader is locked. As long as you haven't taken all the over the air updates, you can still unlock it (and then root it). Follow this guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Click to expand...
Click to collapse
If your bootloader is locked with status code of 0 (zero), your phone has NEVER been rooted and the bootloader has never been unlocked.
As @TheSt33v says, as long as you are not on the very latest firmware from March 2017, then you can unlock your bootloader and root your phone. Verizon released an update last month to block unlocking the bootloader on the Droid Turbo XT1254. Do NOT take any OTA updates!
TWRP is a "custom recovery" to replace stock recovery. It lets you make backups of your system (to restore your phone to earlier time in case of disaster) but also lets you "flash" zipped files like SuperSu to root.
If you are new to this, go read his guide in the link above, VERY CAREFULLY. All the information can be a little overwhelming. But do NOT take any OTA updates if you have not already. Because if you are on the very latest firmware, you are out of luck in unlocking the bootloader and rooting. Good luck.

when i type "fastboot flash recoveryTWRP.img"
ChazzMatt said:
If your bootloader is locked with status code of 0 (zero), your phone has NEVER been rooted and the bootloader has never been unlocked.
As @TheSt33v says, as long as you are not on the very latest firmware from March 2017, then you can unlock your bootloader and root your phone. Verizon released an update last month to block unlocking the bootloader on the Droid Turbo XT1254. Do NOT take any OTA updates!
TWRP is a "custom recovery" to replace stock recovery. It lets you make backups of your system (to restore your phone to earlier time in case of disaster) but also lets you "flash" zipped files like SuperSu to root.
If you are new to this, go read his guide in the link above, VERY CAREFULLY. All the information can be a little overwhelming. But do NOT take any OTA updates if you have not already. Because if you are on the very latest firmware, you are out of luck in unlocking the bootloader and rooting. Good luck.
Click to expand...
Click to collapse
when I type "fastboot flash recovery TWRP.img" into Minimal ADB and Fastboot it comes back "targer reported max download size of 536870912 bytes ; error: cannot load 'TWRP.img : No error"
did I possibly put the file in wrong place when it said to copy it to same directory as Minimal ADB and Fastboot?

cannon8694 said:
when I type "fastboot flash recovery TWRP.img" into Minimal ADB and Fastboot it comes back "targer reported max download size of 536870912 bytes ; error: cannot load 'TWRP.img : No error"
did I possibly put the file in wrong place when it said to copy it to same directory as Minimal ADB and Fastboot?
Click to expand...
Click to collapse
Reading the guide we told you about, have you unlocked your bootloader yet with Sunshine exploit? That's necessary prerequisite before trying to flash TWRP recovery.
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion. If you've already unlocked the bootloader, then ignore this question.

ChazzMatt said:
Reading the guide we told you about, have you unlocked your bootloader yet with Sunshine exploit? That's necessary prerequisite before trying to flash TWRP recovery.
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion. If you've already unlocked the bootloader, then ignore this question.
Click to expand...
Click to collapse
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?

cannon8694 said:
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
Click to expand...
Click to collapse
You can install a file manager app from the play store. ES is probably the most popular free one but I prefer File Manager+.
Definitely do more research on unlocking the bootloader and flashing things, once you get root you can make mistakes which can brick your phone. But with that responsibility comes more freedom to do what you want to your device.
Sent from my XT1254 using Tapatalk

ChazzMatt said:
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion.
Click to expand...
Click to collapse
cannon8694 said:
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
Click to expand...
Click to collapse
Before we go any further, please go to Settings/About Phone, and look at your build number.
{
"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"
}
Here's some examples above. It will look something like this, on one of those screenshots. We need you to tell us EXACTLY what the "Build Number" says on your phone, please?

My WiFi is saying unavailable. Can't connect in order to get app store

cannon8694 said:
My WiFi is saying unavailable. Can't connect in order to get app store
Click to expand...
Click to collapse
Not asking about Wi-Fi or anything in the apps store.
Just tell us the build number in Settings/About Phone. Type in the exact numbers and letters, please.
Take a screenshot if you have to.
Capture a Screenshot - DROID TURBO by Motorola. To capture a screenshot, simultaneously press and hold the Power and Volume Down buttons. To view the screenshot you've taken, navigate: Apps > Photos from a Home screen.
Click to expand...
Click to collapse
But you can also just look at the screen and type.

SpyderPride said:
You can install a file manager app from the play store. ES is probably the most popular free one but I prefer File Manager+.
Definitely do more research on unlocking the bootloader and flashing things, once you get root you can make mistakes which can brick your phone. But with that responsibility comes more freedom to do what you want to your device.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
but how do I get it to install on my phone with no sim card, service or wifi

ChazzMatt said:
Not asking about Wi-Fi or anything in the apps store.
Just tell us the build number in Settings/About Phone. Type in the exact numbers and letters, please.
Take a screenshot if you have to.
But you can also just look at the screen and type.
Click to expand...
Click to collapse
SU4TL-49

cannon8694 said:
SU4TL-49
Click to expand...
Click to collapse
Fantastic. You're eligible for bootloader unlock. Just don't take any OTA updates from Verizon.

ChazzMatt said:
Fantastic. You're eligible for bootloader unlock. Just don't take any OTA updates from Verizon.
Click to expand...
Click to collapse
ok but im stuck on installing the sunshine.apk on the phone, and it said to copy the twrp.img to the same directory that minimal adb and fastboot? what that mean

cannon8694 said:
but how do I get it to install on my phone with no sim card, service or wifi
Click to expand...
Click to collapse
SIM cards are free, go pick one up or order one and activate the phone?
Sent from my XT1254 using Tapatalk

Hardbricked G6 Plus

Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!

Can you still boot in the bootloader?

Thomas Hunter said:
Can you still boot in the bootloader?
Click to expand...
Click to collapse
Yes, bootloader is working fine.
Just Recovery isnt working, it goes in but wont load menu.

You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
OEM unlock is unticked so... I cant really unlock the bootloader..

The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
I tried to unlock it but i always got an error, something like "go to Settings and activate OEM Unlock" or something like this..

Could you provide a image

Thomas Hunter said:
Could you provide a image
Click to expand...
Click to collapse
Sure!
{
"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"
}

TrueGodFlow said:
Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!
Click to expand...
Click to collapse
Hi, Dan...
I really do wish I had some good news to impart, but sadly I suspect your Moto G6 Plus is probably not recoverable.
The OEM Unlocking setting in Developer Options is part of Googles Factory Reset Protection scheme. Ostensibly, it's designed to prevent lost or stolen devices from being reflashed back to stock and dishonest individuals then claiming the device as their own.
I ran afoul of this myself, four years ago, with my (then) new Nexus 9 tablet which originally shipped with Android 5, Lollipop and it was the first device I'd owned that required OEM Unlocking to be enabled in Developer Options before the bootloader could be unlocked.
I won't bore you with the details here, but if you have a mind to, you can read about my thwarted endeavours to resurrect my Nexus 9 here...
https://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Fortunately, my Nexus 9 was still new, and I had a no-quibble warranty that I'd paid extra for, so I was able to get it replaced at the store from which I'd bought it.
-----------------------------------------
Around 2015 a solution (of sorts) was eventually found for this problem, for both the Nexus 6 phone and the Nexus 9 tablet, however it required a very specific set of criteria for it to work.
The OEM Unlocking setting in Developer Options flips a binary state flag, from either ON (Enabled) or OFF (Disabled) and it's stored in a special Persistent (PST) partition, which doesn't get touched when factory resetting the device, when receiving OTA updates or when reflashing it. As the name suggests, it 'persists'.
So it required somebody to create a dump image file of the PST partition with the OEM Unlocking flag already set to ENABLED on their device. This dump image file would be created by using a <dd, if, of> command in a terminal shell.
The person whose device was semi-bricked, would download this dump image file of the PST partition, and flash it to their device using a similar <dd, if, of> shell command, via ADB in TWRP Custom Recovery. This would overwrite their PST partition, where the OEM Unlocking flag is NOT enabled...
...with a version where it IS enabled, and consequently fastboot flash commands would then work.
*****
It required root on both devices, and TWRP custom recovery to be already flashed on the semi-bricked device, since ADB shell commands can not be run in the normal stock recovery.
You can read about the technical details here...
https://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
-----------------------------------------
Theoretically, the method detailed above could perhaps be adapted for the Moto G6 Plus ~ you'd just need to find somebody with an already rooted Moto G6 Plus prepared to create a dump image file of their PST partition, with the OEM Unlocking setting enabled, and your G6 Plus would also need to be able to boot into TWRP to run the necessary ADB shell command to flash it.
And which is impossible, since (due to your locked bootloader) you can't either remotely boot TWRP from a laptop using fastboot boot twrp.img or flash it directly using fastboot flash recovery twrp.img
As I say, I wish I had better news for you.
-----------------------------------------
I hope all of the above makes sense; it is a little technical.
If I have any ideas that may be helpful, I'll post them here. But as it stands right now, and knowing what I know about this topic, I'm not optimistic there is a solution to your problem.
Ged.

The only other thing I can think of that may or may not work is a blankflash. Search the forums for it.
Sent from my moto g(6) plus using Tapatalk

You don't need to unlock oem as I got the same problem a year ago with my moto g5 plus so basically what I did was keep trying to flash a different fimware and eventually it worked with installed a firmware with oem locked.

General Progress/How to in modding(rooting, recoveries,etc)

Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
EDIT: IT SEEMS LIKE WE CANT UNLOCK THE BL
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash

#YetAnotherPerson said:
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
Click to expand...
Click to collapse
Hi! Thanks for requesting this page!
For anyone considering buying this phone, just like OP said, DON'T buy if you want to MOD it in any way!
Also, if anyone has any information on this phone, like the firmware, exploits, etc. PLEASE share it since this device is not even that known in XDA.

Sad update, I backed up my Linux computer to install windows and use many apps to retrieve stock firmware for rooting and when device gets bricked, but no success, and I installed Linux again. I did not dual boot because of storage issues

Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are

#YetAnotherPerson said:
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
Click to expand...
Click to collapse
But wouldn't we need to at least unlock the bootloader to flash anything?

JoeBro19 said:
But wouldn't we need to at least unlock the bootloader to flash anything
Click to expand...
Click to collapse
There is a bootloader unlock option in settings, developer options

#YetAnotherPerson said:
There is a bootloader unlock option in settings, developer options
Click to expand...
Click to collapse
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...

JoeBro19 said:
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
Click to expand...
Click to collapse
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!

#YetAnotherPerson said:
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
Click to expand...
Click to collapse
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.

JoeBro19 said:
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
Click to expand...
Click to collapse
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them

#YetAnotherPerson said:
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
Click to expand...
Click to collapse
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.

JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet

#YetAnotherPerson said:
Ok, but
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
Click to expand...
Click to collapse
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.

JoeBro19 said:
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
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"
}

#YetAnotherPerson said:
View attachment 5902653
Click to expand...
Click to collapse
Just as I thought.... damn this companies...
So, unless some miracle happens and someone discovers an exploit on the processor or something that allows us to decipher the unlock code, there is absolutely nothing than we can do...

You can only unlock the bootloader on the new Honor at the Honor office. But this is only possible if the Honor employee is your friend.

volkodav1975 said:
You can only unlock the bootloader on the new Honor at the Honor office. The workers there have such smartphones, I have a friend among such workers and he made a request for me in a friendly way. I think that you will not see such a photo anywhere else. Alas, as long as it's useless, I need a custom one Recovery, But I don't know where to get it.
Click to expand...
Click to collapse
Well that's... disappointing... can't believe we have to even consider that. In my case, we don't have those centers, so I'm definitely screwed... good job Honor...