Database Info

Fastboot not working anymore?

Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!

Also tried in Ubuntu still no luck >_<

are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

bige914 said:
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I am using a Asus Laptop. Thanks for the response!

im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc

sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
got the same issue guys

Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..

We are all stuck with this unless we send it to asus for RMA
Sent from my VS840 4G using xda premium

SpyFi said:
Also tried in Ubuntu still no luck >_<
Click to expand...
Click to collapse
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?

tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
the problem is not the computer itself, the real problem is that the tablet doesn't get in fastboot mode...

Thank you for the update.

SpyFi said:
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Click to expand...
Click to collapse
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
matt95 said:
got the same issue guys
Click to expand...
Click to collapse
partypage said:
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
Click to expand...
Click to collapse
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
Try this:
-use unlock tool
-boot tablet into USB MODE
(it will say fastboot mode,waiting)
-using the steps,copying over the fastboot files to one folder, with TWRP as the recovery, run fastboot command.
-done successfully,you be good
Click to expand...
Click to collapse
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command

I decided to automate the process of entering commands. Post

philos64 said:
Try this:
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
Click to expand...
Click to collapse
thank you, i'll try this out tomorrow! :good:

no way, i can't get it to fastboot damn it
---------- Post added at 11:45 PM ---------- Previous post was at 11:16 PM ----------
ok i solved the problem just now...
1-reboot the tablet in bootloader while connected to usb
2-use vol down to navigate to the usb mode and then vol up
3-the tablet won't show nothing but actually it is connected
4-proceed to any fastboot command
hope this helps

I had this issue when I first started flashing stuff (although I was flashing CWM not TWRP)
In my experience, if you don't see anything listed in fastboot devices, it doesn't matter because it still flashes.
Just try using the flash command (fastboot -i 0x0b05 flash blah blah blah.blah) and see if it works.
You -should- be able to see your device in "adb devices", and that's really what matters.
Also, what matt95 said is exactly what I do. Whether it shows anything or not, I just flash my stuff. Works fine, but I also don't use fastboot alot because with the new changes to the bootloader, one can flash stock through CWM now without having to fastboot flash it.

I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?

jm700wx said:
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
Click to expand...
Click to collapse
my solution above didn't help?

matt95 said:
my solution above didn't help?
Click to expand...
Click to collapse
I'm in the same wagon as all you guys, I just tried that and I can't get into fastboot still. Still waiting for device
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
I'm sorted now, I didn't realise that we needed a different command
I was using
Code:
fastboot flash recovery recovery-jb-touch.img
instead of the correct method of using
Code:
fastboot -i 0x0B05 flash recovery recovery-jb-touch.img
This worked perfectly

it's same as this:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse

TF300t constantly booting into recovery

I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?

tjk639 said:
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
Click to expand...
Click to collapse
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.

cmendonc2 said:
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
Click to expand...
Click to collapse
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.

tjk639 said:
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
Click to expand...
Click to collapse
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"

cmendonc2 said:
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
Click to expand...
Click to collapse
Where do I find "fastboot devices"?

tjk639 said:
Where do I find "fastboot devices"?
Click to expand...
Click to collapse
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.

cmendonc2 said:
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
Click to expand...
Click to collapse
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.

tjk639 said:
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
Click to expand...
Click to collapse
hmm idk. Im guessing you flashed the wrong version of TWRP, which has ended up in a brick for most users, but they had fastboot access and could later recover it using this: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. You dont seem to have either ADB or fastboot, and TWRP is in a non working state. You could try reinstalling your fastboot and ADB drivers with the universal naked drivers, and then retrying ADB reboot bootloader and fastboot.

All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.

tjk639 said:
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
Click to expand...
Click to collapse
No problem, glad I could help!

adb commands not working in fastboot mode. Is it normal?

I was trying to flash a custom ROM on my moto g xt1033. I used choosing the zip from USB otg after wiping and formatting everyrhing but. It flashed but a black screen came instead of cm logo and I was stuck at welcome to cm screen without touchscreen working. http://forum.xda-developers.com/mot...4-4-4-help-t3019082/post58587594#post58587594
Then I tried side loading or pushing method. But problem is adb commands are not working in fastboot mode. They are working when phone is switched on. (Adb devices show serial number and device in normal mode) Fastboot commands are working fine in fastboot mode but not adb. When I type adb devices in fastboot mode there is nothing after list of device attached. So adb push or adb side load give me waiting for device or device not found result. Is it normal. Earlier I have latest Motorola device manager and latest android SDK. Tried uninstalling and installing them, tried changing USB ports, tried rebooting the phone and restarting windows pc several times but still no luck.!!

Yes, it's normal that ADB commands do not work in Fastboot mode. But you can access custom recovery from the fastboot screen.

@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work

Guru.Eclairs said:
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Click to expand...
Click to collapse
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.

lost101 said:
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
Click to expand...
Click to collapse
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot

Guru.Eclairs said:
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Click to expand...
Click to collapse
It doesn't work on all versions of Windows; I think I've had it working in Windows 7. But I mainly use it in Linux - where no driver is required.

I also have windows 7.. Thanks Anyway

Guru.Eclairs said:
I also have windows 7.. Thanks Anyway
Click to expand...
Click to collapse
It's a driver issue. Your phone is not being recognised. If you boot a Linux LiveCD from DVD / USB, you can access recovery mode ADB that way.
sudo apt-get install android-tools-fastboot​

Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.

audit13 said:
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
Click to expand...
Click to collapse
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything

I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.

audit13 said:
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
Click to expand...
Click to collapse
If adb doesn't work in fastboot mode then whats the propose of word "sideload"

Guru.Eclairs said:
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Click to expand...
Click to collapse
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/

audit13 said:
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
Click to expand...
Click to collapse
​
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom

Guru.Eclairs said:
​
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Click to expand...
Click to collapse
Sorry, I don't know how to increase speed except try a different radio/modem on your phone. I rarely use data on my phone because I have an iPad with LTE.

Guru.Eclairs said:
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
Click to expand...
Click to collapse
Sounds like your fastboot driver is working fine but your adb driver is not...go into your custom recovery and then check Device Manager in Windows to see if you have all your drivers working properly.
If you are having adb driver issues you could try the Universal adb driver setup file attached.

adb commands don't work in fastboot mode. Install a recovery (Preferably TWRP because I forget how CWM's adb sideload works). For TWRP, go to advanced, then adb sideload. Make sure to install the adb drivers tho, or else the sideload won't work. If you're sticking with stock, press the Vol+ button for about 15 secs, then tap the power button. Use the Vol- and + keys too scroll. There should be an option like "Install firmware through adb" or something. Scroll to that, then hit the power button to go to that option. Then, just sideload the firmware.

Check device manager 1st phone is conected properly

adb has no relation to fastboot.adb will not work while in fastboot, it never worked that way either.
There is no sideload while in fastboot, you're confusing it with the adb sideload, that has nothing to do with fastboot.
Reading and comprehension are desirable here.

Moto G bricked?

Hey guys this is my first thread, I hope it's in the right section
Here's my problem:
Yesterday my Moto G 2013 with CM12.1 just froze (I could turn the screen on and off but that was it)
I tried opening the reboot menu, which worked, but it got stuck on "rebooting", so I just holded the power key until it turned off.
After that I got to the boot logo, but nothing happened from there, not even the boot animation showing up.
Next I tried to boot into TWRP, but it only got to the TWRP boot logo and nothing happened after that, so I flashed CWM, which I could access, but when trying to flash something it just doesn't progress. When I press "reboot to bootloader" on CWM it just freezes there aswell.
In another thread I read that flashing the gpt.bin should fix everything but it didn't help.
I don't really want to perform a factory reset, because of the data loss, but I think this would be my only option.
My question is:
How can I fix my phone (preferably without a factory reset), for example by getting TWRP to work again, because I have a Backup of my system and a zip of CM12.1 on it?
Btw another thing to mention is that when being in Recovery/System USB doesn't really work, but if my phone is turned off or in bootloader it works just fine.

Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".

_that said:
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
Click to expand...
Click to collapse
When I try "fastboot boot twrp.img" it reboots and get's stuck at the boot logo of android (Motorola logo) and I can hear the "Device disconnected" sound of windows.
But I flashed TWRP into recovery and it get's to the curtain screen. But it doesn't recognize my phone which might have to do with that as soon as it boots into a system USB just won't work

The following command will get TWRP working: fastboot erase userdata

lost101 said:
The following command will get TWRP working: fastboot erase userdata
Click to expand...
Click to collapse
But this will delete everything like my pictures folder, right? Isn't there a way to backup these files ?

@Ju43
adb pull /sdcard/ c:/motog_backup/​

lost101 said:
@Ju43
adb pull /sdcard/ c:/motog_backup/​
Click to expand...
Click to collapse
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)

Ju43 said:
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Click to expand...
Click to collapse
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.

lost101 said:
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
Click to expand...
Click to collapse
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?

Ju43 said:
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Click to expand...
Click to collapse
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot​

lost101 said:
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot​
Click to expand...
Click to collapse
I see what you mean but I got adb to work most times when android was still working (just not in recovery) but I also had problems with charging when the phone was turned on, so I assume it's a problem with android, but I'll search for a Ubuntu Live CD that should be layng around somewhere here (lol) and I'll try it

@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...

Ju43 said:
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Click to expand...
Click to collapse
Use: sudo fastboot devices

lost101 said:
Use: sudo fastboot devices
Click to expand...
Click to collapse
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.

Ju43 said:
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Click to expand...
Click to collapse
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?

lost101 said:
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
Click to expand...
Click to collapse
Nope, because as I mentioned it doesn't get to the TWRP logo at all

Ju43 said:
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Click to expand...
Click to collapse
Try CWM.

lost101 said:
Try CWM.
Click to expand...
Click to collapse
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o

Ju43 said:
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Click to expand...
Click to collapse
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.

lost101 said:
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
Click to expand...
Click to collapse
Downloading it right now, could you please exactly tell me what to flash with which command ?

Mi4i problem

so my mi4i is stuck in boot loop i flashed the stock firmware miui 6 using miflash . my volume down buttons dead so i cant use it to boot in fastboot . i could go in recover (stock ) at best .

You can use adb commands to boot into fastboot mode. Check Google for instructions.

hell1134 said:
You can use adb commands to boot into fastboot mode. Check Google for instructions.
Click to expand...
Click to collapse
kanishk @Mi4i said:
so my mi4i is stuck in boot loop i flashed the stock firmware miui 6 using miflash . my volume down buttons dead so i cant use it to boot in fastboot . i could go in recover (stock ) at best .
Click to expand...
Click to collapse
According to what he said open a terminal and type adb reboot-bootloader
But u must have adb drivers installed. But without booting into Android I don't think ADB will work
If this does not work try booting into recovery and check if ADB works. Good luck!

sharan.nyn said:
According to what he said open a terminal and type adb reboot-bootloader
But u must have adb drivers installed. But without booting into Android I don't think ADB will work
If this does not work try booting into recovery and check if ADB works. Good luck!
Click to expand...
Click to collapse
thanks .

PC can read my internal storage when i reboot to recovery mode [[in this case i'm using TWRP, i'm not sure whether stock recovery is readable too]] as long as the usb driver have installed on my PC .
Try it, if you can acces your internal storage on your PC, you can download your device ROM and flash it via recovery .