Related
So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.
Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.
Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.
Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.
Got myself a google LG Nexus 4.
Connecting via USB - 2 different cables, 2 computers, 3 different operating systems (archlinux, debian, windows vista ) - i get nothing (*).
the phone does not acknowledge that it is connected to a computer, but it charges ok.
the computers do not recognize the phone in any way, not even in dmesg (or device manager in windows).
i have tried changing options inside the phone (debugging on/off, mtp/ptp...), even a full factory reset, and going into recovery and wiping cache/dalvik cache. - nothing.
wiggling the cable and such does not help.
i even replaced the usb connector, no change whatsoever.
so something tells me that it is not a hardware problem.
the phone has been upgraded to android 5.0 (before i became the owner).
my endless searches show that nobody knows what's going on, it might be hardware fatigue, it might be related to the upgrade to 5.x, it might be a firmware problem...
any helpful pointers, including downgrading & softbricking the system would be helpful (i just want to install ubuntu phone onto it).
(*) my other android phone connects ok with both cables, to all machines and operating systems.
With the phone in fastboot or recovery mode, is it recognized?
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Go into device manager with your phone connected and uninstall the drivers. Then install "universal adb driver"(google it it's from Koush) with your phone NOT connected.
audit13 said:
With the phone in fastboot or recovery mode, is it recognized?
Click to expand...
Click to collapse
i tried adb, the device list is empty.
booting into recovery, replugging the usb cable, i still get nothing. it's like there's nothing to communicate to, both from the computer's and the phone's point of view.
i will have to play with fastboot (i gather it works only while the phone is booted into recovery?), but i doubt it'll change anything.
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Click to expand...
Click to collapse
do you mean the connector from the usb port, that flat cable snap-on thingy (far right on this image)?
is it realistic to try to fix that?
PS:
meanwhile the battery drained completely and i had a "Red light of death" which i managed to fix like this. i think it will take a while to recharge properly.
Adb commands will work with the phone booted into the rom. Use fastboot commands with the phone in fastboot mode.
Yes, the flat part at the it her end of the USB cable is what connects to the motherboard and is not worth fixing if that is causing the charging problem.
With a red LED, just connect it to a 2.0 amp charger using the original charging cable and let it charge for a few hours.
thanks again.
next thing i realized that the volume rocker isn't working (anymore?).
so i can't boot into recovery.
i don't know how, but once i managed to get into recovery, but couldn't make any choices in there.
anyhow, that sort of cinches it: i'm done with this phone. project failed.
(nevermind, it was a cheap ebay shot)
ubuntu phone will have to wait.
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
enochthegreat said:
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
Click to expand...
Click to collapse
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
I used the hiensberg guide https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
What do you think is the best option from here?
Are you trying to get into fastboot with it connected to computer?
Iceburn1 said:
Are you trying to get into fastboot with it connected to computer?
Click to expand...
Click to collapse
No im already in fastboot mode. Im just trying to restore my devioe so that it works. When i power on my phone it displays the unlocked bootloader warning then goes into fastboot mode. The screen reads-
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
On top of this my device will not connect to my computer through usb and all my data is deleted included twrp. I really dont know what to do
acejavelin said:
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
Click to expand...
Click to collapse
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
enochthegreat said:
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
Click to expand...
Click to collapse
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
acejavelin said:
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
Click to expand...
Click to collapse
The response is no devices attached. I am android 6.0
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
Have you tried rsd lite it might recognize your device?
acejavelin said:
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
Click to expand...
Click to collapse
My pc operating system is windows vista and my device used to show up on device manager. I used to be able to plug the usb and be able to look at my phone saying device connected
enochthegreat said:
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
Click to expand...
Click to collapse
Do you have this when you boot into bootloader/fastboot mode?
Power off, vol - & power?
I think you can't repair it in home.
It looks like you flashed something wrong or something in wrong place.
F.e.: twrp into boot partition.
jonomods said:
Have you tried rsd lite it might recognize your device?
Click to expand...
Click to collapse
Hmm i just tried that and no device showed up. I think after this im just gonna buy a fresh usb cord and if that does work i am scarping this phone. I overall had a very bad experience with this phone anyways. Ill get back to you once i try.
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
acejavelin said:
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
Click to expand...
Click to collapse
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
enochthegreat said:
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
Click to expand...
Click to collapse
Hmm... Sounds like bad luck, hopefully a new, quality cable will take care of it for you
Looks like it was all bad luck. A day after I bricked my phone my charger port broke
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Waancho said:
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Click to expand...
Click to collapse
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
ibphantom said:
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
Click to expand...
Click to collapse
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Waancho said:
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Click to expand...
Click to collapse
Okay, well even from there it's not showing up in XiaoMiFlash's device list
ibphantom said:
Okay, well even from there it's not showing up in XiaoMiFlash's device list
Click to expand...
Click to collapse
Did you try the edl tool AND different cables? I always test cables just to be sure.
Waancho said:
Did you try the edl tool AND different cables? I always test cables just to be sure.
Click to expand...
Click to collapse
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
ibphantom said:
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
Click to expand...
Click to collapse
Did you try flashing a full edl image for your phone?
Waancho said:
Did you try flashing a full edl image for your phone?
Click to expand...
Click to collapse
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
ibphantom said:
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
Click to expand...
Click to collapse
Have you tried using the EDL Tool?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Stupid question, did you take the SD card out?
Hey there guys, so as the title suggests, i'm having a bootloop problem on my m30s sm-307f, i can't access recovery mode, and i'm unable to start the flashing process because i can't even install the usb driver, i've tried several drivers, using several cables, on several systems (windows 7 / windows 10 / windows 11), and i always get that infamous yellow triangle on the SAMSUNG Mobile USB CDC Composite Device in the Universal Serial Bus Controllers section in the device manager, the phone was operating normally one day, and the next day when i try to power it on, i get this, i'm absolutely certain that i did nothing to the phone, not even an update, and it most definitely didn't fall to the ground, please respond, i have really important data there, and it would devastating to lose it, and thanks a lot.
Can you access Download Mode?
UniX1803 said:
Can you access Download Mode?
Click to expand...
Click to collapse
Yes i can.
Ok. Can Odin detect your phone?
UniX1803 said:
Ok. Can Odin detect your phone?
Click to expand...
Click to collapse
No, unfortunately it can't, which is to be expected since windows itself can't detect it.
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
UniX1803 said:
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
Click to expand...
Click to collapse
I do know how to get to download mode, i did of course try, and although it does appear on the phone that it's working, the computer doesn't detect the latter as i explained, and as such, odin doesn't detect it as well.
I was talking about Recovery Mode.
UniX1803 said:
I was talking about Recovery Mode.
Click to expand...
Click to collapse
Sorry, i didn't notice that, i'm unable to access recovery mode either because the phone just keeps rebooting.
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
UniX1803 said:
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help, i really appreciate it, some people are saying that it's a motherboard problem, what do you think ?
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
UniX1803 said:
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
Click to expand...
Click to collapse
You're right, again, thanks a lot for your help.
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
treety said:
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Click to expand...
Click to collapse
I've already tried them, they didn't work as intended unfortunately, thanks for the reply though.
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
stoag said:
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
Click to expand...
Click to collapse
Unfortunately, i wasn't able to, but i think it's most likely hardware related.