Database Develop

[TUT] Unlockin (we hope) any Bootloader

Ok, i only write here the method/Infos we have used for the guys who hazzle with the thread from here
Phone must be rooted. I have done this with 20A official ADEUWH (262-000)
Open a terminal on your device (Play Sore app that i have used)
type the following:
su root
cat /sys/firmware/fuse/odm_reserved >/data/local/tmp/odm_reserved
after that edit the file odm_reserved loctated here: /data/local/tmp/
change the line that it reflects this one: 0x00000000000000000000000000000000000000000000000000000040000000c8
save the changes, back to the terminal enter:
echo /data/local/tmp/odm_reserved >/sys/firmware/fuse/odm_reserved
than i used my PC (Phone connected via USB, USB-Debugging enabled) and entered
adb reboot bootloader
fastboot oem unlock
in a comand prompt
Press Vol Down, then Power Button from the Phone to unlock, screen went#s back, i waited 30Sec and rebootet
the phone, after that i rebootet back to the bootloader and installed the unsecure boot img and CWM.
And don't thank me - thx to Derjan23 for finding this out for us all!!!!!!!!!!!!!!

here is a script from exFAT, this script will do the job for you

fire3d said:
here is a script from exFAT, this script will do the job for you
Click to expand...
Click to collapse
I didn't need to issue the fastboot oem unlock command

Fantastic!
Absolutely brilliant, Worked fist time. Im now running CWM 6.0.3.1 touch recovery and just looking to install Cyanogenmod 10.1.
UK 234-000 V20A UNLOCKED. :good:
---------- Post added at 05:10 PM ---------- Previous post was at 04:51 PM ----------
cupidstunt said:
I didn't need to issue the fastboot oem unlock command
Click to expand...
Click to collapse
+1 Just a sweet and simple Fastboot command to push CWM to recovery.

works on 232-10 *_*

Omgf omgf it work it works!!!!!

fire3d said:
Ok, i only write here the method/Infos we have used for the guys who hazzle with the thread from here
Phone must be rooted. I have done this with 20A official ADEUWH (262-000)
Open a terminal on your device (Play Sore app that i have used)
type the following:
su root
cat /sys/firmware/fuse/odm_reserved >/data/local/tmp/odm_reserved
after that edit the file odm_reserved loctated here: /data/local/tmp/
change the line that it reflects this one: 0x00000000000000000000000000000000000000000000000000000040000000c8
save the changes, back to the terminal enter:
echo /data/local/tmp/odm_reserved >/sys/firmware/fuse/odm_reserved!
Click to expand...
Click to collapse
Here I get permission denied

Emin3ms said:
Here I get permission denied
Click to expand...
Click to collapse
Terminal must run at root now I'm on cm10.1
Sent from my rooted P880

Emin3ms said:
Here I get permission denied
Click to expand...
Click to collapse
Remember the to type su root and click enter/return first.

Done with 268-01!
Thanks a LOT!

@non4 said:
Terminal must run at root now I'm on cm10.1
Sent from my rooted P880
Click to expand...
Click to collapse
It runs at root
It returns "/system/bin/sh: can't create /sys/firmware/fuse/odm_reserved: Permission denied"

device rooted?
Which Rom is installed?

No sorry i closed the window when I edited odm_reserved, i try after enter su root now
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
C:\root>adb reboot bootloader
C:\root>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 45.707s
But the hidden menu says Unlock. It's ok I can flash CM 10.1 ?
Thanks you guys for every tuto ^^ great community on xda

Emin3ms said:
No sorry i closed the window when I edited odm_reserved, i try after enter su root now
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
C:\root>adb reboot bootloader
C:\root>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 45.707s
But the hidden menu says Unlock. It's ok I can flash CM 10.1 ?
Thanks you guys for every tuto ^^ great community on xda
Click to expand...
Click to collapse
There's no need to do any unlock command, once you have modified the file it's already unlocked, yes just install CWM with ROM manager and flash away!
Sent from my rooted P880

Can someone just confirm, the string of zeros that replace the original:
0x000000000000000000000000000000000000000000000000 00000040000000c8
Are you saying there is a space or is that a carriage return?
I cut and past it onto a rooted version of the 20A Rom that was leaked originally, no issue with replacing the file itself, but after a adb oem reboot it hangs at the LG screen.
Any advice please?

@lbert said:
Can someone just confirm, the string of zeros that replace the original:
0x000000000000000000000000000000000000000000000000 00000040000000c8
Are you saying there is a space or is that a carriage return?
I cut and past it onto a rooted version of the 20A Rom that was leaked originally, no issue with replacing the file itself, but after a adb oem reboot it hangs at the LG screen.
Any advice please?
Click to expand...
Click to collapse
You don't need to do this! Changing this file already unlocked it! But the screen you refer to is the boot loader, your command should have been adb reboot oem-unlock
Sent from my rooted P880

WORKS!!!! THX!!!

lol rofl xd!!!111 It worked. 262-000 Germany. Finally unlocked.

@non4 said:
You don't need to do this! Changing this file already unlocked it! But the screen you refer to is the boot loader, your command should have been adb reboot oem-unlock
Sent from my rooted P880
Click to expand...
Click to collapse
Yes I see, I only noticed the post above after I posted my question, I'm unlocked, with no warning or disclaimer, no erase or factory reset, in fact legally, LG mustn't have a leg to stand on here in terms of warranty because they never even got a chance to put the agree or disagree warning up.
Thank you for this. :crying:this is an emotional moment!

Emin3ms said:
No sorry i closed the window when I edited odm_reserved, i try after enter su root now
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
C:\root>adb reboot bootloader
C:\root>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 45.707s
But the hidden menu says Unlock. It's ok I can flash CM 10.1 ?
Thanks you guys for every tuto ^^ great community on xda
Click to expand...
Click to collapse
Try "C:\root>adb reboot oem-unlock"...

Did I really just brick a NEXUS?!?!

Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...
At this point I think I am screwed!! Any suggestions would be GREATLY appreciated!

Can you not get into fastboot and try to OEM unlock that way?

Xaikar said:
Can you not get into fastboot and try to OEM unlock that way?
Click to expand...
Click to collapse
I can get into fastboot but get this when I try to unlock
C:\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.000s
C:\Android\sdk\platform-tools>​
And of course I cannot check that because I cannot boot into Android

So it currently says device locked?

Xaikar said:
So it currently says device locked?
Click to expand...
Click to collapse
10-4
I can get into stock recovery, but I don't know of anything to flash with the stock recovery and adb sideloading 5.1 isn't working

http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

There's a thread about this over at the Nexus 9 help forum. Might want to check there.

Xaikar said:
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Can't flash the images while locked, thanks though

ChristianJay said:
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Click to expand...
Click to collapse
Ah, thanks! Any idea which section?
Edit: Found it!

YankInDaSouth said:
Ah, thanks! Any idea which section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312

Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img

WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.

ajjames01 said:
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Custom recovery isn't currently on the device ...
Dusty Rhodes said:
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
Click to expand...
Click to collapse
Tried that too ... but the .img's cannot be flashed while locked, keeps failing

If you have TWRP on the device can you adb push a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.

ajjames01 said:
If you have TWRP on the device can you a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
Click to expand...
Click to collapse
I don't have TWRP, sorry that was a typo. It's stock recovery as I was trying to go fully stock 5.1 ...

@YankInDaSouth
Did you try booting twrp and not flashing it and go from there?
Fastboot boot recovery twrp.img

when Google decided to add the "OEM Lock" checkbox they should have committed to every Nexus device also having SD card capability, not only for the convenience that SD cards bring but also to be able to load the images that way in the event of a catastrophe.
But I guess forcing everyone into buying cloud storage is the new modus operandi.

Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot

efrant said:
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
Click to expand...
Click to collapse
Still get the message about checking the box in dev options ...

Not sleeping tonight huh bro? I know the feeling when this **** happens, it sucks. I think someone will come up with a work around, a lot of brains around here.
Sent from my Nexus 9 using XDA Free mobile app

[GUIDE] How to Unlock Bootloader ZC554KL (DO WITH YOUR OWN RISK!)

I realize that our device have the source code on Asus website and the unlock tool haven't been released by Asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame Asus for that! But, I could stop thinking and doing this and (BAM!) the bootloader unlocked and I'm able to boot patched boot.img with Magisk Manager app.
READ THIS FIRST!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
PLEASE READ CAREFULLY!
1. Reboot to Bootloader by pressing power + vol up
2. Type fastboot command below:
echo > key.txt
fastboot oem get_unlock_key key.txt
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. Enjoy the freedom of Android experience with annoying verifiedboot caution on the start ( Blame Google for that) but it's not a big problem.
To relock bootloader type this in fastboot (Thanks to @shakalaca for telling that in this thread)
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
REMEMBER! DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE AND YOUR LIFE FOR DOING THIS! GOOD LUCK!
PS: I dont have any device to take a shot from my device because this Zenfone was my only device that I have.
To do list:
- Get rid of the caution at startup that reminds our bootloader state
NOTE: This method works only for version below 215. If you're updated to latest firmware. It won't work since Asus update the bootloader. And the bootloader just temporarily unlocked with this method. If device restarted, the bootloader get locked automatically

Не работает
Here's what happens:
C:\adb>fastboot oem get_unlock_key
...
(bootloader) @!
OKAY [ 0.004s]
finished. total time: 0.005s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.004s

aaaaaaziskurnia said:
i realize that our device have the source code on asus website and the unlock tool haven't been released by asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame asus for that! But, i could stop thinking and doing this and (bam!) the bootloader unlocked and i'm able to boot patched boot.img with magisk manager app.
Read this first!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
Please read carefully!
1. Reboot to bootloader by pressing power + vol up
2. Type fastboot command "fastboot oem get_unlock_key" then press enter key
3. After that type "fastboot oem unlock-go"then hit enter again
4. Check the bootloader status by rebooting to bootloader back using command "fastboot reboot-bootloader"
5. Enjoy the freedom of android experience with annoying verifiedboot caution on the start ( blame google for that) but it's not a big problem.
Remember! Do with your own risk! I'm not responsible for what happens to your device and your life for doing this! Good luck!
Ps: I dont have any device to take a shot from my device because this zenfone was my only device that i have.
To do list:
- find a hack to relock again the bootloader
- get rid of the caution at startup that reminds our bootloader state
Click to expand...
Click to collapse
you have 2/16 or 3/32 ???

Johann Richter said:
you have 2/16 or 3/32 ???
Click to expand...
Click to collapse
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls

aaaaaaziskurnia said:
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls
Click to expand...
Click to collapse
I have 8917, no options with this?

Johann Richter said:
I have 8917, no options with this?
Click to expand...
Click to collapse
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.

aaaaaaziskurnia said:
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.
Click to expand...
Click to collapse
After much suffering, 15 times to unlock the bootloader. Thank you!!!

Johann Richter said:
After much suffering, 15 times to unlock the bootloader. Thank you!!!
Click to expand...
Click to collapse
I've suffering same thing as you in the first but it's unlocked. Good luck and enjoy development

Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..

shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
It works on my TW sku ..
Click to expand...
Click to collapse
Thanks shalaca, I'll include it to the first Page :good::laugh:

shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..
Click to expand...
Click to collapse
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?

Johann Richter said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?
Click to expand...
Click to collapse
Just wait for TWRP. I've got built TWRP but still messed up. Stil investigating.

tks for your guide
can you root with supersu?? or can you send a custom recovery to flash zip file?

Mr Foot said:
can you root with supersu?? or can you send a custom recovery to flash zip file?
Click to expand...
Click to collapse
I suggest using Magisk. Since the stock rom protected /system by selinux. If you doing any modifications in /system , it will result hangs or unbootable device and you should clean flash again.

If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..

shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
so is he a worker?

Johann Richter said:
so is he a worker?
Click to expand...
Click to collapse
who ? me ?

shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Thanks, it works

shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
I'm already have a device tree written two weeks ago.
https://github.cm/aaaaaaziskurnia/twrp_device_asus_X00ID
But messed up many times so I freshly uploads all the device tree.
I'm still new but I can sure that I'm fast learner. Should we collab?

shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Good day, which firmware do you use?

oreo twrp install error

Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?

kadirc5 said:
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
Click to expand...
Click to collapse
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)

CarlosAG10 said:
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
Click to expand...
Click to collapse
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED

kadirc5 said:
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
Click to expand...
Click to collapse
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory

CarlosAG10 said:
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
Click to expand...
Click to collapse
Yes, shows a number
How can ı check?

kadirc5 said:
Yes, shows a number
How can ı check?
Click to expand...
Click to collapse
Download the files again and make sure you are correctly using fastboot

since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere

Striike said:
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Click to expand...
Click to collapse
Im gonna try at the weekend thanks

Official Pie ROM

Guys,
Anyone already had Pie update?
It should be released on 17 November 2018, and some users already had it.
Anyone have the link to download the OTA file?
I want to port dolby from that file, thanks!

heindrix said:
Guys,
Anyone already had Pie update?
It should be released on 17 November 2018, and some users already had it.
Anyone have the link to download the OTA file?
I want to port dolby from that file, thanks!
Click to expand...
Click to collapse
Yeah i have updated to pie 2days ago :fingers-crossed:
For OTA :
https://motoota.lolinet.com/
Fill in the data according to your model. I can't do this bcoz i already have Pie

thanks, i've got it : https://mirrors.lolinet.com/firmware/moto/chef/official/

heindrix said:
thanks, i've got it : https://mirrors.lolinet.com/firmware/moto/chef/official/
Click to expand...
Click to collapse
how to update?

tnmsrkr said:
how to update?
Click to expand...
Click to collapse
Check your model cid and the cid of the pakage. If they match then open flashfile.xml see the commands for flashing (you have to use bat commands for the equivalent).
Put the phone in fastboot mode , executive the commands one by one and be sure to copy the data bcoz it will reset your device if u use 'fastboot erase userdata' but its recommended if u update using Fastboot method

tnmsrkr said:
how to update?
Click to expand...
Click to collapse

Can anyone dump stock pie to GitHub or somewhere? Thanks in Advance.

gyarados025 said:
Check your model cid and the cid of the pakage. If they match then open flashfile.xml see the commands for flashing (you have to use bat commands for the equivalent).
Put the phone in fastboot mode , executive the commands one by one and be sure to copy the data bcoz it will reset your device if u use 'fastboot erase userdata' but its recommended if u update using Fastboot method
Click to expand...
Click to collapse
how to check CID please help if possible?

azhar63 said:
how to check CID please help if possible?
Click to expand...
Click to collapse
fastboot getvar all and check the cid value (will be in hexadecimal)

gyarados025 said:
fastboot getvar all and check the cid value (will be in hexadecimal)
Click to expand...
Click to collapse
Thanks a lot dear here is the result so how can I get my proper rom to make it stock
(bootloader) cid: 0x0000

flash stock rom
gyarados025 said:
fastboot getvar all and check the cid value (will be in hexadecimal)
Click to expand...
Click to collapse
i flashed without checking CID.
flash completed when the mobile is unlocked
re locked the bootloader
in fastboot mode it shows flashing_locked.
I want OEM_locked message in fastboot mode
i am getting warning message using other os
after locked the bootloader
how to flash full rom that erases every thing and re lock's the boot loader just like new box peace

gyarados025 said:
Check your model cid and the cid of the pakage. If they match then open flashfile.xml see the commands for flashing (you have to use bat commands for the equivalent).
Put the phone in fastboot mode , executive the commands one by one and be sure to copy the data bcoz it will reset your device if u use 'fastboot erase userdata' but its recommended if u update using Fastboot method
Click to expand...
Click to collapse
i flashed without checking CID.
flash completed when the mobile is unlocked
re locked the bootloader
in fastboot mode it shows flashing_locked.
I want OEM_locked message in fastboot mode
i am getting warning message using other os
after locked the bootloader
how to flash full rom that erases every thing and re lock's the boot loader just like new box peace
i want OEM LOCKED in fastboot

lbcsc.clx said:
i flashed without checking CID.
flash completed when the mobile is unlocked
re locked the bootloader
in fastboot mode it shows flashing_locked.
I want OEM_locked message in fastboot mode
i am getting warning message using other os
after locked the bootloader
how to flash full rom that erases every thing and re lock's the boot loader just like new box peace
i want OEM LOCKED in fastboot
Click to expand...
Click to collapse
It will stay that way on the fastboot menu. You can Flash the different bootlogo to remove that warning on Boot