Related
I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus
I tried to install CM9 to my kindle, but I didn't realize I was supposed to install TWRP first. I am stuck at the yellow triangle, can't get into recovery (of any sort).
When I plug in the USB cable I type in
Code:
fastboot getvar product
which returns: kindle.
I tried to push TWRP using
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
and it returns: sending 'recovery' (5568 KB) but nothing ever happens.
I have tried draining the battery and recharging it completely. I have been able to get into recovery before by tapping the power button but don't seem to be able to do it anymore.
adb doesn't work at all. I should mention I am on a mac so KFU didn't work for me either.
I promise to be more careful in the future, can someone please help me save my kindle?
Try omitting the "-i 0x1949" from your command and flash it again.
EDIT: While you're at it, download TWRP again and confirm its md5 checksum before flashing it again.
md5 is ok, I tried without the switch as well still nothing
whtmgcwmn said:
md5 is ok, I tried without the switch as well still nothing
Click to expand...
Click to collapse
What recovery did you use to flash CM9 in the first place? What happens when you try to boot into the system?
I'm starting to recall some people having problems with the mac version of fastboot. Do you have another OS available just to compare things?
in my case the commands only return "is <waiting device>"
I had CWM I believe it's still in there somewhere. But I can't get to it anymore. Sometimes I think CM9 is going to start up because I do get the splash screen but it just goes on for like 15 minutes then the kindle restarts and goes back to the yellow triangle of doom.
EDIT: No unfortunately all I have is the mac
nailanb13 said:
in my case the commands only return "is <waiting device>"
Click to expand...
Click to collapse
If you're using Windows, read the first three posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
and make sure your drivers are working properly.
whtmgcwmn said:
I had CWM I believe it's still in there somewhere. But I can't get to it anymore. Sometimes I think CM9 is going to start up because I do get the splash screen but it just goes on for like 15 minutes then the kindle restarts and goes back to the yellow triangle of doom.
EDIT: No unfortunately all I have is the mac
Click to expand...
Click to collapse
I hope you weren't using Hashcode's CWMR...
In any case, I believe I've seen another user struggle with fastboot on the mac. You might be having the same problem, but I can't find that thread. You might want to look into building Ubuntu Linux on a USB stick and try running that on your mac. Otherwise, you'll have to wait for someone who's used those tools on the mac to chime in here. I've never played around with it.
kinfauns said:
I hope you weren't using Hashcode's CWMR...
In any case, I believe I've seen another user struggle with fastboot on the mac. You might be having the same problem, but I can't find that thread. You might want to look into building Ubuntu Linux on a USB stick and try running that on your mac. Otherwise, you'll have to wait for someone who's used those tools on the mac to chime in here. I've never played around with it.
Click to expand...
Click to collapse
I have no idea which CWM I have. I couldn't find the mac fastboot thread either, I guess I will just put it away for now until I get access to a pc.
Looking above there is a good chance twrp sent I'm pretty sure now all you need to do is reset your bootmode
fastboot oem idme bootmode 4000
fastboot reboot
Do you try use factory cable? If not, let factory cable and run command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
chamnv said:
Do you try use factory cable? If not, let factory cable and run command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Click to expand...
Click to collapse
Not to just sit here and tromp on your toes chamnv but the title of this thread is "kindle stuck in fastboot mode but wont accept commands" my impression of a factory cable is that it puts you in fastboot and secondly above he has attempted to send a new recovery why would he then send an old one?
Thepooch said:
Not to just sit here and tromp on your toes chamnv but the title of this thread is "kindle stuck in fastboot mode but wont accept commands" my impression of a factory cable is that it puts you in fastboot and secondly above he has attempted to send a new recovery why would he then send an old one?
Click to expand...
Click to collapse
sorry to laugh but hehehe
whtmgcwmn said:
I tried to install CM9 to my kindle, but I didn't realize I was supposed to install TWRP first. I am stuck at the yellow triangle, can't get into recovery (of any sort).
When I plug in the USB cable I type in
Code:
fastboot getvar product
which returns: kindle.
I tried to push TWRP using
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
and it returns: sending 'recovery' (5568 KB) but nothing ever happens.
I have tried draining the battery and recharging it completely. I have been able to get into recovery before by tapping the power button but don't seem to be able to do it anymore.
adb doesn't work at all. I should mention I am on a mac so KFU didn't work for me either.
I promise to be more careful in the future, can someone please help me save my kindle?
Click to expand...
Click to collapse
Just unplug the KF from the USB, hold the power button and turn it back on. Repeat the process.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!
escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2
soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!
escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
I'm in a similar situation. TWRP will not mount anything, If i try to wipe cashe, ect it says failed. If i try adb push it does not work. At this point I would be fine with just going back to stock. Hopefully someone can find a solution to our problem.
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
androidschima said:
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
Click to expand...
Click to collapse
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
androidschima said:
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
Click to expand...
Click to collapse
im stuck....
i flashed new recovery through fastboot because this was supposed to get the twrp 2.3.3.0 bug out of the system formatting the data partition in a way i could flash a rom onto it. so new twrp 2.7 flashed through fastboot. according to the cmd it worked all fine...
now i come into white blue boot loade choose recovery and kindle wont boot from there.
this is just f***d up. Next time i jsut keep my hands of jailbreaking hardware.
anychance anyone out there could give me a hand and get this fixed? I am
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
androidschima said:
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
Click to expand...
Click to collapse
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
kindle fire first aid has them. But it downloads them off the net last i heard so you wont find the images directly in there unless i am mistaken.
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43569633
This should be all u need
-》Sent from my mind to your screen.
Thank you! I will look into it!
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?
ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv