[Q] Stuck in bootloop, Volume button broken, ADB not working - HTC One V

So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.

myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons

red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.

myhtconeV said:
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
Click to expand...
Click to collapse
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other

red de0392 said:
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
Click to expand...
Click to collapse
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.

myhtconeV said:
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
Click to expand...
Click to collapse
Hahahah...That's a Beast

myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Recently I have seen one interesting issue that might appear like solution to your problem. According to the description you may try turning off your phone and plugging in a charger. If you will have the same behaviour your phone should start into recovery mode. =)
Edited: Doh! TWRP...
You may try All-In-One-Kit as well. It has high level interface to run adb commands (including Boot into Recovery). Yeah yeah, I've seen your note that adb does not recognize your device, anyway...

Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes.
I have given it for repairs.I have decided not to sell or dispose it.
Its only sometime before I buy a moto g or xperia device. Waiting for my new credit card :fingers-crossed:
which phone would you suggest?
Vickrant.

If you are good with 16gb storage better buy Moto G if not there are a few options like Xperia M , Canvas series and all..

Sorry to be so late to the party, but in case other people get this issue. ADB will often work just after the kernel finishes loading, before it gets shut off. So between the htc boot screen and when the boot anim starts you have a window to commit abd commands. I often use this to save time when flashing kernels etc, notably because my WIP roms rarely make it past bootanim!

red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
You sure about this?i am stuck there and i have cwm recovery installed,will it switch itself straight to recovery after the battery is dried up?i am using sony xperia c

Related

[Q] [Cry] Galaxy Nexus bricked. (Dead fastboot, dead 3e recovery, only safemode

Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium

[Q] Bootloop and not working Volume Rocker - Any Solution?

Hey Guys
I really could need a good Advise. In the past my USB-Port was broken, so i repaired it with a new one, anyway i wasnt careful enough - i pulled of the Volume-Rockers' Connector. There are no contacts left on the Mainboard, so i cant easily install some new Volume Rockers.
Well that wasnt a big Problem for me so far, i just used a Volume-Widget instead. But unfortunately my Device is now stucking within a Bootloop.
Due to the missing Volume-Rocker, i cant access Fastboot or Recovery. I tried to access the Device with the GNex-Toolkit but it wont let me install the Drivers, i guess the Driver crashes within the Bootloop. Letting the Device Boot while connected via USB, wont recognize it as ADB-Device.
I am owning a Galaxy S4 now, but i would like to repair the GNex, so that my Gilfriend might use it. Any chance to access Fastboot Mode or Recovery without the Volume Rockers on a Bootlooping Device?
I allready downloaded the OMAPFlash_tuna Package and managed it to install the OMAP 4440 Driver (it is giving me 2 Seconds to install them when i plug in the powered-off Device). After a few attempts the Omap-Flash Bat-File was running properly. But the Device is still stuck in its Bootloop. Any Advices would be really great.
Best regards
apsis said:
Hey Guys
I really could need a good Advise. In the past my USB-Port was broken, so i repaired it with a new one, anyway i wasnt careful enough - i pulled of the Volume-Rockers' Connector. There are no contacts left on the Mainboard, so i cant easily install some new Volume Rockers.
Well that wasnt a big Problem for me so far, i just used a Volume-Widget instead. But unfortunately my Device is now stucking within a Bootloop.
Due to the missing Volume-Rocker, i cant access Fastboot or Recovery. I tried to access the Device with the GNex-Toolkit but it wont let me install the Drivers, i guess the Driver crashes within the Bootloop. Letting the Device Boot while connected via USB, wont recognize it as ADB-Device.
I am owning a Galaxy S4 now, but i would like to repair the GNex, so that my Gilfriend might use it. Any chance to access Fastboot Mode or Recovery without the Volume Rockers on a Bootlooping Device?
I allready downloaded the OMAPFlash_tuna Package and managed it to install the OMAP 4440 Driver (it is giving me 2 Seconds to install them when i plug in the powered-off Device). After a few attempts the Omap-Flash Bat-File was running properly. But the Device is still stuck in its Bootloop. Any Advices would be really great.
Best regards
Click to expand...
Click to collapse
i dont see a way to boot into fastboot mode without volume keys or adb
i suggest to get a usb jig and flash stock via odin
samersh72 said:
i dont see a way to boot into fastboot mode without volume keys or adb
i suggest to get a usb jig and flash stock via odin
Click to expand...
Click to collapse
Thanks mate, i really appreciate your Help. I'm sorry that im just answering so late, but i was waiting for my USB jig to arrive. I didnt knew that there is this Option with the USB Jig, i just want to let you know that everything went well, and my Galaxy Nexus is finally back to life.
Thanks for your fast reponse :good

Need help ASAP, can pay for you to fix my phone

Apparently my phone is bricked..
I rooted my phone a long time ago when I first got it, never installed any roms or anything.
I get this message on the LG Screen:
"Secure Booting Error problem
Device UnLock!!, so Boot Success!!"
I've tried multiple ways to fix my phone and I can't get any of them working.
I'd be happy to pay the person in a steam game of your choice!!!!
Thank you
AustinBobDox said:
Apparently my phone is bricked..
I rooted my phone a long time ago when I first got it, never installed any roms or anything.
I get this message on the LG Screen:
"Secure Booting Error problem
Device UnLock!!, so Boot Success!!"
I've tried multiple ways to fix my phone and I can't get any of them working.
I'd be happy to pay the person in a steam game of your choice!!!!
Thank you
Click to expand...
Click to collapse
If you use lg flash tool to go back to stock it should work.
2SHAYNEZ
shayneflashindaily said:
If you use lg flash tool to go back to stock it should work.
2SHAYNEZ
Click to expand...
Click to collapse
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
Uninstall and reinstall drivers ... Try different computer. Lg flash tools should fix your problem . goodluck
2SHAYNEZ
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
That message upon boot is normal if your phone has been modified. Mine says it too and my phone is booting up perfectly fine. In fact, it always has said that from the day I first modified it.
Most likely your software is just bricked. First of all, BE HAPPY YOUR PHONE IS JUST SOFT BRICKED! :laugh:
(I recently hard bricked my phone by accidentally flashing a file for a completely different phone... phone was completely dead!)
You need to provide more info for anyone to help you, whether it's me or someone else:
1) What phone are you using? E980, E988, E986, F240, etc etc.
2) Do you have a custom recovery, like CWM or TWRP? (I'm hoping you are because getting software back will be easier).
2.1) Can you boot into this recovery? (hold volume up and power button at the same time. The boot animation will begin and the screen will then shut off again. Once it does, let go of the power button, but keep holding the volume up key. The phone should reboot into recovery. It's tricky to do, and if any other readers notice that I described it wrong, please correct me!)
3) Do you ever see the LG boot animation? (The animated LG logo)
4) Once you see that message upon boot, do you wait for it to pass and hope the phone boots, or do you panic and force the phone off?
5) To get the drivers to install for using LG FlashTool, have you done the following?
- First download and install the drivers from the LG site (I'd link you to it, but I only know the link to the E980 drivers. I don't know what phone you have).
- Once installed, plug your usb cable into your computer, but not the phone.
- Hold the volume up and volume down buttons at the same time while plugging the usb cable into the phone
- Phone should now boot into Download mode and your computer will start installing more drivers. Let them install.
- Change the Com port of the phone to Com41 (ask if you don't know how to do this)
- Continue using the LG Flash Tool.
I apologize if any of this sounds like I'm insulting your Android phone intelligence. I don't know how much of this stuff you know.
spexwood said:
That message upon boot is normal if your phone has been modified. Mine says it too and my phone is booting up perfectly fine. In fact, it always has said that from the day I first modified it.
Most likely your software is just bricked. First of all, BE HAPPY YOUR PHONE IS JUST SOFT BRICKED! :laugh:
(I recently hard bricked my phone by accidentally flashing a file for a completely different phone... phone was completely dead!)
You need to provide more info for anyone to help you, whether it's me or someone else:
1) What phone are you using? E980, E988, E986, F240, etc etc.
2) Do you have a custom recovery, like CWM or TWRP? (I'm hoping you are because getting software back will be easier).
2.1) Can you boot into this recovery? (hold volume up and power button at the same time. The boot animation will begin and the screen will then shut off again. Once it does, let go of the power button, but keep holding the volume up key. The phone should reboot into recovery. It's tricky to do, and if any other readers notice that I described it wrong, please correct me!)
3) Do you ever see the LG boot animation? (The animated LG logo)
4) Once you see that message upon boot, do you wait for it to pass and hope the phone boots, or do you panic and force the phone off?
5) To get the drivers to install for using LG FlashTool, have you done the following?
- First download and install the drivers from the LG site (I'd link you to it, but I only know the link to the E980 drivers. I don't know what phone you have).
- Once installed, plug your usb cable into your computer, but not the phone.
- Hold the volume up and volume down buttons at the same time while plugging the usb cable into the phone
- Phone should now boot into Download mode and your computer will start installing more drivers. Let them install.
- Change the Com port of the phone to Com41 (ask if you don't know how to do this)
- Continue using the LG Flash Tool.
I apologize if any of this sounds like I'm insulting your Android phone intelligence. I don't know how much of this stuff you know.
Click to expand...
Click to collapse
No, no I understand!
1)E980
2)I have TWRP.
3)I only see the LG Logo, the error message and that's it, it goes right to TWRP after that.
4)I wait for it to pass, and it goes to TWRP.
5)I will try this on a different PC, because when I boot into download mode and plug in the phone, the drivers attempt to install but fail. I have attempted to re-install them multiple times, but I'll give it a shot on my laptop tonight, and let you know if that works.
Thanks for the help, and I may PM you later!
AustinBobDox said:
No, no I understand!
1)E980
2)I have TWRP.
3)I only see the LG Logo, the error message and that's it, it goes right to TWRP after that.
4)I wait for it to pass, and it goes to TWRP.
5)I will try this on a different PC, because when I boot into download mode and plug in the phone, the drivers attempt to install but fail. I have attempted to re-install them multiple times, but I'll give it a shot on my laptop tonight, and let you know if that works.
Thanks for the help, and I may PM you later!
Click to expand...
Click to collapse
Have to tried install cwm through twrp then wiping clean and installing a ROM ...
2SHAYNEZ
Me thinks his botloop is due to a bad rom flash, flash a rom(EZ kat is a good choice if you want the AT&T stock experience). follow shayne's instructions.
@AustinBobDox:
I know EXACTLY what the problem is. You ran into the notorious recovery bootloop, which seems to be happening to many Kitkat users running recoveries incompatible with KK.
I had it a few times myself while using CWM, PhilZ Touch, and TWRP (Yeah, I got them on all 3!)
Unfortunately, the TWRP and CWM recoveries posted in this forum cause this bootloop randomly if you have the stock Kitkat rom installed (whether rooted or not). Personally, I have not been able to get out of it. I ended up flashing a "fix" that was supposed to get me out of it, but... it was for a completely different phone (an HTC) and it hard bricked my phone.
SO DON'T FLASH ANY "FIXES"!!!!!!!!!
Technically, the ROM is perfectly fine. I read that this bootloop is caused by the phone setting a flag that tells it to boot straight into recovery. Basically, when you initiate the recovery boot, it sets this flag, and when you reboot the phone, it's supposed to clear the flag. In the case of this bootloop, it doesn't get cleared for some reason.
Luckily, since you are on TWRP, you can try this:
Open the TWRP command console thing (I think it's under Advanced or something).
Type this command EXACTLY:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
DOUBLE CHECK YOUR SPELLING, SPACES, ETC!!
EDIT: I put a part in bold because it's .1
The decimal could easily have been missed if reading on a smaller screen or something.
Submit the command and try to reboot to system via the TWRP menu.
If this doesn't work, then you have no choice but to use the tot method once you get it working.
EDIT: Oh and before getting the drivers to install by plugging in the phone, install these drivers:
http://www.lg.com/us/support-mobile/lg-E980
(Look under Software Update tab)
Whether the command works or not, once you get the phone up and running again, install this recovery:
http://forum.xda-developers.com/showthread.php?t=2760895
It's the only recovery right now that's definitely working on Kitkat without the bootloop issue. The only downside is that it can't mount the external_SD, so anything you flash must be on the internal storage.
EDIT: Oh and in case you can't tell, don't flash this recovery! You install the APK in Android and then open the app and install recovery from there. You need to root first though.
---------- Post added at 03:48 AM ---------- Previous post was at 03:38 AM ----------
luisoman2000 said:
Me thinks his botloop is due to a bad rom flash, flash a rom(EZ kat is a good choice if you want the AT&T stock experience). follow shayne's instructions.
Click to expand...
Click to collapse
With this recovery bootloop, even if you flash a new rom, the bootloop could remain. I wasn't able to try a whole new flash, but I did try restoring a backup (different things, I know) and I still kept booting into recovery.
Oddly enough, this has happened to me on all cwm versions, flashing the hacked twrp was the only way i could get out of it. I use cwm to flash roms, twrp i only use when in bootloop or to flash mods.
Sent from my LG-E980 using Tapatalk
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
Did you make sure under, device manager, your port is set to com 41 for your device?

Htc desire 320 rebooting bootloop (no recovery, no OS, no bootloader)

hi to everyone,
I have a htc desire 320 and I rooted it then flash a not compatible recovery moded and got in bootloop.
after this said the cellphone keeps restarting so I cant use the adb fastboot because its always disconnecting from computer.
I have no recovery to restore from my backup.
I have no OS to boot on.
I never had a bootloader locked or unlocked. none.
I have connecting problem to computer as adb should help.
my brain hurts and my phone is dead I think.
what should I do to just put on a recovery or unlock a bootloader I never had to bring everything back to normal ?
thanks in advance for support,
have a nice day.
mitch1490 said:
hi to everyone,
I have a htc desire 320 and I rooted it then flash a not compatible recovery moded and got in bootloop.
after this said the cellphone keeps restarting so I cant use the adb fastboot because its always disconnecting from computer.
I have no recovery to restore from my backup.
I have no OS to boot on.
I never had a bootloader locked or unlocked. none.
I have connecting problem to computer as adb should help.
my brain hurts and my phone is dead I think.
what should I do to just put on a recovery or unlock a bootloader I never had to bring everything back to normal ?
thanks in advance for support,
have a nice day.
Click to expand...
Click to collapse
Sorry this is for the desire.
Saf98 said:
Sorry this is for the desire.
Click to expand...
Click to collapse
Whats the real codename of the desire 320 is it still like bravo
I finally had pass the problem with flashing it and facing error from the CID
supercid on this model is possible?
Help
mitch1490 said:
Whats the real codename of the desire 320 is it still like bravo
I finally had pass the problem with flashing it and facing error from the CID
supercid on this model is possible?
Click to expand...
Click to collapse
Hello!
I also flashed a recovery.img which put the phone into a boot loop. I am not able to flash my backup because in SP Flash Tool my HTC Desire 320 keeps disconnecting (error 2004).
How did you manage to flash your phone? Could you please help? Or is my phone dead?
Thanks.
Avan7 said:
Hello!
I also flashed a recovery.img which put the phone into a boot loop. I am not able to flash my backup because in SP Flash Tool my HTC Desire 320 keeps disconnecting (error 2004).
How did you manage to flash your phone? Could you please help? Or is my phone dead?
Thanks.
Click to expand...
Click to collapse
dear Avan7,
I managed to flash it by doing checksum checked and usb high speed without battery inside press the volume down hold it and plug <-- important in the computer the usb cable...
you click download first then press button and plug the process will begin in SP flash tool my friend have a nice day....
PS: use the HTC_Desire_320_V01_U_K44_SENSE53_htc_europe_1.00.401.3_by_jamesjerss.zip
its the rom I used and working perfectly moded from stock.
happy Christmas since im noel and have a nice day.
~no more errors peace
mitch1490 said:
dear Avan7,
I managed to flash it by doing checksum checked and usb high speed without battery inside press the volume down hold it and plug <-- important in the computer the usb cable...
you click download first then press button and plug the process will begin in SP flash tool my friend have a nice day....
PS: use the HTC_Desire_320_V01_U_K44_SENSE53_htc_europe_1.00.401.3_by_jamesjerss.zip
its the rom I used and working perfectly moded from stock.
happy Christmas since im noel and have a nice day.
~no more errors peace
Click to expand...
Click to collapse
Thanks a lot! I am going to give it a try .
Blessings.
mitch1490 said:
dear Avan7,
I managed to flash it by doing checksum checked and usb high speed without battery inside press the volume down hold it and plug <-- important in the computer the usb cable...
you click download first then press button and plug the process will begin in SP flash tool my friend have a nice day....
PS: use the HTC_Desire_320_V01_U_K44_SENSE53_htc_europe_1.00.401.3_by_jamesjerss.zip
its the rom I used and working perfectly moded from stock.
happy Christmas since im noel and have a nice day.
~no more errors peace
Click to expand...
Click to collapse
I have Tried plugging mine in holding down the down button and still just kept disconnecting and reconnecting. Is there any other way you know of to flash back to stock? or installing cwm/twrp?
I have even tried on multiple computers...
n3m37h said:
I have Tried plugging mine in holding down the down button and still just kept disconnecting and reconnecting. Is there any other way you know of to flash back to stock? or installing cwm/twrp?
I have even tried on multiple computers...
Click to expand...
Click to collapse
please try removing the battery first.
mitch1490 said:
please try removing the battery first.
Click to expand...
Click to collapse
Already tried, with battery in it boots and crashes, when plugged in without battery it just connects and disconnects over and over.
Have tried multiple cords, usb 2.0 & 3.0 ports. Same story.
Installed mediatek driver, uninstalled; you name it I tried it with the exception of opening it. Haven't got to that stage yet, I'm lazy.
n3m37h said:
Already tried, with battery in it boots and crashes, when plugged in without battery it just connects and disconnects over and over.
Have tried multiple cords, usb 2.0 & 3.0 ports. Same story.
Installed mediatek driver, uninstalled; you name it I tried it with the exception of opening it. Haven't got to that stage yet, I'm lazy.
Click to expand...
Click to collapse
if adb cant be able to be able to connect and stay connected ( bootloop or restarting problems )
then take SP Tool flasher to flash the Scatter MT6582 from stock KK by only remove battery first and let it out.
plug the universal usb port on cable but on the end of the cellphone dont plug it yet...
in SP Tool check the checkboxe in settings to checksum DL DA. and select usb high speed and W/O battery options.
then when the scatter is loaded then you ready to flash. the latest SF Tool is recommanded.
click on Download on SP tool when done the steps. it will hang on idle but at this moment press de volume down button first.
keeps holding that button until the end of flashing process and when hold it now plug the cable to your computer and bam you will be able to flash it to stock or custom your desire 320 without problems and its will not disconnect during process since you holding the volume down button.
that's how I did resolve my problem about months and find my own solution.
hope this helps... dont be shy to let me know if it worked for you or if you still need assitance.
have a nice day.
peace.
This is a forum for the HTC Desire Bravo A8181.
This is a forum for the HTC Desire Bravo A8181.
See with your own eyes.
Help please
mitch1490 said:
if adb cant be able to be able to connect and stay connected ( bootloop or restarting problems )
then take SP Tool flasher to flash the Scatter MT6582 from stock KK by only remove battery first and let it out.
plug the universal usb port on cable but on the end of the cellphone dont plug it yet...
in SP Tool check the checkboxe in settings to checksum DL DA. and select usb high speed and W/O battery options.
then when the scatter is loaded then you ready to flash. the latest SF Tool is recommanded.
click on Download on SP tool when done the steps. it will hang on idle but at this moment press de volume down button first.
keeps holding that button until the end of flashing process and when hold it now plug the cable to your computer and bam you will be able to flash it to stock or custom your desire 320 without problems and its will not disconnect during process since you holding the volume down button.
that's how I did resolve my problem about months and find my own solution.
hope this helps... dont be shy to let me know if it worked for you or if you still need assitance.
have a nice day.
peace.
Click to expand...
Click to collapse
After searching and searching, seems someone actually had the same problem as I do. But for my part even when pressing the volume down before connecting to the computer doesn't keep the phone from connecting and disconnecting, even tried all the buttons combination you can imagine.
I'm wondering if it could be a driver issue, in your case was your device disconnecting every 5 seconds? And do you have any special driver that I should be aware of, personally I have Preloader USB VCOM port version 2.0.0.0...
I hope you got something in mind, I don't know where to look anymore haha.
Thanks again
PS I did everything else, remove battery, disable signature, got scatter MT6582 + download agent for flash tool (also updated), tried with ADB but can't detect device (of course it keeps deconnecting :silly: )
Metal Addict said:
After searching and searching, seems someone actually had the same problem as I do. But for my part even when pressing the volume down before connecting to the computer doesn't keep the phone from connecting and disconnecting, even tried all the buttons combination you can imagine.
I'm wondering if it could be a driver issue, in your case was your device disconnecting every 5 seconds? And do you have any special driver that I should be aware of, personally I have Preloader USB VCOM port version 2.0.0.0...
I hope you got something in mind, I don't know where to look anymore haha.
Thanks again
PS I did everything else, remove battery, disable signature, got scatter MT6582 + download agent for flash tool (also updated), tried with ADB but can't detect device (of course it keeps deconnecting :silly: )
Click to expand...
Click to collapse
even if you have mediatek usb vcom driver or adb drivers else original driver it works on all with the button press.
but set the setting like I said USB support normal without battery W/O and high speed.
don't set it to mediatek com ports on SP tool. but if you have mediatek com port change to port 20. that's what I did change the port com.
mitch1490 said:
even if you have mediatek usb vcom driver or adb drivers else original driver it works on all with the button press.
but set the setting like I said USB support normal without battery W/O and high speed.
don't set it to mediatek com ports on SP tool. but if you have mediatek com port change to port 20. that's what I did change the port com.
Click to expand...
Click to collapse
What version of SP Flashtool are you using?
Well I have tried everything everyone has said so far
No matter what I try I get
BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
Have tried using both
SP_Flash_Tool_v5.1352.01
SP-Flash-Tool-v5.1532.00
Both do the exact same thing, tried checking the AD DL ALL with Checksum boxes, unchecked usb high speed and full speed. Pressing the down button before plugging it it, after. Nothing I do seems to work, in the device manager it just keeps appearing and disappearing over and over
I think a found the solution guys. After a sleepless night , I stumble into a russian forum who got the same problems as ours.
The correct version of the SP FlashTool we need for our device is the SP_Flash_Tool_v5.1348.01_SEC (http://mediafire.com/download/eaar07r2nm1v7t6/SP_Flash_Tool_v5.1348.01_SEC.rar). I read somewhere that it was because of the HTC Desire 320 has a security boot.
If you got a 4008 error, it's probably because you're using Win8-Win10. You need Win7. I'm installing Win7 on my PC right now, so I will tell you more about it later.
If you looking for the stock roms, I found this site : http://easy-firmware.com/index.php?a=browse&b=category&id=1449
If you speak russian, feel free to correct me.
Have a good one guys.
Source: http://4pda.ru/forum/index.php?showtopic=331715&st=12120#entry40719887 (Russian)
EDIT: Alright guys, confirmed working with 0PF1IMG_V01_U_K44_SENSE52_Telus_1.02.661.2_Radio_MOLY_WR8_W1315_MD_WG_MP_V42_F1_P9_release on Windows 7 x64. Model: OPF1100
If you got a CID Error, it's probably because you have flash the wrong rom for your device. I didn't have to restore the NVRAM after this flash, but maybe you will have to.
Hi
I have desire 200 won't turn on,stay in HTC logo
I just have recovery and fastboot with hboot 1.20.0000,,,s-on
I want to flash any ROM on it
Any one help me,please?
Sent from my V3 Plus using Tapatalk
cafestrabac said:
I think a found the solution guys. After a sleepless night , I stumble into a russian forum who got the same problems as ours.
The correct version of the SP FlashTool we need for our device is the SP_Flash_Tool_v5.1348.01_SEC (mediafire.com/download/eaar07r2nm1v7t6/SP_Flash_Tool_v5.1348.01_SEC.rar). I read somewhere that it was because of the HTC Desire 320 has a security boot.
If you got a 4008 error, it's probably because you're using Win8-Win10. You need Win7. I'm installing Win7 on my PC right now, so I will tell you more about it later.
If you looking for the stock roms, I found this site : easy-firmware.com/index.php?a=browse&b=category&id=1449
If you speak russian, feel free to correct me.
Have a good one guys.
Source: 4pda.ru/forum/index.php?showtopic=331715&st=12120#entry40719887 (Russian)
EDIT: Alright guys, confirmed working with 0PF1IMG_V01_U_K44_SENSE52_Telus_1.02.661.2_Radio_MOLY_WR8_W1315_MD_WG_MP_V42_F1_P9_release on Windows 7 x64. Model: OPF1100
If you got a CID Error, it's probably because you have flash the wrong rom for your device. I didn't have to restore the NVRAM after this flash, but maybe you will have to.
Click to expand...
Click to collapse
You my friend are a gentleman and a scholar! downloaded and flashed right away and booted up Am on Win 7 x64 Pro
cafestrabac said:
I think a found the solution guys. After a sleepless night , I stumble into a russian forum who got the same problems as ours.
EDIT: Alright guys, confirmed working with 0PF1IMG_V01_U_K44_SENSE52_Telus_1.02.661.2_Radio_MOLY_WR8_W1315_MD_WG_MP_V42_F1_P9_release on Windows 7 x64. Model: OPF1100
If you got a CID Error, it's probably because you have flash the wrong rom for your device. I didn't have to restore the NVRAM after this flash, but maybe you will have to.
Click to expand...
Click to collapse
Thanks for it, i've got that problem after trying to install custom recovery. I also got the error 2004 but i fixed myself by using DA_SWSEC.bin. Not sure if it work for ur guys or not.
I also learn that althrough HTC 320 is Mt6582 devices but we cant use the method they wrote in mtkrom site to install custom recovery. Now i can find the stock rom of my phone to check flashing custom rom via splashtool. I used telus rom above and i got problem wrong CID and the flash camera not work, if i have msg or phone call missing, it flashes like notice led! At least now my phone is working ok then. I'll try to contact HTC to get stock rom of my phone
Leoisback said:
Thanks for it, i've got that problem after trying to install custom recovery. I also got the error 2004 but i fixed myself by using DA_SWSEC.bin. Not sure if it work for ur guys or not.
I also learn that althrough HTC 320 is Mt6582 devices but we cant use the method they wrote in mtkrom site to install custom recovery. Now i can find the stock rom of my phone to check flashing custom rom via splashtool. I used telus rom above and i got problem wrong CID and the flash camera not work, if i have msg or phone call missing, it flashes like notice led! At least now my phone is working ok then. I'll try to contact HTC to get stock rom of my phone
Click to expand...
Click to collapse
Yeah I forgot to mention that, you need to use the DA_SWSEC on the SP Flashtool. What's your htc 320 model? Your probably have the wrong rom. The telus one is only for NA device.
EDIT: Are you using the HTC Desire 320 with dual sim: http://drop.ndtv.com/TECH/product_database/images/15201573649PM_635_htc_desire_320.jpeg
If this is your device, the Telus rom is not for your device.
This is the EU rom: http://www.mediafire.com/download/z...NSE53_htc_europe_1.00.401.3_by_jamesjerss.zip

I cant boot my oneplus 3 at all

i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?

Categories

Resources