Related
Hi everybody!
You might have already seen the flagship Galaxy devices (S, S2, S3) getting support for various new tools. One of these is Heimdall. It is an Open-Source Cross-Platform Flashing Suite originally meant to run on the Galaxy S, but thanks to its popularity, the S2, S3 and other devices also got the support. Literally speaking, it is the Linux and OS X alternative of Odin (It supports Windows as well.). (Read more about Heimdall here.)
Since our device is a variant to the SGS2, the download mode protocol of the two devices are the same. This enables us to use this tool with our device so we don't have to stick with Windows if we want to reflash a stock rom or install a recovery via download mode.
I have compiled the latest version (1.4 RC1) for Linux if you want to try it out. I'm running a 64-bit Ubuntu 12.10. The tool might work on other distributions, but not on 32-bit systems! (There are precompiled 32-bit versions on the website of the author.)
So what do you need to get it running?
Download my precompiled binary (http://www.mediafire.com/?85nny8d1mpea5hp) and extract it somewhere. Then install libusb-1.0 which is a prerequisite of running the tool. Finally, give the Heimdall executable execute rights and make sure you run it as root.
First steps to do for making it sure that the tool works and communicates with your device:
Put your device into download mode by holding down Volume down, Home and Power keys.
Connect your USB cable.
Execute: 'heimdall detect' (This will show if the phone cannot be detected.)
Execute: 'heimdall download-pit --output SGR.pit' (This will download the PIT (Partition Information Table) file of the device.)
Execute: 'heimdall print-pit --file SGR.pit' (This will give you detailed information about the partition structure of the device and this information can be used to identify partitions which you will flash to.)
The three most important information shown by the PIT file are 'Identifier', 'Partition Name' and 'Flash Filename'. For example if you want to flash a recovery image, you will look for 'recovery.img' as 'Flash Filename'. You can find that the corresponding 'Identifier' is '14' and 'Partition Name' is 'SOS' for our device. You can flash your recovery.img with one of the following commands:
Code:
heimdall flash --[COLOR="Red"]SOS[/COLOR] /path/to/recovery.img
Code:
heimdall flash --[COLOR="Red"]14[/COLOR] /path/to/recovery.img
Notice the 'Partition Name' and 'Identifier' values highlighted in red.
This was just an example scenario. You can flash full factory images, repartition the device, change the bootloader, or dump a whole partition. There are many opportunities. If you are interested in using this tool, don't neglect taking time for reading about it first as it can seriously brick your device (Even though APX mode gives an enormous help in recovering the device.). I don't recommend that you use this tool for those not having much experience in what they do. However, this tool can help a lot if you use Linux and don't want to reboot to/use Windows if you want to return to a stock rom.
Every custom modification to devices have risks. Use this at your own risk!
Have fun and enjoy!
wow... you are great buddy!!!!
Sent from my GT-I9103 using xda app-developers app
Are the pre-compiled 32-bit versions compatible with our device? If not, can u compile a 32-bit version for our device?
Thnx!
The-Droidster said:
Are the pre-compiled 32-bit versions compatible with our device? If not, can u compile a 32-bit version for our device?
Thnx!
Click to expand...
Click to collapse
It should be. The website says that 1.3.2 has some issues with certain devices, it also recommends 1.3.1.
Sent from my GT-I9103
trying to install heimdall on my macbook air 64bit os 10.7.5 but getting this error 'heimdal frontend cannot be opened because of a problem check with the developer to make sure heimdall-frontend works with this version of macos.'
and for boot.img its --LNX
Envoyé depuis mon GT-I9103
Thanks
Envoyé depuis mon GT-I8190
Adam77Root said:
Hi everybody!
You might have already seen the flagship Galaxy devices (S, S2, S3) getting support for various new tools. One of these is Heimdall. It is an Open-Source Cross-Platform Flashing Suite originally meant to run on the Galaxy S, but thanks to its popularity, the S2, S3 and other devices also got the support. Literally speaking, it is the Linux and OS X alternative of Odin (It supports Windows as well.). (Read more about Heimdall here.)
Since our device is a variant to the SGS2, the download mode protocol of the two devices are the same. This enables us to use this tool with our device so we don't have to stick with Windows if we want to reflash a stock rom or install a recovery via download mode.
I have compiled the latest version (1.4 RC1) for Linux if you want to try it out. I'm running a 64-bit Ubuntu 12.10. The tool might work on other distributions, but not on 32-bit systems! (There are precompiled 32-bit versions on the website of the author.)
So what do you need to get it running?
Download my precompiled binary (http://www.mediafire.com/?85nny8d1mpea5hp) and extract it somewhere. Then install libusb-1.0 which is a prerequisite of running the tool. Finally, give the Heimdall executable execute rights and make sure you run it as root.
First steps to do for making it sure that the tool works and communicates with your device:
Put your device into download mode by holding down Volume down, Home and Power keys.
Connect your USB cable.
Execute: 'heimdall detect' (This will show if the phone cannot be detected.)
Execute: 'heimdall download-pit --output SGR.pit' (This will download the PIT (Partition Information Table) file of the device.)
Execute: 'heimdall print-pit --file SGR.pit' (This will give you detailed information about the partition structure of the device and this information can be used to identify partitions which you will flash to.)
The three most important information shown by the PIT file are 'Identifier', 'Partition Name' and 'Flash Filename'. For example if you want to flash a recovery image, you will look for 'recovery.img' as 'Flash Filename'. You can find that the corresponding 'Identifier' is '14' and 'Partition Name' is 'SOS' for our device. You can flash your recovery.img with one of the following commands:
Code:
heimdall flash --[COLOR="Red"]SOS[/COLOR] /path/to/recovery.img
Code:
heimdall flash --[COLOR="Red"]14[/COLOR] /path/to/recovery.img
Notice the 'Partition Name' and 'Identifier' values highlighted in red.
This was just an example scenario. You can flash full factory images, repartition the device, change the bootloader, or dump a whole partition. There are many opportunities. If you are interested in using this tool, don't neglect taking time for reading about it first as it can seriously brick your device (Even though APX mode gives an enormous help in recovering the device.). I don't recommend that you use this tool for those not having much experience in what they do. However, this tool can help a lot if you use Linux and don't want to reboot to/use Windows if you want to return to a stock rom.
Every custom modification to devices have risks. Use this at your own risk!
Have fun and enjoy!
Click to expand...
Click to collapse
Hello and thank you.
I always get:
libusb error: 0
When downloading or printing.
any Ideas, please?
Fintanusa said:
Hello and thank you.
I always get:
libusb error: 0
When downloading or printing.
any Ideas, please?
Click to expand...
Click to collapse
Did you run it as root?
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
Did you run it as root?
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I will try that in the morning. Thank you.
Fintanusa said:
I will try that in the morning. Thank you.
Click to expand...
Click to collapse
Ok. Did that. revieved this error:
~$ sudo heimdall-frontend
[sudo] password for fintan3:
Error: "/var/tmp/kdecache-fintan3" is owned by uid 1000 instead of uid 0.
"/org/freedesktop/UDisks2/drives/SAMSUNG_HM320HJ_S2AUJDBB501625" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/hp______DVD_RAM_UJ8B1_SKB2426348" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/SAMSUNG_HM320HJ_S2AUJDBB501625" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/SAMSUNG_HM320HJ_S2AUJDBB501625" : property "Device" does not exist
Error: "/tmp/ksocket-fintan3" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-fintan3" is owned by uid 1000 instead of uid 0.
Click to expand...
Click to collapse
Got my .pit file though. Thnaks. I think I will dig a bit deeper before flashing anything. Cheers
I do not know how to execute it at all. What am I supposed to do? Do I just go into terminal and type sudo heimdall-frontend? That does not do anything. I extracted the executable, but I have no idea as how to run it. I have Linux Mint Petra 16 Cinnamon.
Adam77Root said:
Hi everybody!
You might have already seen the flagship Galaxy devices (S, S2, S3) getting support for various new tools. One of these is Heimdall.
----
Every custom modification to devices have risks. Use this at your own risk!
Have fun and enjoy!
Click to expand...
Click to collapse
Hey, any new pre compiled version available to share? Thanks! :good:
Hello! Yesterday I was putting a custom recovery on my LG p500, and as I am a noob in phones and everything else I fcked up something, and now i have the ''fastboot mode started'' screen. Now, on this http://www.androidpure.com/unbrick-lg-p500-stuck-at-fastboot-mode-due-to-bad-recovery-flash/ page, i have downloaded all the things listed there.
Now, my computer recognizes the phone, it doesn't open the ''removable disk F'' as it has always, but it says it is recognized.
WHen i downloaded Android SDK, on the page they say I should have a directory on disk C, but I DONT KNOW HOW TO INSTALL ANDROID SDK!! When i click on SDK manager it just opens a window similiar to cmd prompt, and then the window close after some seconds.. Please help me!!
Also, on that link there is the cmd program open and he says what to write to unbrick it, but I don't understand anything about it!! Please someone help me I am mad!!!
Instead of messing with the entire Android SDK, which isn't needed BTW, why not use Android Flash Recovery to install another recovery? Link for Android Flash Recovery ( AFR ) is in my signature. It's just a simple UI for the fastboot executable from the Android SDK. No command windows to deal with and nothing to type. Point and click...
As per you problem with the SDK, Android can't find your Java installation. Did you install Java 6 or 7 SDK as well?
shinobisoft said:
Instead of messing with the entire Android SDK, which isn't needed BTW, why not use Android Flash Recovery to install another recovery? Link for Android Flash Recovery ( AFR ) is in my signature. It's just a simple UI for the fastboot executable from the Android SDK. No command windows to deal with and nothing to type. Point and click...
As per you problem with the SDK, Android can't find your Java installation. Did you install Java 6 or 7 SDK as well?
Click to expand...
Click to collapse
I got rid of the problem, but if the problem gets back i will use your link! thanks!
Kk connect USB goto sdk and find fastboot binary use cmd. And do fastboot flash recovery /path to SD/
Sent from my LG-P500 using xda app-developers app
[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux
Ciao xda users, I'm here to introduce a new tool of mine, MiUnlockTool.
MiUnlockTool is an unofficial tool used to unlock bootloader on Xiaomi devices. This tool is copied from the original windows MiFlashUnlock tool and works the same way. The main feature of this tool is compatibility with linux and mac operating system (and windows too).
If you want more information about the tool and the story behind you can read below, if you just want the download link, here it is:
DOWNLOAD LINK
Requirements: java (javafx for gui if not included in your jdk/jre)
Usage:
- Download and extract the zip file
- If you don't have it, install java
- On windows:
-- open MiFlashUnlock.bat for graphical interface or:
-- open a cmd windows and cd into extracted dir and use "MiUnlockTool.bat username password" command for command-line usage
- On linux:
-- open a terminal window and cd into extracted dir and use "sudo ./MiUnlockTool.sh" command for gui interface or "sudo ./MiUnlockTool.sh username password" for command-line
- On mac:
-- open (double click) MiFlashUnlock.command for graphical interface or
-- open a terminal window and cd into extracted dir and use "./MiFlashUnlock.command username password" for command-line
- Attach your locked device in fastboot mode.
- If you are using gui just follow what you see on your screen
- If you are using command line version remember that there is no confirmation request before unlock and no check if the bootloader is already unlocked.
Possible errors:
- If you get a permission related error on linux or mac when launching the tool, open a terminal and cd into extracted dir and use "chmod 777 MiUnlockTool.sh" (or MiUnlockTool.command on mac) to set the executable permission.
- If your device isn't recognized:
-- On windows: install adb drivers
-- On linux/mac trying launching the tool with sudo (sudo ./MiUnlockTool.sh on linux or sudo ./MiUnlockTool.command on mac)
- Other problems launching the tool: try running "java -jar bin/MiUnlockTool.jar" command
- If you get some errors with javafx class not found stuff when you try to launch the gui, then you are missing javafx library. See openjfx package on linux.
- Any other problem: provide feedback in the comments.
Additional info: original MiFlashUnlock tool is just a bridge between fastboot, you (and your account login credentials) and xiaomi server: the tool gets device info from the device and send them to the server together with the account login token, the server checks wherever you satisfy all their requirements (account authorized, account associated with device in developer settings etc) and if everything is okay the server reply with the unlock key for your device instance (every time you reboot your phone you need a new key). Then the tool send the key to the device with a custom build of fastboot and if the key is right then the device is unlocked, else it reboots. After I discovered all the process behind the original unlock tool (and all the security encryption techniques) I decided to replicate it with a java (cross-platform) tool which embeds a custom fastboot version and replicates what the original tool does. That's a simple explaination of how my tool works (obviously it's more complicated than that).
This tool requires all of what is required by the original tool (an authorized xiaomi account binded to the device through developer options for three days if I remember correctly).
FAQs:
- Is this tool safe to use?
Yes, the main part is communication between tool and server, a safe thing. Also the unlock procedure itself is safe: or the key is correct or it is not. In both cases the device will not be damage.
- How did you find out how to replicate the original tool?
Thank you for your question. It's been a bit difficult since the original tool has been obfuscated and virtualized (protected against reverse engeneering) with a powerful protector: VMProtect. I've spent some time to reverse it (and custom fastboot too) and I finally did it. I will not explain in details how I did it.
- Is this tool more powerful than the original on? why should I use it on Windows?
Absolutely not, my tool is worst than the original one (it will have more bugs and on windows it doesn't manage drivers for example), that's why you should NOT use it on Windows. I made it work even with Windows because it was very simple to do. You can use it one Windows just to test it if you like, but I recommend using the better original tool MiFlashUnlock.
- Wow, you did a tool already done by developers paid by xiaomi, who is paying for the effort you put into this?
No one, I try to help people and getting appreciation for my work is a bit of a reward to me, but if you want to show your gratitude even more and support me as a developer you can make a donation, I will appreciate that even more (donation link below)
- I have to put my xiaomi account credentials, should I trust this?
I'm the developer of XiaoMiTool, I hope that a little bit of my reputation together with the hopefully good early feedback of reckless users on this tool is enough. If you are more a geek you can track the traffic and see that the only server connected are xiaomi and miui.
- I wanted too see the source of this tool but I see it is a bit obfuscated, why?
Xiaomi clearly doesn't wanted people to see how MiFlashUnlock works (since they obfuscated it a lot), I don't want to disrespect xiaomi decision by releasing the source plain, so I decided to obfuscated it a bit just to make it a bit harder to see (even if my tool is 100 times easier to reverse than the original)
- Can I share this tool?
Of course yes, but I would like you to share it using the xiaomitool.com link (not mega.nz one) so that if I release an update new people will get that and not the old version (there is no tool update enginge built in).
- You're english is not wonderful...
I know, hopefully it is understandable enough
Feedback.
I love feedback, feedback is the best you can do to help me improving this tool. I have not time to answer everybody's questions but I generally read feedback and do my best to make the tool work. If the tool worked or if the tool didn't worked you can write it in the comments, adding additional information like what error you get, what screen you see when the tool get stuck or even what you tried to solve the problem are precious to me. I have not all of xiaomi devices, I fully ested my tool only with two devices (a redmi 4x and a mi note 2) and only on two operating systems (linux and windows), so any new combination could lead to new errors or problems. Please include also your operating system when leaving feedback. Sometimes there are problems on gui which are not on command-line version, so if the tools fails launching or when using gui I suggest trying the command-line version.
Donation: free software is great from users prospective, but developers who spend hours of their time and don't get money for it are more unhappy to develop further free tools, so if you liked the tools and it saved you from the need to do 5000 kilometers to get a windows pc, or from the need to download a virtual machine image with your 32kB internet connection, you can show your gratitude by offering me a tasty, cold beer by clicking the link below
DONATION LINK
Download: you missed the download link at the top? Here it is again:
DOWNLOAD LINK
Fully obfuscated tool. Maybe bloatware or password hijacker
Problems with mi unlock on ubuntu system
Dear,
I tried to run this miunlock on my linux pc and it did not work. I installed the javafx using "sudo apt install openjfx" . After I ran "sudo ./*.sh". The program open, but when I put my email and password, it does not connect with the xiaomi server. I tried to access using facebook login and I have the same problem. How can I solve this problem? Do you have any idea?
Thanks
Danillo
The program does not find the phone connected. But "sudo fastboot reboot" work
---------- Post added at 12:03 PM ---------- Previous post was at 11:51 AM ----------
dpvalverde said:
Dear,
I tried to run this miunlock on my linux pc and it did not work. I installed the javafx using "sudo apt install openjfx" . After I ran "sudo ./*.sh". The program open, but when I put my email and password, it does not connect with the xiaomi server. I tried to access using facebook login and I have the same problem. How can I solve this problem? Do you have any idea?
Thanks
Danillo
Click to expand...
Click to collapse
Reinstall certs
disconnects phone on checking bootloader status with an error message on top left corner of phone "press any key to shutdown"
and stays stuck after reconnecting in fastboot mode when reading device info.
How to install it on manjaro arch Linux. did u keep it in AUR.?
Status : Success unlock bootloader
Device : Redmi 4X
Waiting Time : 72hours
Thx for the tool . love3 ??????
worked a treat.
had been struggling to use the mi tool for windows and my device was not being detected.
this took me barely a minute to unlock.
Waiting for a fastboot device...
Well, the communication with the 'net seems to work as intended but that is where it stops:
Code:
[18:01:15][INFO ] Starting login procedure
[18:01:24][INFO ] Login procedure succeeded
[18:01:25][INFO ] Checking account unlock permission
[18:01:27][INFO ] Unlock permission confirmed
[18:01:27][INFO ] Waiting for a fastboot device
Using the fastboot command line works for the same user account so this won't be solved by running the tool as root. The device reports itself as 18d1:d00d Google Inc. and shows up clearly when using the fastboot command line tool:
Code:
$ fastboot devices
deadbeef fastboot
(no, my device ID is not deadbeef)
Tried OpenJDK 10 and 9, Oracle JRE 8, no difference.
Digging deeper using strace shows the problem: the 'special' fastboot command you include (in bin/MiUnlockTool_res) is a 64-bit executable while I'm running the tool on a 32-bit machine. Substituting the provided tool for a link to the version already present on this machine makes the command progress to the error:
Code:
$ java -jar bin/MiUnlockTool.jar '[email protected]' 'mysupersecretpassword'
[18:19:25][INFO ] Starting login procedure
[18:19:36][INFO ] Login procedure succeeded
[18:19:36][INFO ] Checking account unlock permission
[18:19:39][INFO ] Unlock permission confirmed
[18:19:39][INFO ] Waiting for a fastboot device
[18:19:39][INFO ] Device connected: deadbeef
[18:19:39][INFO ] Obtaining device info...
[18:19:40][INFO ] Device info obtained
[18:19:40][INFO ] Checking if unlock will erase data and server message
[18:19:42][INFO ] Unlock procedure will erase userdata
[18:19:42][INFO ] Server message: An unlocked device is an easy target for malware which may damage your device or cause financial loss.
[18:19:42][INFO ] Querying unlock server for unlock key
[18:19:48][ERROR ] Unlock request replied with error code 20036
[18:19:48][ERROR ] Error meaning: After %d hours of trying to unlock the device
I guess I have to wait, how long I do not know as this is not shown in either mode (command line or GUI).
Anyway, you might want to add a 32-bit fastboot command or just tell users to install a native version and use that.
@YetAnotherForumUser
I see the same error message when I tried to unlock MI 8 (global version bought yesterday in official Xiaomi store in Poland). I tried official Xiaomi tools on Windows 10, but without any success (verify failed at 50%).
I'm using it on a Linux laptop, I get "buffer overflow detected" after "starting final unlock procedure" and then it fails
i have this 2 errors on linux tring to unlocking my redmi note 5 [20:59:38][ERROR ] Unlock request replied with error code 20036
[20:59:38][ERROR ] Error meaning: After %d hours of trying to unlock the device
After waiting 360 hours I was able to unlock my Mi 8 with this tool on my Ubuntu! With official MiFlashUnlock tool I wasn't able to unlock this device on Windows 10. Thanks a lot!
YetAnotherForumUser said:
Code:
...
[18:19:48][ERROR ] Unlock request replied with error code 20036
[18:19:48][ERROR ] Error meaning: After %d hours of trying to unlock the device
I guess I have to wait, how long I do not know as this is not shown in either mode (command line or GUI).
Click to expand...
Click to collapse
After about 13 days - I only tried twice in between - the thing is now unlocked. I needed to run the tool on a 64-bit machine as the 32-bit fastboot crashed (with a message in the lines of "* buffer overflow detected *"), possibly due to the longish argument used in the unlocking procedure.
YetAnotherForumUser said:
After about 13 days - I only tried twice in between - the thing is now unlocked. I needed to run the tool on a 64-bit machine as the 32-bit fastboot crashed (with a message in the lines of "* buffer overflow detected *"), possibly due to the longish argument used in the unlocking procedure.
Click to expand...
Click to collapse
I also used 64-bit OS -> Ubuntu 18.04 x64. It would be nice to see amount hours instead of %d, however it's just a minor bug. This tool is the best choice for Linux, MacOS and event Windows 10 users.
Hey guys,
Although I've unlocked & rooted other Android's in the past, this is my first time with a Xiaomi device. I've tried running the tool, and appear to get the "Error meaning: After %d hours of trying to unlock the device" error. Am I right in thinking this is just a bug in terms of the hours displayed, and that I will just need to wait the 15 or so days before I can unlock the device? At what point does that 15 days begin?
Also, once unlocked, what is the best way to flash a ROM? ADB via Terminal?
Looking to flash the Global MIUI over the Chinese one I currrently have.
Thanks!
Help. Can not connect to my phone in fastboot when using this tool. But the MiUnlock is still connected
huynhkhoa said:
Help. Can not connect to my phone in fastboot when using this tool. But the MiUnlock is still connected
Click to expand...
Click to collapse
Windows or linux ?
naik2902 said:
Windows or linux ?
Click to expand...
Click to collapse
window bro, please help me :crying:
huynhkhoa said:
window bro, please help me :crying:
Click to expand...
Click to collapse
Why r u not using original miunlock tool for windows ?
Did u enable oem unlock, usb debugging?
Installed fastboot drivers
Use fastboot devices command to check if u r device connected to pc.
Did u bind ur account to miunlock status in developer option?
I need google pay, looks like it won't run on onlocked bootloader, has anyone experience relocking bootloader
yerman said:
I need google pay, looks like it won't run on onlocked bootloader, has anyone experience relocking bootloader
Click to expand...
Click to collapse
I have bought 2 devices as an early bird backer, one of them had issues (battery problems), so I had to relock it before sending it back to the official store. From past experience with MIUI, I reflashed my original MIUI version (was 12.0.2.0 at that time which came from factory) without locking first. Rebooted to see if it works, then flashed the same version again with the flash_all_lock script and everything went ok.
Unlocking again ofc would be through Mi unlock tool. Just don't do it on a custom Rom.
Slim K said:
I have bought 2 devices as an early bird backer, one of them had issues (battery problems), so I had to relock it before sending it back to the official store. From past experience with MIUI, I reflashed my original MIUI version (was 12.0.2.0 at that time which came from factory) without locking first. Rebooted to see if it works, then flashed the same version again with the flash_all_lock script and everything went ok.
Unlocking again ofc would be through Mi unlock tool. Just don't do it on a custom Rom.
Click to expand...
Click to collapse
Good news, did you use mi flash tool, any more info on flash_all_lock script and how to use it.
thanks for the quick reply
yerman said:
Good news, did you use mi flash tool, any more info on flash_all_lock script and how to use it.
thanks for the quick reply
Click to expand...
Click to collapse
I didn't use flash tool. The flash_all script/s can be found inside the .tgz fastboot firmware as a .bat file for windows (CMD) and/or .sh for linux (terminal). There is no real difference between the tool and script, however the tool is easier to work with for beginners, since it is a GUI.
There are three types of scripts:
flash_all. Flashes w/o locking, formats data partition
flash_all_except_data_storage. Flashes w/o locking, doesn't format data partition.
flash_all_lock flashes with locking, formats data as well.
Instructions for using scripts:
as admin run terminal or cmd inside the folder where the script and the rest of the firmware files are.
fastboot devices to make sure device is connected.
Then type fastboot followed by dragging and droping the script to terminal/cmd, then Enter.
I prefer terminal over flash tool for the info I get during installation (very detailed if something goes wrong).
Slim K said:
I didn't use flash tool. The flash_all script/s can be found inside the .tar fastboot firmware as a .bat file for windows (CMD) and/or .sh for linux (terminal). There is no real difference between the tool and script, however the tool is easier to work with for beginners, since it is a GUI.
There are three types of scripts:
flash_all. Flashes w/o locking, formats data partition
flash_all_except_data_storage. Flashes w/o locking, doesn't format data partition.
flash_all_lock flashes with locking, formats data as well.
Instructions for using scripts:
as admin run terminal or cmd inside the folder where the script and the rest of the firmware files are.
fastboot devices to make sure device is connected.
Then type fastboot followed by dragging and droping the script to terminal/cmd, then Enter.
I prefer terminal over flash tool for the info I get during installation (very detailed if something goes wrong).
Click to expand...
Click to collapse
thanks again for the help, appreciated
Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-)
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test my luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
turistu said:
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test by luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
Click to expand...
Click to collapse
Thank You!
It realy works!
Thanks,
Worked for me with Android 13/RealMe UI 4.0.
Now to magisk...
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Is there a way to use this script on realme 9 pro 5g eu rmx3472?
Edit: It works perfectly and i was also able to change my region to ru.
mister_slowhand said:
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Click to expand...
Click to collapse
Try https://rms01.realme.net/sw/RMX3472GDPR_NN.X.NN_YYYYMMDDHHMM0000.zip,
(replacing the N, Y, etc with the actual version of the firmware).
Also the variants with .7z instead of .zip.
hatbo said:
Thank You!
It realy works!
Click to expand...
Click to collapse
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
RobertoSt25 said:
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
Click to expand...
Click to collapse
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
I love you Turistu, thank you for the guide!
I've had the problem, that the device wasn't getting recognized in fastboot mode.
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, settings -> windows update -> advanced options -> reset options -> advanced restart. Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
I have attached the Oneplus drivers i've used for fastboot and a patched boot.img with magisk 26.1 from RMX3311_11.C.10_EU_202303171905.
You did a great job! Thank you!
PS. Dacă ești român, ești foarte tare frate!
turistu said:
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
Click to expand...
Click to collapse
Hello there,
I tried your method, I did everything step by step and it actually worked and it did unlock the bootloader.
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Now I really do not know what to do -.-
Any advice would help.
Thanks Rob
RobertoSt25 said:
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Click to expand...
Click to collapse
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
turistu said:
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
Click to expand...
Click to collapse
yes top of the screeen is START green, but when I pressed power just keeps rebooting into fastboot.
RMX 3474 REALME 9 5G
Thanks