I my honor 5x KIW-L24 is stuck in a bootloop for approximately 4months now and I have no idea how to fix it. I had installed cyanogenmod 13 onto it and replaced the recovery with the cyanogenmod one. Whenever i boot my phone it doesnt even go past the logo part. My computer doesnt even detect or recognize the phone!! ((
vyarngnork said:
I my honor 5x KIW-L24 is stuck in a bootloop for approximately 4months now and I have no idea how to fix it. I had installed cyanogenmod 13 onto it and replaced the recovery with the cyanogenmod one. Whenever i boot my phone it doesnt even go past the logo part. My computer doesnt even detect or recognize the phone!! ((
Click to expand...
Click to collapse
If you have adb installed use it and flash twrp latest one off there site for kiwi. Once done do a full wipe under advanced then connect phone to PC and see if it pops up should and copy latest copy of Lineage cm 13 also gapps if needed.
Sometimes windows 10 might be a booger and not detect your phone and there is a mtp inf file u might have re install to get it to detect it.
Related
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
A.R.Cante said:
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
Click to expand...
Click to collapse
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
abidifethi said:
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
Click to expand...
Click to collapse
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
A.R.Cante said:
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
Click to expand...
Click to collapse
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
abidifethi said:
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
Click to expand...
Click to collapse
I tried this now on my Desktop Computer and it worked fine. I didn't need to install drivers manually. It installed it by itself and therefore i was able to use odin!
I flashed the new recovery and put the omnirom and pa-gapps on my sd card (I also tried this on my notebook but my card reader is maybe broken)
so i installed teamwin recvovery over pc, put rom and gapps on my sd card and flashed them over recovery.
Now all works fine.
Thank you for your help.
But what I don't understand is my Win 7 OS (32 bit) is recently set up on my VM everything was fresh but it didnt recognized my device... Google says a lot of people are having this issues. I've tried everything whenever I found allegedly a solution for this problem. None of them worked. I simply switched the computer and everything is fine. This is ridiculous. One year ago, when I had running windows as main OS, there were no problems at all. If the problem was caused by a virtual machine I think that not many people would complain about this issue.
Kind regards
Why would old Win 7 recognize your device unless you install drivers .
JJEgan said:
Why would old Win 7 recognize your device unless you install drivers .
Click to expand...
Click to collapse
I don't really understand your comment. The Problem of this USB error has no root. When your Windows System says error code 10: device cannot start then you have a big problem because you don't know why and how to fix this. Try and Google this. You will find thousands of people complaining the same error. Everyone has other solutions for that. Some edit their registry, others simply do a soft-reset and try another USB-Port.
Samsung support can't help you at all because they don't know why this is happening. And the solving of this problem is really random. i tried for hours to solve this with no success (except switching to another computer).
Windows says on my laptop the device cannot start but it is perfectly connecting to my other computer. How can this happen? I don't know. Maybe the error code 10 is not that specific and there is something other wrong than my device.
i have a nexus 5 used to run cm13. now only twrp.
when i wanted to instal a new rom, i deleted the old one(did full wipe, all options avileble in the twrp option), before realesing i had no new rom. i went to my computer to put a new rom on in. the my computer would not find my phone. which it used to do. drivers and everything are up to date. i tested it on multiple computers. even other computer where other nexus 5 did connect on.
since the nexus 5 does not support sd card or otg. so i can not put the file on any other way than trough my computer but since i cant connect it. i was hoping someone might now a way to get the file on my phone
tl;dr
-no rom only twrp
-no computer acces
jellestap said:
i have a nexus 5 used to run cm13. now only twrp.
when i wanted to instal a new rom, i deleted the old one(did full wipe, all options avileble in the twrp option), before realesing i had no new rom. i went to my computer to put a new rom on in. the my computer would not find my phone. which it used to do. drivers and everything are up to date. i tested it on multiple computers. even other computer where other nexus 5 did connect on.
since the nexus 5 does not support sd card or otg. so i can not put the file on any other way than trough my computer but since i cant connect it. i was hoping someone might now a way to get the file on my phone
tl;dr
-no rom only twrp
-no computer acces
Click to expand...
Click to collapse
You can try to install nexus driver...do pc find the nexus in download or recovery mode?
hi everyone i have a 10.1 " chinese tablet on an mtk6592 cpu with 3gb ram running marshmallow . i left it plugged into my windows 10 pc that was having issues with its modified xeon cpu . basically my daughter unplugged it from the pc used it then switched t off overnight next day it hangs on android screen and doesnt boot . adb doesnt see it so im assuming usb debugging is switched off . fastboot sees it but wont flash it.
when i boot it into recovery mode nd run a test it states it has a missing xbin file and 3 modified files but my daughter swerars she didnt root it or touch anything. now when i try to apply update from sd card it goes into the os on the tablet but doesnt list any files on the sd card . i have since swapped out the xeon for an old quadcore chip and reinstalled an os but went with linux mint . now i can only see the device in fastboot but not in adb and i get a mount error when i try to connect to pc in anything but fastboot mode . im no pro but im pretty competent on pcs but ive literally zero experience on android flashing etc all ive tried so far is from 3 weeks of reading forums online but im no closer to solving my problem does anyone have any ideas what i can do on a linux os . ps flashtool doesnt recognise it as connected either.
thanks for any help in advnce
I am having same problem
Brother i am having same problem. But difference is that i did it bu mistake. I installed custom bootloader and custom recovery and usb debugging is off and now my phone is stuck at company logo. if you find and aolution please inform me too
sagarrathee77 said:
Brother i am having same problem. But difference is that i did it bu mistake. I installed custom bootloader and custom recovery and usb debugging is off and now my phone is stuck at company logo. if you find and aolution please inform me too
Click to expand...
Click to collapse
no worries dude i think my daughter knocked something on the computer because i had installed kingo root to root a couple of android boxes and it was open when i came back to my machine
strongbow235 said:
hi everyone i have a 10.1 " chinese tablet on an mtk6592 cpu with 3gb ram running marshmallow . i left it plugged into my windows 10 pc that was having issues with its modified xeon cpu . basically my daughter unplugged it from the pc used it then switched t off overnight next day it hangs on android screen and doesnt boot . adb doesnt see it so im assuming usb debugging is switched off . fastboot sees it but wont flash it.
when i boot it into recovery mode nd run a test it states it has a missing xbin file and 3 modified files but my daughter swerars she didnt root it or touch anything. now when i try to apply update from sd card it goes into the os on the tablet but doesnt list any files on the sd card . i have since swapped out the xeon for an old quadcore chip and reinstalled an os but went with linux mint . now i can only see the device in fastboot but not in adb and i get a mount error when i try to connect to pc in anything but fastboot mode . im no pro but im pretty competent on pcs but ive literally zero experience on android flashing etc all ive tried so far is from 3 weeks of reading forums online but im no closer to solving my problem does anyone have any ideas what i can do on a linux os . ps flashtool doesnt recognise it as connected either.
thanks for any help in advnce
Click to expand...
Click to collapse
Did you install mtk usb drivers? If not, try to install it for SP Flash Tool to recognize your device. I also got the same problem before but installing mtk usb drivers solved it. It's worth a try. Hit thanks if it helped you.
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
sagarrathee77 said:
Brother i am having same problem. But difference is that i did it bu mistake. I installed custom bootloader and custom recovery and usb debugging is off and now my phone is stuck at company logo. if you find and aolution please inform me too
Click to expand...
Click to collapse
Install SP flash tool, install mtk usb drivers, download the correct rom for your device. The zipped rom should come with a 'scatter file' when unzipped. Run sp flash tool as administrator load scatter file then when sp flash tool reads your device (you can see it at the boottom of sp flash tool window), click download and wait for it to finish. That should solve to bootloop. Hit thanks button if it helped you.
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.
I've been attempting to recover my samsung galaxy A8 from a brick, by flashing the original firmware for 3 days. I successfully got TWRP flashed, and couldn't connect to the phone using MTP, so I ended up using an SD card to transfer the firmware zip. Long story short, I tried to treble it, and it completely bricked, leaving me without TWRP, or anything to boot.
I've put it in download mode, swapped through 10 different USB C cables, and still can't get my PC to recognize it. I've tried two computers, one running arch linux, and the other one through windows 10 and arch linux. Nothing. Whenever I run "lsusb" I can't see the phone. I also can't see it in device manager.
windowsagent said:
I've been attempting to recover my samsung galaxy A8 from a brick, by flashing the original firmware for 3 days. I successfully got TWRP flashed, and couldn't connect to the phone using MTP, so I ended up using an SD card to transfer the firmware zip. Long story short, I tried to treble it, and it completely bricked, leaving me without TWRP, or anything to boot.
I've put it in download mode, swapped through 10 different USB C cables, and still can't get my PC to recognize it. I've tried two computers, one running arch linux, and the other one through windows 10 and arch linux. Nothing. Whenever I run "lsusb" I can't see the phone. I also can't see it in device manager.
Click to expand...
Click to collapse
have you tried flashing it as update via sideload in adb ?
do you have the latest samsung drivers installed ?
try using my tool located here
gav83collins said:
have you tried flashing it as update via sideload in adb ?
do you have the latest samsung drivers installed ?
try using my tool located here
Click to expand...
Click to collapse
I'm stuck without TWRP, so I can't adb sideload. I did try it back when TWRP did boot, but it still didn't recognize it (I tried lsusb and adb devices)
windowsagent said:
I'm stuck without TWRP, so I can't adb sideload. I did try it back when TWRP did boot, but it still didn't recognize it (I tried lsusb and adb devices)
Click to expand...
Click to collapse
you dont need twrp to sideload, you can do it via adb, my tool above will guide you through the process
gav83collins said:
you dont need twrp to sideload, you can do it via adb, my tool above will guide you through the process
Click to expand...
Click to collapse
I'll try to do it then, while in download mode. Thanks!
windowsagent said:
I'll try to do it then, while in download mode. Thanks!
Click to expand...
Click to collapse
my tool will boot you into download mode when necessary. just follow the onscreen instructions
gav83collins said:
my tool will boot you into download mode when necessary. just follow the onscreen instructions
Click to expand...
Click to collapse
My device is just not listed. I see it's just running adb devices, and nothing shows up.
windowsagent said:
My device is just not listed. I see it's just running adb devices, and nothing shows up.
Click to expand...
Click to collapse
Plus I've already got all the drivers installed.
windowsagent said:
Plus I've already got all the drivers installed.
Click to expand...
Click to collapse
you havent got your phones settings for usb set to "charge only" have you ?
gav83collins said:
you havent got your phones settings for usb set to "charge only" have you ?
Click to expand...
Click to collapse
My phone doesn't boot. I deleted the system partition. It's on a bootloop, and the only thing I can do is access download mode.
I was able to plug it in. I used the sim card remover to try to clean up the port.. I'm seriously an idiot...
windowsagent said:
I was able to plug it in. I used the sim card remover to try to clean up the port.. I'm seriously an idiot...
Click to expand...
Click to collapse
so even in download mode, my tool doesnt detect it ? what about in device manager ? does it show up in there ? are you running a windows machine or windows via a virtual machine
Hi so im having a almost same situation here with my a8 2018 so it seems on the phone that it was doing an update and failed and cant boot to android (i think it got corrupted or something) i can access the samsung recovery but if i do reboot or any data deletion i cant get it to work i tried installing twrp recovery but im a biginer and well idk how to do it from the adb update option
ocasds said:
Hi so im having a almost same situation here with my a8 2018 so it seems on the phone that it was doing an update and failed and cant boot to android (i think it got corrupted or something) i can access the samsung recovery but if i do reboot or any data deletion i cant get it to work i tried installing twrp recovery but im a biginer and well idk how to do it from the adb update option
Click to expand...
Click to collapse
update: i managed to get twrp installed
also i found out i need to install new android so if you can link me something good for the a8 2018 i would be gratefull