I've searched all over the internet for 2 days now and couldn't find any help.
My phone isnt detected by ADB during its boot. After bootup it shows up in the list of attached devices. Im trying to port MIUI v4 to my device so I need a logcat during the boot because it just hangs at the bootanimation but ADB doesnt see my device during boot. If I force a logcat, the log is emply. Can someone help me please?
I have tried several ROMs and on both Windows and Ubuntu and still no result.
Do you have the right drivers installed?
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Oh yes. ADB and logcat works when the phone is turned on. Just not during boot or bootanimation
Sent from my MB526 using XDA
Can you get to the bootloader/recovery? If you can, wipe data and reflash the ROM.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yes there is nothing wrong with my phone. Im just tryin to port MIUI so I need adb working during boot. But it doesnt detect my phone during the bootanimation.
It works fine after bootanmiation! Problem is when i try to boot MIUI it doesnt go past the animation so I need a logcat. But ADB doesnt work at that time!
Do you find a solution ?
I have the same problem with my tablet.
Adb works well in recovery or when the system is booted up, but not when it is booting... It's very frustrating ^^
Related
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Uberjim said:
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Click to expand...
Click to collapse
Still trying to fix this I now have no recovery and just get the two icons wipe data and fast boot or it just keeps trying to load a Rom that isn't there so it sticks on the main logo screen if I could get it to show in windows that would be great but now I have no recovery I'm not sure how to even get it to install anything once I do !
deleted
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It shows up but then says failed to install driver will try it on different pc,s see if it works thanks for the replies seems fairly easy
Ive found on my device that it sometimes requests two different drivers. One for adb/fastboot, and one for mtp. I just cancel the one for mtp as they are not in the naked driver set, and windows then detects another different device.
Sent from my SO-01C using xda app-developers app
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Uberjim said:
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Click to expand...
Click to collapse
Okay, you're half way home! The reason why nothing shows in adb is because fastboot and adb are two completely different interfaces. When in fastboot, your device will be expecting the fastboot command only.
Now what you will have to do is find a recovery that is in the blob format. Cwm would probably be okay. Twrp would be good, however the new version requires the nvflash version of the bootloader.
Once you find the blob of the recovery you want, place this in the same folder as the file fastboot.exe
It should be in the same place as adb. If not, place the blob somewhere easy to remember.
Then in a command prompt, type
fastboot -i 0x0b05 flash recovery blobfilename
If you placed the blob in the same place as fastboot, then the above will be the blob filename, or better would be to include the path as well.
Sent from my SO-01C using xda app-developers app
Looks like this could help
http://forum.xda-developers.com/showthread.php?t=1662158
Sent from my PadFone using Tapatalk 2
hi guys and girls happy to report that thanks to the community my prime is aliiiive !!! used a utility off here called knives and forks to install adb and then downloaded fast boot and extracted to my users directory then used the fast boot command to push the blob to the prime into recovery then used adb push adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/ and installed virtuous to get it running then it all shows up thankyou to everyone so happy took all of five minutes lol. my trip to london for 3 hours will be less boring now !!!:laugh::highfive:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
ICruentusI said:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
Click to expand...
Click to collapse
Adb doesnt work in fastboot. Use fastboot flash boot boot.img then flash the kernel modules in recovery.
Sent from my HTC6435LVW using xda app-developers app
Wow
Thank you very much. Complete noob at playing with Android devices .
When you flash a kernel, you have to make sure to also flash the kernel modules in recovery. That's what caused the wifi to stop working. Same thing happened to me haha.
Sent from my (Viped out)³ DROID DNA
I messed up I know I did but please help me! I have an HTC One X+ (AT&T) and currently I'm at a dead end. I tried to install and flash Cyanogenmod 10 but my phone did not boot up. I panicked and wiped the whole SD like an idiot to get the ROM off. But now I have no OS to boot up in and no Roms in my SD to Flash. My PC no longer recognizes my phone is connected when in TWRP. So I've tried multiple ways like Side loading or using the ADB Push command but nothing seems to work. I've heard if you have an OTG Cable you can stick a Flash Drive directly in and transfer the ROM on that way. Any help is appriciated!
As far as i know, USB on the go only works when Android is booted. Even if you wiped the device it should affect your device being recognized in recovery. Are you sure you have all the drivers installed?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
As far as i know, USB on the go only works when Android is booted. Even if you wiped the device it should affect your device being recognized in recovery. Are you sure you have all the drivers installed?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
I'm almost 100% guaranteed I have the correct drivers. HTC Sync boots up whenever my phone was plugged in (When it had an OS) and let me access the phones files. Is there any other methods of pushing the ROM.zip in the CMD? Thanks for the reply BTW.
Your best bet is sideloading. But sometimes it takes ages before your device is detected in recovery... If i was you i'd boot into recovery, connect to your PC, then go make something to eat \ go for a walk \ have a game of COD ect lol Come back in 15 mins then try sideloading.
Sent from my HTC One X+ using Tapatalk
I'll give it a go. Thank you so much for the fast replies and help especially. I will let you know what happens!
Sent from my Nexus 7 using xda app-developers app
uninstall htc sync, it messes with adb\fastboot.
uninstalling htc sync, won't uninstall the drivers
Hey, well I finally got the ROM onto my device but now comes a new issue. The phone will not boot after I install the ROM. (I've tried multiple Roms just to see if the one I chose was incompatible). No ROM is working. Here's what I'm doing.
Open boot loader
Select fastboot
Go on my PC and type "fast boot flash boot boot.img" in CMD
Then I go into recovery mode (TWRP)
Clean the dalvik-cache and cache
Go to install
Install the rom
Reboot the device
Sits in boot screen "Htc quietly brilliant"
Sent from my Nexus 7 using xda app-developers app
My phone is from chinavasion it is galaxy i8550 WIN clone with lower specs it is mocor droid 2.0.5 with a fake jellybean speadtrum sc6820 it is rooted i connected the phone via adb and reboot into recovery i have stock recovery not cwm and i tried fixing it btw i meessed up my build.prop file but anyways i tried to fix it via adb and i got a permission error and i have a backup of my build.prop tho ...i just gave up and rebooted to recovery and wiped data/factory reset and ofcourse it didnt work but i lost my adb drivers i cant turn on usb debugging so i cant use adb and i dont know how to accesss recovery i keep ending up in the speadtrum factory test where u test phone hardware nothing else please help if u can altho i highly doubt it and also when i used adb to reboot in recovery and used a zip file it would say signature verification failed :crying::fingers-crossed: But i trust in xda please help even to give me the phone combination keys to recovery and that give me a zip that will be accepted PLEASE i only had the phone for a month
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Fixing
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk[/QUOT
I just fugured out something the problem occured when i took a backup of my build.prop (original one) from my sd card and replaced it with the one in my system folder and forgot to add permissions to it and i restarted my phone and now its bootlooped. When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....ps. my phone is rooted and has mocor droid 2.3.5 with 4.2.2 jellybean so u know its a fake jellybean cuz its a cloned phone and i have no cwm :crying:
Click to expand...
Click to collapse
@BenDroid1
You can write the custom recovery to your recovery partition using dd in an android terminal emulator from the play store. You would need to know which partition holds your recovery.
For MY device (your partition is different) it would be as followed in the terminal emulator:
Code:
su
Code:
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p21
/dev/block/mmcblk0p20 is the partition that holds my recovery on my device - yours will be different!
You can also use this method for the boot.img towards the boot partition as well as data to data partition, and so forth.
If you have CWM and you were smart enough to create a backup of your device, then I would write the custom recovery to your recovery partition, boot in to CWM, and restore your device with your backup. Then, reboot, plug device in to your computer, allow the computer to reinstall the drivers and hopefully at this point you should be able to establish connection with adb/fastboot again.
Sent from my K2_CL using Tapatalk
Example 1
Sent from my K2_CL using Tapatalk
Example 2
Sent from my K2_CL using Tapatalk
Cant do that
How do uexpect me to do all of that when everytime i boot my phone the its stuck on the logo and i Dont have cwm ...my phone is bootlooped
BenDroid1 said:
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....
Click to expand...
Click to collapse
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
no i havent and sorrry i ...i will be clearer when i press power plus volme up i get speadtrum factory test where u test phone hardware but no android recovery
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
unfortunately looks like u cant help me cuz neither that wont showup
BenDroid1 said:
unfortunately looks like u cant help me cuz neither that wont showup
Click to expand...
Click to collapse
I'm sorry bro. Maybe someone else on here will pickup where I left off. Good luck friend.
Sent from my K2_CL using Tapatalk
I have done a lot of Googling over the past couple weeks trying to solve this issue.
I have two Alcatel OneTouch Elevate phones (5017B). One is working and the other is bricked. I tried to turn off the softkeys using a root app (something I had done successfully before) and it never booted past the Alcatel boot logo screen after that (screen goes black). I can boot into (stock) recovery, and wiping cache and data don't fix the issue. I am pretty sure I have corrupted something.
I have managed to extract all of the partitions from my good phone (system.img, boot.img, recovery.img, etc.), and I can boot into recovery on the bricked phone. However, it is stock recovery, and I have yet to find a twrp or cwm for the phone (I am currently looking into making my own or using one for a different phone with the same chipset).
Does anyone know how I can unbrick this phone or how I can create a bootable sd card so I can start up the phone and try to fix what's broken?
Thanks!
Are you rooted? Does adb detect the device? If so, I can probably help you fix it easily.
Sent from my XT1609 using Tapatalk
RealWelder said:
Are you rooted? Does adb detect the device? If so, I can probably help you fix it easily.
Sent from my XT1609 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Yes I am rooted. I have not been able to get the bricked phone recognized by adb yet. I have tried to connect while in recovery with no success. When regularly booting (such that it goes to black screen as stated), my computer (Windows) makes the "usb device plugged in" beep sound, but nothing comes up in explorer and adb does not recognize anything when I use 'adb devices'. I am not sure if my device has a download mode; that (I feel like) is my last hope if I can't reinstall my partitions with an SD card or something.