I have been going at it for a week straight and unable to find help. I am using Nexus Root Tool Kit 2.1.0. My Device is unlocked and OEM unlocked. However when i try to root the phone restarts into AP Fastboot Mode and nothing happens but the program seems like its trying but just unable to finish.
Log File:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini 3099
- AndroidDeviceListFull.ini 3099
- AndroidDeviceListFlash.ini 3099
SHAMU-SHAMU: Android 6.0.0 - Build: MRA58N
Live log initiated [2015-11-28]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Flashing Root Kernel to BOOT partition...
fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\root_kernel_shamu_mra58n.img"
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Rebooting your device...
Waiting for your device...
I have also tried to flash a custom boot.img but NRT stops at rebooting device.
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Flashing boot.img to BOOT partition...
fastboot flash boot "C:\Users\Dave\Desktop\volantis-mra58n-boot-system\boot.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
my screen just never does anything i remember last time i rooted on Android L it went with no problems.
just stays at
AP Fast boot Flash Mode (Secure)
BL: moto-apq8084-71.15 (sha-96f7faf, 2015-08-04 11:36:17)
Base Band : D4.01-9625-05.27+fsg-9625-02.104
just installed ADB and tried from command prompt to flash TWRP and i got failed (data transfer failure (unknown error) )
well, you are doing it wrong for a nexus owner, you dont need a root toolkit. to root m you need to flash any custom kernel for m as well as the latest supersu(as well as the latest twrp recovery so you can flash a custom kernel and supersu).
Don't use Root kits and follow these steps. Start from step 1 if you already have your bootloader unlocked and if you have SDK tools installed (adb and fastboot). And you should be fine...
yes wont let me install recovery TWRP
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11700 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.012s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
thats because you dont use adb for this. you have to use fastboot while you are in your recovery. read that again, FASTBOOT instead of ADB. you always use fastboot to flash the factory image or any part of it, or twrp recovery.
simms, the command he posted that failed WAS fastboot.
HOWEVER, if adb is reporting devices, you are likely either booted to android or recovery... reboot to the bootloader
(turn off device, then hold volume down and while holding vol down press and hold power until the device boots to the bootloader mode.
Make sure that you have twrp in the same folder, and that you have renamed it to recovery.img (not .img.img as a lot of people accidently do) That last part isn't completely necessary, as its really just "fastboot flash recovery <file name>", and you can replace <file name> with the name of the recovery image it doesn't HAVE to be recovey.img, and it doesn't have to be in the same folder if you include path... but people find it easier to just rename it to recovery.img, copy it to their platform tools folder and use the command you ran.
ahh.. yea @scryan i didnt see that fastboot was used(later in the post). now i see hes uding adb devices instead of fastboot devices.
As far as I can see, you are trying to flash recovery using fastboot flash recovery recovery.img while not in bootloader (or you didn't copy everything you did).
You should:
1. adb reboot bootloader (your phone will reboot into bootloader)
2. now you can write "fastboot devices" to see if your phone is recognized
2. then if it's there: "fastboot flash recovery recovery.img"
EDIT: If you still did everything correctly, quick google search said it could be problem with computer's USB port. Try another port...
I have tried every port on my pc some give unrecognized USB error while others work. If I am able to charge and transfer files along with send adb commands (restart phone,adb sees my phone) does that rule out the USB cable? I bought a pack of four on ebayhttp://m.ebay.com/itm/4x-6Ft-Micro-USB-Charger-Sync-Data-Cable-Nylon-Braided-for-Samsung-Galaxy-HTC-/221891441910?txnId=1650092351012
I no longer have the cable I used to flash marshmallow but I did use this to unlock the device.
Related
hi there,
been busy all evening on my Mac trying to unlock and root my nexus one retail. Got the phone unlocked after extensive reading on SDK and ADB Hoped that the positive flow would continue when switching over to the rooting process, but unfortunately I seem to get stuck and have failed
I downloaded the correct superboot version for my phone and placed it in my home folder (on same drive as where I successfully did the fastboot procedure for unlocking). And then I entered this in Terminal:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /superboot
suikerchiller-macbook-3:superboot suikerchiller$ chmod +x install-superboot-mac.sh
suikerchiller-macbook-3:superboot suikerchiller$ ./install-superboot-mac.sh
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... OKAY
suikerchiller-macbook-3:superboot suikerchiller$
---
As a result my phone automatically reboots into basic settings. Does anybody know what I'm doing wrong??? I'm a total n00b but am really eager to learn In a bit of trouble now as well, because I don't know what to do anymore and dare to touch my fone either.
Any help would be great. Can't wait to finally be released from Vodafone's retail nexus one terror and want to challenge all those ignorant iphone studs out there and show how cool and superior my Nexus one actually is
P.S. I searched for quite some time on the forum and couldn't find a post/thread that was related to my problem. Please forgive me if this is some sort of double post.
If your phone is unlocked, don't bother with superboot, just flash a custom recovery and use it to install the su zip...
http://forum.xda-developers.com/showthread.php?t=682828
Place the recovery image in your sdk tools folder, place the su zip on your sd card, connect via fastboot and type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Flash the su zip from recovery, and you're done!
many many thanks for the quick reply I placed the recovery image in my sdk tools folder.
However, still have a couple of questions:
I don't know what you exactly mean with a su zip??? Where can I get this file?
what do you mean with: "flash the su zip from recovery"?
I put a link in my original post. The eclair/froyo version works for gingerbread, also...
Once in recovery, you chose the flash zip from sd option, and then the chose zip from sd option, find and select the zip... It will be obvious when you do it...
sorry, it's still too much rocket science for me I guess
I uploaded the su zip file (did not unzip or rename file) to my sd card (activated usb storage and dropped the zip via Mac in the main folder of my phone).
what do you exactly mean with "connect with fastboot"? I shut down my fone first and pressed power button at same time with track ball. Then I did this:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:~ suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ cd ~
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
As you can probably see it didn't really work haha what am I doing wrong? Sorry for my n00biness!
You said you have already unlocked your bootloader. In order to unlock the bootloader I you have to connect with fastboot...
How did you unlock the bootloader?
I unlocked it via the first 7 steps of this procedure (sorry have to copy paste a lot of text because im not allowed to post outside links on forum yet haha):
-----
Connect your Nexus One to your PC/Mac and turn it off.
Hold the trackball and hit the power button (while holding the trackball). You should see the following bootloader screen.
Now from the files you downloaded previously, you will see a folder called ‘fastboot‘ (if you extracted fastboot.zip that is!).
On a Windows machine – launch Command Prompt and CD to fastboot folder. (Type in ‘cd ‘ (without the quotes and drag and drop the fastboot folder to the command prompt). Type in ‘cd fastboot‘ again and now type the following command ‘fastboot-windows oem unlock‘ (without quotes) and hit enter.
On a Mac or Linux machine – launch the Terminal and CD to fastboot folder (type in ‘cd ‘ and drag and drop the folder. Now hit enter.). Now CD to the other fastboot folder and type the following (without quotes): ‘./fastboot-mac oem unlock‘ (for Mac) or ’./fastboot-linux oem unlock’ (for Linux) and hit enter. You will see the following. Ignore the error.
This is the screen that you will see now. Use the volume button (on the side) to select ‘Yes’. (Please read the full message displayed on the screen thoroughly). Now push the Power button to select this option (weird, I know. Trackball would have been a better choice to select!).
Great! You have successfully unlocked the bootloader! You will see the unlock image while your phone boots up.
----
I did this successfully and had the black screen and selected unlock phone. So when I press the power button & trackball at same time now I get a white screen now and it says in pink on top: ***Unlocked***
Ok substitute the term fastboot-mac instead of fastboot, into my previous instructions
damn, still doesn't seem to be working:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
----
it's really weird, it looks like my fastboot is not responding anymore... Any idea what's going wrong here???
thanks so much for taking time and helping with figuring this one out!!!
Just tested something. When my phone is switched on normally and connected via USB, Terminal recognizes it as an adb device. However, when I switch into fastboot, Terminal doesn't recognize it:
---
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
HT07YP804207 device
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
adb will only work when it can see the adbd on your phone, so the phone had to be booted to either recovery or fully bolted.
fastboot will only connect when your phone is booted in fastboot. If its not connecting, reboot your phone and mac and try again...
suikerchiller said:
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
Click to expand...
Click to collapse
Sorry, just re-read this...
Command not found, NOT device not found.
You should be typing fastboot-mac, not fastboot...
Do you have a file called fastboot-mac in the same folder as your adb and recovery img?
rebooted my mac and phone... Still no difference, this is my latest command:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
---
can this be the reason: my fastboot folder is in a different (other) folder than my 'android sdk' folder... should i drag and drop fastboot into the tools folder of sdk???
YES!
Put the fastboot-mac file in the same folder as the other stuff!! xD
haha ok, so I copied my fastboot-mac file (original file from fastboot folder) into AndroidSDK/tools folder. It's in the same folder now where the .img file is in as well.
But it still doesnt seem to be working. These are the commands that I have been using:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac boot recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$
---
What's going wrong??? I'm going slightly mental now. Also running out of beer at same time. Not a good combination
can you list the contents of that folder, and tell me what result you get?
this is the list of files in my AndroidSDK/tools folder:
--
suikerchiller-macbook-3:tools suikerchiller$ ls
Jet hierarchyviewer
NOTICE.txt hprof-conv
adb-mac layoutopt
adb_has_moved.txt lib
android mksdcard
ant monkeyrunner
apkbuilder proguard
ddms recovery-RA-passion-v2.2.1-CM.img
dmtracedump source.properties
draw9patch sqlite3
emulator traceview
etc1tool zipalign
fastboot-mac
---
and here are the commands for fastboot, in case they can be of any usage
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
Hmmmmm, well the file is there, so that's really weird because you mac is definately saying that it's the command it can't find...
I'm not much of a mac guy, but I do know that your mac is the one having the problem...
Try:
./fastboot-mac flash recovery name-of-recovery.img
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
sending 'recovery' (3380 KB)... OKAY
writing 'recovery'... OKAY
I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?
danherbert said:
I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?
Click to expand...
Click to collapse
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Sent on my Moto X
flashallthetime said:
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Click to expand...
Click to collapse
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.
danherbert said:
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.
Click to expand...
Click to collapse
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Sent on my Moto X
flashallthetime said:
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Click to expand...
Click to collapse
Your suggestion worked. I didn't have easy access to a Windows machine so I couldn't use rsdlite. I had to manually reset to stock. For anyone who stumbles upon this thread, these are the steps I used which worked for me:
Make sure adb and fastboot from the Android SDK are already part of your PATH.
Download moto-fastboot for Mac OS X
Download the Kitkat 4.4 update for Sprint (Make sure to download the version that matches the build number from "Settings -> About Phone" in your device)
Download the Kitkat 4.4 version of TWRP
Extract the factory image .zip to a folder
Copy the moto-fastboot binary to the folder you extracted the factory image to and rename it to "mfastboot"
Copy the TWRP .img file to the folder with the factory image files
Create a file named "factoryreset.sh" and paste the following as its contents
Code:
#!/bin/sh
FASTBOOT=./mfastboot
$FASTBOOT getvar max-download-size
$FASTBOOT oem fb_mode_set
$FASTBOOT flash partition gpt.bin
$FASTBOOT flash motoboot motoboot.img
$FASTBOOT flash logo logo.bin
$FASTBOOT flash boot boot.img
$FASTBOOT flash recovery recovery.img
$FASTBOOT flash system system.img
$FASTBOOT flash modem NON-HLOS.bin
$FASTBOOT erase modemst1
$FASTBOOT erase modemst2
$FASTBOOT flash fsg fsg.mbn
$FASTBOOT erase cache
$FASTBOOT erase userdata
$FASTBOOT erase customize
$FASTBOOT erase clogo
$FASTBOOT oem config carrier sprint
$FASTBOOT oem fb_mode_clear
Open a terminal and navigate to the directory you created
On your device, navigate to "Settings -> About Phone" and tap on the build number 7 times to enable developer mode
Go back to the main "Settings" screen, open "Developer Options", and enable USB Debugging
Connect your device to your computer. Go back to your device, make sure you choose to trust your computer to use ADB in the dialog that pops up, then run the following command from your terminal
Code:
adb reboot-bootloader
Once your device is in fastboot mode, run the command
Code:
sh factoryreset.sh
From the device choose to boot normally and wait for it to finish booting completely.
Run the command
Code:
adb reboot-bootloader
Once the device is in fastboot mode again, run the command
Code:
fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
From your device, power up normally then reboot into the recovery. If everything went smoothly you'll boot into TWRP recovery.
Code:
adb reboot recovery
Hi,I have a problem with bootloader ,I can not get to it by combinations power+vol+ or power + vol- is my google log unless it is bootloop I wanted to come back with version google edition on sense, I wanted to go back to stock possessed s-off or unlocked bootloader so I uploaded 1.28.401.7 firmware mode oem rebootRUU
Copy downloaded .zip to adb location (e.g. c:/android-sdk/platform-tools/)
Re-name .zip file to HTC.zip
Connect device to the PC.
Open command prompt; cd to HTC.zip location (cd c:/android-SDK/platform-tools/)
Type: fastboot reboot-bootloader or boot your device in fastboot mode (vol down + power ===> fastboot)
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip HTC.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash HTC.zip again just to make sure.
Type: fastboot flash zip HTC.zip and wait for process to complete
Type: fastboot reboot.
and after uploading successfully,standing on the log google,and I can not enter the bootloader sorry for my english
delete
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
I am on mac so cannot use Mi Flash
EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.
Only i dont understand: (recomend this others from this year locked boot loader) ?
EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/
every time I type:
fastboot oem edl
the screen of the smartphone goes off
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?
No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.
Is Snapdragon SDK actually Qualcomm drivers?
helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
zepolyerf said:
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
Click to expand...
Click to collapse
Drivers installed?
Hi! How can I check if drivers are installed? I'm on Linux, if that matters.
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
V0latyle said:
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
Click to expand...
Click to collapse
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
zepolyerf said:
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
Click to expand...
Click to collapse
Your device might not have a recovery partition; in A/B partition layout devices, recovery lives in the boot image.
A bit of an explanation:
When you use fastboot boot <image> you're telling the device to load the image you're sending - so if you use fastboot boot twrp.img you're telling it to load the TWRP.img on your computer. This is what you should be using if you want to boot TWRP.
When you use fastboot flash <partition> <image> you're telling bootloader to flash the specified partition with the specified image. So, if you used fastboot flash boot twrp.img, bootloader will overwrite /boot with the TWRP image...meaning the device will only boot into TWRP.
As for why the device would only boot into stock recovery after you flashed the custom ROM, I suspect that it didn't flash the kernel, or otherwise may have corrupted the boot image. So, when the device tries to start the kernel, it failed and just boots into recovery instead.
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
zepolyerf said:
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
Click to expand...
Click to collapse
Reboot to bootloader. If you're currently in recovery mode, cancel the command (Ctrl+C) and use adb reboot bootloader. If you're currently in bootloader but it's not responding, just use the button combo to force a reset.
Remember, you can only use fastboot commands in bootloader mode. If you're in recovery, you can only use some ADB commands, but in this case, I don't think that will be much help.
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
I went into fastboot mode by pressing Vol Down + Power buttons.
Plugged the phone in to my Linux machine. Have VirtualBox recognize my device.
Opened MiFlash tool. Selected the flash rom from Xiaomi's site. Got an Antirollback error. Here's the logs:
Code:
[4:41:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:25 AM]:GetScriptDevices
[4:41:28 AM]:add device f8b471a6 index 0
[4:41:48 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:48 AM]:GetScriptDevices
[4:41:51 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:41:51 AM]:add device f8b471a6 index 0
[4:41:51 AM]:Thread start,thread id 11,thread name f8b471a6
[4:41:51 AM]:start process id 4212 name cmd
[4:49:16 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:16 AM]:GetScriptDevices
[4:49:16 AM]:add device f8b471a6 index 1
[4:49:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:24 AM]:GetScriptDevices
[4:49:24 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:49:24 AM]:add device f8b471a6 index 1
[4:49:24 AM]:Thread start,thread id 12,thread name f8b471a6
[4:49:24 AM]:start process id 1704 name cmd
[4:49:25 AM]:Thread stopped, thread id 12, thread name f8b471a6
[4:51:22 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:51:23 AM]:GetScriptDevices
[4:51:23 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:51:23 AM]:add device f8b471a6 index 1
[4:51:23 AM]:Thread start,thread id 19,thread name f8b471a6
[4:51:23 AM]:start process id 3400 name cmd
[4:52:26 AM]:GetUserInfo
[4:52:39 AM]:authentication edl error:Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[4:56:31 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:56:31 AM]:GetScriptDevices
[6:00:17 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:18 AM]:driver oem5.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\Windows\INF\oem5.inf,result True,GetLastWin32Error
[6:00:19 AM]:set RegistryKey value:android_winusb.inf--oem5.inf
[6:00:19 AM]:mkdir "C:\Users\IEUser\.android"
[6:00:19 AM]:output:A subdirectory or file C:\Users\IEUser\.android already exists.
[6:00:19 AM]: echo 0x2717 >>"C:\Users\IEUser\.android\adb_usb.ini"
[6:00:19 AM]:output:
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:20 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:20 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:21 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:driver oem6.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:22 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\Windows\INF\oem6.inf,result True,GetLastWin32Error
[6:00:22 AM]:set RegistryKey value:qcser.inf--oem6.inf
[6:01:33 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:34 AM]:GetScriptDevices
[6:01:34 AM]:add device f8b471a6 index 1
[6:01:55 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:55 AM]:GetScriptDevices
[6:01:55 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[6:01:55 AM]:add device f8b471a6 index 1
[6:01:55 AM]:Thread start,thread id 12,thread name f8b471a6
[6:01:55 AM]:start process id 6280 name cmd
[6:01:56 AM]:Thread stopped, thread id 12, thread name f8b471a6
Any idea on what to do next?
BigChungus321 said:
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
Click to expand...
Click to collapse
It might as well be a brick haha. I must be dumb (very likely) or there's just not a lot of clear and comprehensive resources out there to fix this kind of thing.
Ahh anti roll back error is pretty simple to fix, you just have to remove the check from the .bat files, there are tutorials on YT that can help, after that reflash stock rom in MiFlash.
If you're worried about anti roll back, don't worry, ARB value for the device has been 3 so far so it's safe to downgrade. Goodluck
Seeing a ton of Bricked Notes on here this last week, Y`all making me nervous about doing anything with mine lol
I faced this problem in linux got around it with usb 2.0 interface doesn't worked with usb 3.0 and above but my device was different when I got this recovery flash waiting problem. Also try to updated the platform tools.
So the solution was to entirely ditch Linux and use Windows to play with fastboot and adb commands via the terminal.
I don't understand why it worked when I did it on Windows when I was using the same platform tools on Linux. Oh well.