My phone is stuck in bootloop. I factory resetted my phone, so usb debugging is now off so, when i connect it to pc and go to recovery it shows in device manager android phone>adb composite device but can't do anything. I also tried fastboot but device not found shows in command prompt. Device is rooted. Phone model is hitech amaze s3. Temporary custom recovery is working. Rom is not available anywhere. It's service centre is in far cities. Does anyone know the solution.
Related
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
MAGnum_21 said:
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If it has a custom recovery, boot into it and wipe data/factory reset.
If it does not, flash a custom recovery. These forums are chockful on guides how to root, flash stuff and fix bootloops.
I looked up how to install recoveries but when i plug in my nexus to my computer it is not recognized. At the bottom of the bootloader screen it says "USB Control Init" and then "USB Control Init End". I do have the proper drivers installed. Is there a fix for this?
Are you sure that you have the correct drivers installed, though?
It's known that people who use Windows have a lot of success with the PDAnet drivers (you can search around here for those), rather then with the standard USB drivers the Google SDK provides.
Greetz
Did you try to run "fastboot devices" in command prompt while it's at fastboot mode and plugged into the PC? What do you see as the result? The guides on XDA should help, but you may also head over to nexusshacks_dot_com for more references.
Sent from my Nexus S using XDA App
With pdanet it requires me to plug in my phone with usb debugging turned on to get the drivers with i cant do because of the bootloop. and when i go into command prompt it says "waiting for device" and won't recognize it. Thanks for the help
Hi all,
Looked through the forum here but mine's slightly different. Installed MM ROM and tried to do factory reset. Phone booted and now stuck on "flashing" TWRP screen. Can't connect through ADB/Odin as getting msg "USB device not recognised.. device malfunction etc". Tried 4 cables and all same. I've both Samsung USB and universal ADB drivers installed on PC. Any help would be appreciated.
Thanks.
hello, I searched but cannot seem to find this situation.
Phone stops at first samsung logo that shows model no and goes no further.
SD card is formatted and there is nothing on it (no backups).
I can boot into recovery (not always), but not download mode. There is nothing available in recovery as card is formatted.
I normally use linux, but used odin in windows.
USB drivers are ok except mtp connection to phone via usb. Phone is recognized as Samsung Android device. I used developer usb drivers and not kies; Should I have used kies.
If someone could point me to a thread that'd be ideal for this situation, I'd appreciate it.
edit:
every once in a while I can log into download mode or recovery. Phone keeps restarting and I have to remove the battery to turn it off and then enter download or recovery.
I can't seem to get the windows drivers to work as the phone is in either booting or in download mode when installing drivers.
kjarak said:
hello, I searched but cannot seem to find this situation.
Phone stops at first samsung logo that shows model no and goes no further.
SD card is formatted and there is nothing on it (no backups).
I can boot into recovery (not always), but not download mode. There is nothing available in recovery as card is formatted.
I normally use linux, but used odin in windows.
USB drivers are ok except mtp connection to phone via usb. Phone is recognized as Samsung Android device. I used developer usb drivers and not kies; Should I have used kies.
If someone could point me to a thread that'd be ideal for this situation, I'd appreciate it.
edit:
every once in a while I can log into download mode or recovery. Phone keeps restarting and I have to remove the battery to turn it off and then enter download or recovery.
I can't seem to get the windows drivers to work as the phone is in either booting or in download mode when installing drivers.
Click to expand...
Click to collapse
OP has already posted in the correct section:
http://forum.xda-developers.com/galaxy-s3/help/soft-brick-t3408861
Thread closed.
i bought yureka plus a month ago and i decided to install custom rom on it but i ended up hard bricking it. i managed to fix it however i noticed that imei has been changed to 123456... I looked for some tutorials on youtube to fix it. None of them worked for me. I have windows 8 on pc and lineage 13 on yureka currently. When i connect my phone to pc its detected as android phone. From here i dont know how to install adb.(when i connect phone for "picture transfer" its detected as adb interface) i followed some vids but whenever i type "adb shell" in terminal it says "adb not found" . if i try to connect in diag mode it gets disconnected. so if i use imei repair tool it doesnt show any devices in diag mode. its been a month since this happened. Any help will be appreciated.
Sorry if I made any mistakes.
hi, im new to this so be kind, i tried to root my Vizio Smartcast Tablet and bricked it, i dont know if is a soft or hard brick because the tablet boots and stays in a bootloop
what the tablet does and doesnt:
it boots
it charges
i can access recovery mode
it cant be recognized by pc
it cant access bootloader
doesnt have USB debuggin enabled
doesnt have MTP enabled
what i already did:
tryed to get into bootloader... doesnt work
tryed to wype/factory reset... doesnt work
tryed to wipe cache... doesnt work
tryed to flash a custom rom(not for this tablet)... doesnt work
tryed ADB fastboot commands... doesnt work
tryed to install TWRP... doesnt work
As this is a very unusual device, i didnt find any stock rom or OEM USB driver(that way my pc can recognize it an restore via pc) for this device, i got in contact with vizio support to see if they can send me a copy of the rom that this devices uses(Android 6.0.1) but as the product is no longer under warranty they couldnt help me.
One curious thing is that when i "select the apply update from adb" from the recovery menu, my pc can recognized it but when i open any recovery tool it stays on "connecting device"