Recently, i was on bootloop ... i tried to flash my original recovery and fastboot. But, i accidentally execute the wrong command... Now there's no way i cant get to bootloader or flash something again, any other ways?
ads
Affichage des articles dont le libellé est fastboot. Afficher tous les articles
Affichage des articles dont le libellé est fastboot. Afficher tous les articles
jeudi 1 octobre 2015
lundi 28 septembre 2015
[Q] Computer won't Recognize Kindle in Fastboot Mode [Q]
Before we start this: I am new to Android, especially FIRE OS, and really need some help. Also, this is refering to a Amazon Kindle Fire 7" 2nd Generation.
Lets start from the beginning. I decided to root my kindle, and I installed Google Play Services on it. I then updated, and decided to wipe the services (It was causing some problems) and reinstall it. Because "vending.app" is the main files that runs the services (I thought), I found a "Vending" folder under /SYS in the file directory. Me being an idiot, I deleted it, and it froze my kindle, I forced a restart, but then all I got was the Blue "Kindle Fire" screen. It would show the logo, crash, then restart again, basically a boot-loop. I did some research, and decided to fastboot my kindle, wipe it clean, and install a recovery. I bought a FACTORY CABLE, and successfully fast-booted my device. I then installed a portion of (what I think) is the Android Developer thing-a-ma-bob that contains the ABD and fastboot files. The thing is, I have my fastbooted kindle connected to the computer via USB, but ADB AND FASTBOOT DOES NOT RECOGNIZE IT. All its says is "<waiting for device>". Does this have something to do with the "Vending" File I deleted, or is it a computer problem.
PS: I have a MAC, and(I don't think) requires drivers, so drivers is not the cause. I also cannot use any 3rd party recovery softwares due to not being able to run .bat and .exe
THINGS I HAVE TRIED:
-Switching to the normal Kindle Charger (USB)
-Hard Starting the Kindle
-Trying to boot into recover w/ VOLUME UP (Does not Work)
-Changing USB Ports
Any Help Will Be Appreciated, Thanks!
Lets start from the beginning. I decided to root my kindle, and I installed Google Play Services on it. I then updated, and decided to wipe the services (It was causing some problems) and reinstall it. Because "vending.app" is the main files that runs the services (I thought), I found a "Vending" folder under /SYS in the file directory. Me being an idiot, I deleted it, and it froze my kindle, I forced a restart, but then all I got was the Blue "Kindle Fire" screen. It would show the logo, crash, then restart again, basically a boot-loop. I did some research, and decided to fastboot my kindle, wipe it clean, and install a recovery. I bought a FACTORY CABLE, and successfully fast-booted my device. I then installed a portion of (what I think) is the Android Developer thing-a-ma-bob that contains the ABD and fastboot files. The thing is, I have my fastbooted kindle connected to the computer via USB, but ADB AND FASTBOOT DOES NOT RECOGNIZE IT. All its says is "<waiting for device>". Does this have something to do with the "Vending" File I deleted, or is it a computer problem.
PS: I have a MAC, and(I don't think) requires drivers, so drivers is not the cause. I also cannot use any 3rd party recovery softwares due to not being able to run .bat and .exe
THINGS I HAVE TRIED:
-Switching to the normal Kindle Charger (USB)
-Hard Starting the Kindle
-Trying to boot into recover w/ VOLUME UP (Does not Work)
-Changing USB Ports
Any Help Will Be Appreciated, Thanks!
Moto G 3rd Gen XT1540 won't boot into fastboot mode.
Hi there, i recently got this phone and I tried to flash a stock rom using fastboot. The issue here is that I finished flashing the rom, it boot once then it shutdown by itself and now it won't boot, not even into fastboot. The pc is not recognicing the phone at all... Please, some help is needed :/
Fastboot flash recover fails - any help please?
Hi Guys,
I've got a brand new Nexus 7 (2013) flo/wifi version.
I'm trying to add Timur's kernel to it however I'm struggling.
I've installed ADB to my windows 10 pc and when I type adb devices I see the device, so I type adb reboot bootloader, thats fine.
I downloaded twrp-2.8.7.0-flo.img from the twrp.me site and and renamed it to twrp.img, then I moved it in to the same directory that adb and fastboot are running in.
I type fastboot flash recover twrp.img and I get this below:
I've tried 3 different USB ports and 2 different cables - I restarted my desktop pc too
Can anyone help me out please?
I've got a brand new Nexus 7 (2013) flo/wifi version.
I'm trying to add Timur's kernel to it however I'm struggling.
I've installed ADB to my windows 10 pc and when I type adb devices I see the device, so I type adb reboot bootloader, thats fine.
I downloaded twrp-2.8.7.0-flo.img from the twrp.me site and and renamed it to twrp.img, then I moved it in to the same directory that adb and fastboot are running in.
I type fastboot flash recover twrp.img and I get this below:
Code:
sending 'recovery' (8956 KB)...
FAILED (data transfer failure (Unknown error))
finsihed. total time: 5.011sCan anyone help me out please?
[Q] Win10 fastboot - Doesn't work. Once worked. S1boot doesn't show up device manager
Hi,
I tried every way and guides shown here. Even disabling driver integrity checks et cetera.
Currently, there's a default stock ROM on my Xperia Z2.
I install the adb-setup-1.4.2.exe installer which installs adb / fastboot + the drivers for my X64 Win10.
Alright.
Reboot.
Then I plug in the USB cord into my turned off phone and hold Volume Up.
My phone vibrates.
I release the button.
Then in tthe Device Manager, this shows up:

Everytime.the.same.****ing.THING!
Anybody had the same problem?
One time, through some curious wonder, it worked. S1boot showed up and even the correct driver was instaled (back then via the adb-setup by a XDA user).
Well, what am I doing wrong?
I would be glad for any help. I've tried any troubleshooting guide there is by now and I am at the end of my knowledge.
Thanks for any help,
Michael
I tried every way and guides shown here. Even disabling driver integrity checks et cetera.
Currently, there's a default stock ROM on my Xperia Z2.
I install the adb-setup-1.4.2.exe installer which installs adb / fastboot + the drivers for my X64 Win10.
Alright.
Reboot.
Then I plug in the USB cord into my turned off phone and hold Volume Up.
My phone vibrates.
I release the button.
Then in tthe Device Manager, this shows up:
Everytime.the.same.****ing.THING!
Anybody had the same problem?
One time, through some curious wonder, it worked. S1boot showed up and even the correct driver was instaled (back then via the adb-setup by a XDA user).
Well, what am I doing wrong?
I would be glad for any help. I've tried any troubleshooting guide there is by now and I am at the end of my knowledge.
Thanks for any help,
Michael
dimanche 27 septembre 2015
LG L70 recovery via fastboot (hard mode) (solves infinite loop and others)
If you killed your LG L70, and can no longer access the recovery menu, follow these steps.
First do the Download LG Laf Recovery multitool on your computer, and extract to any folder.
Turn off your device (advise that the clearance was connected via USB, but cases of infinite loop will not have as then is dispensable).
Plug in fastboot mode (when off connect USB and press vol +) will appear on a black screen as the image below:
[IMG]https://blogger.googleusercontent.com/img/proxy/AVvXsEjJuMZRKPyTWNhv6ZOf2rtQ5QIOCdZzalCbuHhQb8SQn2Aom2TVeAIMMvMV0Vl451hT3G607RP_bRs75hM_ELP253dlVtjKVzxOfEfAU9pMwcXpJ6eW9f6VwCxc6HF3Yec= jpg&container=blogger&gadget=a&rewriteMime=image%2 F*[/IMG]
Inside the folder you extracted before press Shift + click right mouse button, and click "Open command window here"
Enter fastboot devices (to activate the fastboot) and hit enter.
Enter fastboot boot recovery.img and press enter again.

Ready, your bricked device enter into recovery mode. With this you can install another rom normally or return to the previous rom if you made a backup.
Obs .: Do this only when your phone is not going into recovery mode by typing the command window "fastboot reboot recovery"
The next time you want to access the recovery, you can use the above command. You can also use the adb devices.
Sorry for my bad English, original post on my blog (Brazilian) search on google Arenandroid :Boa:
First do the Download LG Laf Recovery multitool on your computer, and extract to any folder.
Turn off your device (advise that the clearance was connected via USB, but cases of infinite loop will not have as then is dispensable).
Plug in fastboot mode (when off connect USB and press vol +) will appear on a black screen as the image below:
[IMG]https://blogger.googleusercontent.com/img/proxy/AVvXsEjJuMZRKPyTWNhv6ZOf2rtQ5QIOCdZzalCbuHhQb8SQn2Aom2TVeAIMMvMV0Vl451hT3G607RP_bRs75hM_ELP253dlVtjKVzxOfEfAU9pMwcXpJ6eW9f6VwCxc6HF3Yec= jpg&container=blogger&gadget=a&rewriteMime=image%2 F*[/IMG]
Inside the folder you extracted before press Shift + click right mouse button, and click "Open command window here"
Enter fastboot devices (to activate the fastboot) and hit enter.
Enter fastboot boot recovery.img and press enter again.

Ready, your bricked device enter into recovery mode. With this you can install another rom normally or return to the previous rom if you made a backup.
Obs .: Do this only when your phone is not going into recovery mode by typing the command window "fastboot reboot recovery"
The next time you want to access the recovery, you can use the above command. You can also use the adb devices.
Sorry for my bad English, original post on my blog (Brazilian) search on google Arenandroid :Boa:
HTC desire c "unknown USB device(Device failed enumeration)" in Fastboot mode
hello everyone my HTC Desire c got loaded into bootloader by volume down + power button
but in the device manager..i got a yellow triangle with "unknown USB device(Device failed enumeration)"
and i think in fastboot mode windows 10 is not recognizing my phone what to do ..? any help would be appreciated
-thanks in advance
but in the device manager..i got a yellow triangle with "unknown USB device(Device failed enumeration)"
and i think in fastboot mode windows 10 is not recognizing my phone what to do ..? any help would be appreciated
-thanks in advance
Stuck in Erase, Can get Fastboot!
Hi,
My Nexus 7 2013 is stuck in a boot loop in that it anything beyond fast boot results in a constant erase mode. This is interesting because the last command given was to erase all data.
it is a flo 04.05 32G rev e hardware and it is unlocked.
Any help would be appreciated.
My Nexus 7 2013 is stuck in a boot loop in that it anything beyond fast boot results in a constant erase mode. This is interesting because the last command given was to erase all data.
it is a flo 04.05 32G rev e hardware and it is unlocked.
Any help would be appreciated.
samedi 26 septembre 2015
[Q] Fastboot Kindle Fire not Recognized by Computer
Before we start this: I am new to Android, especially FIRE OS, and really need some help.
Lets start from the beginning. I decided to root my kindle, and I installed Google Play Services on it. I then updated, and decided to wipe the services (It was causing some problems) and reinstall it. Because "vending.app" is the main files that runs the services (I thought), I found a "Vending" folder under /SYS in the file directory. Me being an idiot, I deleted it, and it froze my kindle, I forced a restart, but then all I got was the Blue "Kindle Fire" screen. It would show the logo, crash, then restart again, basically a boot-loop. I did some research, and decided to fastboot my kindle, wipe it clean, and install a recovery. I bought a FACTORY CABLE, and successfully fast-booted my device. I then installed a portion of (what I think) is the Android Developer thing-a-ma-bob that contains the ABD and fastboot files. The thing is, I have my fastbooted kindle connected to the computer via USB, but ADB AND FASTBOOT DOES NOT RECOGNIZE IT. All its says is "<waiting for device>". Does this have something to do with the "Vending" File I deleted, or is it a computer problem.
PS: I have a MAC, and(I don't think) requires drivers, so drivers is not the cause. I also cannot use any 3rd party recovery softwares due to not being able to run .bat and .exe
THINGS I HAVE TRIED:
-Switching to the normal Kindle Charger (USB)
-Hard Starting the Kindle
-Trying to boot into recover w/ VOLUME UP (Does not Work)
Any Help Will Be Appreciated, Thanks!
Lets start from the beginning. I decided to root my kindle, and I installed Google Play Services on it. I then updated, and decided to wipe the services (It was causing some problems) and reinstall it. Because "vending.app" is the main files that runs the services (I thought), I found a "Vending" folder under /SYS in the file directory. Me being an idiot, I deleted it, and it froze my kindle, I forced a restart, but then all I got was the Blue "Kindle Fire" screen. It would show the logo, crash, then restart again, basically a boot-loop. I did some research, and decided to fastboot my kindle, wipe it clean, and install a recovery. I bought a FACTORY CABLE, and successfully fast-booted my device. I then installed a portion of (what I think) is the Android Developer thing-a-ma-bob that contains the ABD and fastboot files. The thing is, I have my fastbooted kindle connected to the computer via USB, but ADB AND FASTBOOT DOES NOT RECOGNIZE IT. All its says is "<waiting for device>". Does this have something to do with the "Vending" File I deleted, or is it a computer problem.
PS: I have a MAC, and(I don't think) requires drivers, so drivers is not the cause. I also cannot use any 3rd party recovery softwares due to not being able to run .bat and .exe
THINGS I HAVE TRIED:
-Switching to the normal Kindle Charger (USB)
-Hard Starting the Kindle
-Trying to boot into recover w/ VOLUME UP (Does not Work)
Any Help Will Be Appreciated, Thanks!
Can't access FastBoot mode & sporadically won't power back on after I attempt it!
When it's working, my brand new Nexus 7 2013 Wi-Fi powers on and off normally when pressing and holding the power button for 3 seconds. But when I attempt to enter FastBoot mode (I plan on rooting it) by pressing the power & vol up/down simultaneously, nothing happens, just a black screen as if the device is dead. What's worse is that I then have great difficulty getting the Nexus to even power on normally. Right now it appears to be dead but if I press & hold the power button in many attempts it might come back on. This always happens right after I attempt to enter fast boot mode. Using Android 5.01. Can anyone help me with this problem? I'm on the verge of RMAing it since I can't seem to get it to power on anymore but will keep trying. I really would like to root this but it seems impossible at this point.
Libellés :
access,
after,
attempt.,
back,
Can't,
fastboot,
Mobile 1,
mode.,
Power,
sporadically.,
won't
KFHD 8.9 1st Gen. (Jem) Orange logo screen, not recognized, no ADB or fastboot
I've had a 1st Gen Kindle Fire HD 8.9 (or jem-pvt-prod-04) for ages. Rooted it years ago using KFFirstAide, which installed ADW Launcher (I think), but I never took the custom ROM plunge, and now I hardly ever look at it anymore. When I was thinking about installing custom ROM on my phone for the first time, I thought I'd get some practice on a device I don't mind losing (since I barely know what I'm doing...). Had the Kindle in Fastboot Mode and tried to flash different bootloader & recovery (from http://forum.xda-developers.com/show....php?t=2128175 ), and I probably flashed something I shouldn't have and corrupted the bootloader:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
Upon rebooting, the Orange Kindle Fire logo appeared, and froze (it never became animated or turned blue). It is now stuck there. I have held down power button for 30+ seconds, I have tried that with and without using vol down and vol up buttons. I have fully depleted the battery and recharged. I have attempted six ways to Sunday to get my computer to recognize the device so I could issue ADB or Fastboot commands, but when I connect the USB cable and start up the Kindle, Device Manager (I'm on Win 10) sees it as Android Device and shows Android ADB Interface driver for literally one second, then sees the device as disconnected. When I show hidden devices, I can update the driver for that device, and I've tried various ones, but all to no avail. I went further out on a limb and created a Ubuntu Live USB (though I have never used a Linux OS on my PC). I tried to get Java and SDK working in Ubunto OS, but I'm way out of my depth.
If anybody has any suggestions (other than quit doing things to your devices that you don't fully understand...), or can help me try other ways to get the device recognized and able to receive ADB/Fastboot commands, I'd really appreciate it.
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
Upon rebooting, the Orange Kindle Fire logo appeared, and froze (it never became animated or turned blue). It is now stuck there. I have held down power button for 30+ seconds, I have tried that with and without using vol down and vol up buttons. I have fully depleted the battery and recharged. I have attempted six ways to Sunday to get my computer to recognize the device so I could issue ADB or Fastboot commands, but when I connect the USB cable and start up the Kindle, Device Manager (I'm on Win 10) sees it as Android Device and shows Android ADB Interface driver for literally one second, then sees the device as disconnected. When I show hidden devices, I can update the driver for that device, and I've tried various ones, but all to no avail. I went further out on a limb and created a Ubuntu Live USB (though I have never used a Linux OS on my PC). I tried to get Java and SDK working in Ubunto OS, but I'm way out of my depth.
If anybody has any suggestions (other than quit doing things to your devices that you don't fully understand...), or can help me try other ways to get the device recognized and able to receive ADB/Fastboot commands, I'd really appreciate it.
vendredi 25 septembre 2015
Stuck on fastboot and recovery with hboot 1.61 S-On
My HTC One is currently unlocked at hboot 1.61, S-On, with ClockworkMod Recovery v6.0.4.6 installed. no carriers
I have a backup of the stock rom before I install any roms, and I have install SU to my device afterwards.
I was intended to install Insertcoin 7.1.3 rom, I did a factory reset/wipe caches and then install the rom via clockworkmod.
However, my device does not boot into the custom but reboot will automatically 'entering in recovery' instead,
perhaps that was to do with the S-On, or it's a failed rom I got?
Anyway, I tried to restore the stock rom backup I did, it said restore completed but it reboot into recovery still...
Now I can only able to access fastboot and recovery, I tried download and put in the by using "mounts and storage" -> "mount USB storage" on ClockworkMod, but it won't let me as it does not appear on my Windows 10 as it usually should.
Can anyone help me to solve this mystery? Ideally, I would like to get back to stock rom at least...
I only had experience on rooting from my Desire HD(retired), there's a sdcard to storage roms back then...
What I've got now is:
- a backup from clockworkmod, and I didn't copy to my PC
- a stock rom and kernel, I downloaded from internet and HTC webpage.
- a InsertCoin rom for m7
I have did some research on similar issue previously, but doesn't seems to help me out. if anyone knows the same issue has been addressed and solved in some posts, please don't hesitate to feed me with those posts, as I could have missed them by struggling on reading foreign language for the entire evening...
lastly, if i did anything idiotic through the process I did, please don't judge my stupidity
I have a backup of the stock rom before I install any roms, and I have install SU to my device afterwards.
I was intended to install Insertcoin 7.1.3 rom, I did a factory reset/wipe caches and then install the rom via clockworkmod.
However, my device does not boot into the custom but reboot will automatically 'entering in recovery' instead,
perhaps that was to do with the S-On, or it's a failed rom I got?
Anyway, I tried to restore the stock rom backup I did, it said restore completed but it reboot into recovery still...
Now I can only able to access fastboot and recovery, I tried download and put in the by using "mounts and storage" -> "mount USB storage" on ClockworkMod, but it won't let me as it does not appear on my Windows 10 as it usually should.
Can anyone help me to solve this mystery? Ideally, I would like to get back to stock rom at least...
I only had experience on rooting from my Desire HD(retired), there's a sdcard to storage roms back then...
What I've got now is:
- a backup from clockworkmod, and I didn't copy to my PC
- a stock rom and kernel, I downloaded from internet and HTC webpage.
- a InsertCoin rom for m7
I have did some research on similar issue previously, but doesn't seems to help me out. if anyone knows the same issue has been addressed and solved in some posts, please don't hesitate to feed me with those posts, as I could have missed them by struggling on reading foreign language for the entire evening...
lastly, if i did anything idiotic through the process I did, please don't judge my stupidity
Need a fastboot rom for mi4 i cant download from chinese site for some reason
Where do i find a fastboot rom that works with miflash ???
jeudi 24 septembre 2015
unlock & root failed, then flash FTF, but now cannot fastboot boot recovery.img
First time success unlock & use TWRP,
then install SU.zip in TWRP but the phone cannot normal boot in;
therefore flash FTF, now can use the phone but cannot use TWRP again ( fastboot boot recovery.img).
Unlock status is unknown.
Can flash FTF.
What the driver is used in fastboot in Windows?
How can I know the phone is connecting correctly?
Any solution to use TWRP & root? :confused:
then install SU.zip in TWRP but the phone cannot normal boot in;
therefore flash FTF, now can use the phone but cannot use TWRP again ( fastboot boot recovery.img).
Unlock status is unknown.
Can flash FTF.
What the driver is used in fastboot in Windows?
How can I know the phone is connecting correctly?
Any solution to use TWRP & root? :confused:
Fastboot Stuck with locked bootloader
My problem is much similar to a guy on this post:
http://forum.xda-developers.com/moto...t2634982/page5
I've tried to upgrade my ROM (Retail) from 4.4.4 to 5.1
I had my bootloader unlocked before doing that.
When i did, my phone was unable to finish the update and I got stuck on fastboot. But know it behaves and states that its "Locked". When I try to unlock it, I get that error:
I already tried flashing both the 4.4.4 version I was using, and the version I updated.
I gives me the following error:
I'm unnable to boot into recovery and anything else, except the fastboot.
Please, help me solving it.
http://forum.xda-developers.com/moto...t2634982/page5
I've tried to upgrade my ROM (Retail) from 4.4.4 to 5.1
I had my bootloader unlocked before doing that.
When i did, my phone was unable to finish the update and I got stuck on fastboot. But know it behaves and states that its "Locked". When I try to unlock it, I get that error:
Code:
c:\motox\adb>fastboot oem unlock XXXXXXXXXX
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. Total time: 0.278sI gives me the following error:
Code:
c:\motox\adb>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.932s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.035sPlease, help me solving it.
trying to root but get stuck in fastboot mode
Hello im trying to root my nexus 7 2013 with nexus root toolkit got 5.1.1 but when the tablet boots to fastboot mode it wont continue even that i got it unlocked tryed another tool but same problem there aswell, anyone know what i should do?
Phone stuck in bootloop, can't boot into fastboot or recovery, Please help
After trying to flash a TBO calendar/calculator inverted app I rebooted from recovery only to now be stuck in a bootloop. The only thing the phone will do is begin to reboot itself if I press all three buttons to "hard restart". (power+vol up+vol dwn). Tried using adb/fastboot to reboot into recovery or bootloader but I don't think that the phone is far enough into the boot process to be recognized by adb/fastboot because typing adb reboot-bootloader just returns "waiting on devices".
I don't know of any other way of getting into recovery to restore a nanroid. Any one have a good suggestion? Please!
I don't know of any other way of getting into recovery to restore a nanroid. Any one have a good suggestion? Please!
mercredi 23 septembre 2015
Fastboot mode Started - help
So this morning i thought it would be a great idea to revert back to stock.
i was following the KDZ lg flash tool however while it was flashing (got to about 2%) i stupidly knocked the phone and the usb cable came out....
so now when i turn my phone on it goes to a black screen with
Fastboot mode started
---reset---
---port charge--
i have tried going into download mode again but it still goes into this fastboot mode.
i found a lot of threads on this such as
http://forum.xda-developers.com/lg-g...arted-t2995854
this got me to install adb/fastboot which i did via
http://forum.xda-developers.com/show....php?t=2588979
however when i try and run through fastboot it just comes up as waiting for device
i have attempted to install lg drivers for this but still nothing.
inside device manager it comes up as
other devices - android?
so clearly the computer is recongnising it, i just need a better driver.
I have the ldf ready to go, if only i could get it to recognise the fastboot command...
anyone able to help, i realise there is a lot of information on the web for this, after extensive research everyone seems to suddenly get into download mode each time. which is something i cannot go. and no recovery doesnt work either.
other things to note, just to save questions..
i am running LG D855 16gb.
when i attempt to go into recovery it comes up with the option to wipe device, but when i follow through menu comes back to fastboot mode started.
i attempted to install lg pc suite in hope that it would suddenly pick up the device and go through the fix upgrade errors (to no luck)
so to clarify, i cannot get into recovery, or download mode. my screen is sat on fastboot mode started.
i am running windows 8.1 although i have attempted to plug into a laptop with ubuntu but same story.
any suggestions? i have also seen a through about jtag...but i dont have any screwdrivers at this point so trying to avoid that.
thank you for reading, kind regards
i was following the KDZ lg flash tool however while it was flashing (got to about 2%) i stupidly knocked the phone and the usb cable came out....
so now when i turn my phone on it goes to a black screen with
Fastboot mode started
---reset---
---port charge--
i have tried going into download mode again but it still goes into this fastboot mode.
i found a lot of threads on this such as
http://forum.xda-developers.com/lg-g...arted-t2995854
this got me to install adb/fastboot which i did via
http://forum.xda-developers.com/show....php?t=2588979
however when i try and run through fastboot it just comes up as waiting for device
i have attempted to install lg drivers for this but still nothing.
inside device manager it comes up as
other devices - android?
so clearly the computer is recongnising it, i just need a better driver.
I have the ldf ready to go, if only i could get it to recognise the fastboot command...
anyone able to help, i realise there is a lot of information on the web for this, after extensive research everyone seems to suddenly get into download mode each time. which is something i cannot go. and no recovery doesnt work either.
other things to note, just to save questions..
i am running LG D855 16gb.
when i attempt to go into recovery it comes up with the option to wipe device, but when i follow through menu comes back to fastboot mode started.
i attempted to install lg pc suite in hope that it would suddenly pick up the device and go through the fix upgrade errors (to no luck)
so to clarify, i cannot get into recovery, or download mode. my screen is sat on fastboot mode started.
i am running windows 8.1 although i have attempted to plug into a laptop with ubuntu but same story.
any suggestions? i have also seen a through about jtag...but i dont have any screwdrivers at this point so trying to avoid that.
thank you for reading, kind regards
Inscription à :
Articles (Atom)