Database Info

problem with recovery

Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.

giganielsie said:
Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.
Click to expand...
Click to collapse
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.

DeuXGod said:
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.
Click to expand...
Click to collapse
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error

giganielsie said:
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error
Click to expand...
Click to collapse
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now

DeuXGod said:
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now
Click to expand...
Click to collapse
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?

giganielsie said:
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?
Click to expand...
Click to collapse
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now

DeuXGod said:
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now
Click to expand...
Click to collapse
Also don't work
This is the error:
{
"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"
}
In that folder are all of the files I needed so it should work though he don't work
And my phone also recognize as Android ADB Interface.
Edit: It's working!!! My brother fixed it! Thanks for the replies!!!:good::victory:

Now I have recovery but now I have another problem. When I reboot my phone, I can't go anymore to recovery. I see then a green android with a open stomach. Anybody a solution? It looks like there is something went wrong with the install of the recovery but what?
And I have root permission now but with rom manager I can install recovery but when I reboot into recovery, the green android with open stomach come back...

Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Thanks!!! It looks like it works! Thanks for youre fast replies:good::good:

I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.

GripR said:
I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have just flash CWM from the fastboot, enter in recovery and do a full wipe and install another ROM or even the stock image. Don't forget to remove the system/etc/install-recovery.sh file if you flash the stock ROM so CWM won't be overwritten every time you do a reboot.

DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
from the dead droid reboot with power+ vol up
enter jb and with a file manager (like es file..or something else) delete both:
-/system/recovery-from-boot.p
-/system/etc/install-recovery.sh
reboot and reinstall cwm via fastboot

Only problem with that is he will require root access to do that.
Which I am assuming he currently doesn't have.
Anyways as someone already stated. Unlock bootloader if it isn't already. That will wipe your data off the phone.
Boot or flash a custom recovery.
Flash su.zip or supersu etc to get root
Boot up and make sure you actually have root.
Do as above poster said and remove those files.
Either flash recovery from a app like goo manager or rom manager. Hell now that that I think about it. I think rom manger has the option to remove those files for you when it flashes cwm. Or reboot into the bootloader and flash the recovery with fastboot. It will stick. Keep in mind that you need to download the fastboot version of the recovery if you go that route. It will be a .img. the others will be a .zip .
If you don't know how to use fastboot. Read the quides/stickies etc.

[Q] help!!¡!!!!!!root for acer a700

I have an acer a700,but i updaded to jeally bean,please help me root this device.thanks .

cuibapngo said:
I have an acer a700,but i updaded to jeally bean,please help me root this device.thanks .
Click to expand...
Click to collapse
First I think you need to learn to post in the right section.
Then Learn to READ in the right section!
See it's EasyRoot

Vorbeth said:
First I think you need to learn to post in the right section.
Then Learn to READ in the right section!
See it's EasyRoot
Click to expand...
Click to collapse
So,i just want to root,i҆m happy with romstock,not romcook.i want root to install apps that requires to root such as:titanium back up,root explorer....
Here information my device:
Model number: a700
Android vesion: 4.1.1
Kenel vesion: 3.1.10+
Image vesion: acer av501-pa-a700-rv18rc01-pa-cus1
Build number: 1.502.00-pa-cus1
Image p/n: fm.s1ma0.04a
Is this successful?i҆m newbie,so i҆m a little scared if unsuccessful
Later i want use romcook,still can be up to normal or not?
thanks for bothering you
Sorry my english

cuibapngo said:
So,i just want to root,i҆m happy with romstock,not romcook.i want root to install apps that requires to root such as:titanium back up,root explorer....
Here information my device:
Model number: a700
Android vesion: 4.1.1
Kenel vesion: 3.1.10+
Image vesion: acer av501-pa-a700-rv18rc01-pa-cus1
Build number: 1.502.00-pa-cus1
Image p/n: fm.s1ma0.04a
Is this successful?i҆m newbie,so i҆m a little scared if unsuccessful
Later i want use romcook,still can be up to normal or not?
thanks for bothering you
Sorry my english
Click to expand...
Click to collapse
Just run Vorbeth's EasyRoot. You won't mess anything up.
MD

Moscow Desire said:
Just run Vorbeth's EasyRoot. You won't mess anything up.
MD
Click to expand...
Click to collapse
thank you.i will try: Ngón tay vượt qua:,but please guide supplied by one of the images?because
i may not post new threads, may not post replies, may not post attachments
i may edit my posts: Khóc:
here is one of the questions?
You need:
-Acer Iconia Tab A700 with unlocked bootloader & already be running Jelly Bean(this is whehe i have to download?)
-ClockworkMod Recovery - 6.0.1.5 or newer(i have downloaded 2files.1 is recovery a700 6015. 1 is recovery a700 6015 touch.so spend what?)
Download:
A700 EasyRoot 2.0 md5: 8876aca04e29fe69d7368bc02006359c(there to 12files.down all always?down to set in place?it is not a zip file?
-How to flash:
Download zip and place it on your virtual or external SD card
Boot your phone into ClockworkMod Recovery (via adb or with a key combo)
In main menu, select "install zip from sdcard"
Select "choose zip from sdcard" and browse to the location of zip
After flashing process is complete, reboot the device
Alternative install for Stock patched kernel ONLY:
Reboot to bootloader
Extract boot.img from the zip
Flash boot.img via fastboot
How to get root:
Install SuperSu via CWM
Install BusyBox from Play(these steps can you give me one of the images?)
-Download:
Stock patched kernel md5: 4638ffe2bcb00352ccc702fdfab1d8cb(link die)
iconiaN source built kernel md5: 76b8e1020c6054debedf60efffdca609(link die)
please guide me in detail,thanks for bothering

No one to guide me out?

cuibapngo said:
No one to guide me out?
Click to expand...
Click to collapse
Dude, it's pretty easy.
1. Unlock your bootlooader. To do this, go into tablet /Settings/Development Options and select USB Debugging.
2. Plug your tab into PC (your Acer USB drivers must be installed first)
3. Open a Command Window in the folder you downloaded all those files. (shift & right mouse click)
4. Check to make sure ADB is working by typing adb devices (you should get some numbers) if not, you have a windows driver issue.
5. Type adb reboot bootloader (tab should reboot to bootloader)
6. Type fastboot OEM unlock (you should get a couple of images. One with an unlock, and one with a lock door) Use Vol - to switch between the 2. Use vol + to select. You have to be quick, as it times out after 5 seconds or so.
When you reboot, it should say bootloader version number (unlocked mode) or something similar.
Go back to the Command window, and run the batch file. "easyroot.bat" by typing in easyroot.bat , then hit the Enter button. The batch file should install all you need, You may need to select things that it prompts you for.
No, there's not a video, as it ain't rocket science. If you can't understand these instructions, perhaps it is better if you do not root your tablet. Doing this, is not for everybody.
Also note, once you unlock your bootloader, you can no longer get OTA from Acer. And, once you unlock it, you cannot lock it back. Not without installing a whole new stock rom.
Also, next time, post your questions in the Q&A forum. Otherwise, nobody will answer them.
MD

help me
grigaman said:
Help please. I tried to establish root on the A700 in the second way. But I didn't notice that this way is available for 4.0.4, and on my tablet was established 4.1.1. At me at inclusion gives out here such and more than anything. The debugging mode joins and determined by USB by the computer, but I don't know what to do, prompt please! And still it doesn't load updating with SD the card. And before doing root I unblocked the loader
Click to expand...
Click to collapse
please help me
{
"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"
}

Moscow Desire said:
Dude, it's pretty easy.
1. Unlock your bootlooader. To do this, go into tablet /Settings/Development Options and select USB Debugging.
2. Plug your tab into PC (your Acer USB drivers must be installed first)
3. Open a Command Window in the folder you downloaded all those files. (shift & right mouse click)
4. Check to make sure ADB is working by typing adb devices (you should get some numbers) if not, you have a windows driver issue.
5. Type adb reboot bootloader (tab should reboot to bootloader)
6. Type fastboot OEM unlock (you should get a couple of images. One with an unlock, and one with a lock door) Use Vol - to switch between the 2. Use vol + to select. You have to be quick, as it times out after 5 seconds or so.
When you reboot, it should say bootloader version number (unlocked mode) or something similar.
Go back to the Command window, and run the batch file. "easyroot.bat" by typing in easyroot.bat , then hit the Enter button. The batch file should install all you need, You may need to select things that it prompts you for.
No, there's not a video, as it ain't rocket science. If you can't understand these instructions, perhaps it is better if you do not root your tablet. Doing this, is not for everybody.
Also note, once you unlock your bootloader, you can no longer get OTA from Acer. And, once you unlock it, you cannot lock it back. Not without installing a whole new stock rom.
Also, next time, post your questions in the Q&A forum. Otherwise, nobody will answer them.
MD
Click to expand...
Click to collapse
so,i haved I downloaded the usb driver and sdk on my pc and then
First, i install usb driver.sau I plug my A700 to the PC, I did not see what happened. do not know my tab has been updated to the new driver?
*I download the sdk for it in the c drive (because when I extract it, do not see the files installed)
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
I do not know to type the path to the sdk, it's all wrong! I to the sdk folder in c / program files/adt-bundle-windows-x86 .đặt thư mục sdk ở program files có đúng không?

cuibapngo said:
so,i haved I downloaded the usb driver and sdk on my pc and then
First, i install usb driver.sau I plug my A700 to the PC, I did not see what happened. do not know my tab has been updated to the new driver?
*I download the sdk for it in the c drive (because when I extract it, do not see the files installed)
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
I do not know to type the path to the sdk, it's all wrong! I to the sdk folder in c / program files/adt-bundle-windows-x86 .đặt thư mục sdk ở program files có đúng không?
Click to expand...
Click to collapse
Dude. Why are you messing with the Android SDK? When you mess with the SDK, you also have to install the Java JRE kit as well. Then, you have to modify your PATH and CLASSPATH on windows, or else you'll get the messages you got.
I thought you just wanted to get Root on your tablet. Everything you need is in the package that Vorbeth has for easyRoot. His package contains adb.exe, fastboot.exe, and the windows dll's necessary to do it from the folder you saved them all too. Leave the SDK alone unless you know what you are doing.

Moscow Desire said:
Dude. Why are you messing with the Android SDK? When you mess with the SDK, you also have to install the Java JRE kit as well. Then, you have to modify your PATH and CLASSPATH on windows, or else you'll get the messages you got.
I thought you just wanted to get Root on your tablet. Everything you need is in the package that Vorbeth has for easyRoot. His package contains adb.exe, fastboot.exe, and the windows dll's necessary to do it from the folder you saved them all too. Leave the SDK alone unless you know what you are doing.
Click to expand...
Click to collapse
wow.not need unlock boadloader that still root?thanks.i try.

cuibapngo said:
wow.not need unlock boadloader that still root?thanks.i try.
Click to expand...
Click to collapse
You still have to unlock bootloader.,
But run your commands in the package you downloaded. (adb and fastboot). You don't need the SDK for this.
MD

Moscow Desire said:
You still have to unlock bootloader.,
But run your commands in the package you downloaded. (adb and fastboot). You don't need the SDK for this.
MD
Click to expand...
Click to collapse
xin please guide me add a few more, i open test adb và fastboot is it to open but it running very fast and auto closed back.is it wrong?
so, run easy root first or run adb with fastboot first?

cuibapngo said:
xin please guide me add a few more, i open test adb và fastboot is it to open but it running very fast and auto closed back.is it wrong?
so, run easy root first or run adb with fastboot first?
Click to expand...
Click to collapse
I'm having a little trouble with adb and fastboot.i can not to open it.i open with right click and run as administrator, it runs fast and close automatically. above my tab do not see anything.i`ve tried turning off my the computer and tab and then do it again but still does not work. How can I do?
can i run the easy root without running adb command and fastboot?
at run adb and fastboot commands to shutdown tab? think is not it.

cuibapngo said:
I'm having a little trouble with adb and fastboot.i can not to open it.i open with right click and run as administrator, it runs fast and close automatically. above my tab do not see anything.i`ve tried turning off my the computer and tab and then do it again but still does not work. How can I do?
can i run the easy root without running adb command and fastboot?
at run adb and fastboot commands to shutdown tab? think is not it.
Click to expand...
Click to collapse
You MUST open a CMD (command) Window first.
In the folder you downloaded all the stuff to, find a nice empty place (DO NOT SELECT A FILE),
Hold your SHIFT key, and then do a RIGHT MOUSE CLICK
Then, select Open Command Window
You should have a black window, with the directory path. If you don't, then you have issues with your PC.
Next, (where you see the little flashing curser) type in adb devices then hit ENTER
(make sure the pc recognizes your tablet. You should see something like, killing dameon server :devices attached with several numbers)
Type adb reboot bootloader then hit ENTER
(tab reboots to bootloader)
use your left VOL- key to navigate between locked and unlocked. Use VOL+ to select
Reboot your tab. Should say unlocked mode on boot.
Then go back to that black Command Window, and type in adb devices and hit ENTER (once again, you should see your device like the first time)
Then type in 701easyroot.bat and hit ENTER
Should see some stuff, mostly warnings. But at this point, it will ask you to;
1. Keep your stock Recovery
2. Install the CWM Recovery
if you select 1, program quits, and you can just reboot your tab, because as soon as you ran the bat file, it rooted it.
MD

help!!!!did come here.and began restart my tab and it is the following message:
BOOTLOADER VJB-653B3D3 STARTING USB DOWNLOAD PROTOCOL
it stood like that for 20 minutes without seeing anything like couple of images.....lock or unlock
ell.i fear brick my tab, but luckily I power off and then turn it back to normal
type in 701easyroot.bat or easyroot.bat?
what can i do next?

well well, missing the fastboot oem unlock command to unlock
hen I opened the lock, I run orders easy root.bat.and I choose number 1.My tab runs report success, but I do not see superuser file on my tab?I tested the software files explorer, it says your device is not root?
What do I do next?
help help help!!!!!!!!!

can anyone here help me?MOSCOW DESIRE, where are you?

I tried to go back to work 3 times, but the result is the same.said root successful.including selecting the number 2 to do all over again the next time I do look closely and see the following message:
can not load root / boot.img
and then:
can not load root / recovery.img
I press continue and it indicates a successful root as shown. but there is not anything
what's wrong?

no one to help me?:crying::crying::crying:

[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 ?

HELP PLEASE!!! Device stuck on bootloop, no OS, no Recovery, not recognised by PC and only boots to fastboot.

I recently tried the dumb move of updating Magisk through the app itself. When rebooted it got stuck on bootloop, I then booted to Orangefox on my Redmi K20 Pro. I then did resetting to defaults in settings which showed 2 errors- Unable to mount system root and vendor(invalid arguement something like that) which resulted in my data being encrypted.
When I tried to reboot it said no OS installed. I didn't know what to do so I watched a youtube video instructing to wipe data and rebooting to recovery to fix this(encrypion) and so i did another dumb move of doing it which resulted in my device getting rid of Orangefox then, and now I am stuck on either boot loop with no recovery or in fastboot mode which isn't really doing much since it's not being recognised by my pc.
I am not much of a knower in this side but I knew some of the basics and followed instructions to install recovery and root and now have managed to break it. And now I'm panicking. SOMEONE HELP!!

If you are still able to go into fastboot mode and bootloader unlocked then you need to download firmware or use your back up of firmware then write them in fastboot mode and see it can help. /user might need to be wiped if it is encrypted. /cache maybe need to erase too if phone does not boot.
I don't know if it is you are already installed custom recovery such as TWRP, CWM, if it is installed then you need to flash /system and /boot. if it is not installed, flash /system and /boot and /recovery (or /recovery_ramdisk).
Make sure you have using same version installed firmware you try to flash.

aheadofsingularity said:
If you are still able to go into fastboot mode and bootloader unlocked then you need to download firmware or use your back up of firmware then write them in fastboot mode and see it can help. /user might need to be wiped if it is encrypted. /cache maybe need to erase too if phone does not boot.
I don't know if it is you are already installed custom recovery such as TWRP, CWM, if it is installed then you need to flash /system and /boot. if it is not installed, flash /system and /boot and /recovery (or /recovery_ramdisk).
Make sure you have using same version installed firmware you try to flash.
Click to expand...
Click to collapse
How do I write them in fastboot mode. Pardon but I don't know more technical stuff that much. My pc is unable to detect my phone so how can I write it. And I didn't quite fully understand the rest of it as well. Could you dumb it down?

Watch this video

Shiromani said:
How do I write them in fastboot mode. Pardon but I don't know more technical stuff that much. My pc is unable to detect my phone so how can I write it. And I didn't quite fully understand the rest of it as well. Could you dumb it down?
Click to expand...
Click to collapse
If your device is in fastboot mode
Its should recognised by pc
Check your driver's on device manager
Or download adb drivers
Then download firmware for your device
Fastboot type : fastboot devices
Then drag the flash all bat from flash file on cmd press enter
Note- u must have unlocked bootloader

samsujjamanrifat said:
If your device is in fastboot mode
Its should recognised by pc
Check your driver's on device manager
Or download adb drivers
Then download firmware for your device
Fastboot type : fastboot devices
Then drag the flash all bat from flash file on cmd press enter
Note- u must have unlocked bootloader
Click to expand...
Click to collapse
Update- I manged to install TWRP on my device but it was encrypted so unfortunately had to format data to remove it, but it still aks me to "keep data in red only mode?" Anyhow I ccopied the rom to my internal storage but it still shows the error- Failed to mount system_root and vendor(invalid argument). How do I fix that

Download ADB from Here
Download Xiaomi Redmi K20 Pro USB Driver Here
Install Usb driver
If you using windows then select "Download SDK Platform-Tools for Windows"
If you finished downloading zip file, open zip, then put "platform-tools" folder in C:\
{
"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"
}
Then add "C:\platform-tools" to your environment variables
To add it to environment variables,Ctrl+X, "system details">"environment variables">"User variables"
>"path" variables, add "C:\platform-tools" to "path" variables into the last.
Now you can use adb and fastboot commands everywhere in cmd, but you need to stick with image file, so you need to use Change Directory (cd) command for path of image folder.
Then put all firmware file (img) into platform-tools folder.
If you don't have firmware file go easy-firmware you should pay for it (I am not sure Xiaomi hosting free firmwares)
Ctrl+R then type "cmd" then Enter
In CMD type "cd C:\platform-tools", so you now cmd is looking at where your image files located.
type "fastboot devices"
type "flash-all.bat" or
"fastboot flash system <your system img file name>" / "fastboot flash system_root <your system img file name>"
"fastboot flash boot <your boot img file name>"
"fastboot flash recovery <your recovery img file name>" / "fastboot flash recovery_ramdisk <your recovery img file name>"
"fastboot flash vendor <your vendor img file name>"
"fastboot reboot"
you may need to execute these command too
"fastboot erase user"
"fastboot erase cache"
PS firmware files for Huawei P20 Pro
Filenames should vary but maybe looks like this (I'm not xiaomi user so...)

aheadofsingularity said:
Download ADB from Here
Download Xiaomi Redmi K20 Pro USB Driver Here
Install Usb driver
If you using windows then select "Download SDK Platform-Tools for Windows"
If you finished downloading zip file, open zip, then put "platform-tools" folder in C:\
View attachment 5809235
Then add "C:\platform-tools" to your environment variables
To add it to environment variables,Ctrl+X, "system details">"environment variables">"User variables"
>"path" variables, add "C:\platform-tools" to "path" variables into the last
View attachment 5809249
Then put all firmware file (img) into platform-tools folder
If you don't have firmware file go easy-firmware you should pay for it (I am not sure Xiaomi hosting free firmwares)
Ctrl+R then type "cmd" then Enter
In CMD type "cd C:\platform-tools"
type "fastboot devices"
View attachment 5809239
type "flash-all.bat" or
"fastboot flash system <your system img file name>"
"fastboot flash boot <your boot img file name>"
"fastboot flash recovery <your recovery img file name>" / "fastboot flash recovery_ramdisk <your recovery img file name>"
"fastboot reboot"
you may need to execute these command too
"fastboot erase /user"
"fastboot erase /cache"
PS firmware files for Huawei P20 Pro
Filenames should vary but maybe looks like this (I'm not xiaomi user so...)
View attachment 5809261
Click to expand...
Click to collapse
He made it look easy do that
Shiromani said:
Update- I manged to install TWRP on my device but it was encrypted so unfortunately had to format data to remove it, but it still aks me to "keep data in red only mode?" Anyhow I ccopied the rom to my internal storage but it still shows the error- Failed to mount system_root and vendor(invalid argument). How do I fix that
Click to expand...
Click to collapse
Device system and vendor formated i think

i have no os, how do i flash my custom rom, via adb or normal flash?

Why are you declining follow my tutorial?

@aheadofsingularity do not waste your time at stupid HELP PLEASE!!! threads

[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