yashsingh1/xdaforums huggingface dataset:
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
KDZ has all partitions inside, not spezific like imei, so bootloader also. why is there noone who can bring unlocked BL and pack it into a kdz again to flash for all... (and btw with root and twrp)

on nx4 i mean there where people who can modify bl? right? mhmmm letz discuss more about, its interesting :)
[G4 Q&A, Help & Troubleshooting] esmenikmatixx:
For Sprint LS991, this command autoprime suggested worked to pull boot.img to sd

su

dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot-ls991zv5.img
[G4 Q&A, Help & Troubleshooting] S1L3nTShaDoWz:
That will not work @ flashforall because the bootloader will reject anything that is not signed by the Carrier/LG, so if you tried to flash it it would automatically reject it due to the non C/LG signed signature and would potentially leave you in some sort of emergency mode. At least this is how my other phones have worked, I can't verify it does it like this on LG phones but yeah. If anything, from my post here you at least learned how other BL's work haha.
[G4 Q&A, Help & Troubleshooting] Knowbody42:
What exactly does the signature prevent you from doing?

Does it prevent installing a modified bootloader in the first place, or does it prevent a modified bootloader from working if it is installed?
[G4 Q&A, Help & Troubleshooting] KonterBiER:
I guess it is preventing to install a modified one.

The old bootloader seems to have some loading code for new bootloaders. This code creates a checksum of the new bootloader code and uses a public key to decrypt a special pre or appended area in which a precalculated checksum was placed, encrypted by an unknow private key.

The interesting question is: Is it possible to write into the bootloader memory from an upstartet system, e.g. with dd? Or is some special procedure needed to disable a write protection?
[G4 Q&A, Help & Troubleshooting] KonterBiER:
It looks like the bootloader code is not encrypted on the first view:
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
New idea (remember: i flashed on my e975 optimus G (rollout with jb) a F180 (korean, hw more or less same..) ics kdz. Most worked (no signalwrong modem..)

What if we flash tmobile kdz? Is hardware same enough? Cause when we flash we should have unlocked bl. Then we need only to root and flash recovery then we can flash right modemandall should work...?

But dont know difference between h815 and the unlocked tmobile g4...

Thx for reading and hope u understand what i mean [MENTION=3336320]KonterBiER[/MENTION] my german friend xD

Griang ma scho hi dass ma wos findn zum unlocken... ;)
[G4 Q&A, Help & Troubleshooting] KonterBiER:
Hi 2nd Sky,

I don't know much about the LG KDZ files, what they contain and how important it is to have the correct one for your device model. The G4 is my first LG device. The last 5 years I used a HTC Desire HD ;)

But if the devices are identical from the hardware site, and the KDZ contains the bootloader, it should be worth to try.

But who want's to test it? Is there a risk to brick the device?

OT:

Oha, auch noch bayerisch :)
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
When u look in the folder: all images are in kdz:http://downloads.codefi.re/autoprime/LG/LG_G4/H815/H81510C/ (not the zip files)

Theres also kdz extractor at xda. Dont know if he works on g4 kdz's

I think my option is one of the only ways to become unlocked bl because of signature u cant edit kdz

But if the methode like low effort root works for other partitions its also way...

When u try somethink i would first backup efs partitions (imei and othrs) and have all files on sd so ucan put out sd...

And if you brick it, go to service and say update failed ;) normally u will become new mainboard. So try and risk something:p

OT ja bayrisch ;) hoffe dass ich bald an meinen pc kann und werd mich mal mit dem irc?! channel/chat auseinandersetzen und mit den chefs hier mal reden
[G4 Q&A, Help & Troubleshooting] KonterBiER:
I just downloaded the "LG-H81510C-Flashable.Bootloader.zip" and extracted it.

How is this file created?

It seems like aboot.bin contains some references to lg root certificates. Maybe such a dump of the T-Mobile variant would be very interesting!
[G4 Q&A, Help & Troubleshooting] jal3223:
Any input [MENTION=2684188]autoprime[/MENTION]?
[G4 Q&A, Help & Troubleshooting] xavierlangevin1:
If you could find the first revision of t-mobile version kdz and flash into your G4 that would be awesome. Actually i can't find one... before the 10h...
[G4 Q&A, Help & Troubleshooting] jal3223:
I'm pretty certain that has been tried. Either it fails or gives an insta-brick, I can't remember.
[G4 Q&A, Help & Troubleshooting] xavierlangevin1:
Yeah but i can't remember if a stock kdz could be modified with an injected system.img, so we could flash the 10h of my phone the 812 and apply the system.img of the 811 and unlock it ?
[G4 Q&A, Help & Troubleshooting] cloud1250000:
Hi guys!

Would it be possible to use this http://xdaforums.com/android/software-hacking/guide-how-to-reboot-to-edl-fastboot-t3394292 in order to flash a vulnerable aboot?

Or even forge a chain of trust with our own private /public key set?

They did it for the Redmi note 3 here

http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader-without-official-permission/

Thank you!
[G4 Q&A, Help & Troubleshooting] erasmuswill:
Looks quite interesting. I'm almost at the point of getting another device because of the locked bootloader and no root.
[G4 Q&A, Help & Troubleshooting] ABotelho23:
I'm already past that point. Got a OnePlus 3 and couldn't be happier. Sold my G4 for 400$ CAD and got the OP3 for 600$ CAD after tax.

Never again an LG device.!
[G4 Q&A, Help & Troubleshooting] erasmuswill:
I was looking at the oneplus 3 myself. import taxes are a ***** in south Africa though, and the mail service is extremely unreliable.
[G4 Q&A, Help & Troubleshooting] ABotelho23:
How did u get your G4? Via a carrier?
[G4 Q&A, Help & Troubleshooting] erasmuswill:
Yes. Had the Samsung tab 2 7.0 before, and I hated it. Actually checked the cm page to see if I can use a g4 and then I was like I'm getting this. After countless hours of research I've given up :(
[G4 Q&A, Help & Troubleshooting] ABotelho23:
Yea, I had a similar issue. Got a G4 imported from Taiwan (H815) to Canada from a company in the UK. LG's website didn't mention that the bootloader unlocking was region dependent at the time. So I bought it with the hopes of installing CM13 out of the box. Nope. So I spent over 6 months with a phone I hated.
[G4 Q&A, Help & Troubleshooting] culot:
Screw CAF LK:

#ifdef LGE_BOOTLOADER_UNLOCK
#define SECURITY_UNLOCK_MAGIC1 0x8DB7159E
#define SECURITY_UNLOCK_MAGIC2 0x2D7ED36B
#define SECURITY_UNLOCK_VERSION 0x00000001

typedef struct
{
char device_id[96];
char imei[32];
} unlock_input_data_type;

typedef struct
{
uint32_t magic1; // 0x8DB7159E
uint32_t magic2; // 0x2D7ED36B
uint32_t version; // 1
uint32_t hash_type; // sha256
uint32_t key_size; // rsa256
unsigned char signature[SECURITY_RSA_MAX_SIGN_SIZE]; // raw signature
unsigned char extra[492];
} unlock_certificate_data_type;
#endif // LGE_BOOTLOADER_UNLOCK
[G4 Q&A, Help & Troubleshooting] adds08:
Which device is this actually based off of?

Did you reverse this?
[G4 Q&A, Help & Troubleshooting] culot:
No, follow the link: it's the actual LK code for an LG msm8953 device (fhd tablet?). Roll back the commit one and you'll get some different LG code. Good stuff.

EDIT: woops, it's for the msm8952_p1v_att_us, the LG h740, ATT G Vista 2.
[G4 Q&A, Help & Troubleshooting] cloud1250000:
I think you will not be able to boot it because of the trust chain... you can only use a signed bootloader (with the right key lol).. So even tho you baked one, the device wouldn't boot. (not sure if it would be bricked too).
[G4 Q&A, Help & Troubleshooting] autoprime:
if anyone flashes the tmo kdz to a non-tmo g4 (and it actually flashes).. they will have a brick. it may not even let you flash it tho.

but test all you want ;)

as for specific details to things... nope.
[G4 Q&A, Help & Troubleshooting] leogeeko:
100 bucks to anyone who unlock the H815P bootloader! Oh lord! :p
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
.... Thx..... :(

No partitioninfo? Ok :(
[G4 Q&A, Help & Troubleshooting] Eagle1337:
well someone flashed the system image from t-mo on their h815, needless to say it's throwing an error code.
[G4 Q&A, Help & Troubleshooting] autoprime:
just system alone is different than flashing a kdz. u can fix the error code issue with a simple stock kdz flash.

if you flashed the tmo bootloader (in kdz) onto a non-tmo g4.. it wouldnt boot up into anything.
[G4 Q&A, Help & Troubleshooting] GUGUITOMTG4:
It does work for my h811 Kdz.
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
Ok i think i will look forward into my concept. Cause flash tmo kdz should be like 'convert int to tmo'

Have u [MENTION=2684188]autoprime[/MENTION] any concept for an ul BL? (also per pn answer allowed ;)

Perhaps we look at the

optimus g (att version e70) to nx4 convert thread if it can help but dont think so

I like to find a way so fast as possible! Im tired of seeing asking other people here -__-

But i think we will not find easy one klick methode at first...
[G4 Q&A, Help & Troubleshooting] KonterBiER:
Me too!

If you want to exchange with me, just write me a PM.

Maybe we can meet in an IRC channel tonight and discuss possibilities (maybe in german, that's fast for me :D).
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
add me on hangouts 19tofu97gmail.com but dont expect to much, my skills are minimal ;)

---------- Post added at 12:23 PM ---------- Previous post was at 12:00 PM ----------

link?
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
http://xdaforums.com/g4/general/info-lg-g4-korea-variant-rooted-anable-t3163925/

i check the output between H811 and H815

looks not good, H811 has more paritions then our H815

:/

Check between H815, there are by compare 2 different coutrys only 2 different partitions:

which are not listed by -by name

mmcblk1 and

mmcblk1p1
[G4 Q&A, Help & Troubleshooting] RenaKunisaki:
Isn't mmcblk1p1 just partition 1 of mmcblk1?
[G4 Q&A, Help & Troubleshooting] fpsq:
Dumb but maybe helpful?

I do have a official LG unlock.bin from an H815 that I do not use. Is anybody interested? Maybe it even helps the unlock process?:p

(Had to zip it....)
[G4 Q&A, Help & Troubleshooting] RenaKunisaki:
Looks a bit interesting.

00000000 9e 15 b7 8d 6b d3 7e 2d 01 00 00 00 02 00 00 00 |....k.~-........|
00000010 00 01 00 00 19 1f 4f 06 37 ab fe 52 c6 15 4b 20 |......O.7..R..K |
00000020 e4 d2 6e db e9 df 73 d3 89 f1 23 d5 56 14 87 c5 |..n...s...#.V...|
00000030 69 69 c9 fc 2a cc 2e 8c 1c 59 fc ed d7 7c 37 ae |ii..*....Y...|7.|
00000040 25 53 df d2 10 92 69 d9 4e 97 ce 1f 3c 56 17 f4 |%S....i.N...<V..|
00000050 0d d9 ad 6b 81 00 d5 8b 40 15 9b b2 5d 6c a7 b6 |...k....@...]l..|
00000060 4e bd e4 1f 14 c8 64 92 b8 da 86 db c5 c7 33 59 |N.....d.......3Y|
00000070 6b 3b d7 f2 79 ed 81 a2 19 0e 5d 90 75 20 89 30 |k;..y.....].u .0|
00000080 2b 94 4d 15 aa f2 31 b1 eb 03 3f 3a 87 51 b3 d8 |+.M...1...?:.Q..|
00000090 b5 e3 67 da a5 65 61 1e 76 cf a3 74 90 54 ae 29 |..g..ea.v..t.T.)|
000000a0 14 58 d7 52 93 10 66 76 fa 31 a6 56 f6 79 5a 51 |.X.R..fv.1.V.yZQ|
000000b0 05 49 40 6b cb 48 da fd d1 6c f6 cc e0 2d 35 00 |.I@k.H...l...-5.|
000000c0 7e df 49 82 bd c8 56 54 74 8f 5e 77 02 92 d0 99 |~.I...VTt.^w....|
000000d0 d4 bd e0 2e 01 2f 95 b8 0e 33 59 8c f1 96 9c 1e |...../...3Y.....|
000000e0 4b 80 41 cb 92 14 c5 09 68 2f cc 52 99 ea 22 59 |K.A.....h/.R.."Y|
000000f0 07 a0 b1 50 6c b1 f3 6c 29 4b ab 78 5c 92 31 70 |...Pl..l)K.x\.1p|
00000100 03 a2 82 df 9b 13 db 60 55 61 3b 20 0d 1e be 27 |.......`Ua; ...'|
00000110 ca 71 6d 98 00 00 00 00 00 00 00 00 00 00 00 00 |.qm.............|
00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000400

Quick examination suggests the structure is:

8 byte key or serial number: 9e 15 b7 8d 6b d3 7e 2d

unknown int32 field: 0x00000001

unknown int32 field: 0x00000002

int32 payload length: 256 bytes

payload data

padding until end of file

There's no obvious pattern to the payload data; it's likely encrypted (or might even be a crypto key). The first 8 bytes are probably based off the phone's IME, serial number, or something else. (Do you recognize it as any of the info from your phone?)

The real question of course is what would happen if someone else used this on their phone... or if we can get more unlock.bin files to compare.
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
With unlock.bin i cant beginn anything. I hope other can find something important. (i have nothing to do with that known..)

Atm we have 2 options:

Do anything with unlock.bin

Do anything with tmo kdz

So a third way is perhaps by team codefire. I hope for more transparence...

When i could compare partitions of f180 and e975 optimus G would be cool... But this is wrong forum for that.. So if there also some different it would be interesting to flash tmo on int but for me my int is too expensive (im not a rich ***** :p)... I like to try but i need my g4 as daily driver :/ (no i dont like to use s3...)

So i hope team codefire can give a statement of theyr actualy situation (also per pn possible if they dont like to talk to all..)
[G4 Q&A, Help & Troubleshooting] KonterBiER:
The unlock.bin file seems to contain a lot more than only the bootloader (called aboot.img in KDZ). The first thing I would do (when I would sit on a PC now :crying: ) is searching the offset of some byte strings known by a dumped aboot.img file. Maybe this way it is possible to find the bootloader inside unlock.bin, if it is not encrypted in some way.

Next step would be extracting it and disassembling it with an ARM disassembler ( IDA pro, gnu objcopy) and trying to find the kernel loading code.

Then do the same with the locked aboot.img and try to find the differences.

Just my first thoughts. But I believe it isn't that easy and something is encrypted or compressed with an unknown algorithm.
[G4 Q&A, Help & Troubleshooting] KonterBiER:
Okay, sorry, I've overseen the posting of RenaKunisaki.

If this is a real unlock.bin from LG, then this is just a package which assures the bootloader that he's allowed to unlock itself. This is not a full "modified" bootloader. Just the official "order" to unlock.

So the unlock-behavious has to be found in the aboot.img...
[G4 Q&A, Help & Troubleshooting] esmenikmatixx:
i was trying to backup laf.img then zero it to access fastboot and mistakenly backed up aboot and zeroed that out resulting in a brick. got a new g4 and put my sd card in and aboot.img was saved there from the old phone but i deleted it. ill see if i can get another copy off the new phone. maybe somebody with an unlockable model could post one too, and we can compare? mine is sprint ls991 zv5
[G4 Q&A, Help & Troubleshooting] KonterBiER:
Nice idea esmenikmatixx!

I think the bootloader has a special memory area which is zeroed in locked mode. At the initialization, the bootloader is applying some "mathematics" on this memory area (with an co-processor? seen on diasassembly) and then decides if it is in unlocked mode or not.

The unlock.bin seems to be written into this memory area and contains phone dependend signature code.
[G4 Q&A, Help & Troubleshooting] neonero:
Hi all,

I tried to unlock my LG H815 via LG Dev web site. I put my IMEI and Device ID and I get this message : Unfortunately, your device (SFR/FRANCE) does not support unlocking the bootloader.

My phone is sim locked by the French carrier SFR.

I look to another way to unlock the bootloader ?
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
No Provider Phones are supported by LG.

ONLY H815 for open marked (no branding or simlock..)

I got this:

Unfortunately, your device (Germany, (VODAFONE(GERMANY)) ) does not support unlocking the bootloader.
[G4 Q&A, Help & Troubleshooting] montusk:
Small OT: even if i don't understand anything about these numbers, letters, encrypting & decrypting things i love the passion you guys put in this trying to unlock the bootloader.. So i wish you good work and also a bit of luck :D
[G4 Q&A, Help & Troubleshooting] fpsq:
Well:

Device Id: 3A8C8EF4B6FAAAA8154BE34131DF4ECB8CC93340D776657184B36EFDD56AD54F

IMEI 359872-06-220273-3

I tried it on a different LG G4:

Wrong device or similar was the error message. I can not recreate it, as I am already unlocked. But you can try.
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
To explain how u become ur unlock.bin.

Heres step by step via lg developer page:

http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS

in own words:

First u look at IMEI (in dialer *#06# or Settings >> About phone >> Status >> IMEI )

enable usb debugging and oem unlock at developer settings (tap 7times on build number)

then u look at device-id: (adb reboot bootloader, fastboot oem device-id

enter imei and device-id at lg dev page and u will become unlock.bin via email!

now put unlock.bin at adb folder and type fastboot flash unlock unlock.bin

so when we look at the unlock.bin. how many numbers are inside?

IMEI: 15 numbers (for me!)

Device-ID: 64 letters (20 alphabets and logicial then 44 numbers)

device id at lg dev (example) has 22alphabets and 42numbers)

does it fit to the unlock.bin?
[G4 Q&A, Help & Troubleshooting] RenaKunisaki:
Does your device show the IMEI in hex? (Maybe on a barcode under the battery, or on the box?) I don't know how they're converted. If we just ignore the hyphens and convert it as one long number we get 1474D3E6EA36D which doesn't appear in that data. The device ID isn't found there either. So there's almost certainly some hashing going on. Though I don't know what hash algorithm would give an 8-byte output. Even MD5 is 16 bytes.

It's also possible that the 8-byte string is also looked up in the database, but I'd question why they need both IMEI and device ID then. Most likely IMEI is looked up to find the crypto key, and device ID (and probably also IMEI) is hashed (among with who knows what other information/salt) to produce the 8-byte signature.

I can't try it on my own G4 right now because it's in the shop getting unbricked. But it sounds like that confirms that there's a device-specific ID in the file. That would also mean, if you took an unlock.bin that is for your device and changed one of the bytes from offset 0x14 - 0x114, it would probably give a different error such as "invalid key" instead of "wrong device". If so, that would confirm the meanings of those fields. (But it might just say "wrong device" any time the data is incorrect, too.)

Anyway I don't think we can learn much more from static analysis unless someone finds a pattern with that IMEI/device ID that I didn't notice. The thing to try now would be changing the unknown fields and/or disassembling the code that actually interprets this file.
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
I would love to test any semi safe bootloader unlock methods
[G4 Q&A, Help & Troubleshooting] KonterBiER:
I don't believe that each device has it's own private/public key pair. That would mean a lot of administration effort for LG.

One single key pair is enough. This could also answer the question why LG is only able to unlock the non-carrier G4 versions. The carriers could have their own key pair independently of LG.

If you don't have the encryption key you can't generate the cipher, even if you know it's plaintext. Inside this ciphertext could be some "conditional access" information like the device id, by which the bootloader can decide whether the message is for him or not. This is how it is done in smartcard based paytv systems all over the world, and these have to be even more secure ;)
[G4 Q&A, Help & Troubleshooting] LwannaCM:
Maybe some LG Developer that hangs out in this forums and is really underpaid might solve the question or give any hints without comprimsing his job.

Thank you in advance if you exist :).

That LG gives you a chance to unlock the bootloader on official H815 devices is nice, but from LG to decide to give that decision to the providers is very poorly and quite unfair. Reminds me of the old SIMlock days.

T-Mobile was dumb enough or maybe smart enough to create a bootloader that in unlockable, so now i hate beeing on the wrong carrier and use my good old G3 with an AOSP-Rom.
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
Could be that file important for bl unlock? O.o
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
Hm i wonder if anybody that has the h815 eu version and has used the official unlock could maybe provide a copy of his system to check for differencesin files like these.
[G4 Q&A, Help & Troubleshooting] fpsq:
Tell me what shall I do?

Sent from outer space using telepathy
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
Do you have the h815 eu version with a officialy unlocked bootloader
[G4 Q&A, Help & Troubleshooting] fpsq:
Yes.

Sent from outer space using telepathy
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
Try using a computer to use this command. You should be able to use the adb.exe that came in the lg root tools folder. Your phone needs to be connected to your computer and adb debugging needs to be on.

adb.exe pull /system

After the command finishes you compress it as a zip or 7z your choice and then upload it here for us people to compare.
[G4 Q&A, Help & Troubleshooting] fpsq:
OK. What is in System? Will I be giving away my IMEI, Android Device Id and the like?
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
No it is the same thing that isflashed in thread to root the models that cant officially unlock. It is essently the equivalent of windows system folder only for android
[G4 Q&A, Help & Troubleshooting] fpsq:
Will do asap

Sent from outer space using telepathy
[G4 Q&A, Help & Troubleshooting] 2nd Sky:
I got the file by hidden settings:

Dialer: 277634#*#

Svc menu

Log service

Copy log files

Look at sd or internal for folder 'logger'

Search folder dontpanic

Open cmdline0 (i used root explorer)

For me: h815 vodafone branding and NOT rooted
[G4 Q&A, Help & Troubleshooting] xxsashixx:
Will a bootloader unlock ever be possible for other h815 variants?

Thanks
[G4 Q&A, Help & Troubleshooting] fpsq:
7260 files pulled. 0 files skipped.
2641 KB/s (3432824494 bytes in 1269.235s)

Any idea where to host such a large zip file?
[G4 Q&A, Help & Troubleshooting] player911:
Probably place like Google Drive or equivalent. The goal is to get it to a dev. They can disburse it amongst themselves as needed.

I think the goal is to compare an unlocked state to a locked state.
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
Yeah i recommend google drive or megaupload. and yes the goal is to compare the system folder for differences between a locked and unlocked state.
[G4 Q&A, Help & Troubleshooting] fpsq:
Try:

https://spideroak.com/browse/share/SPQR/System/G4/

7zip pass is:

LGG4System

Tell me when you successfully downloaded the file. I will take down the link after that. Do me a favour, keep in mind that people want to encrypt their devices even if unlocked & rooted :)

I hope it helps!
[G4 Q&A, Help & Troubleshooting] KonterBiER:
In another thread at (I believe) AT&T G4 device forum I read something about "zeroing out the laf partition" to disable the secure boot feature.

Did anyone test this?
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
Ok i am downloading now when i am done may i have your permission to reupload on my megaupload account without a password. So you can take down your link to perserve storage.

---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------

I read that to i will try looking into that. I did not read any more about it though
[G4 Q&A, Help & Troubleshooting] fpsq:
Sure! Go ahead. Just make sure the zip file contains everything you need. I debloated and froze a few apps. Not that you miss something important.

Sent from outer space using telepathy
[G4 Q&A, Help & Troubleshooting] Shadicbypass:
Ok thanks here is the link

https://mega.nz/#!bgokBQAT!bXzIPuIPmNuhNAwKrAHCfOkrFcboNzWG6euYWlh517I