Hello
I have a Kindle Fire HD 7 2nd gen and it is stuck on the "Kindle Fire" logo. I bought a factory cable and get a 'fastboot' screen when connected to my Windows laptop. But in ADB no devices are listed and when I try the command 'fastboot -i 0x1949 getvar product' it says ' <waiting for device>' What can I try next? Any help would be great
Thanks in advance
check the device manager of PC, then maybe you will see a warning devices. install the attach files.
Finally someone replied. I looked in Device Manager and saw something in yellow called "Tate-PVT-08". So Windows was not recognizing the Kindle. I installed the Kindle ADB drivers from rootjunkysdl.com and now "fastboot -i 0x1949 getvar product" gives me "Tate-PVT-08"
My guess it is working now, but when I try to flash boot, recovery, and system img's from the KFRT here it does nothing and I'm still stuck in "Kindle Fire" logo/bootloop. What is the problem ? Is this thing hard bricked ?
Yes. I also have similar issue:
during I'm running the "fastboot -i 0x1949 flash system system.img"
My thread
I feeling that's should be a root problem. Since during I'm running (adb shell su -c reboot fastboot) there shown a pop windows on the KFTT.
shall ask the permission
with my understanding, that should be can mount -o remount rw /system. to get rw privilege to reflash system.
But, nothing..
and sdcard, no data can be removed or deleted. Read only..
I read your thread and if you had root (I did not) that may be the issue or else try a new USB 2 port or computer. But I need to ask where you got bootloader.img from ? I found out boot.img is only the kernel and ramdisk, so it is likely the bootloader is damaged.
seskanda said:
I read your thread and if you had root (I did not) that may be the issue or else try a new USB 2 port or computer. But I need to ask where you got bootloader.img from ? I found out boot.img is only the kernel and ramdisk, so it is likely the bootloader is damaged.
Click to expand...
Click to collapse
a long story. Before, I rooted it to remove some initial software from official version. then, turn it down a long time, about 2 years. Last week, I'd like to reboot it to check. Then, I found the system looks like to read only on lastest time. Even login system to remove any software, after reboot. they would be back. I tried to flash the img, such as boot, recovery, system and so on. you can check.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
except kfhd7*.img . I reflashed them one by one, except system, other should be OK.
I tried "adb shell mount -o remount rw /system" or "chmod 669 " but doesn't work.
looks I have to click the allow the "shell" privilege as same as I ran "adb shell su"
I tried to hold the root to run all commands....
That is a lot of partitions in this screenshot, where did you find and get them from? The ones of interest are bootloader, crypto, dfs, dkernel, efs, idme, and xloader. Most of these I have no clue what they do and are for. Other than the obvious like boot and bootloader. I think xloader has something to do with the bootup process too. I'm not able to use ADB at this point, only fastboot, and that only takes img files, and system is a folder in the firmware .bin files from Amazon. There is no easy way to convert that into a system.img
seskanda said:
That is a lot of partitions in this screenshot, where did you find and get them from? The ones of interest are bootloader, crypto, dfs, dkernel, efs, idme, and xloader. Most of these I have no clue what they do and are for. Other than the obvious like boot and bootloader. I think xloader has something to do with the bootup process too. I'm not able to use ADB at this point, only fastboot, and that only takes img files, and system is a folder in the firmware .bin files from Amazon. There is no easy way to convert that into a system.img
Click to expand...
Click to collapse
where did you find and get them from? From Website. Yes, official way only the bin file. But if you'd like to write the KFTT with fastboot to flash. only img. files.
There is no problem on the img files. only I can't flash. There should be a way to format /system as re-partition something like that. Or a way to reset chip of memory.
03300209 said:
where did you find and get them from? From Website. Yes, official way only the bin file. But if you'd like to write the KFTT with fastboot to flash. only img. files.
There is no problem on the img files. only I can't flash. There should be a way to format /system as re-partition something like that. Or a way to reset chip of memory.
Click to expand...
Click to collapse
I see and which website might that be? But what i meant is where did the website get the partitions from. Yes hope to find out how to turn a System folder to an img
If you look up some commands for fastboot there is a format option but not sure if it will work for you. I'd try it anyways just to see the errors. That will be quite hard to do
seskanda said:
Finally someone replied. I looked in Device Manager and saw something in yellow called "Tate-PVT-08". So Windows was not recognizing the Kindle. I installed the Kindle ADB drivers from rootjunkysdl.com and now "fastboot -i 0x1949 getvar product" gives me "Tate-PVT-08"
My guess it is working now, but when I try to flash boot, recovery, and system img's from the KFRT here it does nothing and I'm still stuck in "Kindle Fire" logo/bootloop. What is the problem ? Is this thing hard bricked ?
Click to expand...
Click to collapse
I am stuck in a similar bootloop as you describe. I can only get the device to power on for a second. It shows the Kindle Fire Screen, the fastboot screen, then it shuts back down. I tried this with the OEM cable, a third-party cable, and a fastboot cable. I also tried all three cables in my PC over USB 2 and Windows constantly sends a notification saying USB device not recognized.
Related
DISCLAIMER:
1) You are doing this at your own risk.
2) Educate yourself first and try this ONLY if you feel comfortable with modifying with your phone.
3) If you break your phone it is not my fault nor is it my responsibility to fix your phone.
Things could go wrong but they shouldn't if you follow the directions and have some general knowledge of Android.
##############################
Go from this:-------------------------------------------------To This:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----------
##############################
Things needed:
ADB/Fastboot knowledge - HERE and HERE
RGB565Converter v0.3c - Thanks to DeToX-cz!
UPDATE: You must have the engineering bootloader flashed for access to splash1. Follow the steps here to flash the S=OFF bootloader. -Thanks to jcase
Instructions:
Find an or create an image (.png, .bmp, .jpg, or .gif -- 320x480 is preferrable)
Open RGB565 Converter
Ensure that "To RGB565 (binary)" tab is selected
Click "Open Image", select your image
Click "Convert to RGB565" (RGB565 Converter will make your image 320x480 if it is not already)
CLOSE RGB565 CONVERTER
Reboot phone into Fastboot using this command: adb reboot bootloader
OR Button combo: SEND/CALL + END/POWER
Flash image using this command: fastboot flash splash1 <your_image_name>.rgb565
Reboot phone using this command: fastboot reboot
OR fastboot oem powerdown if not then remove your battery
View the results of your hard work.
Enjoy!
As of right now there is no way to read the splash1 partition to back it up short of some kind of kernel mod to partition splash1 from NAND as a new MTD. At least that's how I understand it, please correct me if I'm wrong.
You must flash the S-OFF BOOTLOADER for this to work.
You can use the RGB565Converter tool to flash your image successfully without needing to type commands.
Below is another method used to keep your phone from rebooting unexpectedly during the process:
joshw0000 said:
I tried using the "Flash Splash1" button that someone had posted earlier and I almost **** myself. I think my phone tried to load the file I originally used to root it. I was getting really nervous so I pulled the battery and, to my relief, it powered on and it booted normally. I'm sure that method works but I'm scared of it now.
I tried the original instructions and it rebooted my phone before I was ready so I did this in the command prompt (this was mentioned on the first page of posts):
cd C:\android-sdk-windows\tools
adb shell
su
reboot bootloader
fastboot flash splash1 <copy and paste file name here>
fastboot reboot
Of course this will only work if you've downloaded the program, converted your picture and placed it in the tools directory of SDK.
Worked great for me. I couldn't be happier!
Click to expand...
Click to collapse
didnt seem to work for me, but im not rooted, ill try this with my brothers rooted phone in a bit and repioret back
Wow that worked great! Thanks
Reboot phone into Fastboot (Power down, hold Send press and hold Power)
Click to expand...
Click to collapse
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
ch4sethe5un said:
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
Click to expand...
Click to collapse
no, Hold Call button and end button to get into fastboot
and this is ONLY FOR ROOTED PHONES
thanks
thanks i will try it out. Im using ivan's 0.7
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
ch4sethe5un said:
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
Click to expand...
Click to collapse
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
there should be an option to go to HBOOT menu and then into recovery and reboot from there.
I used this one:
Great tutorial. Thanks!
Here's mine if someone likes it they are free to use it.
+1 rep (if only we could do that). I was looking for something like this. Thanks!
t2noob said:
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
Click to expand...
Click to collapse
I did a battery pull myself too lazy to go into recovery from hboot. My phone did not explode after doing a battery pull so it "should" be safe however do so with caution.
moved thread by request of OP.
Best regards,
Flar
Ive learned that battery pull is the easyiest way,
As a fan of FFXIII, I could not pass up the opportunity to do this.
[Taking Requests also ]
Maybe we should come up with a thread so people can post all boot images and animations in one place, no?
Just remember to convert it like mentioned in the first post
Here is one(as a fan =] ):
Was just thinking about changing and found this. Thanks.
Awesome!!!
Thanks for the tutorial.
Worked great!
My phone is soft bricked, I tried flashing to the stock rom using odin but the phone fails to boot up once the flash has finished it just stays on the 'Samsung Galaxy S III GT-I9305 screen, I can get the phone into download mode but not recovery mode, could anybody please help?
You have two phones ???
see your identical post .
Have you tried after flashing in odin to boot to stock recovery and do a factory reset?
trippy202 said:
Have you tried after flashing in odin to boot to stock recovery and do a factory reset?
Click to expand...
Click to collapse
Yep, nothing happens, just stays on the boot up screen
bump
bluereus said:
bump
Click to expand...
Click to collapse
Do a factory reset then re flash a stock rom
Raistlin1158 said:
Do a factory reset then re flash a stock rom
Click to expand...
Click to collapse
I can't do a factory reset though can I? All I can do is enter download mode
Ok, inside the zip of the rom you flashed, there is a file called boot.
On your desktop, drag out the boot.img.
It's an easy way to get fastboot and adb access without having to download android sdk. Extract the folder to your desktop. put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd. Then change the directory of the prompt so that it aims to the ADB-Fastboot folder. Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot. On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Raistlin1158 said:
Ok, inside the zip of the rom you flashed, there is a file called boot.
On your desktop, drag out the boot.img.
It's an easy way to get fastboot and adb access without having to download android sdk. Extract the folder to your desktop. put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd. Then change the directory of the prompt so that it aims to the ADB-Fastboot folder. Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot. On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Click to expand...
Click to collapse
This is all I have in the zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If anyone can sort this out for me I'll happily throw you a fiver on paypal
bluereus said:
If anyone can sort this out for me I'll happily throw you a fiver on paypal
Click to expand...
Click to collapse
Unzip the zip then unzip again to split up the rom, You don't need to pay as we are all here to help each other :good:
Raistlin1158 said:
Unzip the zip then unzip again to split up the rom, You don't need to pay as we are all here to help each other :good:
Click to expand...
Click to collapse
I've got this far, where is the ADB-Fastboot folder? (sorry)
And I'd like to as a thank you, it'd be £25+ to send it off for repairs
Any chance you could do this for me on teamviewer or something tomorrow? I'm really out of my depth here (like you couldn't tell)
bumping
come on guys
Put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd.
Then change the directory of the prompt so that it aims to the ADB-Fastboot folder.
Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot.
On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Raistlin1158 said:
Put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd.
Then change the directory of the prompt so that it aims to the ADB-Fastboot folder.
Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot.
On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Click to expand...
Click to collapse
What is the ADB-Fastboot folder?
bluereus said:
What is the ADB-Fastboot folder?
Click to expand...
Click to collapse
Create a folder called ADB-Fastboot
Put the boot.img inside the folder called ADB-Fastboot. then follow the instructions... :good:
Raistlin1158 said:
Create a folder called ADB-Fastboot
Put the boot.img inside the folder called ADB-Fastboot. then follow the instructions... :good:
Click to expand...
Click to collapse
By 'change the directory of the prompt what exactly do you mean?
In CMD you have to open the folder you created ie ADB-Fastboot
So type cd ADB-Fastboot , you are changing the directory to the one you created.
Then follow the other instructions.
Without being rude you do not seem to have sufficient knowledge to dabble with you phone....
Once you get it going I would not play with it till you have read a bit more and watched a few videos to bulk up the level of competency,
Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Leader0fr4tz said:
Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Click to expand...
Click to collapse
adb root; adb remount
Does your phone get recognized by your pc?
Mine went black a few days ago and i cant do anything.
LuK1337 said:
adb root; adb remount
Click to expand...
Click to collapse
Hi LuK1337
Firstly thanks for the help.
adb root returns a message saying adb already has root access.
asb remount only remounts the /system partition (unless im using it incorrectly).
So far I have well and truly wiped every partition of this device excluding the /data partition which returns a message saying partition is read-only
So I have now officially proved that this is a hardware issue at least for me, look here for my findings:
http://forum.xda-developers.com/moto-g-2014/help/battery-drained-encrypted-device-pinned-t3079871/page2
Short version I've used every available software method including 'Fastboot Erase all' which has no effect.
So would anyone be able to help build a usb jig or finding a hardware way to fix this ? my device has been opened so I would be able to provide high res pictures of the motherboard to anyone who needs it, will also upload when my 10 post count has been reached
Solved: Dead battery stuck in fastboot mode unable to flash any image. Works for all.
Same thing happened to me.
Nothing to do with the hardware.
Steps to Follow:
1) Open fastboot mode in your phone.
2)Connect to your pc and open cmd in platform-tools folder.
3)Place the twrp.img file in platform tools.
4)In cmd, type : fastboot boot twrp.img (Very Important Command)
Now your phone will boot to recovery mode i.e. TWRP and the connect it to charger. It will charge slowly.
Now you can flash anything using ADB Sideload.
(If found helpful, hit the thanks button )
Recently while updating my Kindle Fire HD 7, my device went into a bootloop where it would boot into TWRP and the TWRP logo kept blinking, I live at a place where it is impossible to procure a factory cable. After numerous failed attempts on making one myself i gave up on factory cables. I however wasn't satisfied enough by my failures so i went the hard way and out of curiosity connected my Kindle to my Laptop and did an ADB device lookup. VOILA ! It was there but now i was wondering how to get it into the fastboot mode from there. After crashing my head several times and punching a few commands my device booted into the orange heaven for a hacker. "The FASTBOOT Mode." So if you are in the same situation i hope this guide will be able to help you unbrick your device.
Steps:
1. Power on your device until the dreadful TWRP LOGO starts flashing.
2. Connect your kindle with your PC.
3. Type in "adb devices" and check if your device is available.
4. If your device shows up in ADB Devices List, Proceed to the next step.
5. Type in "adb reboot bootloader"
6. Now the device will boot into the fastboot mode.
7. Download TWRP from here
8. cd to the folder where your twrp image has been downloaded and type "fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img" to flash it
TWRP downloading from the link indicated installs a Trojan on your PC. Caution
ancestrale59 said:
TWRP downloading from the link indicated installs a Trojan on your PC. Caution
Click to expand...
Click to collapse
This version TWRP has been uploaded by @Hashcode , Kindly use the second button to download (BlueColor) and not the 1st one.
Title
Do you want me to test it? I will be able to do so in about 1-2 months because I have the same problem. I'm gonna save this page in favorites until then.
Sent by my kfhd7 with BeanStalk-4.4.4065-20141002-tate and Twrp 2.8.7.0
Okay, I've put in the last command, and now it says it is waiting for any device. It doesn't seem to want to detect my device, any ideas?
EDIT: Nevermind, just had to set it to the adb composite driver!
device never booted into fastboot mode
sxrmafia said:
Recently while updating my Kindle Fire HD 7, my device went into a bootloop where it would boot into TWRP and the TWRP logo kept blinking, I live at a place where it is impossible to procure a factory cable. After numerous failed attempts on making one myself i gave up on factory cables. I however wasn't satisfied enough by my failures so i went the hard way and out of curiosity connected my Kindle to my Laptop and did an ADB device lookup. VOILA ! It was there but now i was wondering how to get it into the fastboot mode from there. After crashing my head several times and punching a few commands my device booted into the orange heaven for a hacker. "The FASTBOOT Mode." So if you are in the same situation i hope this guide will be able to help you unbrick your device.
Steps:
1. Power on your device until the dreadful TWRP LOGO starts flashing.
2. Connect your kindle with your PC.
3. Type in "adb devices" and check if your device is available.
4. If your device shows up in ADB Devices List, Proceed to the next step.
5. Type in "adb reboot bootloader"
6. Now the device will boot into the fastboot mode.
7. Download TWRP from here
8. cd to the folder where your twrp image has been downloaded and type "fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img" to flash it
Click to expand...
Click to collapse
I've done all the steps the device is recognized but unauthorized, it doesn't boot into fastboot mode at all. I'm stuck here so many headaches i've had from this
movemaker said:
I've done all the steps the device is recognized but unauthorized, it doesn't boot into fastboot mode at all. I'm stuck here so many headaches i've had from this
Click to expand...
Click to collapse
I am encountering the same issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have bricked my A2 today. I first unlocked the bootloader then insatlled GCAM.
everything was fine, but i tried to install XPOSED (sdk 27) from Magisk module, then rebooted from magisk. My set is stuck at android one animation.
I downloaded official firmware of A2 and tried to flash via mi flash tool, always gets an error of "FLASH_DEVCFG_A ERROR" . Then i tried by clicking on "flash_all_except_data.bat" file, cmd just opened and closed very soon, Same thing happended with "flash_all_lock.bat" ,again cmd just opened and closed.
Still my phone is stuck at Android one animation, and i cant flash or boot my set.
EDIT :: USED. /FASTBOOT -W TO UNBRICK PHONE
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
should i flash only those images? because i have some more image files than the llist, kindly check the screen shot
minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Now stuck at devcfg
PS C:\Users\KSN\Desktop\platform-tools> fastboot flash devcfg_b C:\Users\KSN\Desktop\images_V9.6.10.0.ODIMIFE_8.1\images\devcfg.img
target reported max download size of 536870912 bytes
sending 'devcfg_b' (47 KB)...
OKAY [ 0.005s]
writing 'devcfg_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.007s
bluetooth_a , bluetooth_b was flashed successfully
try fastboot flashing unlock_critical
munchy_cool said:
try fastboot flashing unlock_critical
Click to expand...
Click to collapse
This appears everytime . :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Syed Shahriar said:
This appears everytime . :/View attachment 4581400
Click to expand...
Click to collapse
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
munchy_cool said:
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
Click to expand...
Click to collapse
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Syed Shahriar said:
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Click to expand...
Click to collapse
GOT THESE ERROR::
PS C:\adb> fastboot flash system_a C:\adb\images\system.img
error: cannot load 'C:\adb\images\system.img'
my system iso is there in that location
but successfuly done fastboot flash vendor_b C:\adb\images\vendor.img
and fastboot flash vendor_a C:\adb\images\vendor.img
What are you even doing with all those commands
You need to download latest ADB, that is the first that you need to do, and second, copy all of the images from stock rom to your adb folder, it will be easier for commands to work.
And then start your cmd.exe with administrative privileges (right click on cmd in search bar of windows start, and "run as administrator").
Then move yourself from directory to your adb directory with commands from DOS, like "cd.." for going back from directory, and "cd nameofdir" to go into directory.
So move yourself in adb directory, then type the commands from the upper link to flash those .img one by one.
Oh yes, one other thing, you need to check if you see your mobile device in fastboot, did you install correct drivers.
When you are in adb folder, in cmd type fastboot devices, and you should see your mobile connected, if not, then you can type all you want, the phone is not recognized with pc connection.
Right, so... follow this guide to make sure you've unlocked your bootloader successfully. After you've finished, also add in the command "fastboot flashing unlock_critical". I'm not sure why it didn't work for you in the first place - but I know for a fact it works, because I did it to my own A2.
Make sure you've installed adb/drivers as attached by that link above. Why? 'Cause that's what I did, so I know it should work.
Then go here, extract the files to the same folder as platform-tools (the adb and fastboot tools folder), and run flash-all.bat.
Hey bro i do it too, tô solve, just do a fastboot unlock_critical
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
I had the same issue, no OS installed.
Adb Sideload and OTG didn't worl no matter what I tried.
I followed this thread, and it worked properly without errors, not even one.
It took me 5 minutes to recover my dead MiA2 device to a smooth original/official ROM built.
Locled OEM, rebooted the device and everything is working perfectlt.
Thank you all for the info.