Hello ,
First of all Thanks to Buster99 and his Solution for fixing this problem,
This guide is for helping you to fix Unrecoverable bootloader error, Hope it will help you out of this problem,
Step-by-step guide:
1 - Download the Stock rom .
2 - Extract downloaded file and put the blob file in fastboot folder.
3 - if you need adb,apx,fastboot drivers , i attached these drivers so you can download it from below.
4- Power off the tablet.
5- Connect the tablet to PC via USB cable.
6- Boot your tablet into the recovery mode. Press and hold Volume DOWN+Power keys together.
7- Open command prompt. For this, go to Start. Select ‘Run’ and type ‘cmd’. go to your fastboot folder.
8- type following command-lines in cmd-window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob(depending on where you stored extracted blob file)
fastboot -i 0x0B05 reboot
Remember : Wait until you've seen in the CMD window that erase or upload is finished.
hope this solution works for whoever is facing the same problem,
I'm very glad, you saved your tablet
Related
Hi there,
I'm new to all things development. I have an HTC Sensation on Virgin mobile in Canada. I am trying desperately to root my phone and I have followed this guide (http://forum.xda-developers.com/showthread.php?t=1632553). I've done lots of searching on this forum and google and can't find anyone with my specific problem.
I have put the SupperSU.zip file into my SD root, unlocked my bootloader through the HTC dev website and flashed CWM using the One X program. However, when I try to boot into recovery it stalls on the white HTC loading screen. I have tried to boot into recovery using One X, a command control from my android folder on my computer and using the power button and down volume button but it always stalls. Since I cant boot into recovery I cant use CWM flash the SuperSU.zip, which I understand finishes the rooting process.
Also: I am pretty sure my drivers are up to date but when I tried to install the drivers from One X it always interrupts the installer saying the Device is in Use...andnI dont know if that means my phone (which its not) or my computer. I uninstalled my antivirus because I read that might be blocking it... but still no luck!
I would really appreciate any help or guidance you can offer! I am a complete newbie when it comes to this and I have done my best to search out answers and tutorials before coming here for help.
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
rzr86 said:
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
Click to expand...
Click to collapse
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
kellai15 said:
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
Click to expand...
Click to collapse
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
rzr86 said:
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
Click to expand...
Click to collapse
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
--
I also tried to open a command window there and reflash the recovery.img by typing fastboot flash recovery recovery.img ...except it said "error: "cannot load recovery.img" except the file is definitely in that folder and named recovery.img
kellai15 said:
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
Click to expand...
Click to collapse
try this
fastboot boot recovery.img
rzr86 said:
try this
fastboot boot recovery.img
Click to expand...
Click to collapse
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
kellai15 said:
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
Click to expand...
Click to collapse
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
rzr86 said:
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
Click to expand...
Click to collapse
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
kellai15 said:
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
Click to expand...
Click to collapse
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
rzr86 said:
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
Click to expand...
Click to collapse
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
kellai15 said:
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
Click to expand...
Click to collapse
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
rzr86 said:
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
Click to expand...
Click to collapse
I have now flashed 4ext and installed a customROM! Couldn't have done it without your help
Hi to all from a new user
Your help has been useful to me several times but I can not solve this last problem.
I have an Asus tf300tl: after unlocking the bootloader and installed the cwm the terminal will start cwm mode only.
The I cwm release Cache errors in the mount, partition, system, sd etc. In addition, the terminal does not start in download-mode and therefore can not act fast-boot mode.
With adb I can get shell access and view the content. With adb-push can not install a *. Zip and when I enable sideload from cwm communication between the PC and the device stops.
I apologize for my English
thanks a buster99:
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
thi is the guide:
1) download the firmware from the asus website and unpack it so that you have copied the file blob that will go in a folder
(named TF300t) that go inside the folder adb
2) connect the tablet to your PC by installing the drivers, so that the PC sees it as android bootloader interface (or adb)
3) avoid apx you only lose time and the process should be done in nvflasher
4) Reset the tablet, while holding vol. -
5) when you restart let the symbol RCK do not press anything
6) click on Run CMD
7) c:\users\yourname> (if you have set at the beginning of the computer configuration)
8) type cd:\adb press enter
9) type cd:\fastboot
10), make sure a file blob extracted from the firmware using the command :dir
11) started to write in this order:
12) fastboot -i 0x0b05 erase system
13) fastboot -i 0x0b05 erase recovery
14) fastboot -i 0x0b05 erase userdata
15) fastboot -i 0x0b05 erase boot
16) fastboot -i 0x0b05 erase misc
17) fastboot -i 0x0b05 erase cache
18) fastboot -i 0x0B05 flash system c:\ adb\TF300t\blob (if all goes well the symbol rck it flashes, and a progress bar appears blue
to indicate that you are copying the firmware on the tablet)
19) fastboot -i 0x0B05 reboot
Asus tf300tl bricked
m&n69 said:
thanks a buster99:
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
thi is the guide:
1) download the firmware from the asus website and unpack it so that you have copied the file blob that will go in a folder
(named TF300t) that go inside the folder adb
2) connect the tablet to your PC by installing the drivers, so that the PC sees it as android bootloader interface (or adb)
3) avoid apx you only lose time and the process should be done in nvflasher
4) Reset the tablet, while holding vol. -
5) when you restart let the symbol RCK do not press anything
6) click on Run CMD
7) c:\users\yourname> (if you have set at the beginning of the computer configuration)
8) type cd:\adb press enter
9) type cd:\fastboot
10), make sure a file blob extracted from the firmware using the command :dir
11) started to write in this order:
12) fastboot -i 0x0b05 erase system
13) fastboot -i 0x0b05 erase recovery
14) fastboot -i 0x0b05 erase userdata
15) fastboot -i 0x0b05 erase boot
16) fastboot -i 0x0b05 erase misc
17) fastboot -i 0x0b05 erase cache
18) fastboot -i 0x0B05 flash system c:\ adb\TF300t\blob (if all goes well the symbol rck it flashes, and a progress bar appears blue
to indicate that you are copying the firmware on the tablet)
19) fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
not start in download-mode
Hello,
I have the TF300T and installed twrp 2.5 and the android 5.0 rom. After a some time my TF300T became slow so I went in twrp and did a advanced wipe.
After that I wanted to install the again the rom but I got errors, so I did a reboot and now I have nothing expert the Teamwin logo that keeps booting.
I think the file format of the system is corrupted. Any Idea what I can try? The WIPE in the start menu when you power on the device with power down key I see the 3 logo's.
SOLVED: thanks to fastboot I installed the stock firmware. All works fine now.
Im again in TWRP thanks to fastboot
Code:
1) to have the correct driver for fastboot you can install asus PC sync from the asus website
2)download fastboot from internet and extract to c:\fastboot\
3)download from goo.im openrecovery-twrp-2.4.4.0-tf300t-4.2.blob and put in the fastboot directory
4)boot the tf300t holding power + volume down and connect at the pc
5)open command prompt (run cmd.exe) and navigate to c:\fastboot\
6) to know if the device is connected correctly use the command "fastboot devices" it should show you a string with numbers and letters
7)to install the recovery use the command fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
8)Reboot with the command fastboot -i 0x0B05 reboot-bootloader
Now the big problem that I have is that it cannot mount the /data, /system, ...
Any help would be welcome
Hi i use this rom http://forum.xda-developers.com/moto-g/development/stable-aosp-caf-t3284323
and i have a problem , my phone rebooted and stuck after the boot animation in a black screen.
I tried wipe cache , nothing and then i tried fix permission and now i cant go into my recovery , restarts itself, flassed revovery again , same thing.
Now i want to flass the rom with fastboot , what wipe commands i have to do?
I found online this
fastboot erase system -w
fastboot erase boot
fastboot update rom.zip
is this ok?
Thanks
[email protected] said:
Hi i use this rom http://forum.xda-developers.com/moto-g/development/stable-aosp-caf-t3284323
and i have a problem , my phone rebooted and stuck after the boot animation in a black screen.
I tried wipe cache , nothing and then i tried fix permission and now i cant go into my recovery , restarts itself, flassed revovery again , same thing.
Now i want to flass the rom with fastboot , what wipe commands i have to do?
I found online this
fastboot erase system -w
fastboot erase boot
fastboot update rom.zip
is this ok?
Thanks
Click to expand...
Click to collapse
I literally JUST unbricked my Moto G XT1032 after searching for a long while and piecing instructions together. Here's how:
PREPARATIONS
1) Download XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip
This is the stock firmware you need to flash. I haven't tried it with anything else. The instructions that follow are specific to this file, although you should be able to follow the general idea to install different ROMS.
Get the firmware (or a different one) here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
2) Ensure that you also have the correct Motorola drivers for this phone. Download 32-bit or 64-bit versions depending on your PC.
Get them here http://forum.xda-developers.com/showthread.php?t=2550635
3) Download MFastBoot v2
Go to http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518
or simply download the file at (https://mega.nz/#F!xUh10AAD!5NvRwDf6eAfjE3bUWZfk7g)
Note: From what I've experienced, you CANNOT use normal Fastboot on this phone. You will keep getting errors such as Failed (remote failure). You have to use MFastBoot.
Open the downloaded file. There will be two other zip files inside it. Extract all contents of mfastboot-v2.zip to a folder of your choice.
4) Download TWRP Recovery. It's usually a good idea to have a recovery, even though it's not used to flash the ROM.
Get the highest version of it here: https://dl.twrp.me/falcon/
Extract the .img file to the SAME folder as where you extracted mfastboot and rename it to twrp.img (not really necessary, but it's easier to type into the command prompt).
5) Extract all contents of XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip to the SAME folder as where you extracted mfastboot.
6) Ensure the phone is off. Hold VOL DOWN first, and then press POWER button for about 5 seconds, then release POWER button before releasing VOL DOWN. You should be in fastboot mode. Plug the USB cable into the phone now.
If you see Device is locked. Status 0, follow the instructions in the UNLOCKING THE BOOTLOADER section.
If you see Device is unlocked. Status 3, continue to step 7.
FLASHING THE FIRMWARE
7) Open the folder where everything has been extracted to.
Hold CTRL+Shift and right click in an empty area of the folder. You will see a normally hidden option to "Open Command Window Here". Select that option and a command prompt window will open. If you are not seeing this, you may not have administrative rights on your account.
Type this into the command prompt: mfastboot reboot
I'm unsure if this is required or not, but mfastboot wouldn't work unless I rebooted it from the command prompt before any other instruction.
8) This is the step where the TWRP recovery and ROM files are flashed.
Type the following into the command prompt, pressing enter after each line. Alternatively, just copy each line and right click>paste into the command prompt. Credits to AgentChaos for the following:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot flash recovery twrp.img
If you used normal fastboot at this step, it will fail and give you an error of "Failure (remote failure)". or it will say it could not find or write to some directory.
Hopefully it does not fail, and should say OKAY after writing each file. This step will take several minutes.
If you used a different firmware than I did, you will have to flash the correct files to the correct directories, and they MAY be different than the ones listed above. I think (but I am not sure) that the only difference would be having to flash and additional sparsechunk.3 or 4. I would not suggest doing this if you aren't sure.
After all files have been flashed, do one final mfastboot reboot and press VOL DOWN and select Recovery, then press VOL UP to start it. You should see the TWRP recovery screen. The screen may glitch out but otherwise be operable. You can press REBOOT then SYSTEM to start the phone normally.
I hope this has been helpful.
UNLOCKING THE BOOTLOADER
A) Open the folder where everything has been extracted to.
Hold CTRL+Shift and right click in an empty area of the folder. You will see a normally hidden option to "Open Command Window Here". Select that option and a command prompt window will open. If you are not seeing this, you may not have administrative rights on your account.
Connect the USB and type this into the command prompt: mfastboot oem get_unlock_data
You will see a string of characters that looks like:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
B) Go to Motorola's unlocking bootloder tool website here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You will need to create an account with a legitimate email account, which takes 1-2 minutes.
There is a text box on Motorola's site where you need to type the exact combined code you received from top to bottom with symbols included, but don't include "(bootloader)". Agree to their terms and services.
C) You will receive an email with your bootloader unlock code.
Go to the command prompt and type: mfastboot reboot to reboot the device. Alternatively, just reboot it manually.
Type: mfastboot oem unlock UNIQUE_KEY where UNIQUE_KEY is the unlock code you received. The screen should go black and you should see the word "Unlock...". The phone may stop responding at this point, in which case simply wait 1-2 minutes to ensure it is finished doing what it was doing, and then manually reboot it.
Boot into fastboot again and now your device should say "Device is unlocked. Status 3"
Thought I would make a thread, which could help someone.
My bootloader is unlocked
I was using Marshmallow LOS 13 unofficial build by Qbanin.
But these directions should be the same for anyone on MM unlocked.
You will need to know how to use ADB from PC and have platform-tools.
The reason I upgraded to 14.1 unofficial instead of official is because official requires the MM modem, and I had already flashed the stock nougat rom when i started looking for roms to flash.
Download the Nougat Stock Firmware:
https://androidfilehost.com/?fid=889964283620765304
Drop the contents of unzipped stock nougat into your platform-tools folder.
Hit the shift button and right click the mouse and 'open command window here'
Connect your MM device to your pc - booted into your current rom with usb debugging enabled
In the command windows type 'adb devices', you may need to confirm access on the screen of your phone, and try the command again.
Make sure your device is listed and authorized.
Type in the command window 'adb reboot bootloader'
Your device will reboot into the bootloader and is ready to program
Run these commands to flash stock nougat, make sure each command succeeds.
If they do not, run any command that fails multiple times until it succeeds and move on to the next, if a command fails more than 5-10 times in a row, start over from the beginning.
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata -w
fastboot reboot
If your device reboots into bootloader repeatedly run this command:
fastboot oem fb_mode_clear
fastboot reboot
Your device will reboot, wait a while during Nougats first run.
Once Nougat is loaded and you pass setup, enable developer options and then ADB usb debugging.
run 'adb devices' command again and confirm the device is listed and authorized.
Download latest official TWRP 3.2.1.0
https://eu.dl.twrp.me/clark/
rename the file to twrp.img and place in the platform-tools folder
Download LOS 14.1 Unofficial (the latest build 2/23 is for MM modem: avoid)
Grab the 2/18 build or read around the forums for latest compatible build
https://androidfilehost.com/?w=files&flid=131793
Move the file to the root of your external sd card via MTP.
Download ARM64 7.1 OpenGapps and move to root of your external sd card
http://opengapps.org/
Run these commands in the command prompt
adb reboot bootloader
adb flash recovery twrp.img
Press 'down vol' for the recovery option and then press the power button
Phone should reboot into TWRP recovery
Allow TWRP to modify contents by swiping at the bottom.
Remember TWRP makes you swipe if your screen shuts off, so you may need to swipe twice to peform operations, ALWAYS PAY ATTENTION IN TWRP.
Select WIPE in twrp, and then ADVANCED WIPE.
Select the Data checkbox and hit the Repair or Change File System at bottom.
Select CHANGE FILE SYSTEM at bottom right.
Select F2FS and proceed with the format.
Select WIPE (again) from home screen choose to wipe dalvik,system,internal & cache
Select INSTALL from home screen and choose the LineageOS 14.1 build.
You will need to SELECT STORAGE at bottom left and choose your external card.
Add the openGapps 7.1 to the install queue as well.
Swipe to confirm flash and let the new rom and gapps install.
After complete wipe dalvik/cache and reboot.
Enjoy your new rom.
I also flashed systemless root in twrp.
https://drive.google.com/file/d/1GjKdxvoTi9YCU43HIy2XTTcB-bGnNn84/view?usp=sharing
This is for unofficial 14.1 only using the 2/10 or 2/18 build only.
The 2/23 build as I understand is a test build for MM modem only.
All future builds should be verified around the forum with hashbangs notes/recommendations as they do not exist at the time of this post.