I was in TWRP when I inserted the OTG cable to flash a new ROM, and suddenly the phone went dead.
No boot (vol+/vol- power)
Not detected by adb
No LED when charging
I believe some OTG contact shorted and damaged the power circuitry, any experience about that?
Very sad about that...
Related
I tried to make the internal memory swap adb method found on the forum, but the command adb devices stuck. I tried to restart and nothing, I removed the power cord and still not finished, I removed the USB cable and so died. I put the power cord back but never lit, illuminates only when connecting the USB cable, I managed to get into recovery mode, I managed to install firmware restarted and the screen remained black. the idea is that it is powered only by the USB port, which led me to do? has anyone happened to that? Thank you!
I wiped cache and davik but i think i accidently clicked on system, that's only explanation why phone would be stuck in bootloop, and twrp says there's no OS installed, it'd be easy to unbrick with odin but... usb port is kinda dead, fast charging while using bad usb cable burned charging port, i thought replacing only connector would fix, it did at some point (charging chip on board is damaged), it takes 6 hours to charge from 0 to 100, fast charging isn't working, it is detected by pc but can't tell what is connected, just reacts that something is plugged in and uninstalling/installing samsung drivers also triggers it, but it can't do anything else, Galaxy S6 doesn't have sd card slot (cmon samsung) so is there any way to unbrick phone exept replacing whole daughterboard?
my idea is to use terminal to download img, is it possible?
anyone?
dear all...
i have a very strange situation here, after my kenzo updating to MIUI 9, when i enter fastboot mode and plug in to my USB, it was not detected anymore on device manager, and when i turn off the phone, and i plug in charger, LED will blinking red on the top of the phone,.
if the phone is turn on, charging is working, USB is detected by computer...
is this somekind of new protection from Xiaomi? or i have problem in my hardware? i was planning to downgrade again to MIUI 8 using EDL mode but when i plug the EDL special cable it was just blinking RED.
any opinion or anyone having kenzo device can try to detect fastboot and charging on power off condition? and share feedback?
thanks a bunch
I had the same problem and i opened the back case and unplugged the battery pin and plugged again.
i did it already re plug the battery now phone only hang on logo, can access fastboot but not detected in my computer, try using Deep Flash cable, only blinking red, try charging only blinking red
bump, anyone?....
Hi,
I have a Hisense u989 pro with a custom recovery installed, I performed a restore from a previous backup. After completed, when wanting to reboot, I saw a msg "No OS installed, leaving the phone connected to my pc and charging via usb, my wife needed a usb cable and unplugged my phone. when I returned some time later the phone was completely dead.
Some issues: Phone not charging or switching on, cant boot into recovery or fastboot, sp flash tool not detecting phone via usb cable, tried different usb cables, cleaned the micro usb charging port. left phone connected to charger for over 24hrs and still nothing. Im unsure whether it could be the charging port or the battery.
Ive got the hisense u989 pro stock rom, i just need it to switch on. Any advise or assistance to resolve my phone issue will be appreciated.\
thanking you
Like the title, my Poco F1 got this issue since last week, just right when I want to flash clean from PE+ to PE11 beta, pendrive OTG doesn't work or no way to use usb connection when connected to PC(just charging). I've tried Wipe All Data of PE+, flashed back to stock recovery rom(via twrp, and I forgot to reflash Twrp and now I'm staying forever on stock until fixed)
Pendrive OTG, PC connection, Headset Type C, QuickCharge simply don't work.
Meanwhile, Keyboard and Mouse via OTG work normally.
Is the USB connector or USB board the one at fault? Or is the mainboard/QCOM chip at fault?