Help Please - Fire Q&A, Help & Troubleshooting

My fire 5th gen tablet worked for the longest time with gow but I was gonna change the boot screen with a boot animation changer and now I cant get my computer to recognise that its hooked up while it is now stuck in a boot loop although i can still get to fast boot and stock recovery but with the computer not pickup when I hook it up how can I do anything please help asap the last rom that was on it before I flashed to amazon nexus by gow was 5.3.10 fire os.

Crashoverride1993 said:
My fire 5th gen tablet worked for the longest time with gow but I was gonna change the boot screen with a boot animation changer and now I cant get my computer to recognise that its hooked up while it is now stuck in a boot loop although i can still get to fast boot and stock recovery but with the computer not pickup when I hook it up how can I do anything please help asap the last rom that was on it before I flashed to amazon nexus by gow was 5.3.10 fire os.
Click to expand...
Click to collapse
Reboot PC. Try changing the USB cable; amazing how often this is the culprit. Also try a different USB port, preferably USB2. Avoid external hubs which can block tethered communications. If all else fails try a different computer.

Davey126 said:
Reboot PC. Try changing the USB cable; amazing how often this is the culprit. Also try a different USB port, preferably USB2. Avoid external hubs which can block tethered communications. If all else fails try a different computer.
Click to expand...
Click to collapse
is it possible for 3 Diffrent USB cables to be bad all at once one of them is relatively new and if this was not enough I tryed on my desktop and it too is not seeing the tablet If I had been the one that had the funds to by it I would have gotten a much more hackable tablet but this one was a christmas gift.

Crashoverride1993 said:
is it possible for 3 Diffrent USB cables to be bad all at once one of them is relatively new and if this was not enough I tryed on my desktop and it too is not seeing the tablet If I had been the one that had the funds to by it I would have gotten a much more hackable tablet but this one was a christmas gift.
Click to expand...
Click to collapse
Probably not. Possible device has a problem with USB port. Open Windows Device Manager; look for any activity while tethering/untethering while device is in recovery mode (specifically the option that permits reloading FireOS).

Davey126 said:
Probably not. Possible device has a problem with USB port. Open Windows Device Manager; look for any activity while tethering/untethering while device is in recovery mode (specifically the option that permits reloading FireOS).
Click to expand...
Click to collapse
I got it recognising it in fastboot but not adb can I restore it with fastboot somehow

Crashoverride1993 said:
I got it recognising it in fastboot but not adb can I restore it with fastboot somehow
Click to expand...
Click to collapse
Unfortunately, no as fastboot environment is crippled on this device.

Davey126 said:
Unfortunately, no as fastboot environment is crippled on this device.
Click to expand...
Click to collapse
I dont know why it dosent see the device when booted into adb but it dosent but it see's the device booted as fast boot so what could be wrong Also the adb sees it when its constantly rebooting from the boot loop but its only temporary because when it reboots it temporarly disconnects so any thing else I really want to fix this thing but dont know what else to do.

Crashoverride1993 said:
I dont know why it dosent see the device when booted into adb but it dosent but it see's the device booted as fast boot so what could be wrong Also the adb sees it when its constantly rebooting from the boot loop but its only temporary because when it reboots it temporarly disconnects so any thing else I really want to fix this thing but dont know what else to do.
Click to expand...
Click to collapse
Assume you are selecting "apply update from ADB" in recovery *prior* to adb connection attempt. While a long shot also try the two wipe options although I'd be surprised if either changed the situation.
Good chance irreversible damage occurred when you tried to change the bootloader (vs ROM) boot animation. As the bootloader is locked on this device little more can be done beyond the steps previously outlined.

yes I tried the wipe options nothing changed as for adb update I tried while connected and when I tried that app I thought it was gonna change the ROM animation I dont think the bootloader was quite touched as it still says amazon and then shows the custom boot screen then reboots without actually booting the rom but yes the the rom boot screen was my intended change Good news I think however is I belive now that my cable is faulty because When messing with it it seems while in adb mode I get unknown device

Crashoverride1993 said:
yes I tried the wipe options nothing changed as for adb update I tried while connected and when I tried that app I thought it was gonna change the ROM animation I dont think the bootloader was quite touched as it still says amazon and then shows the custom boot screen then reboots without actually booting the rom but yes the the rom boot screen was my intended change Good news I think however is I belive now that my cable is faulty because When messing with it it seems while in adb mode I get unknown device
Click to expand...
Click to collapse
That was the first thing mentioned and is often the primary culprit. Add your experience to countless others who dismiss or underweight potential cable issues. Also look for a loose USB connector (rare) which can exhibit similar symptoms.

Davey126 said:
That was the first thing mentioned and is often the primary culprit. Add your experience to countless others who dismiss or underweight potential cable issues. Also look for a loose USB connector (rare) which can exhibit similar symptoms.
Click to expand...
Click to collapse
Its weird that the cable is the problem cause it seems 3 did nothing and one says unknown device buying another cable though Im not sure when I can do.

Crashoverride1993 said:
Its weird that the cable is the problem cause it seems 3 did nothing and one says unknown device buying another cable though Im not sure when I can do.
Click to expand...
Click to collapse
Just giving an update I bought a brand new actual amazon usb cable and got it running again no sweat even rerooted and blocked ota updates

Related

Bricked Nexus One?

Took my Nexus One off my cradle today to see it was locked up. Thought no biggie, I'll pull battery and restart it.
Now when it boots it comes up with four bars. Red, Green, Blue, White and the 3 skateboarding Droid Bots. I have no clue what to do now.
I was running Cyanogenmod (Forget the version, but it was 2-3 months old. I have not done anything to my phone except add the ebay app to it yesterday.
I can not get my computer to recognize it as a Nexus One anymore so I can not use Fastboot. I tried recovery from HBOOT, but keep coming up the same way.
Please Help
Ray
Picture of my Nexus One from Wifes iPhone...
I can get to FASTBOOT and when connected to USB it says FASTBOOT USB, but my computer fails to recognize the device and it goes back to FASTBOOT.
I can not turn on USB Debuging because it will not boot normal. I do not know what to do.
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Yes its the only thing I see.
I do not see anything Prior.
I have tried to boot to recovery many many times. I have 3 different results.
1. Nexus X with nothing else
2. Nexus X with Unlocked icon below
3. The screen you see
Either way, it does not move forward it just hangs. Is there a way to turn on USB debugging from FASTBOOT or HBOOT?
Ray
Russ T. Nail said:
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Click to expand...
Click to collapse
looks like the bootloader screen, thats what the rainbow screen was on the g1.
havent seen it on the nexus though so it could be something else.
Did you try a factory reset using hardware keys?
I believe you do this by holding vol-down, power and trackball for 5 secs.
That does not seem to do anything but take me to FASTBOOT
There has to be a way to turn on USB Debugging from FASTBOOT?
If you can get fastboot usb to work you could try the following (using latest amon_ra recovery.img):
Code:
fastboot boot c:\path\to\recovery.img
To boot into recovery, then use adb or try nand-ing etc.
if you get that far (recovery)
Code:
adb shell reboot normal
should take you into os.
However, the colored bars look like some pretty serious hardware failure I'd guess...
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
check this out to help you get fastboot to work http://forum.xda-developers.com/showthread.php?t=613217
i know its titled ADB but it might help you out.
TheQue said:
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
Click to expand...
Click to collapse
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
have you tried to contact htc or even google?theyve helped me over the phone even knowing i have an unlocked bootloader.
pvillasuso said:
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
Click to expand...
Click to collapse
not the sd card if it was a bad card it would just bootloop
if you have SDK you can see what the phone is doing with ddms
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
That pic reminds me of the MDA Win Mobile 5 boot screen, real similar...
Don't know how to help, keep us updated if you figure this one out.
gtrplr71 said:
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
Click to expand...
Click to collapse
I 2nd that. Try using ddms or logcat.
Good luck man!
What happens when you try to flash a rom?

[Q] HTC One Half Bricked?

So, pretty much the title. I'm pretty noobish when it comes to phones, and think i messed it up. I'm currently with Rogers, and what i did i unlocked it, and put the Google Play edition onto my phone, because i personally did not like the Blink Feed. So me being awful with phones, after the update came out for the Google Play 4.4 KitKat, I decided to update the firmware... Not realizing that it would mess my phone up... I have no rom to go back too, which would of probably saved this whole problem... Also another huge problem, my Phone does not want to be found by my computer... I would of just easily fixed it by flashing another rom, but i can't because it doesn't want to be recognized. Basically my phone right now boots up half way to the Google Logo, and then goes to a blue/green screen and stays there till i decide to turn it off.. I can get into bootloader, but that's as far much as i can do... Any help would be awesome, because i'm lost as far as it goes and decided to come here to post about it... Considering this is the best website for phones and whatnot... Thanks ahead of time guys!!
BUMP!
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
SaHiLzZ said:
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
Click to expand...
Click to collapse
The thing is, the only time it can recognize it is when it is in fastboot, it says it's connected but it on the phone but doesn't connect to the computer :/
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
SaHiLzZ said:
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
Click to expand...
Click to collapse
Sorry for super late reply, fell asleep. Also Windows 7, tried installing different drivers to no avail
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
SaHiLzZ said:
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
Click to expand...
Click to collapse
Says it's connected, [FastBoot USB] Also says it's connected via Device Manager, http://gyazo.com/f9dfe5d0ab3f184f3b085d776e765d2c But, does not appear in my computer. http://gyazo.com/b23dc0defe0d657a7a4aab8abcc2866e Wish i could get a picture of my phone as well, but you know

[Q] MTP MHL not functioning

So, finnaly solved!
After reading the whole internet (literally) about this problem happening to many HTC (but not only HTC) phones, including not chargind just when turned off, not recognized by computer (including adb, fastboot), going in car mode, I finally found the solution
Here is what I tried
Several custom and stock kernel and recovery flash, different nandroid backups, different roms including stock even clean install (weird, see later why), different cables, drivers, port cleaning.(RUU isn't possible as the phone doesn't get recognized)
The solution however was muck simpler, just wipe cache and dalvik cache and BAM! all working (at my initial arhd rom)
What I suggest (the order doesn't matter) from all the reading done before conclude it's a hardware problem is:
DO A NANDROID BACKUP!
Try different cables and drivers, even computers
Uncheck the fastboot option in power settings and reset
Clean the port with alcohool (or similar), with the phone shut down and then dry it completely
Wipe cache and dalvik cache
Restore the nandroid backup several times, at some people this did the trick
Boot in safe-mode if possible (APM), this way you can check if it's a 3rd party software that can give problems as in safe mode only stock apps are available
Hope I helped
Hello,
Long story short, out of the blue my One doesn't get recognized by any computer, I tried 3 different laptops, all 3 with win7,different cables, latest HTC drivers installed, uninstalled and installed again, but no succes, even my One doesn't get the usb icons show up when I connect it to any laptop, BUT it does charge
Anyway I tried flashing another Rom,factory reset, kernel but nothing changes, adb and fastboot don't recognize my phone
Also the Icon appears when I connect the phone to an MHL adapter but no picture shows up on TV, it worked before
edit: when booted in fastboot it says fastboot AC, not fastboot usb
The get back to HTC solution is a no go as I don,t have any invoice of buying this phone and in EU is required for warranty
I'm currently on ARHD 41.0 kk 4.4 and Elementalx 10.10.1 kernel, S-off, usb debugging on, TWRP 2.6.3.4
What should I try to fix this? Thanks for any suggestions made!
I have the exact same thing, but the device is the HTC One V. It'll charge, but any attempt for it to be recognized as a usb device fail. I have figured out that the usb connector is bad.
Do you get a snug fit when you plug it in to a usb cable,or is it loose and wobbly?
BCH/HTC said:
I have the exact same thing, but the device is the HTC One V. It'll charge, but any attempt for it to be recognized as a usb device fail. I have figured out that the usb connector is bad.
Do you get a snug fit when you plug it in to a usb cable,or is it loose and wobbly?
Click to expand...
Click to collapse
It's not wobbly at all. But if it's a usb connector failure, why does charging work?
tudorlv said:
It's not wobbly at all. But if it's a usb connector failure, why does charging work?
Click to expand...
Click to collapse
I agree. It's bizzare. If it's charging fine and it's not loose, it doesn't make sense. I assume that HTC sync won't recognize it either? Have you tried relocking the bootloader and go back completely stock? Do you also get the Windows error that the "usb device has failed"?
BCH/HTC said:
I agree. It's bizzare. If it's charging fine and it's not loose, it doesn't make sense. I assume that HTC sync won't recognize it either? Have you tried relocking the bootloader and go back completely stock? Do you also get the Windows error that the "usb device has failed"?
Click to expand...
Click to collapse
No, htc sync does not recognize it, didn't try relocking and get stock. Have you? so I don't go that way without succes. Lastly, no windows error when connecting the phone, not even that annoyng beep sounds.
tudorlv said:
No, htc sync does not recognize it, didn't try relocking and get stock. Have you? so I don't go that way without succes. Lastly, no windows error when connecting the phone, not even that annoyng beep sounds.
Click to expand...
Click to collapse
Crap. I just realized that relocking the bootloader is impossible if it can't be recognized as "usb fastboot" or "adb device".
That sucks man. It really doesn't make sense. Try uninstalling everything HTC related, reinstall drivers, and then reboot your pc.
install drivers again and see if that does anything.
BCH/HTC said:
Crap. I just realized that relocking the bootloader is impossible if it can't be recognized as "usb fastboot" or "adb device".
That sucks man. It really doesn't make sense. Try uninstalling everything HTC related, reinstall drivers, and then reboot your pc.
install drivers again and see if that does anything.
Click to expand...
Click to collapse
I know it sucks. Already tried uninstalling and reinstalling everything related with no succes. I'm thinking this could be solved (or tried) by terminal emulator commands on Rom toolbox, if it's not hardware related. I will backup my sdcard trough airdroid (it will take long) and try to format it
WTF my internet data connection does't work either, wifi and gps works though
EDIT: data works, carrier fault now it's ok
tudorlv said:
WTF my internet data connection does't work either, wifi and gps works though
Click to expand...
Click to collapse
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
BCH/HTC said:
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
Click to expand...
Click to collapse
Ok, I will try later this day with other cables, hope it works. I will get back here if successful
BCH/HTC said:
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
Click to expand...
Click to collapse
So tried right now with a working cable, win7, it does recognize a galaxy3 but not the One
Just realised that if I format the sdcard there is no way of reinstalling or recovering anything
tudorlv said:
So tried right now with a working cable, win7, it does recognize a galaxy3 but not the One
Just realised that if I format the sdcard there is no way of reinstalling or recovering anything
Click to expand...
Click to collapse
Man...this is bizarre. I wish I had some other suggestions for you. The only thing I can think of is that the data partition is now corrupted within the device. How that would happen though, I have no idea.
I found this write-up on the web. Maybe it can help you, but to be honest, I am not positive it'll help. There has to be some other more experienced veterans on this site that can help you out some more.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
BCH/HTC said:
Man...this is bizarre. I wish I had some other suggestions for you. The only thing I can think of is that the data partition is now corrupted within the device. How that would happen though, I have no idea.
I found this write-up on the web. Maybe it can help you, but to be honest, I am not positive it'll help. There has to be some other more experienced veterans on this site that can help you out some more.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
Click to expand...
Click to collapse
Well, thank you for trying to help, but it seems nothing that can be done by connecting to a computer (adb fastboot commands) is working.
I am pretty sure that the micro usb port is not damaged because this morning when I booted the One after 3 or so minutes (still connected to my win7 64b laptop) it was detected by windows, even both usb icons appeared in statusbar on phone, and pretty surprised I disconnected and reconnected it but it failed.Tried to move the usb connection in ever way possible without breaking it but nothing. You can't imagine the frustration...
I can't go back to stock as I can't flash the recovery or anything else from computer as I stated before.
As everything else is working perfectly including charging I'm afraid to try possible solutins without being able to revert them easily, so my cry for help is to someone who knows how to use terminal emulator commands and make something out of it.
Thanks again!
tudorlv said:
Well, thank you for trying to help, but it seems nothing that can be done by connecting to a computer (adb fastboot commands) is working.
I am pretty sure that the micro usb port is not damaged because this morning when I booted the One after 3 or so minutes (still connected to my win7 64b laptop) it was detected by windows, even both usb icons appeared in statusbar on phone, and pretty surprised I disconnected and reconnected it but it failed.Tried to move the usb connection in ever way possible without breaking it but nothing. You can't imagine the frustration...
I can't go back to stock as I can't flash the recovery or anything else from computer as I stated before.
As everything else is working perfectly including charging I'm afraid to try possible solutins without being able to revert them easily, so my cry for help is to someone who knows how to use terminal emulator commands and make something out of it.
Thanks again!
Click to expand...
Click to collapse
Sorry to hear that man. I hope everything gets sorted. Good Luck!!:good:
BCH/HTC said:
Sorry to hear that man. I hope everything gets sorted. Good Luck!!:good:
Click to expand...
Click to collapse
Solved, check first post (wipe cache and dalvik cache)
tudorlv said:
Solved, check first post (wipe cache and dalvik cache)
Click to expand...
Click to collapse
Wow!...I can't believe it was that easy. That's awesome though. Glad you got it up and running again.
tudorlv said:
Solved, check first post (wipe cache and dalvik cache)
Click to expand...
Click to collapse
how to wipe dalvik cache without custom recovery
tudorlv said:
So, finnaly solved!
After reading the whole internet (literally) about this problem happening to many HTC (but not only HTC) phones, including not chargind just when turned off, not recognized by computer (including adb, fastboot), going in car mode, I finally found the solution
Here is what I tried
Several custom and stock kernel and recovery flash, different nandroid backups, different roms including stock even clean install (weird, see later why), different cables, drivers, port cleaning.(RUU isn't possible as the phone doesn't get recognized)
The solution however was muck simpler, just wipe cache and dalvik cache and BAM! all working (at my initial arhd rom)
What I suggest (the order doesn't matter) from all the reading done before conclude it's a hardware problem is:
DO A NANDROID BACKUP!
Try different cables and drivers, even computers
Uncheck the fastboot option in power settings and reset
Clean the port with alcohool (or similar), with the phone shut down and then dry it completely
Wipe cache and dalvik cache
Restore the nandroid backup several times, at some people this did the trick
Boot in safe-mode if possible (APM), this way you can check if it's a 3rd party software that can give problems as in safe mode only stock apps are available
Hope I helped
Hello,
Long story short, out of the blue my One doesn't get recognized by any computer, I tried 3 different laptops, all 3 with win7,different cables, latest HTC drivers installed, uninstalled and installed again, but no succes, even my One doesn't get the usb icons show up when I connect it to any laptop, BUT it does charge
Anyway I tried flashing another Rom,factory reset, kernel but nothing changes, adb and fastboot don't recognize my phone
Also the Icon appears when I connect the phone to an MHL adapter but no picture shows up on TV, it worked before
edit: when booted in fastboot it says fastboot AC, not fastboot usb
The get back to HTC solution is a no go as I don,t have any invoice of buying this phone and in EU is required for warranty
I'm currently on ARHD 41.0 kk 4.4 and Elementalx 10.10.1 kernel, S-off, usb debugging on, TWRP 2.6.3.4
What should I try to fix this? Thanks for any suggestions made!
Click to expand...
Click to collapse
HI man , I have a similar problem,the app car mode start automatically, the pc doesn't recognize my htc one and doesn't recharge it, but i have the options of 'fastboot usb' so i've flash other room : cyano and gpe stock, but however it doesn't work. the strange thing is that after connecting the phone to pc i'cant recharge it with the charger but I have to restart it before and so it works. I've wiped cache and dalvik cache but it still not work :crying:
Mr.Ronik said:
HI man , I have a similar problem,the app car mode start automatically, the pc doesn't recognize my htc one and doesn't recharge it, but i have the options of 'fastboot usb' so i've flash other room : cyano and gpe stock, but however it doesn't work. the strange thing is that after connecting the phone to pc i'cant recharge it with the charger but I have to restart it before and so it works. I've wiped cache and dalvik cache but it still not work :crying:
Click to expand...
Click to collapse
I know this is very late but have you get any solution for it?

[Q] Kindle F.HD 7-doesn't boot and win won't recognize device

Hi Guys,
So a few months ago I was trying to update to CM10 and when I was with TWRP i stupidly pressed wipe all instead of just flash as it was required at that time. I ended up deleting EVERYTHING or so it seams. Kindle won't even show any logos, screens, nothing, key combinations do nothing and when I connect it to any PC the PC "goes crazy" with it, the sound windows make when a USB device is connected and when you disconnet one? it constat, like it connects/disconnects/connects/disconnects/ and so on. I get a message that windows cannot recongize the device.
My guts tell me I absolutely wiped everything even twrp and now its a blank piece of hardware. is there a way to come back from this??
Appreciate any helpo I could get (and yes, regular users should not mess with stuff lie this. i know. )
Thanks, Charlie.
Do you have a fastboot cable? You will need to get into fastboot and flash a full restore.
Red_81 said:
Do you have a fastboot cable? You will need to get into fastboot and flash a full restore.
Click to expand...
Click to collapse
Unfortunately I don't, and customs in my country won't let almost anything go through if I buy it online. If there is still hope to recover it I will try and have a friend buy one when abroad.
Once I get my hands on said cable what will it do and what would the next steps be?
Thanks a lot for replying @Red_81!
You can make one yourself if you're handy. Check out the SRT tool for how to do a full restore

Tried flashing franco to Linneage 15.1 -- need some help unbricking

Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.

Categories

Resources