Database Develop

[Q] So tired.. I will give up with these alien words.

Guys I have been looking through tutorials for rooting etc. I know I am the 23473047230th noob asking around and believe me the last option for me was to post here. I have made the unlocked bootloader (yaaay! :victory: ), and then as I am on 4.3 - 12.1.A.1.201 I said oh wait! I read on various comments that the Wi-Fi is not working after flashing the kernel into 12.1.A.0.266 so I freaked out and did not proceed.
My question comes. Flashing a kernel into 12.1.A.0.266 is just downgrade so as to root it? I am reading this guide which has not detailed info (for noobs)
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf to the folder containing fastboot binary
flash the SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf using fastboot:
Click to expand...
Click to collapse
I have downloaded this file "SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf" and got a Flashtool. On a video guide it says to move the file into D:\Flashtool\firmwares is it right? Do I need anything else? Should I proceed? After this I will proceed with this root guide
Rooting Instructions
[ how to root ]
once you have flashed the kernel from the 1st post
download the latest SuperSU update.zip from: http://download.chainfire.eu/supersu
save it on sdcard of device
reboot into recovery
flash the supersu update.zip
reboot from recovery into OS
you should now get proper root access!
Click to expand...
Click to collapse
... and then I will throw a heavy metal party to relax and stress out of my nerves!

IreneGR said:
Guys I have been looking through tutorials for rooting etc. I know I am the 23473047230th noob asking around and believe me the last option for me was to post here. I have made the unlocked bootloader (yaaay! :victory: ), and then as I am on 4.3 - 12.1.A.1.201 I said oh wait! I read on various comments that the Wi-Fi is not working after flashing the kernel into 12.1.A.0.266 so I freaked out and did not proceed.
My question comes. Flashing a kernel into 12.1.A.0.266 is just downgrade so as to root it? I am reading this guide which has not detailed info (for noobs)
I have downloaded this file "SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf" and got a Flashtool. On a video guide it says to move the file into D:\Flashtool\firmwares is it right? Do I need anything else? Should I proceed? After this I will proceed with this root guide
... and then I will throw a heavy metal party to relax and stress out of my nerves!
Click to expand...
Click to collapse
Contact me through skype and I'll help you
"UltraWelfare"

UltraWelfare said:
Contact me through skype and I'll help you
"UltraWelfare"
Click to expand...
Click to collapse
I would like to, but I am deaf and can't hear you.. :/ I will add you anyway!!!

Do you know how to check if my TA partition is safe?
EDIT: I run TrackID as I found on your forums and it is working ... I guess I am so lucky lol.
Well I am thinking of relocking the bootloader, should I make a TA partition?

OK I will try and explain this as simply as possible.
IreneGR said:
I have made the unlocked bootloader (yaaay! :victory: ),
Click to expand...
Click to collapse
This is good it will simplify the root procedure. On a side note did you backup the TA partition before doing this?
and then as I am on 4.3 - 12.1.A.1.201 I said oh wait! I read on various comments that the Wi-Fi is not working after flashing the kernel into 12.1.A.0.266 so I freaked out and did not proceed.
Click to expand...
Click to collapse
It doesn't matter if the WiFi stops working as it will start working again when you reflash the stock 201 kernel.
My question comes. Flashing a kernel into 12.1.A.0.266 is just downgrade so as to root it? I am reading this guide which has not detailed info (for noobs)
Click to expand...
Click to collapse
No this is not a downgrade to root you are flashing doom kernel which will allow root where the stock kernel will not.
I have downloaded this file "SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf" and got a Flashtool. On a video guide it says to move the file into D:\Flashtool\firmwares is it right? Do I need anything else? Should I proceed? After this I will proceed with this root guide
Click to expand...
Click to collapse
That it correct after you have finished this root guide you can download and flash the .201stock kernel through flashtool that will clear up any WiFi issues you may have.
Hope this helps clear things up a bit
Sent from my C5303 using xda devlopers app

After a further further research (got almost a headache) I did until unlocked bootloader. I talked with a guy here and he suggested me to relock the bootloader and to do it in other way.
Well I didn't TA partition but TrackID is working and the IMEI is there... I cannot explain it... Do you know any other way to check if they DMR keys are okey?
Also do you know in case I relock my bootloader should I use the TA partition part?

IreneGR said:
After a further further research (got almost a headache) I did until unlocked bootloader. I talked with a guy here and he suggested me to relock the bootloader and to do it in other way.
Well I didn't TA partition but TrackID is working and the IMEI is there... I cannot explain it... Do you know any other way to check if they DMR keys are okey?
Also do you know in case I relock my bootloader should I use the TA partition part?
Click to expand...
Click to collapse
If you already unlocked your bootloader and didnt backup your TA-partition, your TA-partition will be lost forever .
I believe you can lock your bootloader again but this is without DRM-keys (I think).
And I believe TrackID will work even with unlocked bootloader and without DRM-keys. Im using TrackID on CM11 so yeah .
Just type *#*#7378423#*#* for checking bootloader status.

Th3Duck said:
If you already unlocked your bootloader and didnt backup your TA-partition, your TA-partition will be lost forever .
I believe you can lock your bootloader again but this is without DRM-keys (I think).
And I believe TrackID will work even with unlocked bootloader and without DRM-keys. Im using TrackID on CM11 so yeah .
Just type *#*#7378423#*#* for checking bootloader status.
Click to expand...
Click to collapse
I see, no problem then It's ok I will survive! haha! Yes its unlocked. I am checking this video on how to relock it and I will proceed with another guide.
Would you like to exchange Skype and help me through this?
EDIT: I am trying to relock it but it stacks here why?
{
"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"
}

IreneGR said:
I see, no problem then It's ok I will survive! haha! Yes its unlocked. I am checking this video on how to relock it and I will proceed with another guide.
Would you like to exchange Skype and help me through this?
Click to expand...
Click to collapse
Mmmm for relocking your bootloader I thought you dont need extra files anymore because in the newest flashtool there is a button for that (thought I read that somewhere, not sure). Still your DRM keys will be lost, because you dont have backup of your TA-partition. So relocking bootloader isnt that usefull for you. Just keep it unlocked
For your previous post (the pictures) you put your phone in fastboot mode instead of flashmode .

My life is ruined now lol. I have this problem "Stuck on SONY LOGO" so I am downloading a greek stock .. hope it fix it... (it doesnt matter the version number right?)

[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.

Have boot and recovery stock. Need CWM port help

i took my note 3 back to 4.4.2 and got the root on it and pulled and unpacked the boot and recovery img with carliv kitchen (http://forum.xda-developers.com/and...wm-based-recovery-t2973804/page8#post68550781)
I am following that guide. This is my first go at building a recovery and, hopefully, eventually a rom.
Just testing my feet before i jump into working on my note 4 and note 5. *im a samsung guy... all samung are belong to me... lol*
im stuck at the part where he is talking about building the fstab and init.rc.
not sure if this needs to be custom or not. I just want to create a stock rom with CWM recovery. Thats all. Can i just unpack the the stock recovery and boot and shove the CWM custom stuff in and repack it?
thanks for the help

Since the n900a has a locked bootloader, would cwm or twrp be possible?

don't really know if its locked... since i pulled the boot and recovery and it its flashable via odin....
I am having more issues with the basics of building here. not really the full application of the build.
if the boot loader was locked the why was i able to downgrade it? it was running 5.0 now on 4.4.2 and rooted.
don't know if others were not able to do the same but... really just need help understanding the next steps in building the custom recovery.

Even though the bootloader is locked, it may allow a downgrade to 4.4.2 from 5.0. Downgrading the bootloader doesn't automatically mean TWRP or CWM can be flashed to the phone.
People whose phone have a locked bootloader are using safestrap to flash the 900a.

audit13 said:
Even though the bootloader is locked, it may allow a downgrade to 4.4.2 from 5.0. Downgrading the bootloader doesn't automatically mean TWRP or CWM can be flashed to the phone.
People whose phone have a locked bootloader are using safestrap to flash the 900a.
Click to expand...
Click to collapse
well if it helps... i have a unlocked symbol and the word custom that show on the screen when it boots up.
This is kinda irregardless. I can emulate the test... that isn't an issue. I want to work on the basics of building... so my question isn't about the boot loader being locked or not.
I have the Boot.img and the Recovery.img on my local machine, unpacked with carliv kitchen. i just need to know what i need to copy over or what needs to be completely customized by hand. I am really new to the process of creating a custom recovery.
I'll worry about the flashing to device later.

It's my understanding that TWRP and CWM cannot be flashed to a phone with a locked bootloader which is why there is no TWRP build for this particular Note 3.
I wish you luck in your endeavour as I am sure a lot of users will be happy with something other than safestrap.

audit13 said:
It's my understanding that TWRP and CWM cannot be flashed to a phone with a locked bootloader which is why there is no TWRP build for this particular Note 3.
I wish you luck in your endeavour as I am sure a lot of users will be happy with something other than safestrap.
Click to expand...
Click to collapse
you keep talking about the boot loader but never even mention my question. my question has nothing to do with the boot loader or flashing the device.
I am asking about building. not the bootloader... this question is indifferent to even the phone i am on.
I am stuck on the instructions. I am just trying to figure out all the stuff that would need to be copied to the build device tree recovery/root. This should be standard in all phones or devices... I need to know what it is that makes the CWM recovery custom. are there files i need to replace with the original files. my original post has the link in the guide i am following. so if anyone can help answer that question i would appreciate it.
but thank you for the luck... it looks like i need it just to get somebody to answer some basic building questions.

I mention the bootloader because that seems to have been a stumbling block for users that want to use twrp to flash ROMs.
I will be the first to admit that I don't know anything about building twrp.
I will bow out now and leave you to your task.
Thanks for replying to my posts.

Building cwm I can't help you with. But cwm for note 3 att is useless. You can't flash it. Who uses cwm these days? Twrp isn't a preference it's the only real option anymore other than adb and fast boot.
Sent from my DROID Turbo using XDA-Developers mobile app

Some pics. But is not the point of my question. Please read the question.
Ok... this is going to seem like a noob question.... How can i prove that my bootloader is unlocked.
What would i need to do to prove or disprove it. Is there a log or something. This is literally my first go. Show me why it can't be flashed. I am not seeing the answer to this in any of the instructions.
You can't just say something is locked and that be the end of it. How is it locked. I can get into boot loader.
besides. This is solely to help me learn the basics of building a custom recovery. I have another device I want to work on but thats the device i don't want to brick. I am using this as a testing device to learn. I only want to learn to create the thing... i already know how to install the custom stuff... and to answer the question of who uses it... well... obviously.. me... when I am working on an old device learning the basics and building for android 4.4.2...
I am still working on this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Even though the bootloader is locked, this does not prevent a user from entering download or recovery mode.
To verify the bootloader version on your phone, you can install and run the Samsung Info App from the Play store.

audit13 said:
Even though the bootloader is locked, this does not prevent a user from entering download or recovery mode.
To verify the bootloader version on your phone, you can install and run the Samsung Info App from the Play store.
Click to expand...
Click to collapse
I got that installed. I am not sure what i am looking for. bootloader version?
Also, if the bootloader isn't unlocked... what does the picture i posted with the unlocked lock with the word custom beneath it mean?

I believe that, starting with a stock 4.3 ROM, the bootloader was locked. Maybe your phone is running an older ROM before AT&T locked the bootloader?
It looks like your bootloader may be unlocked but I'm not 100% sure as I don't have the n900a, I have an n900w8.
A sure fire way to see if the bootloader is locked would be to flash a stock LP ROM to the phone and then try to flash non-officlal software; however, I don't recommend doing this as it may hard brick the phone.
As far as I know, no one has claimed the XDA bounty for unlocking the AT&T Note 3 and S4 bootloader.
http://forum.xda-developers.com/showthread.php?t=2708609
Notice here that there is no mention of TWRP or CWM: http://forum.xda-developers.com/showthread.php?t=2710972

Well. I sent the OP on that post a message as the thread is locked. since july i think?

I think the thread was locked because safestrap is a viable recovery for the n900a.
I believe there is a version of TWRP for the n900a but it can only be installed on a phone without a locked bootloader.

well i sent the OP and the perosn who locked the thread... Ironically... the guy that locked the bootloader lives about 30 minutes from me...
I wish that more people would see this thread... or perhaps someone could just help me out with the building part... I have figured out most of it.... im just having a hard time understanding some of the small concepts.. what files need to be changed and what files need to be left alone.

therealtaynak said:
well i sent the OP and the perosn who locked the thread... Ironically... the guy that locked the bootloader lives about 30 minutes from me...
I wish that more people would see this thread... or perhaps someone could just help me out with the building part... I have figured out most of it.... im just having a hard time understanding some of the small concepts.. what files need to be changed and what files need to be left alone.
Click to expand...
Click to collapse
Yep that phone still has a locked bootloader

Ok... My question was about building anyway... i don't really care about flashing it... I am only using it because i am trying to learn the building process...

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.