Database Develop

Fastboot Confusion

SOLVED
My cell phone is rooted already and i am trying to clear it through
fastboot erase system -w
fastboot erase boot
I've downloaded the fastboot binary into my C:\android-sdk-windows\tools directory.
What do i need to do in command prompt to be able to run these lines

[Q] Help: Unable to flash TWRP on unlocked bootloader after 4.4 update

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

[Q] Bricked my TF701T

Hi guys..really need help from someone, i'm desperate now.. I am a newbie..so please explain me step by step what should i do next..
I tried to downgrade from kitkat to jb so i can root it without unlocking my tablet and loosing the warranty...i watched a tutorial that sayd that flasing a blob from a UL-K00C-WW-10.26.1.18-user.zip will restore the tablet to stock..but nothing..he cant boot to android no more. Stay in the asus logo with the nvidia tegra pwd. Those are some commands i tried in in fastboot till now and even to extract that update and rename it to T4_UPDATE.zip and put it on a fat32 sdcard...
Code:
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 -w
fastboot -i 0x0B05 format system
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system user.zip
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 format data
fastboot -i 0x0B05 format cache
Any help please ?! Thanks in advance.
LE: I forgot..i also flash a recovery img of macallan BL, i though it was a recovery stock img...

Please...someone help me!

Zuzuitu said:
Hi guys..really need help from someone, i'm desperate now.. I am a newbie..so please explain me step by step what should i do next..
I tried to downgrade from kitkat to jb so i can root it without unlocking my tablet and loosing the warranty...i watched a tutorial that sayd that flasing a blob from a UL-K00C-WW-10.26.1.18-user.zip will restore the tablet to stock..but nothing..he cant boot to android no more. Stay in the asus logo with the nvidia tegra pwd. Those are some commands i tried in in fastboot till now and even to extract that update and rename it to T4_UPDATE.zip and put it on a fat32 sdcard...
Code:
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 -w
fastboot -i 0x0B05 format system
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system user.zip
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 flash boot boot.img
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 reboot
fastboot -i 0x0B05 format data
fastboot -i 0x0B05 format cache
Any help please ?! Thanks in advance.
LE: I forgot..i also flash a recovery img of macallan BL, i though it was a recovery stock img...
Click to expand...
Click to collapse
So let me get this straight:
Your bootloader is locked - correct?
If yes, you cannot flash a recovery and you cannot use any of the fastboot commands you posted.
As far as I know you cannot downgrade from the KitKat firmware to JB either, which is supported by what the instructions on the Asus website state...
Can you still boot into the bootloader and the stock recovery?
If yes, I would just download the latest Asus firmware, extract it once and copy it to a microSD.
Insert it and boot to recovery. If it still works it should recognize the Asus file and flash it.
At least that would get you back to a working system.
I'm not sure why you wanted to just root the tablet - it's a waste of time IMHO. The TF701 runs great on stock and yes - even better on a custom rom. But why would you need just root?

Hello and thanks for replying.
Now, since all this commands it's giving me bootloader error 0x0000 thing but still, even when the bootloader was working the update was not working from the microSD, stopped immediatly.
Anyway, i still can enter in the fastboot where is the rck, android and the wipe thing. What should i do now?
Stupid me, just want it to root it and use a mod on a game..
Thanks in advance.

Zuzuitu said:
Hello and thanks for replying.
Now, since all this commands it's giving me bootloader error 0x0000 thing but still, even when the bootloader was working the update was not working from the microSD, stopped immediatly.
Anyway, i still can enter in the fastboot where is the rck, android and the wipe thing. What should i do now?
Stupid me, just want it to root it and use a mod on a game..
Thanks in advance.
Click to expand...
Click to collapse
Describe in detail, step-by-step, how you tried to flash the official Asus firmware.
I cannot help you if I have to guess at what you did....

Ok, first of all i download the Jelly Bean which is version 10, i extract it and watching a tutorial i flash the blob file from inside tough it will give me back to that stock.
This step costs me because it didnt boot it anymore in the android. After that i saw that i can put the firmware inside a microSD and tablet it will start updating the files/firmware. I put it and not Hung happened.. I changed the name Into T4_UPDATE and restart it. The tablet star it to update but after a while when it sayd: deleting file, stopped and give me error. So, i want it to delete the myself and enter it in fastboot and i execute the erase and format system, cache, appdata and data, which formating data freezzed the cmd and nothing happened. I then tried again to update it from microSD but now failed from the start... I did wrong executing those commands...
Then i again tried to execute the commands which i put the in the code tag but without luck. I also tried to flash recovery.img thoughing it was the stock one, but was from maccalan guy s-o now appears his details when i'm entering in the recovery with the 3 option: rck, android and wipe thing.
This is all, can i do something even if the bootloader is locked, or i need to send it to repair?
Thanks in advance.

Zuzuitu said:
Ok, first of all i download the Jelly Bean which is version 10, i extract it and watching a tutorial i flash the blob file from inside tough it will give me back to that stock.
This step costs me because it didnt boot it anymore in the android. After that i saw that i can put the firmware inside a microSD and tablet it will start updating the files/firmware. I put it and not Hung happened.. I changed the name Into T4_UPDATE and restart it. The tablet star it to update but after a while when it sayd: deleting file, stopped and give me error. So, i want it to delete the myself and enter it in fastboot and i execute the erase and format system, cache, appdata and data, which formating data freezzed the cmd and nothing happened. I then tried again to update it from microSD but now failed from the start... I did wrong executing those commands...
Then i again tried to execute the commands which i put the in the code tag but without luck. I also tried to flash recovery.img thoughing it was the stock one, but was from maccalan guy s-o now appears his details when i'm entering in the recovery with the 3 option: rck, android and wipe thing.
This is all, can i do something even if the bootloader is locked, or i need to send it to repair?
Thanks in advance.
Click to expand...
Click to collapse
You cannot change bootloader or recovery if your tablet is locked. I have no idea what happened when you tried to do that...
You also cannot downgrade the stock firmware from the 11.4.1.27 version.
So your best bet to get the tablet back probably is:
Download the correct SKU (WW, US, JP...) for your tablet.
Extract that file ONCE and copy the resulting zip file to the root of a fat32 formatted microSD. Do not put it into any folders - just copy it to the card.
Insert the card, enter recovery (RCK) and it should find the firmware file and flash it.
Good luck!
Edit: If the above does not work, try to rename the once extracted firmware file to T4_SDUPDATE.zip and copy that to the root of the microSD.
Note the name! You renamed incorrectly when you tried to flash the 10. firmware!!

I just tried now again but i cant enter rck because is giving me bootloader error 0x0000 something like that. What next?

Zuzuitu said:
I just tried now again but i cant enter rck because is giving me bootloader error 0x0000 something like that. What next?
Click to expand...
Click to collapse
I'm sorry friend, but with a locked bootloader Asus is your only option left. Get a quote before you accept their repair. They will probably replace the motherboard and it could be costly....

I call them and in the e next days they will send it in their laboratory. I will pay something even if its in warranty?
Thanks you for your time. Cheers.

Yeah, you will pay.That is why things like this void warranties. Because if you screw up your device, why should Asus pay out?
Sent from my K00C using XDA Free mobile app

[HELP]Moto G hard bricked

Hello guys
Today morning i was on cyanogenmod11 and after some time i decided to restore back to stock Lollipop so i restored a backup of Lollipop system image and suddenly a error poped up saying unable to mount /data /system
I thought this might me minor issue then i tried using fastboot to flash the stock lollipop images
When i started the flashing process i got some serious errors on my cmd
"Failed to erase partition"
"failed to write partition"
And for now only Fastboot Mode is working with UTAG "flashfail" error
i tried to flash recovery images and partition gpt file but no luck looks like my partitions are messed up bad
have a look at my attachments :crying:

any help would be appreciated

Hello ?anyone there?
Sent from my GT-S5830i using XDA Free mobile app

haytham.kenway said:
Hello ?anyone there?
Click to expand...
Click to collapse
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.

doppelhelix said:
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post

haytham.kenway said:
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post
Click to expand...
Click to collapse
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.

doppelhelix said:
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.
Click to expand...
Click to collapse
dude i know how to flash these images,and i tried latest version of fastboot from google still problem persists

Hard brick xt1775 unbricked.

Hello everyone.
My phone was hard bricked 3 monhts ago.
And today I unbrick it.
I use different model(E4 sprint) unbrick file but it work.

.........

......

cAN YOU SHARE THE METHOD?

help
ismail0100 said:
Hello everyone.
My phone was hard bricked 3 monhts ago.
And today I unbrick it.
I use different model(E4 sprint) unbrick file but it work.
Click to expand...
Click to collapse
please share the metod. I have a xt1775 model phone from lenovo, international version, and I cant unbricked

johita2006 said:
please share the metod. I have a xt1775 model phone from lenovo, international version, and I cant unbricked
Click to expand...
Click to collapse
I use this topic. (https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408)
Fisrt Message have a unbrick.img file link on mega. I download this unbrick.img file. I know different phone model but it work.
After use this topic(https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012)
0) Put the Moto g5 on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) (dont do it this part)Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) (For us unbrick.img not mmcblk0.img)Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=unbrick.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
after write file on sdcard use this command and use last firmware.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

ismail0100 said:
I use this topic. (https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408)
Fisrt Message have a unbrick.img file link on mega. I download this unbrick.img file. I know different phone model but it work.
After use this topic(https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012)
0) Put the Moto g5 on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) (dont do it this part)Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) (For us unbrick.img not mmcblk0.img)Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=unbrick.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
after write file on sdcard use this command and use last firmware.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
What did you name the sd card?

paigao said:
What did you name the sd card?
Click to expand...
Click to collapse
I did not remember sorry. Probably not change