Database Info

[Guide] Root on Linux Mint

Rooting a Xiaomi Mi 4i on Linux Mint 17.1 Rebecca
- This guide might also be relevant for users of Debian and Ubuntu
Disclaimer: I accept no responsibility for any damage you do to your phone, body, life or anything else in the past present or future.
This has been written as I had so much difficulty in getting my Mi 4i rooted. I kept trying to do it in Windows through Virtual Box but kept failing.
1. Enable Developer Options
- On your phone, go to Settings
- About phone
- Keep tapping on the Android version until the message at the bottom says that you are a developer
2. Enable USB debugging
- On your phone, go to Settings
- Additional settings
- Developer options
- USB debugging
3. Install the tools
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
4. Try and see the devices
- Connect the phone to your computer
- Run the following command at the terminal
Code:
adb devices
- It will now say List of devices attached.
- If you see another line with an 8 character identifier such as bf1b6529 then you can skip step 5
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
6. Add your computer to trusted devices on your phone
- Enter the following command on the terminal:
Code:
adb devices
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
7. Check that adb devices is working
- Enter the following command on the terminal:
Code:
adb devices
- Check that the device ID is there (8 characters such as bf1b6529)
- Check that it says device after it
8. Kill adb
- Enter the following command on the terminal
Code:
adb kill-server
9. Now for the fun. You will need sudo access for this stage.
- Download boot.img to your computer.
- At the terminal, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
- At the terminal:
Code:
adb reboot bootloader
- You will now see a screen like the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- At the terminal:
Code:
sudo su
fastboot devices
- You will now see your device ID followed by fastboot
Code:
fastboot boot boot.img
- You will now see something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.022s]
booting...
OKAY [ 0.259s]
finished. total time: 1.281s
10. Restart
- At the terminal enter:
Code:
fastboot reboot
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU

Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

thanks....
finally i can connect my mi4i to my linux desktop

Thank you for your guide. I assume this will work on Ubuntu 14.04 as well.
Question to step no.9: "Download boot.img to your current dir" => Which directory do you mean? The root of the phone or on my laptop? Sorry for being newbie. Many thanks.

rmsinaga said:
Which directory do you mean? The root of the phone or on my laptop?
Click to expand...
Click to collapse
You need to download boot.img to your laptop. I've updated Step 9 with the following:
- Download boot.img to your computer.
- At the command line, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
Click to expand...
Click to collapse

Step one on the path to rooting my m4i was getting adb to work.
kblade29m said:
Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
Click to expand...
Click to collapse
After much googling, much time, and trial and error, I had reached this point. Then I come here and here it is! All made simple.
The next hurdle is that adb devices shows the phone with the word "offline," and that is where...
aembleton said:
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
Click to expand...
Click to collapse
...I find I wasn't even seeing the message because the flip cover was closed. Doh.
This is my second Android phone, and I rooted and installed CM on the previous one, a Defy+. Still feel very much a novice, and approaching the rooting is quite scary. Among my worries...
Does this method change the recovery?
Does this method, with boot.img, install a new rom, or does it root the exisiting one?
Will everything else be reset/wiped? (well, backups anyway. Of course).
Will Xiaomi updates still work and be installable?
I am considering using method 1 from "Root/Unroot V6.5.x W/out Losing Stock Recovery [Simplified]" (new member: cannot make that a link) . Any comments?
It is so nice to see the Linux, and especially mint-specific, advice here. Thank you!
(My first post here: usual forum-novice disclaimers apply )

I have used this method to root my mi4i.
Quick answer:
1. No
2. It only roots the existing ROM
3. No
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
5. Never tried before

rmsinaga said:
I have used this method to root my mi4i.
Quick answer:
... ... ...
Click to expand...
Click to collapse
Great answer! :good:
Thank you very much for attention to every detail. The only thing putting me off going for this straight away is that I am travelling in just over a week, which doesn't give me any margin for making mistakes (if they can be made, I will make them!).
You mentioned having failed to make stuff work in a virtual machine. Did you try Wine? I failed to make the Mi PC manager software run in Wine.

Simple, painless and absolutely effective
aembleton said:
10. Restart[/B]
- At the terminal enter:
Code:
fastboot reboot
Click to expand...
Click to collapse
(response typed from memory)
Code:
# fastboot reboot
<Waiting for Device>
...amd it goes on waiting. Does anybody get any other response on the terminal screen after this?
Anyway, Be Patient! Probably better to make tea or something away from the screen. After several minutes of Fastboot screen on the phone, the process continues as premised...
aembleton said:
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU
Click to expand...
Click to collapse
...and all is well.
After the phone had rebooted, I just ctrl-c-ed the fastboot process and exited from the terminal.

Works wonders, thanks!
Could only find ****ty .exe rooting tools that seemed sketchy and don't have windows installed anymore, so this saved me hours.
My computer could find the phone through adb and got authorized, the phone couldn't find my computer through adb though which was strange but it still worked fine. Thanks alot!

Thad E Ginathom said:
4. Will Xiaomi updates still work and be installable?)
Click to expand...
Click to collapse
rmsinaga said:
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
Click to expand...
Click to collapse
Just tried this, it does not work.
Disabled root from SuperSU and updated to the newest weekly developer rom, and my device is now in a boot loop.
I'm currently trying to download the stable fastboot rom from the MIUI forums, but their servers are both incredibly slow and unstable. Doesn't go past 100kb/s and the download loses connection after a while and fails to continue the download. If someone could provide a alternative download link that would be great.
EDIT: Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i

zenolijo said:
Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i
Click to expand...
Click to collapse
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.

aembleton said:
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.
Click to expand...
Click to collapse
Well, the stable fastboot rom isn't the global version, so i only used it to get my phone running again and then flashed the stable global version. Everything works as expected now.

How to update ROM using fastboot in Linux?
Do you know how to update ROM using fastboot in Linux?
Sorry to bother you as I'm new in this Linux world.
Thank you.

Thank you man, you have guided us to the land of light, you are our moses, krishna, muhammad and so on and so forth. We can flash left and right without second thoughts. Please keep up your efforts. Thank you one more time.

My phone is, as per previous posts, rooted, using this method.
Can I now flash TWRP recovery from Linux?

Hey, this is a method only for Xiaomi Mi4i? I have an Estar Crystal-clearview and wondering if I can root it by this method? I run the terminal with the adb install and then for the list of devices attached, and I started thinking about!
P.s. Just searched ''root with mint'' and your post was first!

Thad E Ginathom said:
Can I now flash TWRP recovery from Linux?
Click to expand...
Click to collapse
Eventually I got around to doing this using Flashify. I followed the instructions here on the MIUI forum. It was simple and straightforward and I now have TWRP recovery.
However, when I tried to use it to do a backup, it said there was not enough space. But it was long past bedtime, and that is another story that I have yet to investigate. There is probably a simple answer, err... make more space! The absence of SD card slot and the limited internal memory is the big frustration about this phone.
But I want to upgrade MIUI --- and I don't want to do it without an easy backtrack to the previous ROM.

[Solved] Step 9 not working
Goto developer options
Check if 'fastboot mode' is enabled

Thanks
Hi aembleton,
Thanks a lot. it worked just fine.
does this replace recovery too ?

[ROOT][GUIDE] How to install TWRP and root Wiko Jerry (Magisk)

Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.
After downloaded, extract the ZIP anywhere you want.
You should now have a folder like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.
-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40
Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)
-Find a device called "fastboot Gadget" or similar name with a exclamation mark.
-Right click it and click on "Update drivers..."
-Click on second option on the setup (search manually)
-Click on the second option again.
-On the list, look for Universal Serial Bus Devices and double click it
-Inside the Manufacturer list select WinUsb Device
-On the right list select ADB Device and double click it
-Click on yes
-After installed, close and its fixed!
​When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!

help
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed

GnarlyBuzzard50 said:
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
Click to expand...
Click to collapse
hey you'll need to unlock your bootloader first
FIRST BACKUP EVERYTHING USEFUL FROM YOUR PHONE, THI WILL FACTORY RESET YOUR DEVICE
after getting adb working (debug on and all that stuff)
enter in your cmd prompt
Code:
adb reboot bootloader
then wait till your phone is in fastboot mode
now you'll type in cmd
Code:
fastboot flashing unlock
read carefully what appears in your phone screen and accapt it (at your own risk, it will probably void your warranty)
now type in cmd
Code:
fastboot reboot
done

TWRP file is not working

Code:
fastboot flashing unlock
Click to expand...
Click to collapse
I get "Unlock Failed"

When I try to enter recovery mode, it says: no command

is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?

KitK4t said:
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:​
Open this link and click on SDK Platform-tools for Windows.​After downloaded, extract the ZIP anywhere you want.​You should now have a folder like this:​
Keep the folder open (or just minimize it) and go ahead to the next step.​​
​​Installing ADB on Linux:​
Run one of this commands on your terminal.​-Ubuntu/Debian based Linuxes (APT):​
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):​
Code:
sudo yum install android-tools
Test with:​
Code:
sudo adb version
You should get something like this:​
Code:
Android Debug Bridge version 1.0.40[/INDENT]
[INDENT]Version 4986621
​
​
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
​If you get <waiting-for-device> on command prompt, check this:​
-Open Device Manager (Win key+X, click on Device Manager)​-Find a device called "fastboot Gadget" or similar name with a exclamation mark.​-Right click it and click on "Update drivers..."​-Click on second option on the setup (search manually)​-Click on the second option again.​-On the list, look for Universal Serial Bus Devices and double click it​-Inside the Manufacturer list select WinUsb Device​-On the right list select ADB Device and double click it​-Click on yes​-After installed, close and its fixed!​​
​​When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
Click to expand...
Click to collapse

<thanks man, worked fine for me.
just like he says...
adb reboot-bootloader
fastboot flash recovery <pathoftherenamedTWRP.img>
Take the battery out, back in
press and hold start button, sec later vol down button too
Now TWRP should start
read only
transfer the magisk.zip file to internal storage(PC)
install button(TWRP, Smartphone)
tap on the magisk.zip file and swipe to accept
wait till its done
press on reboot
done

Zaki4t said:
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
Click to expand...
Click to collapse
Worked for me. Where can i see which i have. maybe i can help

z0mb13m4ch1n3 said:
Worked for me. Where can i see which i have. maybe i can help
Click to expand...
Click to collapse
and if you messed up(like I do in my first try) here...
Wiko Mobile: Kundenbereich / Verbindung.
customer-de.wikomobile.com
take out the battery, theres the imei number
youll download a .exe file. stressed me in linux and lend a win 7 laptop. 5min or so and i had a factory fresh jerry to try again

The problem is there is no WinUsb there i dont have it.

Hi, I have a big trouble i followed all the instructions and everything was just fine, until the step 4- Booting into TWRP and root the phone with Magisk, after a take out and put the battery again in the cell, it doesn't boot from logo, just reset an reset, I already try o hard reset, try to enter TWRP, I try all kind of button combination, nothing works can someone helpme. Thks...

Did I brick my Pixel 3 trying to bring it back to stock?

Hello guys,
I needed to send in my Pixel 3 for repair and wanted to bring it back to stock. So I thought that I flash a factory Image and lock the bootloader afterwards.
But It did bug and give me errors like boot.img not in archive etc. even though I completly upacked the zip inside that path.
Anyways, now my adb doesnt find any devices and I cant boot. On the Fastboot screen it says the following:
boot slot: b
Enter reason: error booting boot.img
thanks in advance!

Try to factory reset your phone from recovery.

levibuko said:
Hello guys,
I needed to send in my Pixel 3 for repair and wanted to bring it back to stock. So I thought that I flash a factory Image and lock the bootloader afterwards.
But It did bug and give me errors like boot.img not in archive etc. even though I completly upacked the zip inside that path.
Anyways, now my adb doesnt find any devices and I cant boot. On the Fastboot screen it says the following:
boot slot: b
Enter reason: error booting boot.img
thanks in advance!
Click to expand...
Click to collapse
Do you have the latest sdk platform tools (fastboot)? Run the flash-all batch file you find in the extracted factory image. When you boot into the bootloader run fastboot devices from your pc. Is your device reconized?

Did you download the right image for the current build your on??

anasmhds said:
Try to factory reset your phone from recovery.
Click to expand...
Click to collapse
If I try to acces recovery it just reboots back to fastboot or I get the android logo with no command error
jd1639 said:
Do you have the latest sdk platform tools (fastboot)? Run the flash-all batch file you find in the extracted factory image. When you boot into the bootloader run fastboot devices from your pc. Is your device reconized?
Click to expand...
Click to collapse
I updated from the google webpage . Yes, fastboot devices gives me a a device ID. But with adb it says waiting for devices.
thatsupnow said:
Did you download the right image for the current build your on??
Click to expand...
Click to collapse
I did download android 10, before I was on android 9. Was that my mistake?

levibuko said:
If I try to acces recovery it just reboots back to fastboot
. Yes, fastboot devices gives me a a device ID. But with adb it says waiting for devices.
Click to expand...
Click to collapse
ADB only works when booted in to recovery or system. You need fastboot when booted in to the bootloader. That's why you don't get anything from adb.

Are you sure anything happened when you tried to relock? Since you can get fastboot to recognize the device, try a flash-all.

sliding_billy said:
Are you sure anything happened when you tried to relock? Since you can get fastboot to recognize the device, try a flash-all.
Click to expand...
Click to collapse
I didnt relock yet. If i try the flash all script now it does some more than before but it restarts and shows me the no command (android logo) error. and then the script finishes and says waiting for other devices.

levibuko said:
I didnt relock yet. If i try the flash all script now it does some more than before but it restarts and shows me the no command (android logo) error. and then the script finishes and says waiting for other devices.
Click to expand...
Click to collapse
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.

jd1639 said:
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.
Click to expand...
Click to collapse
Allright, I will try it as soon as I am back home tomorrow.

jd1639 said:
The no command with the dead andriod is the stock recovery. Hold power button and press and release the vol up key, timing can be tricky. If it gets into recovery try a factory reset.
Click to expand...
Click to collapse
levibuko said:
Allright, I will try it as soon as I am back home tomorrow.
Click to expand...
Click to collapse
What JD said. You aren't bricked most likely. Lots of things can be done from stock recovery. Once you are at the recovery command page, you will likely have ADB recognition as well.

sliding_billy said:
What JD said. You aren't bricked most likely. Lots of things can be done from stock recovery. Once you are at the recovery command page, you will likely have ADB recognition as well.
Click to expand...
Click to collapse
I am glad to hear that. So could you recap what I gotta do now?
As far as I understand I need the stock image (any particular one?) and just need to run the flash-all script while in fastboot mode ?
What if it reboots and I am at the no command screen? Do I need to do sth with the phone or wait?

So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.

levibuko said:
So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.
Click to expand...
Click to collapse
There are archives (images) that the device doesn't use and aren't contained in the factory image so that's normal, fastboot tries to run them anyway. But only running a few seconds is not normal. Do you remember, or can try to run the script again, what images it does try to run and what the last thing that it did flash? And it doesn't show any errors? If you see that it doesn't contain certain sig files, that's also normal.
Edit, one other thing. Try downloading the factory image again. Only extract the factory image zip file, don't extract the other zip file you find in it. Then run the flash-all script from within the extracted factory image.

levibuko said:
So I tried it again, I still get some "archive does not contain" errors but after the script ended I was able to get to recovery and factory reset. sadly I still cant boot and I get to the same screen. I dled the factory img from googles webpage so I dont understand why so much files are missing. the scipt also only runs for a few secs.
Click to expand...
Click to collapse
First, the "errors you are seeing about "not containing" are not errors but part of the script. Are you getting to fastbootd after what seemed like a reboot into recovery? Are you doing something there? You shouldn't as it is part of the script that started that way with Android 10. If you watch command prompt, you will see that it is still running and will eventually finish and reboot properly into system. For the Pixel 3 (not 3XL since you are in the P3 forum), you should be using 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...y-bc480ac4.zip. Be sure to check the SHA-256 of the file before you flash. As for flashing, extract the DL either right into your ADB/Fastboot folder or wherever if you have your PATH set properly. Current platform tools are 29.05 available for Windows at https://dl.google.com/android/reposi...st-windows.zip. Then, just run flash-all from command prompt. The next thing you should see after a fairly lengthy reboot through the G screen is your device ready to be setup with Google.
If you can take some pictures with a camera or something and post, that would help with anything you might be seeing. The other thing you could do since you can get into recovery is to run the actual OTA install. Follow the directions here and use 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...8-7a817e0d.zip. Same thing about checking the SHA-256.
This last line in your post "the scipt also only runs for a few secs" leads me to believe you are not letting it run through the fastbootd half.

sliding_billy said:
First, the "errors you are seeing about "not containing" are not errors but part of the script. Are you getting to fastbootd after what seemed like a reboot into recovery? Are you doing something there? You shouldn't as it is part of the script that started that way with Android 10. If you watch command prompt, you will see that it is still running and will eventually finish and reboot properly into system. For the Pixel 3 (not 3XL since you are in the P3 forum), you should be using 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...y-bc480ac4.zip. Be sure to check the SHA-256 of the file before you flash. As for flashing, extract the DL either right into your ADB/Fastboot folder or wherever if you have your PATH set properly. Current platform tools are 29.05 available for Windows at https://dl.google.com/android/reposi...st-windows.zip. Then, just run flash-all from command prompt. The next thing you should see after a fairly lengthy reboot through the G screen is your device ready to be setup with Google.
If you can take some pictures with a camera or something and post, that would help with anything you might be seeing. The other thing you could do since you can get into recovery is to run the actual OTA install. Follow the directions here and use 10.0.0 (QQ1A.191205.008, Dec 2019) https://dl.google.com/dl/android/aos...8-7a817e0d.zip. Same thing about checking the SHA-256.
This last line in your post "the scipt also only runs for a few secs" leads me to believe you are not letting it run through the fastbootd half.
Click to expand...
Click to collapse
Hello,
first of all thank you for the detailed answer!
I did as you told me and got so far:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another question: I just click on the flash-all script and let it run. do i have to open he power shell in w10 and do it within there?
EDIT: I think I dont know how to properly add images. Phone stays at the fastbootd screen and I get the error fastboot error: command failed.

levibuko said:
Hello,
first of all thank you for the detailed answer!
I did as you told me and got so far:
Another question: I just click on the flash-all script and let it run. do i have to open he power shell in w10 and do it within there?
EDIT: I think I dont know how to properly add images. Phone stays at the fastbootd screen and I get the error fastboot error: command failed.
Click to expand...
Click to collapse
Yes, you need to run it from command prompt or PowerShell. There are some differences between the two, but if you just type cmd in PowerShell, it will put it in command prompt mode. Make sure to hold down shift and right click and open power shell widow from here so that the open directory is in the command line when you run flash-all. Withe a batch file in windows in the actual directory, you can just type run-all with no .bat or .\ or anything. Your pics are not showing, but something like what I am showing. BTW, sideloading the OTA needs done from command prompt as well. Like I said, easy way is just to extract the image into the same directory where you have Platform Tools extracted so you don't need to worry about the path.

levibuko said:
Another question: I just click on the flash-all script and let it run.
Click to expand...
Click to collapse
You should be able to just double click the flash all batch file. You don't need to run it in a power shell. It'll open one up to run the fastboot commands.

sliding_billy said:
Yes, you need to run it from command prompt or PowerShell. There are some differences between the two, but if you just type cmd in PowerShell, it will put it in command prompt mode. Make sure to hold down shift and right click and open power shell widow from here so that the open directory is in the command line when you run flash-all. Withe a batch file in windows in the actual directory, you can just type run-all with no .bat or .\ or anything. Your pics are not showing, but something like what I am showing. BTW, sideloading the OTA needs done from command prompt as well. Like I said, easy way is just to extract the image into the same directory where you have Platform Tools extracted so you don't need to worry about the path.
Click to expand...
Click to collapse
I tried everything exactly the way you told me but its the same result. So I tried sideloading the OTA it switches to the no command error na d I get this:
adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: No error
Edit: If I try to boot to recovery via combo keys I get the no command with the android logo too. Is my recovery dmged?
If I try to flash teh image I get to fastbooted and from there I can get into recovery mode. I tried OTA again and now I got this error:
>adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: Invalid argument
and the error when I flash the image:
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/4 (524284 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...

levibuko said:
I tried everything exactly the way you told me but its the same result. So I tried sideloading the OTA it switches to the no command error na d I get this:
adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: No error
Edit: If I try to boot to recovery via combo keys I get the no command with the android logo too. Is my recovery dmged?
If I try to flash teh image I get to fastbooted and from there I can get into recovery mode. I tried OTA again and now I got this error:
>adb sideload blueline-ota-qq1a.191205.008-7a817e0d.zip
serving: 'blueline-ota-qq1a.191205.008-7a817e0d.zip' (~0%) * failed to read command: Invalid argument
Click to expand...
Click to collapse
The no command is not recovery yet. You need to do the step listed in the OTA instructions --To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear. You can't start the sideload from anywhere besides that menu that you seem to not be at yet. I was just about to recommend the OTA sideload since that is a little more reliable. Fastbootd cannot be used for all things. Just start from scratch using the OTA instructions here: https://developers.google.com/android/ota Also, make sure you are getting a 'fastboot devices' devices recognition (for image flash) or an 'adb devices' recognition once in recovery for sideload. Also, be sure to try different cables and ports. Reboot computer, etc to make sure the daemon is completely reset. There is something missing in your steps. Image instructions are here, BTW: https://developers.google.com/android/images. If you can get fastboot devices to recognize the device, you aren't hard bricked. Soft bricked of course, but not hard.
That product error is one that nobody seems to have figured out a reason for. Get yourself to that error, stay connected and in command prompt (I thionk you do have to do a press any key to continue to get back to a prompt once the error happens, but I'm not sure). Just don't close anything. Then do the sideload from fastbootd. Yes, you are using half of the image install and half of the OTA install with different files.

Systemless Root on Ulefone Armor 10 5G: How I did it...

I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 10 5G. Turns out the process is nearly identical to the Armor 8.
My thanks to all contributors to this thread and this one. Here's what worked for me, developed with pieces culled from both.
WHAT YOU'LL NEED:
--The current version of ADB Platform Tools.
--The APK file for MAGISK (Current version, as of this post's date, is 22.0).
--ADB and Fastboot USB drivers. I found my copy here.
--A copy of the Armor 10's current ROM image. This can be had from Ulefone's site (non-EU version). If you need the EU version, use this link.
--A copy of vbmeta_null.img as found here.
HOW TO DO IT:
The usual disclaimers apply; Do this at your own risk, I'm not responsible if you brick or damage your device, or void your warranty, etc. I'm also going to condense the instructions a bit, on the assumption anyone who's serious about rooting already knows the basics.
Unlock your phone's bootloader.
Once you get through the factory initialization again, enable developer options.
Install the ADB platform tools and USB drivers on your PC.
Extract boot.img from the stock ROM download and place it in the same directory as your ADB tools install. Transfer vbmeta_null.bin to the same spot.
Do a sideload install of the Magisk APK file to your phone.
Copy the boot.img file to your phone's local storage using the file transfer method of your choice.
Assuming you survived the above, your phone is now unlocked and ready to root. Proceed as follows:
Open the Magisk app. Click 'Install' for the Magisk Manager app, agree to any prompts, etc.
Next, tick 'Install' for 'Install Magisk' (NOT the manager portion). When prompted for the method, choose 'Select and patch a file.'
Select the 'boot.img' file you transferred to the phone's local storage in step 6 above. Once you do this, the patching process begins on its own.
Magisk will write a root-patched copy, named 'magisk_patched_xxxxx.img,' to the same directory (the X's indicate an alphanumeric string).
Transfer the patched image file back to the ADB tools directory on your PC, with whatever transfer means is comfortable for you.
Now we get to the interesting part. Reboot the phone to fastboot mode, and make sure it's connected to your PC via USB.
Open a command prompt window, on your PC, in the directory your ADB tools are installed.
Type 'fastboot devices' to make sure the system sees your phone.
Assuming all is well, type: 'fastboot flash vbmeta vbmeta_null.img' and hit enter. You should get appropriate responses saying the file was transferred.
Next, type 'fastboot flash boot magisk_patched_xxxxx.img' (naturally, replace the X's with whatever string of characters Magisk supplied).
Assuming no errors, type 'fastboot reboot' and hit enter. Your Armor 10 should now be rooted.
Enjoy!
Happy tweaking.

Hey, thank you for this guide but I'm facing an issue with step 9.
When I try to flash vbmeta_null.img, I'm getting this error "no such file or directory". I tried flashing just magisk but that gives me a bootloop

foumfo said:
Hey, thank you for this guide but I'm facing an issue with step 9.
When I try to flash vbmeta_null.img, I'm getting this error "no such file or directory". I tried flashing just magisk but that gives me a bootloop
Click to expand...
Click to collapse
You're welcome. Did you make sure to put the vbmeta_null.img file in the same directory with your adb and fastboot executables?

kc7gr said:
You're welcome. Did you make sure to put the vbmeta_null.img file in the same directory with your adb and fastboot executables?
Click to expand...
Click to collapse
Yep, I think the error message refers to the phone not having the vbmeta file. But after flashing magisk and rebooting to fastboot, flashing vbmeta works. But I'm still getting a bootloop

The sequence is also important: Install Magisk, flash modified boot.img, flash vbmeta_null. As I understand it, it's the act of installing Magisk which makes it possible to flash vbmeta.
Worst case: Do as I did, look at all available posts and experiment. You can find a sequence which works for you as well.
Stay well...

Did someone try to flash a GSI Rom in the Ulefone Armor 10? I plan to flash Havoc GSI...Has anyone tried if everything is working? Is there also a TWRP Version for this Ulefone?

Hello,
thank you for this Guide. I have Problems unlocking bootloader. "Enable OEM unlock" is set in debeloper settings. I tried "flashing unlock" and "oem unlock". Both give me a "Command failed".
Update: the problem was the USB-driver. The latest version from the web didnt work. Then i use the search-driver-function of windows device-manager. After that it worked.

bd080392 said:
Did someone try to flash a GSI Rom in the Ulefone Armor 10? I plan to flash Havoc GSI...Has anyone tried if everything is working? Is there also a TWRP Version for this Ulefone?
Click to expand...
Click to collapse
Yes. It has and not relesead yet! Need more tests. But you can look here: Some extra informations
Update: TWRP is now ready to use since July 1st. Two users have the file in the 4pda forum. I will not put the file here.
Acetonperoxid said:
Hello,
thank you for this Guide. I have Problems unlocking bootloader. "Enable OEM unlock" is set in debeloper settings. I tried "flashing unlock" and "oem unlock". Both give me a "Command failed".
Update: the problem was the USB-driver. The latest version from the web didnt work. Then i use the search-driver-function of windows device-manager. After that it worked.
Click to expand...
Click to collapse
You need write:
Code:
fastboot flashing unlock
The message appears in the screen. Press Vol+ and wait. Reboot device and you see message about Orange State.. Your device's unlocked!

Acetonperoxid said:
Hello,
thank you for this Guide. I have Problems unlocking bootloader. "Enable OEM unlock" is set in debeloper settings. I tried "flashing unlock" and "oem unlock". Both give me a "Command failed".
Update: the problem was the USB-driver. The latest version from the web didnt work. Then i use the search-driver-function of windows device-manager. After that it worked.
Click to expand...
Click to collapse
I use command for Ulefeno Armor 7
fastboot oem unlock-go
Or
fastboot oem unlock

getting this when I try to push the vbmeta_null.img It is in the directory I'm running the command from
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@kc7gr thanks for the guide
im getting stuck at step 9
is this guide for EU or Non EU version?
i got fastboot running in Windows 7 rather than 10
is this same did u run it in win 10?

finnd1 said:
getting this when I try to push the vbmeta_null.img It is in the directory I'm running the command from
View attachment 5344503
Click to expand...
Click to collapse
You may have the file in the folder your running the command from, but would that be your adb/fastboot root dir?

Hello. There's little information on XDA for Uleafone phones. I've bought an Uleafone Armor X10 Pro. Could I do the same process as described here to install TWRP on it / flash magisk?

kc7gr said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 10 5G. Turns out the process is nearly identical to the Armor 8.
My thanks to all contributors to this thread and this one. Here's what worked for me, developed with pieces culled from both.
WHAT YOU'LL NEED:
--The current version of ADB Platform Tools.
--The APK file for MAGISK (Current version, as of this post's date, is 22.0).
--ADB and Fastboot USB drivers. I found my copy here.
--A copy of the Armor 10's current ROM image. This can be had from Ulefone's site (non-EU version). If you need the EU version, use this link.
--A copy of vbmeta_null.img as found here.
HOW TO DO IT:
The usual disclaimers apply; Do this at your own risk, I'm not responsible if you brick or damage your device, or void your warranty, etc. I'm also going to condense the instructions a bit, on the assumption anyone who's serious about rooting already knows the basics.
Unlock your phone's bootloader.
Once you get through the factory initialization again, enable developer options.
Install the ADB platform tools and USB drivers on your PC.
Extract boot.img from the stock ROM download and place it in the same directory as your ADB tools install. Transfer vbmeta_null.bin to the same spot.
Do a sideload install of the Magisk APK file to your phone.
Copy the boot.img file to your phone's local storage using the file transfer method of your choice.
Assuming you survived the above, your phone is now unlocked and ready to root. Proceed as follows:
Open the Magisk app. Click 'Install' for the Magisk Manager app, agree to any prompts, etc.
Next, tick 'Install' for 'Install Magisk' (NOT the manager portion). When prompted for the method, choose 'Select and patch a file.'
Select the 'boot.img' file you transferred to the phone's local storage in step 6 above. Once you do this, the patching process begins on its own.
Magisk will write a root-patched copy, named 'magisk_patched_xxxxx.img,' to the same directory (the X's indicate an alphanumeric string).
Transfer the patched image file back to the ADB tools directory on your PC, with whatever transfer means is comfortable for you.
Now we get to the interesting part. Reboot the phone to fastboot mode, and make sure it's connected to your PC via USB.
Open a command prompt window, on your PC, in the directory your ADB tools are installed.
Type 'fastboot devices' to make sure the system sees your phone.
Assuming all is well, type: 'fastboot flash vbmeta vbmeta_null.img' and hit enter. You should get appropriate responses saying the file was transferred.
Next, type 'fastboot flash boot magisk_patched_xxxxx.img' (naturally, replace the X's with whatever string of characters Magisk supplied).
Assuming no errors, type 'fastboot reboot' and hit enter. Your Armor 10 should now be rooted.
Enjoy!
Happy tweaking.
Click to expand...
Click to collapse
Hello, gonna do this on an Armor X10 Pro. Already got it's original ROM. About vbmeta_null.img file, is that file universal, is it specific for Ulefone phones, or do I need one of those specific for Armor X10 Pro?

GauchoTche said:
Hello, gonna do this on an Armor X10 Pro. Already got it's original ROM. About vbmeta_null.img file, is that file universal, is it specific for Ulefone phones, or do I need one of those specific for Armor X10 Pro?
Click to expand...
Click to collapse
Here a secure file: vbmeta.img from G

[GUIDE] Here's how to unlock the bootloader of Nokia 5.3.

Code:
#/usr/bin/env python3
from hct_principle import permission, content
print('''
Your warranty is void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
''')
if content.repost('other_content_farm_website_or_tech_forum'):
if not permission:
print('Please DM me for permission')
raise Exception('RepostNotAllowedException')
Recently I got a prototype OS backup from a Nokia 5.3 engineering sample unit that contains ABL image with bootloader unlock capability.
Later I found it can be used on retail unit, but flashing it can be tough depends on Android OS version installed on your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Case 1: If you already have Android 11 or 12 installed
I'm sure that's the mostly seen situation for Nokia 5.3 users. Unfortunately to do this, you'll have to open up the phone and have Qualcomm EDL driver installed, or consider to use bkerler's live DVD on your PC (prepare a spare USB drive).
1. Clone and download this repository, or just boot into LiveDVD mentioned in README. Install it according to README.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Also download prototype ABL and attached firehose programmer from here:
Click here to download Prototype ABL
SHA256 checksum of ABL image: C8021967F91908BBE30C4534AA2174B72FB18A204F73BB96561A3F8A17140F0E
If you see error code 00000101, please use industrial standard web browser like Google Chrome.
2. Power off your phone.
3. Follow this video to disassemble the phone, until 4:40. Make sure you have motherboard exposed and battery DISCONNECTED. Please ask an experienced technician for help if you're not familiar with phone disassembly procedure.
4. (Skip this step if you're using Linux) Change EDL port driver according to README.md of edl toolkit said, and reconnect the phone after driver changed.
5. Execute these commands to backup original ABL and write prototype ABL.
For Windows, you should be able to see Qualcomm EDL Port in Device Manager.
For Linux, you'll have to use lsusb command to check if your phone is listed.
:
Code:
./edl r abl_a,abl_b abl_a.bin,abl_b.bin --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
./edl w abl_a /home/your_user_name/Download/CAP-abl.elf --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
./edl w abl_b /home/your_user_name/Download/CAP-abl.elf --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
After executed and waiting for connection, attach a side of your USB cable on your phone, then use a tweezer to short the test point indicated below. While shorting test point with tweezers, connect it to PC. You may need to repeat this when you execute next 2 commands.
6. Disconnect the phone, reattach the battery and reassemble the phone. Your phone should boot right into Fastboot mode.
7. Execute these commands to perform bootloader unlock:
Code:
fastboot flashing unlock_critical
(confirm unlock on your phone)
fastboot oem unlock-go
(confirm unlock on your phone again)
8. Once bootloader unlock confirmed, execute this command to check if unlock successful:
Code:
fastboot oem device-info
If both unlock state are indicated as True, you can restore the ABL back to retail (if you don't then phone will not boot to normal OS), wipe userdata and reboot:
Code:
fastboot flash abl_a abl_a.bin
fastboot flash abl_b abl_b.bin
fastboot -w reboot
9. If your phone had initial release of Android 12 that bricked the phone after factory reset, unbrick the phone by following this procedure.
10. Enjoy your bootloader unlocked Nokia 5.3 and have fun for hacking.
Watch this video in case you still don't understand:
Case 2: If you know someone who can provide remote phone flash service for you
I can help when the phone has Android 10 installed, but it's pretty rare nowadays, at least it's difficult to find outside China mainland.
However in this case you don't need to disassemble the phone, you'll just need to reinstall stock firmware after bootloader unlock.
1. Grant service permission. I know how the service permission granting works under initial release of Android 10, which I can't disclose here (also how I confirmed bootloader unlock method working).
If you know someone who can flash a recent Nokia phone for you, Then it will work under Android 11 or 12. When you request such service, ask him not to reboot your phone after the procedure completes.
2. Execute these commands to perform bootloader unlock:
Code:
fastboot flash abl CAP-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock_critical
(confirm unlock on your phone)
fastboot oem unlock-go
(confirm unlock on your phone again)
3. Flash stock ABL image and wipe userdata. Stock image from Android 12 release is attached below - extract it before flashing, or it will brick your phone and you'll have to use EDL method to revive it.
It may break OTA functionality, so use with care.
Code:
fastboot flash abl CAP-340A-abl.elf
fastboot -w reboot

I waited a long time, but do not leave this status

thiago92nr said:
I waited a long time, but do not leave this status
Click to expand...
Click to collapse
1. In case that happens, check if your laptop only has USB 3.x port. If yes, try to execute the command before connecting the phone to PC.
2. Execute the command under /home/your_user_name instead of /opt/edl to prevent permission issue.

Worked perfectly. I was able to unbrick my Nokia 5.3 by flashing the stock rom with Fastboot after unlocking the bootloader.

Regarding to stock firmware installation after bootloader unlock.
I'm sure you can obtain a stock ROM somewhere, for example the one I obtained has filename "HMDSW_TA-1229-340A-0-00WW-B01_user_devicekit.zip". (However it can be used on non TA-1229 models like TA-1234)
HMDSW_TA-1229-340A-0-00WW-B01_user_devicekit.zip | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
DO NOT USE MINIMAL ADB AND FASTBOOT! DELETE IT BEFORE YOU PROCEED!
These are possible locations of Minimal ADB and Fastboot:
Code:
C:\adb
C:\Program Files (x86)\Minimal ADB and Fastboot
C:\Program Files\Minimal ADB and Fastboot
C:\Windows\system32
Delete these 4 files: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Extract the firmware package twice and you'll see a batch file named "sm6125_fastboot_all_images.bat". Right click on it and remove the second line (adb reboot bootloader) - since you're already in fastboot mode.
Then, extract Platform Tools from following websites and place files along with firmware files: https://developer.android.com/studio/releases/platform-tools
Make sure fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll are placed altogether with firmware files, then double click "sm6125_fastboot_all_images.bat" to reinstall stock firmware.
As for macOS and Linux, you've probably noticed the existence of Captain_download_mac.sh and Captain_download_ubuntu.sh. Edit them and execute it under terminal.

Hello, do you mind to make a video how to do those steps? It's quite confusing especially for the 1st step and the 6th step.

xmichaxb7 said:
Hello, do you mind to make a video how to do those steps? It's quite confusing especially for the 1st step and the 6th step.
Click to expand...
Click to collapse
I'll have to wait few days to weeks for another Nokia 5.3 test unit's arrival.

hikari_calyx said:
I'll have to wait few days to weeks for another Nokia 5.3 test unit's arrival.
Click to expand...
Click to collapse
Oh, alright. I guess I must wait patiently. My Nokia 5.3 has a problem with the NFC on A12. It just keeps detecting my E-Money card like every 1 second or 0.5 second. So, I hopefully will be able to downgrade to A11 after I unlock the bootloader.

hikari_calyx said:
1. In case that happens, check if your laptop only has USB 3.x port. If yes, try to execute the command before connecting the phone to PC.
2. Execute the command under /home/your_user_name instead of /opt/edl to prevent permission issue.
Click to expand...
Click to collapse
I tried this after facing the same issue as @thiago92nr with no success still stuck on mode detected Sahara.
I used the live CD to try unlocking the bootloader and still no luck

pingusp said:
I tried this after facing the same issue as @thiago92nr with no success still stuck on mode detected Sahara.
I used the live CD to try unlocking the bootloader and still no luck
Click to expand...
Click to collapse
Type the command and press enter before connecting the device, then connect. it worked for me like this

I'll give it a go thanks

thiago92nr said:
Type the command and press enter before connecting the device, then connect. it worked for me like this
Click to expand...
Click to collapse
@thiago92nr I have another eorr.edl.py: No such file or directory

pingusp said:
@thiago92nr I have another eorr.edl.py: No such file or directory
Click to expand...
Click to collapse
remove the .py extension

Tried that and it's giving me this error @thiago92nr

Hey everyone I'm stuck on this part with no idea on what to do

pingusp said:
Hey everyone I'm stuck on this part with no idea on what to do
Click to expand...
Click to collapse
try this command
edl printgpt --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Then this one for Abl flash a and b
edl r abl_a abl_a.bin --memory=emmc --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf

Before I do this should I download all 3 files or the one with the prototype abl

thiago92nr said:
try this command
edl printgpt --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Then this one for Abl flash a and b
edl r abl_a abl_a.bin --memory=emmc --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Click to expand...
Click to collapse
Tried it same message
Apparently it could be due to pkhash does match the device pkhash or hardware doesn't match loader

some indan dude can unluck it without disassembling the Device! thats interesting he gives 20$ for that but i wanna know how its possible????

I think he might use hickari calyx bootloader unlock method or the hmd device toolkit