Database Develop

[TUT] Unlocking 262-000 bootloaders

Alright, so let's start the fun
These are the steps i did for successfully unlocking my BL.
I can't and won't guarantee that theese steps are going to work for you. please report back here if it worked for you or not and please post also the buy-date of your phone
it might be possible that this works for other firmwares too, please try and report back here thanks
Requirements
- a Linux distro (mine is Xubuntu 12.10, but should work on every Linux OS)
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware (preferably ANEUBK)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The steps
1) charge your phone to 100%
2) connect your phone in LG software mode
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
{
"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"
}
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
(if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
4) now you should see this on your phone:
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
10) do the harlem shake and be happy about your unlocked BL
and please, don't post "thanks" if i've helped you, just hit the thanks button

Does it applies on 234 devices too? I ll not have access on a linux pc till monday!

Cool dude, thanks.
Do you think its possible to do this with those bootable Linux OS cd (so i dont have to install linux on my hd just for dooing that) ?
Do you loose the unlocked BL if you install another KDZ after the unlocking?

Someone know why not working on every windows?
I have the android sdk installed and the same procedure worked for me without linux.

nikosblade said:
Does it applies on 234 devices too? I ll not have access on a linux pc till monday!
Click to expand...
Click to collapse
i honestly don't know try it, like i've said, give it a try and report back
profyler said:
Cool dude, thanks.
Do you think its possible to do this with those bootable Linux OS cd (so i dont have to install linux on my hd just for dooing that) ?
Do you loose the unlocked BL if you install another KDZ after the unlocking?
Click to expand...
Click to collapse
hmmm, possible? maybe, but this would be extremely slow, cause you've gotta get adb working first and so on. so i'd say it won't work, but not sure.
but some distros have got the ability to install them as a "windows prog", this creates a virtual harddrive where linux can be booted from, so no need for reformatting the hdd just google about it
some users reported that it will not be lost after flashing a kdz. but also here: not sure, cause i haven't tried it myself yet (my BL is now unlocked for about 3h yet )

verlol said:
Someone know why not working on every windows?
I have the android sdk installed and the same procedure worked for me without linux.
Click to expand...
Click to collapse
i guess it is driver related... what firmware do you use? german or euro-open?

laufersteppenwolf said:
View attachment 1861354
Click to expand...
Click to collapse
This "final" screen I can confirm on my 262-000 from Amazon. I used Windows and http://forum.xda-developers.com/attachment.php?attachmentid=1859693&d=1365149301 for the ADB driver but the same method. It takes like 2sec to do! I installed CWM etc. fine afterwards!! Thank you!

Security error
I don't get the screen like in 4)
I just get Security Error, any ideas?

Don't work with ADEUBK 262 000
I can only unlock with the china 20a.

mrlollog said:
I don't get the screen like in 4)
I just get Security Error, any ideas?
Click to expand...
Click to collapse
This is not universal, seems with latest update LG showed some mercy on German users...rest can feel screwed all over again
F*ck you LG retards they are only good if Google screws them good, who's your papa :silly:

On 234 this didn't work with Linux and the leaked 20A.
I might try later to update the phone (GBR) with the official one but I wouldn't hold my breath.
Sent from my Nexus 7 using Tapatalk 2

laufersteppenwolf said:
i guess it is driver related... what firmware do you use? german or euro-open?
Click to expand...
Click to collapse
I use euro-open.
If its driver related, which driver is needed?
I only know of the Google USB Driver for the Android Composite ADB Interface.

Not works (on linux vitural machine ) The pone says ... Lg Security error...

me too

I do not get unlock

tiflao said:
Not works (on linux vitural machine ) The pone says ... Lg Security error...
Click to expand...
Click to collapse
same here, on win or on vm i got this error ...... (262-00)

when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?

DavidXanatos said:
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
Click to expand...
Click to collapse
The Phone reboots after ~5 secs.

laufersteppenwolf said:
Alright, so let's start the fun
These are the steps i did for successfully unlocking my BL.
I can't and won't guarantee that theese steps are going to work for you. please report back here if it worked for you or not
it might be possible that this works for other firmwares too, please try and report back here thanks
Requirements
- a Linux distro (mine is Xubuntu 12.10, but should work on every Linux OS)
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware (preferably ANEUBK)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The steps
1) charge your phone to 100%
2) connect your phone in LG software mode
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
View attachment 1861346
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
(if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
View attachment 1861348
View attachment 1861349
4) now you should see this on your phone:
View attachment 1861353
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
View attachment 1861354
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
View attachment 1861355
10) do the harlem shake and be happy about your unlocked BL
and please, don't post "thanks" if i've helped you, just hit the thanks button
Click to expand...
Click to collapse
Thanks for the tutorial - but can you explain why is this just working on a Linux OS ? I mean what's the difference between trying to unlock the BL on a Win7/8 OS or a Linux OS ?
THanks

DavidXanatos said:
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
Click to expand...
Click to collapse
Sometimes is semi-bricked, specialy after the "morning-call empty"
Don't worry, re-flashing will solve the problem.

How to dual boot on me176cx part 1

This is only first part. In this part, I will NOT mention any OSes. I will teach you how to run rEFInd on this device.
In other parts, I will edit rEFInd's config file to make it really "work". BUT, after this tutorial, you may fell happy that dual boot will most likely work on the device you just hod in your hands.
This guide is for me176cx only. Steps for other devices may be similar, only try to do this on other devices if you are sure you know where the differences are and how to change the commands!
So let's begin!
My tablet before doing anything
{
"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"
}
on http://www.rodsbooks.com/refind/getting.html , click on get binary zip file
Extract the downloaded zip
look for the folder "refind" inside the extracted folder
////////////////////////////////////////////////////////////////////////////
Now, we need to move it to Efi System Partition.
Istall busybox. Then, install Android Terminal Emulator.
Using some file browser with root rights, make a folder in the root of your device's memory called "esp"
Then, mount Efi System Partition on it:
Run the Android Terminal Emulator, type su, and confirm the SuperUser dialog.
Then, type: busybox mount /dev/block/mmcblk0p3 /esp
it should have no output.
Then, copy the "refind" folder to file system root.
Then (using terminal emulator) copy the refind folder to the ESP.
Then, make sure it is really there
Then write: busybox umount /esp
///////////////////////////////////////////////////////////////////////
Now, add rEFInd's binary to bootorder and set the bootorder to !!!NOT!!! boot it first, becouse you have to test it first (and you do not want to run and buy the first powered hub to be able to get back in android some complicated way)
Download this file and move it to some location where you will execute it from:
http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
(Thanks to social-design-concepts for compiling this to work on android)
Issue this command (the paste function does not work in terminal emulator so you have to rewrite it by hand)
Then, make sure the path is set well:
Then, set the boot order to boot Android first by ./efibootmgr64 -o 0001,0000
Then, set the next boot (only next boot) to rEFInd
////////////////////////////////////////////////////////////////////
Now, just power off the tablet, (do not restart) and power it on again. You will see rEFInd, but you cannot do much without powered hub.
So if you have one, look around with keyboard. If you do not have one (like me), just power off the tablet by holding the power button, power it on again and wait for the next part of this tutorial
EDIT:
tuxic001 edited rEFInd binary so you can select what to boot.
http://forum.xda-developers.com/showpost.php?p=62463032&postcount=60
\\\_///
P.S If you use nandroid backup to update, you only update kernel and ROM (or recovery, fastboot, esp partition and whatever the other partitions are), depends on what you backup. And I don't think UEFI is stored on EMMC, so if UEFI update (or bootloader, recovery, etc. update) is present, you are totally ignoring it. On the other hand, UEFI update is a risk of not being able to access it..

Is refind working with touch or volume\power keys?

A powered hub is non-optional. OTG power is super finicky on this tablet, especially if you're adding a flash drive on top of mouse and KB

t68kv said:
Is refind working with touch or volume\power keys?
Click to expand...
Click to collapse
Voume keys work, but power key doesn't. But tuxic001 is working on editing the source code so it will. Maybe tomorrow this time it will work

Good And Bad news
Which you want to hear first?
Look fo EDIT in the main post.

I also got my tablet down, it boots only to UEFI as there's no efi bootloader to load anymore.... I'll run and get a powered usb hub to try to use the UEFI, cause the vol keys don't cut it.

Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress

Shump said:
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Click to expand...
Click to collapse
Yeah I have run grub 2, it was nice. I got stuck somewhere in kali linux booting process, and then ubuntu-based dostros said bad kernel magic number blah blah. So I tried abother grub. First I found was nice, but still not working with ubuntu. So I tried to use ununtu's grub. It didn't show up in rEFInd. Now I can't find the good grub again What about your progress? Did you need to use powered OTG cable?
EDIT: found working grub again, kali linux stuck at this error: http://unix.stackexchange.com/quest...o-find-a-medium-containing-a-live-file-system

Any new?? This tutorial works on Lollipop?? If do this tutorial exist any risk for example brick??
Can you do a tutorial and upload to youtube??
or someone explain me the process?
Thanks in advance.:good:

I get invalid argument on the first command lenovo tab s8

Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error

jet_98 said:
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
Click to expand...
Click to collapse
have you installed busybox? as simple as that.

Device not detected in Fastbootmode.

SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?

TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?

reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw

TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done

reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"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"
}

TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.

reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:

TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....

reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty

TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...

Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!

Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)

See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution

reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.

Also I got this from continually trying to boot:

TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?

TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc

reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.

Fastboot flashing unlock not working.

Hey everyone, I'm in the need of some help here. My Pixel 4xl was stolen so I'm trying to set up a new one and I'm having problems getting the "Fastboot flashing unlock" command to do anything. All it returns is a list of options. I've never had this problem before with my old 4xl. I've updated adb and platform tools and verified with "fastboot devices" that my pc recognizes my device (it does). Does anyone have a clue what might be wrong here? When I have a chance I can try to upload pictures of what I'm seeing but it's self explanatory. Also, oem unlocking is blue checked and USB debugging is enabled.

Ffgod1 said:
Hey everyone, I'm in the need of some help here. My Pixel 4xl was stolen so I'm trying to set up a new one and I'm having problems getting the "Fastboot flashing unlock" command to do anything. All it returns is a list of options. I've never had this problem before with my old 4xl. I've updated adb and platform tools and verified with "fastboot devices" that my pc recognizes my device (it does). Does anyone have a clue what might be wrong here? When I have a chance I can try to upload pictures of what I'm seeing but it's self explanatory. Also, oem unlocking is blue checked and USB debugging is enabled.
Click to expand...
Click to collapse
Try different cables and ports.

Lughnasadh said:
Try different cables and ports.
Click to expand...
Click to collapse

I'm currently trying that but I only have one USB-c port but I have two different cables. I think I have a USB-a to C one that I'll try

{
"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"
}

First make sure you've enabled developer mode, switch on USB debugging and toogle OEM unlock (or whatever it's called).
Connect the USB, you should have a pop up on the phone about trusting the PC. Allow the connection.
Go to you ADB folder, than 'adb devices'. It should list your device if it's connected.

I have a similar issue with my bramble MP1.0 (NA) device [The Pixel 4a 5G Canada Unlocked]
The difference being that I can see my device in the CMD window or the Power Shell window. I can run any Fastboot or ADB command.
I have ensured that the latest ADB Drivers are installed. I have ensured that "OEM Unlocking" and "USB Debugging" are enabled
But, when I type the "FASTBOOT FLASHING UNLOCK" command, I simply get the fastboot help text as if it is not recognizing the Flashing variable.
I have tried "flashing unlock_critical" though it does not work as expected since "unlock" is a subset of "flashing"
I have also tried "fastboot oem unlock" and get "remote: Invalid oem command unlock" back.
I am at a loss as to how to unlock MY Canadian Pixel 4a 5G phone. after 2 days of web searches.
any thoughts as to what is going on here?
The phone is stock and up to date as of April 15 2022 (Build SP2A.220405.003)
ADB version is 1.0.41
28.0.3

CR_Jon said:
... I am at a loss as to how to unlock MY Canadian Pixel 4a 5G phone. after 2 days of web searches.
any thoughts as to what is going on here?
Are you using a known good USB-A type data cable? Try another similar data cable. Use CMD window, not powershell. If what you have laid out is correct it should be working. If I recall there was also an "unlockability" flag, but I'm not near my Windows PC atm.
Click to expand...
Click to collapse

I have tried 3 different USB A to C Cables, I have also tried a C to C Cable. I have tried 5 different A ports and two different C ports. The GETVAR commands do not work for, they keep returning "Unknown Command" I have tried CMD.
I am confused since I can see the device with "fastboot devices" or "adb devices" and I can send reboot commands I even tried the unlocking command sin Recovery and fastboot modes in addition to the bootloader. nothing is working.
My cables work with other devices for issuing unlock commands.

CR_Jon said:
I have a similar issue with my bramble MP1.0 (NA) device [The Pixel 4a 5G Canada Unlocked]
The difference being that I can see my device in the CMD window or the Power Shell window. I can run any Fastboot or ADB command.
I have ensured that the latest ADB Drivers are installed. I have ensured that "OEM Unlocking" and "USB Debugging" are enabled
But, when I type the "FASTBOOT FLASHING UNLOCK" command, I simply get the fastboot help text as if it is not recognizing the Flashing variable.
I have tried "flashing unlock_critical" though it does not work as expected since "unlock" is a subset of "flashing"
I have also tried "fastboot oem unlock" and get "remote: Invalid oem command unlock" back.
I am at a loss as to how to unlock MY Canadian Pixel 4a 5G phone. after 2 days of web searches.
any thoughts as to what is going on here?
The phone is stock and up to date as of April 15 2022 (Build SP2A.220405.003)
ADB version is 1.0.41
28.0.3
Click to expand...
Click to collapse
Try using the latest Platform Tools (33.0.1)

CR_Jon said:
I have tried 3 different USB A to C Cables, I have also tried a C to C Cable. I have tried 5 different A ports and two different C ports. The GETVAR commands do not work for, they keep returning "Unknown Command" I have tried CMD.
I am confused since I can see the device with "fastboot devices" or "adb devices" and I can send reboot commands I even tried the unlocking command sin Recovery and fastboot modes in addition to the bootloader. nothing is working.
My cables work with other devices for issuing unlock commands.
Click to expand...
Click to collapse
Yeah you are using a very outdated version of the adb/fastboot binaries (June 2019). No wonder it's not working. Remove all copies of adb from your computer. Create a new folder (eg. c:/adb) and then add this folder to your PATH statement, so in the future only this version of adb is called. For maintenance (new versions) simply copy all the files into your adb folder, overwriting the old files.

I feel like an idiot now lol. I was so eager to get this particular phone done that totally spaced on cross referencing my installed version with the latest one I downloaded . Once I verified that I correctly updated my tools, it works.
Thanks for the help.

CR_Jon said:
I feel like an idiot now lol. I was so eager to get this particular phone done that totally spaced on cross referencing my installed version with the latest one I downloaded . Once I verified that I correctly updated my tools, it works.
Thanks for the help.
Click to expand...
Click to collapse
np

CD-17302F (Lenovo Smart Display 7") (Ivy) AVB/Bootloader Unlock, Firmware

How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB C cable
2. You will need fastboot drivers on your PC
3. Unplug the power cable from your device
4. Remove the silicone cover from around the power plug (Might be hard it has adhesive on the back)
5. Plug the USB C cable into the now revealed USB-C port
6. Hold the volume + button and plug in the power cord (Smart plugs or switches help so you don't damage the ports by replugging them constantly)
7. Keep holding volume + for about 10-15 seconds (It is slow to boot to fastboot)
8. Once the device shows up on your computer in a terminal run the following command:
Code:
fastboot flashing unlock
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Word of warning doing this causes the stock OS not to boot fully.
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB unlock zip
2. Run either the avb-unlock.bat or this command in a terminal
Code:
at_auth_unlock.exe creds\
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command or the Avb_lock.bat:
Code:
fastboot oem at-lock-vboot!
Now that you are AVB unlocked you can flash the firmware/partitions from fastboot using the flash-all scripts located in the firmware zips.
Combined firmware: (Flashes both Factory and User firmware one to each slot)
Here
User (Stock) firmware:
Here
Debug/Factory Firmware:
Here
AVB Unlock tool:
Here
Various Screenshots:
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The firmware provided allows you to have adb and adb root on either debug or user. But the downside is with avb off the device can't access its Tee keys so the user firmware will not finish setup. But you can still install other apps and use root which allows you to fully turn off the security restrictions to allow you to edit files on the device. The commands you need to run are these:
Spoiler
Code:
adb root
adb disable-verity
adb reboot
adb root
adb remount
adb shell setenforce 0
Disable-verity will last until you factory reset or run adb enable-verity
Useful adb and android things commands:
Spoiler
Brings up the default launcher selector screen (If a launcher you try opens and then closes it is not supported by Android Things. You will need one that does not have Widget support. Like KISS Launcher)
Code:
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
Lists installed app package names
Code:
adb shell pm list packages
Change the -p to whichever package name you want to launch it emulates clicking the apps icon in launcher so some system apps don't support it.
Code:
adb shell monkey -p PACKAGE_NAME -c android.intent.category.LAUNCHER 1
Will launch the android things settings page
Code:
adb shell monkey -p com.android.iotlauncher -c android.intent.category.HOME 1
This will launch the google setupwizard/launcher
Code:
adb shell monkey -p com.google.assistant.core -c android.intent.category.LAUNCHER 1
Seems to soft reboot the android things system, but not actually reboot the device proper
Code:
adb shell monkey -p com.google.android.apps.quartz -c android.intent.category.LAUNCHER 1
Launches camera app
Code:
adb shell am start -n com.android.camera2/com.android.camera.CameraActivity

Truely impressive work @deadman96385 !! Thank you for the release

So if we turn AVB off, install an apk (like Zello) or other 3rd party launcher (like Nova), then turn AVB back on, will it boot? Or do we have to leave AVB off inorder to use other android apks?

I did the flash, booted Ok the first time but got:
adb devices
HA16XGYL no permissions
Then did the unlock again and
fastboot oem at-lock-vboot
fastboot set_active b
fastboot reboot
but now it's stuck in "Your device will boot in 5 seconds"
How to exactly unlock + boot + adb install myapp.apk?

Edit: Nevermind

Jarkk'o said:
I did the flash, booted Ok the first time but got:
adb devices
HA16XGYL no permissions
Then did the unlock again and
fastboot oem at-lock-vboot
fastboot set_active b
fastboot reboot
but now it's stuck in "Your device will boot in 5 seconds"
How to exactly unlock + boot + adb install myapp.apk?
Click to expand...
Click to collapse
This may help you: https://itsfoss.com/fix-error-insufficient-permissions-device/

thanks for making this thread! ended up with a demo unit a year ago. and couldnt find anything about flashing the OS at the time.

Is there a way to update webview? I tried using Home Assistant app, but it fails with js errors and it seems a newer webview is needed

Hi, sorry, i'm kind of a noob to this.
Finally realized i was in fastboot mode even though the screen stayed black. I was then able to do the AVB unlock, but then i'm not really sure what i'm supposed to do to get an Android Things flashed device.
I ended up trying the flash-all bat, but on reboot the device updated itself after i connected it to google home.

Just as a reference, I've downloaded the ADB Interface Driver (adb_driver_20110720.zip) on https://support.lenovo.com/in/en/downloads/ds022366-adb-interface-driver-thinkpad-tablet to be able to pass stage 1 and 2
Looks like I've successfully passed stage 1 and 2 - AVB Unlocked.
Now I need to start flashing, but don't have a clue which commands to use. @deadman96385 Would you be so kind as to explain what are the last remaining commands. I've downloaded the combined firmware ? I also tried the flash-all.bat without any success

vizharan said:
Is there a way to update webview? I tried using Home Assistant app, but it fails with js errors and it seems a newer webview is needed
Click to expand...
Click to collapse
It looks like you were able to get the device flashed. Maybe you can give me some advise how to get it flashed (last step). Thank you so much

@jangeenidee in the end i wasn't able to flash it correctly, i'll try again when i'm able to block internet access preventing it to self update.
But given it's a third party device with an old webview version, Google blocked web browser usage on this device, rendering it useless for my purpose as it is. It's still a good paperweight google photos gallery though.

vizharan said:
Is there a way to update webview? I tried using Home Assistant app, but it fails with js errors and it seems a newer webview is needed
Click to expand...
Click to collapse
If you're able to root your device with Magisk you can use a Magisk Module like Webview Manager. I had the same issue using the Home Assistant on my CD-18781Y (Lenovo ThinkSmart View) at first but after rooting and installing the module I was able to change the Webview to a newer one in developer settings.