Related
Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.
cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?
I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.
Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.
Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.
Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
voxoph said:
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
Click to expand...
Click to collapse
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
cmulk said:
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
Click to expand...
Click to collapse
Thanks for responding. I am going to try ADB again but I can't get into recovery mode at the time being.
A similar thing just happened to me, except I got right out of it. Device was completely unresponsive, no download mode, adb nothing, indicative of a hard brick. Scared the **** out of me as I've had it less than 6 hours... Started holding buttons, and it came to life after ~1 minute of power button + volume down. Related? Well maybe not, thought I'd post it here. (TWRP 2.8.5 + Rooted CM12)
True Hard Brick, No OS!
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
TSF14 said:
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
Click to expand...
Click to collapse
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
hyelton said:
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
TSF14 said:
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
Click to expand...
Click to collapse
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 plug using the OEM LG cable while holding volup and then plugging in the USB cable?
hyelton said:
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 CCCC?
Click to expand...
Click to collapse
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
TSF14 said:
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
Click to expand...
Click to collapse
Are you sure your battery is not dead??
hyelton said:
Are you sure your battery is not dead??
Click to expand...
Click to collapse
Yes, if only it was that easy.
There are a few things you can try :
1.) Press the Powerbutton for a longer time
If you have a responce like the LG Logo or something like that, you might want to try and plug it to the computer and use the managing software
with which you can emergency reinstall the firmware.
2.) Press Power + Volume Down
If it restarts into the recovery menu, try to find a way to load a flashable stock rom of your handy onto the memory of your phone in order to "reflash" it.
(I don't know how you can do that )
3.) Go to the shop where you bought it and explain your problem, since rooting a LG device is not really easy to detect the chances that your warranty will cover for it are pretty high.
Sent from my LG-D955 using XDA Free mobile app
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Read this.
http://forum.xda-developers.com/att-lg-g3/help/bricked-d850-help-t3064874
Hi! My HTC One XL was hard bricked. Apparently some system files were erased manually and after a reboot it just never started.
It was running ViperXL ROM, rooted, everything was properly done, including recovery.
Now it's just a paper weight. Can't turn it on, can't enter recovery or bootloader, LED doesn't light up (ever). There is no bootloop, it just never starts. Battery is 100% NOT dead, phone is charged.
If I plug it to my PC, Windows recognises the device and even makes the USB-thing connected sound (though it disconnects every 10 seconds or so). Fastboot doesn't see it as a device.
Any ideas will be appreciated, thanks.
Jtag repair is the only option if you are indeed bricked.
Heisenberg said:
Jtag repair is the only option if you are indeed bricked.
Click to expand...
Click to collapse
Thanks for answering. Will wait to see if someone I know can get his hands on a RIFF Box.
My phone was hard bricked after my battery ran out. It only shows a red light when charging.
Luckily the 9008 mode works and through the testpoints i'm able to connecti via edl.
Unfortunately MIFLASH doesn't work since you need an authorized account. However, i'm trying to use QFIL to flash on a fastboot rom. It doesn't seem to work.
Would anyone be able to help me with:
1. a guide on how to flash through QFIL (and which rom i need to use)
2. a No Auth Firehose file for this phone so i can use MIFLASH without authorization.
Thanks!
ok. Some progress now. I'm able to access fastboot. However, the phone is not detected on the computer. Red light while charging is also not present anymore, although i doubt that this is the flexcable issue.
Does anyone know how i can reflash with a locked bootloader in Fastboot?
pimf said:
ok. Some progress now. I'm able to access fastboot. However, the phone is not detected on the computer. Red light while charging is also not present anymore, although i doubt that this is the flexcable issue.
Does anyone know how i can reflash with a locked bootloader in Fastboot?
Click to expand...
Click to collapse
With Mi Assistant but if the phone is not detected it is mission impossible.
some more progress.
Phone is turning on now, but is stuck at the miui logo. I have no idea why this phone is coming back to live so randomly. Still not able to see the phone in windows. (nothing in device manager)
I also don't understand what is going wrong. I didn't reflash anything. I only replaced the flex cable and then my phone only lid up with the red charging light (staying red).
Now the red light is not on anymore. But i'm sure there is connection since i was able to get into 9008 mode with the computer connecting to the phone in EDL.
pimf said:
some more progress.
Phone is turning on now, but is stuck at the miui logo. I have no idea why this phone is coming back to live so randomly. Still not able to see the phone in windows. (nothing in device manager)
Click to expand...
Click to collapse
Try wipe data with recovery.
NOSS8 said:
Try wipe data with recovery.
Click to expand...
Click to collapse
Ill try again, however volume up + power button does not work (and I can therefore not enter recovery mode).
I'll keep trying.
pimf said:
Ill try again, however volume up + power button does not work (and I can therefore not enter recovery mode).
I'll keep trying.
Click to expand...
Click to collapse
Wiped the data, and the first boot still is stuck at the miui logo. Waited for a good 25 minutes. Mi assistant in the recovery menu doesn't let me connect with the computer either. I'm really curious why that is.
pimf said:
Wiped the data, and the first boot still is stuck at the miui logo. Waited for a good 25 minutes. Mi assistant in the recovery menu doesn't let me connect with the computer either. I'm really curious why that is.
Click to expand...
Click to collapse
Change the flexcable and try with Miflash
NOSS8 said:
Change the flexcable and try with Miflash
Click to expand...
Click to collapse
already did that. No go. I'm a bit frustrated as to why the pc doesn't see the phone.
pimf said:
already did that. No go. I'm a bit frustrated as to why the pc doesn't see the phone.
Click to expand...
Click to collapse
If the problem occurred after replacing a component (battery, cable, etc.), surely something is incorrectly mounted or defective.
I have a spare charging pcb. can try that. But i'm not sure that's going to help since i can see the phone in 9008 mode. Just cannot flash the phone due to the mi account restrictions.
tried the new pcb. Same problems. I'm wondering. How do i activate wlan when in recovery mode. It shows that you can download a software package over wlan in recovery mode but everytime i click wlan it activates and immediately deactivates again.
pimf said:
tried the new pcb. Same problems. I'm wondering. How do i activate wlan when in recovery mode. It shows that you can download a software package over wlan in recovery mode but everytime i click wlan it activates and immediately deactivates again.
Click to expand...
Click to collapse
Btw:
Have you changed the battery?
Was the phone detected before?
What is the rom installed?
And now the phone is bootlooping. There is more and more life coming in this phone. But i really cannot understand why this phone is not properly working. There is nothing i'm changing here so the fact it's all of a sudden bootlooping doesn't make much sense to me.
NOSS8 said:
Btw:
Have you changed the battery?
Was the phone detected before?
What is the rom installed?
Click to expand...
Click to collapse
1. Have not changed the battery. Battery seems to be fine.
2. Yes Phone was detected before. I used the last bit of power to get most of my pictures off the phone. Also, now it's still detected under 9008 mode.
3. Rom installed was the stock rom (poco f2 pro global) that came with the phone.
battery is at 98%. Phone just turned on for the first time. It's asking me to login to my mi account to unlock my phone. However, it cannot verify the password because there is no network connection. Wifi is not working, and there is no way of setting the sim settings until my phone is unlocked.
So, now i need to understand why the wifi is not working.
This is seriously the strangest thing i've encountered with phones. just doesn't make sense at all
ok. Just got my phone unlocked. However, phone keeps powering off during first setup. Phone is still highly unstable and the wifi doesn't seem to work well. The phone is at the moment useless. It's too unstable to use as a daily driver. Hopefully this will get better. Does anyone know why the wifi doesn't seem to work. seems to be a problem in all modes (rescue, and normal phone
edit: phone just turned off again while setting the pincode.
edit2: just updated with a new version of miui, wifi is still a problem, and phone turned off during updating all the system apps. Really not sure why this phone is so unstable now.
Ok, still an unstable phone. Seems like WIFI Bluetooth and usb connection don't work.
Does anyone know if it might be a loose cable that i need to reseat? Does it sound like a certain chip that needs to be replaced?
nobody has a clue?
pimf said:
nobody has a clue?
Click to expand...
Click to collapse
From the symptoms described above, it seems that your F2 pro has soldering problems with the SoC (system on chip) which is basically reballing the cpu
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
travy said:
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
Click to expand...
Click to collapse
Same boat as you two. Used "fastboot set_active b" after flashing stock firmware and ignored the bootloader warning. Now im stuck hardbricked with no success blankflashing. Including info for EDL Mode and log from one of my blankflash attempts as well as the correct firehose programmer for this device.
ezril said:
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
Click to expand...
Click to collapse
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Linux_SF said:
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Click to expand...
Click to collapse
I have had no luck whatsoever. Originally I thought I was successful using a blankflash although it was not. I've pretty much given up on that device for now although if you have anything that may help, I have no problem being the guinea pig, lol.
Keith