Develop Bugs

[21 AUG][VIDEO TUT]How To Install CLK

5 minute tutorial video on how to install clk
credit to cedesmith for creating the clk bootloader
if you run into this problem - "when I right click the google drivers file and hit install it says "The INF file you selected does not support this method of installation"
then you need to do this - the problem I had was resolved by changing my windows update settings. I had to change them to always install the best drivers for my device.That got me the boot loader drivers ,android sdk and adb. after that I follewed these steps from post #10: device manager>androiddevice>update software>browse my copmputer>let me choose>have disk>browse to .inf file>click or( double click) the.inf file and see if it will install."

Cant wait till they fix the rmnet issue with clk

nice work!!!
i will add your link to my OP ....

nice video

when I right click the google drivers file and hit install it says "The INF file you selected does not support this method of installation." I'm using same OS as you.
Thanks in Advance

manemzjum said:
Cant wait till they fix the rmnet issue with clk
Click to expand...
Click to collapse
+1 here
PPP drops a lot when compared to the RMNET stability

Hi,
Thanks for the tutorial. Personnaly I prefer using HD2_Toolkit_KSubedi_3.6.
Having a video on it will be great (I think)

adazamim said:
+1 here
PPP drops a lot when compared to the RMNET stability
Click to expand...
Click to collapse
This is not true.....PPP is much more better....use the beta4 and you ' ll see that i'm right...some devs use beta5 that had problems and made that voice go around...then you have to find the best combination of files if you make a ROM based on cLK ....

tdizzle404 said:
when I right click the google drivers file and hit install it says "The INF file you selected does not support this method of installation." I'm using same OS as you.
Thanks in Advance
Click to expand...
Click to collapse
what operating system are you using?

tdizzle404 said:
when I right click the google drivers file and hit install it says "The INF file you selected does not support this method of installation." I'm using same OS as you.
Thanks in Advance
Click to expand...
Click to collapse
try these steps if it doesnt work:
device manager>androiddevice>update software>browse my copmputer>let me choose>have disk>browse to .inf file>click or( double click) the.inf file and see iif it will install.

96edwy said:
try these steps if it doesnt work:
device manager>androiddevice>update software>browse my copmputer>let me choose>have disk>browse to .inf file>click or( double click) the.inf file and see iif it will install.
Click to expand...
Click to collapse
I have win7 64bit isnt this the same steps in the video?

tdizzle404 said:
I have win7 64bit isnt this the same steps in the video?
Click to expand...
Click to collapse
no they are different, if they dont work, you may need to install the android sdk to get the drivers

96edwy said:
no they are different, if they dont work, you may need to install the android sdk to get the drivers
Click to expand...
Click to collapse
Yea I think that's what I need to do I had it working before but I had to re install windows, I tried the new way and it say the folder I specified doesn't contain a driver,make sure it is designed to work with window x64 based system
Thank you for your help

tdizzle404 said:
Yea I think that's what I need to do I had it working before but I had to re install windows, I tried the new way and it say the folder I specified doesn't contain a driver,make sure it is designed to work with window x64 based system
Thank you for your help
Click to expand...
Click to collapse
Bty Im having this issue in boot loader screen
EDIT: Ok the problem I had was resolved by changing my windows update settings. I had to change them to always install the best drivers for my device.That got me the boot loader drivers ,android sdk and adb. after that I follewed your stepes from post #10 "try these steps if it doesnt work:
device manager>androiddevice>update software>browse my copmputer>let me choose>have disk>browse to .inf file>click or( double click) the.inf file and see iif it will install."
That worked . Thanks your video is great and hopefully will help alot of people Maybe people that run into the same issue I did dint have there windows update set up right for new drivers. thanks.

tdizzle404 said:
Bty Im having this issue in boot loader screen
EDIT: Ok the problem I had was resolved by changing my windows update settings. I had to change them to always install the best drivers for my device.That got me the boot loader drivers ,android sdk and adb. after that I follewed your stepes from post #10 "try these steps if it doesnt work:
device manager>androiddevice>update software>browse my copmputer>let me choose>have disk>browse to .inf file>click or( double click) the.inf file and see iif it will install."
That worked . Thanks your video is great and hopefully will help alot of people Maybe people that run into the same issue I did dint have there windows update set up right for new drivers. thanks.
Click to expand...
Click to collapse
thanks man, i will include this in the first post

Having an issue
Task 29 completes ok.
Install ClK but on repboot I get no Android logo just lots of text finishing with the line:-
[2670] -- portchange --
Any ideas please?

i need help. =/. i im trying to install clk. and i get the "the inf file does not support this method of installation"
i go to device manger. right click update drivers. choose myself. but there isnt one for browse disc or anything im using win7 x82 ultimate

My bootloader corrupted
Hi,
I was actually trying to put ICS on my device from GingerBread Nand.I connect device with USB and I was trying to Wipe using HD2 Nand Toolkit.As device reached 100%, it suppose to restart but in my case it hanged at 100% for 30 mins .Then I restart by removing the battery.Now when 3 color screen shows, it shows serial at the bottom but it change to usb when I connect to pc .The problem is now when I try to re-partition ,it says device is not connected.
So I thought I may be able to install windows by downloading actual rom from T-Mobile and place the file to sd card by renaming it to LEOIMG.nbh.I did it using a class 2 16Gb card.As I press both volume down key and power button, it goes right to the rainbow screen.Please help me!
Thanks for reading the issue.

tdizzle404 said:
I have win7 64bit isnt this the same steps in the video?
Click to expand...
Click to collapse
i had the same problem using 64 bit windows. all you have to do is to go to device mananger and right click on android, select update driver and select from computer and then browse to clk install folder and select folder device driver and then select google usb driver folder and select update. it will update driver from there.

sweetdoc said:
i had the same problem using 64 bit windows. all you have to do is to go to device mananger and right click on android, select update driver and select from computer and then browse to clk install folder and select folder device driver and then select google usb driver folder and select update. it will update driver from there.
Click to expand...
Click to collapse
That post was from August 2011, I'd think he's either sorted his problem out or moved on by now

[Q] Gnex stucks on Nexus logo

Hello guys, I need your help with the Gnex.
My friend gave me the phone hoping that I can do something. It stucks on nexus logo while booting. USB debugging is turned off, cwm or twrp is not installed. All I can is to enter Android system recovery with the following options: apply update from adb; apply update from usb drive; wipe data factory reset; wipe cache partition.
I've tried wiping cache partition but is doesn't help. Please advice whether wiping data/factory reset will delete the data from internal SD card - I am afraid to lose the photos.
Please advice what should I do to extract data (photos) in my situation?
Thanks in advance to everyone.

Sync???
were photos synced to google????

tosradde for
Wajeeh4616 said:
were photos synced to google????
Click to expand...
Click to collapse
No, they weren't.

fastboot? try it first..
change ur boot.img /kernel
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

memaro_maro said:
fastboot? try it first..
change ur boot.img /kernel
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please explain - I'm new in this. I can enter fasrboot mode, the status is FAILBootloader locked. What should I do next?

3n3r said:
Can you please explain - I'm new in this. I can enter fasrboot mode, the status is FAILBootloader locked. What should I do next?
Click to expand...
Click to collapse
?? learn about adb & fastboot..
or use this toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
try use modified boot.img
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

wiping
I don't think that anything can help you except that tool because as you are saying that USB debugging is not enabled

Wajeeh4616 said:
I don't think that anything can help you except that tool because as you are saying that USB debugging is not enabled
Click to expand...
Click to collapse
Made wipe data - android loaded but photos are gone.. sad

3n3r said:
Made wipe data - android loaded but photos are gone.. sad
Click to expand...
Click to collapse
before using device too much, quick go to galaxy nexus general section here, and find thread "internal data recovery, yes we can"
you might be able to recover deleted photos.
the way it works when you delete things, is it just tells os that the space isnt being used, so the actual data might still be there and some may still be recoverable.
it is quite a process though. good luck

3n3r said:
Made wipe data - android loaded but photos are gone.. sad
Click to expand...
Click to collapse
You should install a recovery fast as it will help you in future

ashclepdia said:
find thread "internal data recovery, yes we can"
you might be able to recover deleted photos.
Click to expand...
Click to collapse
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?

3n3r said:
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
Click to expand...
Click to collapse
The directory from which you are using adb command
As an example if I am using cmd and typing this command then it should be like
E:/>adb fastboot *********
Then my adb file must be in E drive

Wajeeh4616 said:
The directory from which you are using adb command
As an example if I am using cmd and typing this command then it should be like
E:/>adb fastboot *********
Then my adb file must be in E drive
Click to expand...
Click to collapse
Thank you for your help. I've followed to step 6, but unfortunalely, RAW file is 0 b after creation. I've tried different numbers in this name mmcblk0p12.raw - but with no effect.. Tried to reinstall cygwin, used NetCat file insted of NC - all the same.
Maybe anyone faced this problem with 0 b size of the RAW file? Maybe it's because I have less than 15 Gb of free space on my disk C?
Would be grateful for your advices.

3n3r said:
Thank you for your help. I've followed to step 6, but unfortunalely, RAW file is 0 b after creation. I've tried different numbers in this name mmcblk0p12.raw - but with no effect.. Tried to reinstall cygwin, used NetCat file insted of NC - all the same.
Maybe anyone faced this problem with 0 b size of the RAW file? Maybe it's because I have less than 15 Gb of free space on my disk C?
Would be grateful for your advices.
Click to expand...
Click to collapse
Cant answer your question but can give you an advice....
Leave all this and dont play with your mobile they were only pictures so forget them or else after sometime you will be following a guide to unbrick your phone.

3n3r said:
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
Click to expand...
Click to collapse
I'd like to try explaining this a little better. Basically when using a program from the command prompt in any OS the OS needs to know where the program is (this is not just for command prompt, but I digress). There are a few ways of telling the OS where the program you want to use is located.
For example, lets say you have ADB in the folder "android_stuff" on your E drive.
Option 1: Change Directory to the folder, IE: "cd android_stuff"
Option 2: Provide the "full path name" of the program, "e:\android_stuff\adb"
Option 3: Add the folder location to the system "path"
Options 1 and 2 are fairly easy and straightforward, whereas Option 3 can be done in a few ways.
My suggestion is to go with Option 1, its the easiest and all you would have to do is put all of the files you will be using into a single folder.

Possible to sideload older version of 'Advanced Info' ?

I'm trying to interop unlock my Lumia 550, but it seems the Advanced Info app has updated as when I get to step 2 of unlocking in the vcReg app, it just crashes. Is it possible to download and sideload an older version of the app to allow me to finish the interop unlock?

No

Sideload.
Just erase -zip extension.

augustinionut said:
Sideload.
Just erase -zip extension.
Click to expand...
Click to collapse
Cheers, will give it a go in a sec and see how it goes :good:
EDIT: Not working unfortunately, getting the same crash.

'Advanced Info' req interop unlocked device BTW

Connor_Price said:
Cheers, will give it a go in a sec and see how it goes :good:
EDIT: Not working unfortunately, getting the same crash.
Click to expand...
Click to collapse
Why dont use interoptool?

augustinionut said:
Why dont use interoptool?
Click to expand...
Click to collapse
It doesn't work. I have a Lumia 550, so I click on Restore NDTKSvc (x50) and it says it didn't find the file. However, I accidentally toggled the one for non x50 devices and can't figure out how to undo that, so maybe that is my issue.

You need to put the file inside phone ))

augustinionut said:
You need to put the file inside phone ))
Click to expand...
Click to collapse
I'm following this tutorial: https://forum.xda-developers.com/wi...creg-lumia-reg-editor-interop-unlock-t3451723
I get to step 5 and then get the crash. I have all of the necessary files on the phone.

augustinionut said:
You need to put the file inside phone ))
Click to expand...
Click to collapse
Sorry, I'm on my phone and accidentally posted twice.

https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
Other OEM devices

partition.xml needed for unbricking hardbricked 5X devices!

Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)

qb74 said:
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
Click to expand...
Click to collapse
I have no idea to make such a backup since I cannot access the device's emmc in Linux.
I've used this method on another phone but there I could access the emmc directly as external storage by using a key combo on boot.
Skickat från min Nexus 5X via Tapatalk

Nicktheprofessor said:
I have no idea to make such a backup since I cannot access the device's emmc in Linux.
I've used this method on another phone but there I could access the emmc directly as external storage by using a key combo on boot.
Skickat från min Nexus 5X via Tapatalk
Click to expand...
Click to collapse
here
it's for another chipset, but the same process applies for all chipsets.

qb74 said:
here
it's for another chipset, but the same process applies for all chipsets.
Click to expand...
Click to collapse
Can't help you with that one then since I'm running Linux on all my machines. Too bad, I wouldn't mind having a complete backup.
Skickat från min Nexus 5X via Tapatalk

Maybe the people with Linux machines and free time would wanna try this?
https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/

gogozombiii said:
Maybe the people with Linux machines and free time would wanna try this?
https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
Click to expand...
Click to collapse
@Nicktheprofessor Try checking this out, if you got the time! You would help the community out a ton!

qb74 said:
@Nicktheprofessor Try checking this out, if you got the time! You would help the community out a ton!
Click to expand...
Click to collapse
I'll need an OTG storage device to do this. I can backup the entire thing using dd but it can't be written to the internal storage (for obvious reasons, it would then backup the backup and the backup of the backup and so on).
If I could access it on the computer or send it to the computer then that would work but I'm not aware of any way to do that without storing it locally first (which, as previously mentioned, is impossible to do).
[EDIT] I wonder if it's possible to use adb root pull from TWRP to pull /dev/mmcblk0, I'll try that after cleaning it up. If that works then it's a piece of cake to do this on any phone. [/EDIT]

qb74 said:
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
Click to expand...
Click to collapse
OK, so I managed to do a complete backup via adb pull /dev/mmcblk0
For future reference, this is the easiest way:
From a fastboot boot twrp:
adb root
adb pull /dev/mmcblk0 emmc.img
Now, that's 13GB worth of data that you don't need, I can give you a part table on this (using part) or whatever you need but It's a bit too big to upload as is.
I can run an emulator and mount it as is and that works too but all I can extract from there is data.
Now, shutting down your device and inserting your USB cable while holding vol + AND vol- seems to mount emmc as portable storage, that should mean that you can dd the entire thing right onto the device?

Nicktheprofessor said:
OK, so I managed to do a complete backup via adb pull /dev/mmcblk0
For future reference, this is the easiest way:
From a fastboot boot twrp:
adb root
adb pull /dev/mmcblk0 emmc.img
Now, that's 13GB worth of data that you don't need, I can give you a part table on this (using part) or whatever you need but It's a bit too big to upload as is.
I can run an emulator and mount it as is and that works too but all I can extract from there is data.
Now, shutting down your device and inserting your USB cable while holding vol + AND vol- seems to mount emmc as portable storage, that should mean that you can dd the entire thing right onto the device?
Click to expand...
Click to collapse
Maybe? Not entirely sure if the dd method could work since this kind of hardbrick literally bricks your phone if you don't have the right files. Great job on the backup though! Mind telling me the steps for dd-ing the entire thing onto my device?
Or better, create partition.xml and extract & upload rawprogram0.xml and patch0.xml so that I can use myself as a test dummy.
its a guide for linux systems, hopefully you can help us get one step closer to fixing our devices!

qb74 said:
Maybe? Not entirely sure if the dd method could work since this kind of hardbrick literally bricks your phone if you don't have the right files. Great job on the backup though! Mind telling me the steps for dd-ing the entire thing onto my device?
Or better, create partition.xml and extract & upload rawprogram0.xml and patch0.xml so that I can use myself as a test dummy.
its a guide for linux systems, hopefully you can help us get one step closer to fixing our devices!
Click to expand...
Click to collapse
Yeah, that doesn't help since it's made for extracting a partition.xml from a .KDZ where these partition files exist.
In a copy of your disk that doesn't exist, there isn't a file to copy and paste into that.
I can do the partition table and partition sectors if you want that but without knowing what is actually needed (as in the source code in the tool used to fix the device) I can't really help.
I'll check if i can put a device in that state and see what happens with the emmc connection.

Nicktheprofessor said:
Yeah, that doesn't help since it's made for extracting a partition.xml from a .KDZ where these partition files exist.
In a copy of your disk that doesn't exist, there isn't a file to copy and paste into that.
I can do the partition table and partition sectors if you want that but without knowing what is actually needed (as in the source code in the tool used to fix the device) I can't really help.
I'll check if i can put a device in that state and see what happens with the emmc connection.
Click to expand...
Click to collapse
Get the partition table and partition sectors, that's a start! (even though I got no clue how to continue after that )
Do you mean the source code of QPST/QFIL? That's a rather impossible task though

qb74 said:
Get the partition table and partition sectors, that's a start! (even though I got no clue how to continue after that )
Do you mean the source code of QPST/QFIL? That's a rather impossible task though
Click to expand...
Click to collapse
I'm talking about the source code of the programming tool but I might not need that either if i can just examine it on my own and I have one of those devices on hand come tuesday.
I'm fairly confident that I can build a programmer to rewrite the emmc with whatever I want it to if i can just get a hold of the system calls.
Do you want to work together on this? It seems to me that it would be worthwhile even in the long run as QC are unlikely to change this procedure.

Nicktheprofessor said:
I'm talking about the source code of the programming tool but I might not need that either if i can just examine it on my own and I have one of those devices on hand come tuesday.
I'm fairly confident that I can build a programmer to rewrite the emmc with whatever I want it to if i can just get a hold of the system calls.
Do you want to work together on this? It seems to me that it would be worthwhile even in the long run as QC are unlikely to change this procedure.
Click to expand...
Click to collapse
Absolutely! Even though I don't have the necessary knowledge with Android/Linux, I do have basic Windows knowledge. I'd be glad to help out the community as a whole!

bump!

qb74 said:
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
Click to expand...
Click to collapse
i just found for the nexus 5x the lg tot firmware u can use it to make the partition.xml
lg h791 16g
drive.google.com/uc?id=0B89Fk5GHkvZqb3I3bV9rTksxZFE&export=download
lg h791 32g
cloud.mail.ru/public/G1bp/vhoVk1MwW
i used BoardDiag to extract the frimware
drive.google.com/file/d/0Bw1P9EP0d9nZY0FUall1VWVvc0k/view
and here is how to build partition.xml and extract rawprogram0.xml and patch0.xml from it
youtube.com/watch?v=BmAuzbG9re4
now we need prog emmc firehose 8992.mbn to use with QFIL/QPST
i hope u can find a solution i'm stuck with a dead nexus 5x for the moment

do you need h798 16G version dd image? if you need I can dump to you
---------- Post added at 09:17 AM ---------- Previous post was at 08:40 AM ----------
Nicktheprofessor said:
OK, so I managed to do a complete backup via adb pull /dev/mmcblk0
For future reference, this is the easiest way:
From a fastboot boot twrp:
adb root
adb pull /dev/mmcblk0 emmc.img
Now, that's 13GB worth of data that you don't need, I can give you a part table on this (using part) or whatever you need but It's a bit too big to upload as is.
I can run an emulator and mount it as is and that works too but all I can extract from there is data.
Now, shutting down your device and inserting your USB cable while holding vol + AND vol- seems to mount emmc as portable storage, that should mean that you can dd the entire thing right onto the device?
Click to expand...
Click to collapse
adb pull /dev/mmcblk0 emmc.img
this command does not work
first there no device /dev/mmcblk0 but in /dev/block/mmcblk0 second adb pull /dev/block/mmcblk0 emmc.img does not work.
F:\BaiduNetdiskDownload>adb pull /dev/mmcblk0 emmc.img
adb: error: remote object '/dev/mmcblk0' does not exist

youxiaojie said:
do you need h798 16G version dd image? if you need I can dump to you
---------- Post added at 09:17 AM ---------- Previous post was at 08:40 AM ----------
adb pull /dev/mmcblk0 emmc.img
this command does not work
first there no device /dev/mmcblk0 but in /dev/block/mmcblk0 second adb pull /dev/block/mmcblk0 emmc.img does not work.
F:\BaiduNetdiskDownload>adb pull /dev/mmcblk0 emmc.img
adb: error: remote object '/dev/mmcblk0' does not exist
Click to expand...
Click to collapse
You need to reboot to a TWRP (or whatever recovery that supports unencrypted storage) that supports unencrypted devices before you attempt it.
You have to do this through fastboot boot recovery.img and not through flashing it. You are correct about /dev/block/mmcblk0 though. My apologies for the confusion caused by that.

I got it
Nicktheprofessor said:
You need to reboot to a TWRP (or whatever recovery that supports unencrypted storage) that supports unencrypted devices before you attempt it.
You have to do this through fastboot boot recovery.img and not through flashing it. You are correct about /dev/block/mmcblk0 though. My apologies for the confusion caused by that.
Click to expand...
Click to collapse
after formatting data partition, I removed whole disk encrypt and success run "adb pull /dev/block/mmcblk0 emmc.img" command.
https://pan.baidu.com/s/1bpcvqV1
and do I used "adb push emmc.img /dev/block/mmcblk0" to recover whole emmc when my phone soft bricked?

youxiaojie said:
after formatting data partition, I removed whole disk encrypt and success run "adb pull /dev/block/mmcblk0 emmc.img" command.
https://pan.baidu.com/s/1bpcvqV1
and do I used "adb push emmc.img /dev/block/mmcblk0" to recover whole emmc when my phone soft bricked?
Click to expand...
Click to collapse
file is not working, getting a error when unzipping it

qb74 said:
file is not working, getting a error when unzipping it
Click to expand...
Click to collapse
https://mega.nz/#!Oo9DxJyL!rzFl_s2ie1frCr79TpYTYKoeXNwg78d5dc-a71bkInE
try this again

How To Guide Guide: Unbrick Pixel 6 Oriele or Pixel 6 Pro "Raven"

Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU
This means that there is Exynos boot recovery in the CPU
You can repair the bootloader using the Samsung Exynos Tool
Nothing could be flashed from the mode, however it loads into the RAM the fastboot mode, from here reflash the bootloader image using fastboot
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Set this up using windows 7 32 bit
use this config not the one he has included, but use his tutorial
DNW_STORE exynos down 200 20 bl1.bin
DNW_STORE exynos down 2000 20 bl2.bin
DNW_STORE exynos down 200 20 elr_el3.bin
DNW_STORE exynos down 200 20 lastly.bin
DNW_WAIT
;PIXEL ROM RECOVERY
DNW_STORE exynos down 20000 20 bl.bin
NOTE: this is EDL mode!!
If not working or you need help let me know

@pierre383
Have you recovered any Pixel 6/6 Pro unit in real life yet using this procedure? If so, then kindly post a more elaborate guide so that we can cover it for the portal.
===
AFAIK, a hard-bricked Google Silicon device (e.g. the Pixel 6/6 Pro) by default exposes a serial interface with vendor ID 18D1 (aka Google) and device ID 4F00.

SkandaH said:
@pierre383
Have you recovered any Pixel 6/6 Pro unit in real life yet using this procedure? If so, then kindly post a more elaborate guide so that we can cover it for the portal.
===
AFAIK, a hard-bricked Google Silicon device (e.g. the Pixel 6/6 Pro) by default exposes a serial interface with vendor ID 18D1 (aka Google) and device ID 4F00.
Click to expand...
Click to collapse
Hi sorry am making this fast, when you have it as a unverified device in device managment, install Exynos mode USB driver (USE 32BIT operationing system for the one in the post I linked), prepare the boot + cfg (just take mine), hold the power button and select in the software it should begin, if you have problems uncomment the DNW_WAIT or try another USB cable, the motherboard in your computer is the difference
if your computer say the driver is not compatible on 32bit computer, pick install anyway, install manually a driver for the selected device from a list of installed drivers on the computer (in device manager)
if you need more help or can help me make it better pls let me know
Linux will work also with different tool, but the DNW_WAIT can't be replicated :? so got stuck on pixel rom recovery line, fastboot did not load on the phone
after dnw_wait if phone is not recognized hold power button while DNW_WAIT sequence maybe

Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
Click to expand...
Click to collapse
it's amazing ! but how to unpack these bin files? stock image only has a bootloader.img
or could i use dd to copy it that from my phone filesystem in terminal ?

split bootloader as explained, it is inside bootloader.img if you need more guidence let me know and yes dd can copy bootloader.img however this assume that you phone can't turn on so you can't copy it from dd terminal in the phone because how can you do that in brick state... don't try and prepare for brick, rollback protection will assure that you can't boot a old bootloader from long time ago you prepared incase of brick you need new BL
iCassius said:
it's amazing ! but how to unpack these bin files? stock image only has a bootloader.img
or could i use dd to copy it that from my phone filesystem in terminal ?
Click to expand...
Click to collapse

oh I see it ! it means I need split bootloader.img to 4 bin files .
so it we can get 64bit drivers , it means newly computer and windows is useable?

iCassius said:
oh I see it ! it means I need split bootloader.img to 4 bin files .
so it we can get 64bit drivers , it means newly computer and windows is useable?
Click to expand...
Click to collapse
I recommend using a virtual machine with 32bit Windows 7 or XP or Vista, working with making the Linux work, Install Windows 32 bit on your laptop (you can use a 2nd partition maybe)
It is about fixing the phone that cost 600€, working 1 hour to make Windows 32bit work in 1 or another way is not a big deal
However there are 64 bit drivers around but they are not on XDA, so yes, theoretically it can work with modern 64bit windows

Could you please explain how to split the bootloader image or attach the files?

pierre383 said:
Linux will work also with different tool, but the DNW_WAIT can't be replicated :? so got stuck on pixel rom recovery line, fastboot did not load on the phone
Click to expand...
Click to collapse
Hi @pierre383 thanks for your guide. I have a bricked Pixel 6. But it only stays visible in Pixel ROM Recovery Mode for about 10s.
What linux tool is available? and where?
Thanks

speedpat said:
Hi @pierre383 thanks for your guide. I have a bricked Pixel 6. But it only stays visible in Pixel ROM Recovery Mode for about 10s.
What linux tool is available? and where?
Thanks
Click to expand...
Click to collapse
GitHub - frederic/exynos-usbdl: Unsigned code loader for Exynos BootROM
Unsigned code loader for Exynos BootROM. Contribute to frederic/exynos-usbdl development by creating an account on GitHub.
github.com
Look into building this, or dm me for discord or telegram and I can gladly guide you through building and using it

z3r0skull said:
Could you please explain how to split the bootloader image or attach the files?
Click to expand...
Click to collapse
I could post in the weekend

Hi @pierre383. You might want to change this thread type from "Question" to "How to guide". Just either edit the first post and you can then change the thread type there, or click the 3-dot menu in the upper right corner above the first post and choose "Edit thread" and you can change it there instead - either way.

pierre383 said:
I could post in the weekend
Click to expand...
Click to collapse
Thanks that would be nice.
Also my pixel is not recognized by the "multidownloader" tool mentioned in the other guide. Did you install any specific driver for it to work?
Thank you.

Hi! Any updates on where to get those files?

Also another thing: the driver is not picked up be the phone, it is still stays as USB Composite Device.

z3r0skull said:
Could you please explain how to split the bootloader image or attach the files?
Click to expand...
Click to collapse
@z3r0skull
you can extract the file with imjtool from the bootloader.img
on Linux that would be:
Code:
imjtool.ELF64 bootloader-oriole-slider-1.2-8085990.img extract

pierre383 said:
Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU
This means that there is Exynos boot recovery in the CPU
You can repair the bootloader using the Samsung Exynos Tool
Nothing could be flashed from the mode, however it loads into the RAM the fastboot mode, from here reflash the bootloader image using fastboot
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Set this up using windows 7 32 bit
use this config not the one he has included, but use his tutorial
DNW_STORE exynos down 200 20 bl1.bin
DNW_STORE exynos down 2000 20 bl2.bin
DNW_STORE exynos down 200 20 elr_el3.bin
DNW_STORE exynos down 200 20 lastly.bin
DNW_WAIT
;PIXEL ROM RECOVERY
DNW_STORE exynos down 20000 20 bl.bin
NOTE: this is EDL mode!!
If not working or you need help let me know
Click to expand...
Click to collapse
I extracted the bootloader but I don't see ELR_EL3, LASTLY or BL. Below is a list of the files that were extracted.
abl
bl1
bl2
bl31
gsa
ldfw
partition_0
partition_1
partition_2
partition_3
pbl
tzsw
ufs
ufsfwupdate

jac0b said:
I extracted the bootloader but I don't see ELR_EL3, LASTLY or BL. Below is a list of the files that were extracted.
abl
bl1
bl2
bl31
gsa
ldfw
partition_0
partition_1
partition_2
partition_3
pbl
tzsw
ufs
ufsfwupdate
Click to expand...
Click to collapse
Lastly is BL1 again, EL3 and BL31 is the same, BL is PBL (Short for primary BL)

I can't make the flashing work with the multidownloader
[COM3]Write thread Start##################
[COM3]Write Fail
[COM3]Write thread Exit##################
I'm using a Win7 32bit VM in VirtualBox

Did anyone actually recover a Pixel 6/pro device using this method?? I'm in the same position right now a serial interface with vendor ID bla bla.... cant go into bootloader nothing just dead device.