Related
Hello,
I cannot managed to use Flashtool on my W7 64bit, cause all drivers I have found are refused
I followed for instance this, but it says there are no 64 bit driver !?
( Hopefully I got an old XP PC )
Can someone help me on that ?
Cheers.
ChefChaudart said:
I followed for instance this, but it says there are no 64 bit driver !?
Click to expand...
Click to collapse
Why on Earth, especially when you're a member of xda, would you look anywhere else.
lollylost100 said:
Quick tutorial for unlocking new Xperia devices. Although there is one on the SE developer website, this thread can be used for users to discuss their problems during unlocking etc.
Warning! This procedure will wipe the /data partition of your phone.
1. Download:
-fastboot package: http://www.multiupload.com/BMJ24IL6XY
-32/64bit drivers: http://www.multiupload.com/0XZV1LXRVA
2. Go to: http://unlockbootloader.sonyericsson.com/instructions
3. At the bottom click 'Continue' and enter your IMEI (type *#06# to find out), name and email address
4. You should now receive your unique unlock key
5. Extract fastboot.rar and open fastboot folder
6. Hold SHIFT and right click on the background of the folder
7. Select 'Open command window here'
8. Connect your phone in fastboot mode (turn phone off, hold menu button and plug in USB Cable)
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
10. If a value is returned, it means the phone is correctly connected
11. Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key provided in step 4.
12. You're device should now be bootloader unlocked
If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
Click to expand...
Click to collapse
Very funny
I know this procedure, as I mentioned it myself earlier to someone over here !
If I post a question here, it´s because i did not work for me
( -> Point 1 & 2 )
You said it said there was no x64 driver, I quoted a post that provides one. The problem isn't Windows 7 x64. I assume you've uninstalled the device and started from scratch?
ChefChaudart said:
Very funny
I know this procedure, as I mentioned it myself earlier to someone over here !
If I post a question here, it´s because i did not work for me
( -> Point 1 & 2 )
Click to expand...
Click to collapse
Can you give more details about what didn't work for you? please be specific and give maximum details so we can help you more...
I'm on W7 x64 and it worked for me without any problem at all so i guess it's not a 64 bit driver problem. if you insist i can give you the drivers from my OS, maybe your's corrupt or something.
cheers
Oooh I get an idea
I unchecked "Show only compatible materials", then I was able to see want I wanted and installed it.
I think now it´s ok, but in fact, I have nothing to flash
what does it mean when it says "it will delete the partition"??
Xperia ray fast boot driver
XperienceD said:
Why on Earth, especially when you're a member of xda, would you look anywhere else.
Click to expand...
Click to collapse
The links that you have given to download the drivers don't work they either force you to download ilivid.exe or another zoom downloader. I have tried downloading and installing both but both don't give me the drivers. Something is wrong can you please point me to a decent URL for downloading the 64bit drivers for Windows 7.
ikshf143 said:
The links that you have given to download the drivers don't work they either force you to download ilivid.exe or another zoom downloader. I have tried downloading and installing both but both don't give me the drivers. Something is wrong can you please point me to a decent URL for downloading the 64bit drivers for Windows 7.
Click to expand...
Click to collapse
I installed Flashtool, from Flashtool folder I installed drivers for fastboot and my device and that's all I needed to do.
Not helping much
It's all very well getting all snotty and telling people to use the search, but PLEASE keep your links up to date.
I have a problem with my Arc LT15i and am trying to unlock the boot loader. I have x64 Windows 8 and cannot get Windows to see the phone. ALL of the links I have found on the internet, here, at Sony Ericsson and any other place I have found are ALL dead links or try to foist some crapware on you.
I get the blue light on the phone indicating it is trying to enter Fastboot, but Windows will not see it, it appears as S1 Boot Fastboot in Device Manager, but no driver that I've found will work.
Flashtool may be very good, but it only works if you have an unlocked boot loader (according to Sony Ericsson).
If anyone has a Windows 8 64bit driver I'd really appreciate it if they'd pass on where to get it.
TimKing.ie said:
It's all very well getting all snotty and telling people to use the search, but PLEASE keep your links up to date.
Click to expand...
Click to collapse
XperienceD said:
References:
[TOOL] Fastboot and ADB helper v1.0
[4Noobs] Flashing a Custom Rom & Kernel Using Fastboot
[How-To] Install custom kernel/rom on 2011 xperia device
[HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
How to Flash boot.img / kernel.elf / kernel.sin using flashtool
[TOOL][FASTBOOT] QuikIMG - A frontend for fastboot [0.2 beta]
[Tutorial] How to install CyanogenMod 9.0 on xperia 2011 devices
[TOOL] RecoverX - Recovery installer for almost all android devices
[RECOVERY] TWRP 2.3 for all your Xperias. (downloads + DIY howto)
Fastboot & Flashboot ADB Driver installation on Windows 8 Guide for Sony Xperia Users
How to Install CyanogenMod on your Xperia (bootloader unlock, fastboot, Google Apps, etc.)
Click to expand...
Click to collapse
TimKing.ie said:
If anyone has a Windows 8 64bit driver I'd really appreciate it if they'd pass on where to get it.
Click to expand...
Click to collapse
See above for why you should read the stickys, and if you've not found it by searching, then god knows what you were searching for. - fastboot windows 8 xperia arc
links are not working for drivers
could you please send me the links for s1boot fastboot drivers for xperia mini st15i....
thnx in advance
sumitrohilla1991 said:
could you please send me the links for s1boot fastboot drivers for xperia mini st15i....
thnx in advance
Click to expand...
Click to collapse
Install Flashtool, then look in Flashtool folder (by default C:\Flashtool\drivers) and start and Flashtool-drivers.exe. Choose fastboot drivers.
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
sumitrohilla1991 said:
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
Click to expand...
Click to collapse
Did you run it as administrator?
sumitrohilla1991 said:
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
Click to expand...
Click to collapse
Here they are - mediafire.com/download/rg75cze0aa8yzm7/Adb+%26+Flashtool-drivers.exe
Found here - xperiaray.wordpress.com/2012/10/27/flashing-tool/
solved
www,omniuslogs,net/download,php
change the "," to "." follow th steps and install omnius v3.0.0.1
gd luck
new members cant post links thts y i used th commas
sumitrohilla1991 said:
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
Click to expand...
Click to collapse
I have the same issue, running as admin but drivers won't install!
Hi all, I was wondering if there is a safe way to de-bloat stock ROM? Can I remove useless system apps and can I remove ads somehow from Stock MIUI?
litetaker said:
Hi all, I was wondering if there is a safe way to de-bloat stock ROM? Can I remove useless system apps and can I remove ads somehow from Stock MIUI?
Click to expand...
Click to collapse
Yes you can! There's a really good tool for Windows called "Xiaomi ADB Fastboot Tools"
This tool requires Java installed on your computer. Regular Java didn't work for me, so I link you this version of Java:
Latest release | AdoptOpenJDK
AdoptOpenJDK provides prebuilt OpenJDK binaries from a fully open source set of build scripts and infrastructure. Supported platforms include Linux, macOS, Windows, ARM, Solaris, and AIX.
adoptopenjdk.net
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
dreamytom said:
Yes you can! There's a really good tool for Windows called "Xiaomi ADB Fastboot Tools"
This tool requires Java installed on your computer. Regular Java didn't work for me, so I link you this version of Java:
Latest release | AdoptOpenJDK
AdoptOpenJDK provides prebuilt OpenJDK binaries from a fully open source set of build scripts and infrastructure. Supported platforms include Linux, macOS, Windows, ARM, Solaris, and AIX.
adoptopenjdk.net
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
Click to expand...
Click to collapse
Thanks! Can I still install OTA updates after I debloat stock ROM and with Magisk installed? Or do I need to re-install all the debloated apps and uninstall Magisk everytime I want to do an OTA update?
litetaker said:
Thanks! Can I still install OTA updates after I debloat stock ROM and with Magisk installed? Or do I need to re-install all the debloated apps and uninstall Magisk everytime I want to do an OTA update?
Click to expand...
Click to collapse
After debloating yes, that's completely ok. OTA's work, and you don't have to uninstall/disable apps again after update. It's nice.
But with Magisk you're implying that you unlocked your bootloader and rooted your ROM, right?
When you do that, I think you don't get OTA's anymore.. even on Stock MIUI ROM. It would just show "Up-to-date" and not give you any updates. Atleast that was the case with my Samsung phone! I think the bootloader needs to be locked?
If youre rooted i'd install Titanium backup and uninstall useless apps.
kryptonify said:
If youre rooted i'd install Titanium backup and uninstall useless apps.
Click to expand...
Click to collapse
Titanium Backup is outdated, and some of its features don't work properly anymore. Check Play Store Reviews
dreamytom said:
Titanium Backup is very outdated, and some of its features don't work properly anymore. Check Play Store Reviews
Click to expand...
Click to collapse
Some of its features yes, but the uninstall feature works fine, I just uninstalled Chrome and chrome gone
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
please note that I will make a proper procedure in this post shortly. but in the mean time, you WILL need linux to be able to root your phone, as windows process does not work.,
while using linux, need to change the commands to be python3 where it says python.
just abit snowed under at the moment, but will be done inthe next 48 hours
Hi, to complete what our friend previously said, we are at least three people to have used this tool and made it work. My phone REALME C21 is unlocked and rooted.
I used Windows, albeit it probably wasn't perfectly done.
The solution is to use the mtkclient tool produced on this github and follow each step of the guide on the github, under "Usage / Root the phone (tested with android 9-12)".
You must absolutely use the magisk App given on this github, the official one won't work, this is what prevented me previously to succeed. This magisk app has been patched for mediatek/realme phones.
Do not omit dumping steps, as it is your only way out if it doesn't work.
Also, for obscure reasons, I was unable to chain commands ; tool wouldn't work this way...
So each time I did and succeeded in doing one "mtk" command on the phone, I unplugged it, launched the next command, pushed vol up and vol down, and replugged it.
Maybe I missed something. (note that for the mtk tool to work, phone must be shutdown and then plugged the way I described or that it is described on the guide/tool itself)
Anyway, no guarantee for you here, but hey, it works .
Cherryblue said:
Hi, to complete what our friend previously said, we are at least three people to have used this tool and made it work. My phone REALME C21 is unlocked and rooted.
I used Windows, albeit it probably wasn't perfectly done.
The solution is to use the mtkclient tool produced on this github and follow each step of the guide on the github, under "Usage / Root the phone (tested with android 9-12)".
You must absolutely use the magisk App given on this github, the official one won't work, this is what prevented me previously to succeed. This magisk app has been patched for mediatek/realme phones.
Do not omit dumping steps, as it is your only way out if it doesn't work.
Also, for obscure reasons, I was unable to chain commands ; tool wouldn't work this way...
So each time I did and succeeded in doing one "mtk" command on the phone, I unplugged it, launched the next command, pushed vol up and vol down, and replugged it.
Maybe I missed something. (note that for the mtk tool to work, phone must be shutdown and then plugged the way I described or that it is described on the guide/tool itself)
Anyway, no guarantee for you here, but hey, it works .
Click to expand...
Click to collapse
Congrats
And i wanna point some thinks
Actually using windows for such job is a real pain, i used EndeavourOS.(Based on arch linux)
Magisk app actually not matter if you are on android 10, and actyally @smiley.raver used magisk app from original releases.
Therefore, i already asked differences here;
What is the benefit of pacthed magisk? · bkerler/mtkclient · Discussion #116
I used this tool today and my device was successfully rooted :-) However, I have a question in my mind; What is the differences of magisk app you provided and official magisk app? Why should we use...
github.com
I had not need to replug my phone for each command, but i dont exactly remember how i did, lol.
Does using this method it will erase data / formatting data?
Yes. At least, this is one of the steps in the github guide, and it probably would not work if you don't do it.
A12sma said:
Does using this method it will erase data / formatting data?
Click to expand...
Click to collapse
You should clear data, beacuse it bootloops without clearing data.
Before doing anything you can backup your files from recovery mode, adb can be run as root at recovery mode.
apokogies for not getting a more step by step guirde completed with a series of issues with my mental health..
Bootloader unlock can only be on Android 10 - as soon as you try upgrade to android 11 - fastboot stops working - . I have not yet found a work around for android 11 as of yet - but you can still use the mtkclient tool to flash files like you would fastboot.
do a full phone backup - with python mtk rl out or python mtk rf flash.bin - this will ensure that if you do something wrong, or wipe a partition or bootloop - you can always flash the out directory or the flash.bin file - I am using 2 at the moment - 1 as daily driver - the other i had to restore after screwing around with a few wrong files - but i keep the backup of python mtk r out - and have reflashed and bricked and reflashed it about 15 times in the last 24 hours trying to get fastboot to work with android 11
smiley.raver said:
do a full phone backup - with python mtk rl out or python mtk rf flash.bin - this will ensure that if you do something wrong, or wipe a partition or bootloop - you can always flash the out directory or the flash.bin file - I am using 2 at the moment - 1 as daily driver - the other i had to restore after screwing around with a few wrong files - but i keep the backup of python mtk r out - and have reflashed and bricked and reflashed it about 15 times in the last 24 hours trying to get fastboot to work with android 11
Click to expand...
Click to collapse
I am glad you finally become online after a long time
I have few think to say.
Trying to compile a twrp at same time.
Yeah it's been a rollercoaster of a ride the last few months. Had to put my dog down 2 days before Christmas. So this has been giving me a good distraction .
Found out a fair few things with this phone. Very weird and different to how it operates and upgrades/downgrades.
Been using a mix of sp flash tools, mtkclient and fastboot where applicable.
So what interedting things have happenef while I was away
smiley.raver said:
do a full phone backup - with python mtk rl out or python mtk rf flash.bin - this will ensure that if you do something wrong, or wipe a partition or bootloop - you can always flash the out directory or the flash.bin file - I am using 2 at the moment - 1 as daily driver - the other i had to restore after screwing around with a few wrong files - but i keep the backup of python mtk r out - and have reflashed and bricked and reflashed it about 15 times in the last 24 hours trying to get fastboot to work with android 11
Click to expand...
Click to collapse
Oh also if upgrading to android 11 make sure you have the correct firmware forthe correct region otherwise you get boot loop freezes and all sorts of wonderful $hit
Cherryblue said:
Yes. At least, this is one of the steps in the github guide, and it probably would not work if you don't do it.
Click to expand...
Click to collapse
As with any phone, unlocking bootloader erases all data. This is just android, you are always advised to backup all data prior to preform a bootloader unlock
Cherryblue said:
Hi, to complete what our friend previously said, we are at least three people to have used this tool and made it work. My phone REALME C21 is unlocked and rooted.
I used Windows, albeit it probably wasn't perfectly done.
The solution is to use the mtkclient tool produced on this github and follow each step of the guide on the github, under "Usage / Root the phone (tested with android 9-12)".
You must absolutely use the magisk App given on this github, the official one won't work, this is what prevented me previously to succeed. This magisk app has been patched for mediatek/realme phones.
Do not omit dumping steps, as it is your only way out if it doesn't work.
Also, for obscure reasons, I was unable to chain commands ; tool wouldn't work this way...
So each time I did and succeeded in doing one "mtk" command on the phone, I unplugged it, launched the next command, pushed vol up and vol down, and replugged it.
Maybe I missed something. (note that for the mtk tool to work, phone must be shutdown and then plugged the way I described or that it is described on the guide/tool itself)
Anyway, no guarantee for you here, but hey, it works .
Click to expand...
Click to collapse
Just to clarify, the magical app is not patched as such, it is an alpha branch, which encorporates extra coding/coding that is removed from the normal magisk, and. Can still be used on other phones as well, (it is hard to understand what most changes are as I can not read (assumption Chinese) that magisk alpha is mainly change logged as .
But yes that was one of the issues I faced being that didn't use the magisk alpha app originally.
Under Linux I didn't have to unplug each command. But under windows yes you need to run the command and then plug the phone in under Brom/download mode. You don't have to restart the phone after each command. Just need to unplug and run next command and then plug phone in
smiley.raver said:
Trying to compile a twrp at same time.
Yeah it's been a rollercoaster of a ride the last few months. Had to put my dog down 2 days before Christmas. So this has been giving me a good distraction .
Found out a fair few things with this phone. Very weird and different to how it operates and upgrades/downgrades.
Been using a mix of sp flash tools, mtkclient and fastboot where applicable.
So what interedting things have happenef while I was away
Click to expand...
Click to collapse
We have TWRP, please get in touch with me from telegram.
I had sent you my telegram profile link from privatebmessage
MrMiyamo said:
We have TWRP, please get in touch with me from telegram.
I had sent you my telegram profile link from privatebmessage
Click to expand...
Click to collapse
Ok. Is it working. Because the ones I found were t working and setup for different phone.
Will jump on telegram tonight. Just busy today
smiley.raver said:
Ok. Is it working. Because the ones I found were t working and setup for different phone.
Will jump on telegram tonight. Just busy today
Click to expand...
Click to collapse
We have working twrp for RUI1, but not fully tested.
Booting and decryption works though.
I didn't install the android 11 update on my phone in time,
And I can't find the RUI2 firmware anywhere right now.
(Sofware update center does not show RUI2 update anymore)
So if you have RUI2, we can build twrp for it.
I am looking forward for your message on telegram
I was just wondering on if there's a MSM tool for op9 pro for macOS or any way to use it?
Trying to restore my phone through a virtual machine doesn't work I've tried and I don't seem to be able to bootcamp windows on my MacBook... Thanks for y'all help
There is none for macOS, you have to use BootCamp or a windows machine.
Funk Wizard said:
There is none for macOS, you have to use BootCamp or a windows machine.
Click to expand...
Click to collapse
Thought so.. thank u anyways for your reply
I have a same question, do you find any solutions?
Fomenokd said:
I have a same question, do you find any solutions?
Click to expand...
Click to collapse
I use Linux and I boot a live windows USB (HBPE).
MSM uses Qualcomm emergency download mode, If you feel confident enough i think you could flash with QDL you need to extract the .ops file inside the MSM zip and flash the contents with QDL.
I'm working on this, when I know how to do it I'll post a tutorial.
Eloy68 said:
I use Linux and I boot a live windows USB (HBPE).
MSM uses Qualcomm emergency download mode, If you feel confident enough i think you could flash with QDL you need to extract the .ops file inside the MSM zip and flash the contents with QDL.
I'm working on this, when I know how to do it I'll post a tutorial.
Click to expand...
Click to collapse
Where are you going to get the firehose though? Does the regular OTA have it?
[GUIDE] unbrick and flash Official ROM in EDL on linux
hi, i'm with issues here... the device - xiaomi redmi note 5A (ugg) - is dead. i'm managed for put it in edl mode, just blink the led, and this is what i receive in terminal: $ ./qdl --debug --storage ufs --include...
forum.xda-developers.com
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.