Hello,
I flashed the red logo from this thread, which seemed fairly harmless, but now my phone is rendered useless.
I've tried booting into fastboot or recovery and the phone does vibrate in response, but the screen stays dark and blank, and fastboot devices/adb devices yields nothing.
Is there a fix for this?
Try this:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
timmaaa said:
Try this:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
Click to expand...
Click to collapse
Mate, thank you so much! You put me on the right path, I successfully unbricked it.
-forever grateful student
Awesome sauce
Transmitted via Bacon
Related
Guys
I went to try to switch the runtime from Dalvik to ART. I was on CM11S 33....now my phone keeps rebooting into CM recovery. I tried factory reset but it keeps rebooting into CM recovery. I currently do not know on what to do next. Please assist me.
In cm revovery.. i tried adb sideload the lastest update.zip however while installing update...the error msg "assert failed: apply patch check...installation aborted
Unlock your bootloader and flash the CM11S fastboot images. Check my guide thread for details.
Transmitted via Bacon
timmaaa said:
Unlock your bootloader and flash the CM11S fastboot images. Check my guide thread for details.
Transmitted via Bacon
Click to expand...
Click to collapse
i cant get into fastboot mode as in your guide stated..just a black screen....i can only reboot into cm recovery...is there any way to unlock bootloader by adb commands instead?
i tried adb> fastboot device..now it is stuck in waiting for device
but if i type adb>adb devices ... the phone serial no appears
anyone with any help?
from adb...fastboot devices is not listing anyting...
Adb push a flashable version of CM11S to your phone while in recovery, then flash that.
Transmitted via Bacon
timmaaa said:
Adb push a flashable version of CM11S to your phone while in recovery, then flash that.
Transmitted via Bacon
Click to expand...
Click to collapse
i just tried adb push update.zip /sdcard however an error msg: device not found
You said you were able to communicate via adb earlier, what happened?
Transmitted via Bacon
i still can communicate via adb but only sideloads workds...fastboot and adb push is not working at all
i am trying the hard brick method with color.zip...my pc able to identify my phone as QLOADER 9008 but the Msm8974DownloadTool.exe is not identifying it at all..my phone is not detected..sigh...been trying to solve this since 8 hours ago...didnt knew that changing the runtime to ART could be so complicated
relaksua said:
i still can communicate via adb but only sideloads workds...fastboot and adb push is not working at all
i am trying the hard brick method with color.zip...my pc able to identify my phone as QLOADER 9008 but the Msm8974DownloadTool.exe is not identifying it at all..my phone is not detected..sigh...been trying to solve this since 8 hours ago...didnt knew that changing the runtime to ART could be so complicated
Click to expand...
Click to collapse
Did you have Xposed Framework installed?
Transmitted via Bacon
Nope it was on CM11S .. no xposed framework installed.....i only switch the runtime to ART.....it was rooted..unlocked bootloader....now before it reboot into Cyanogen recovery...i could see a glimpse of the android with the red triangle.
You still can't get the device into fastboot mode?
Transmitted via Bacon
timmaaa said:
You still can't get the device into fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
nope...from adb...it just stats waiting for device and that's it
relaksua said:
nope...from adb...it just stats waiting for device and that's it
Click to expand...
Click to collapse
Have you tried turning it off and using the button combination (power + volume up) to get into fastboot mode?
Transmitted via Bacon
timmaaa said:
Have you tried turning it off and using the button combination (power + volume up) to get into fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
yes i did that...just blank screen...now trying on another comp running vista though...will try to reformat the phone
I managed to flash ColorOS into my phone but now it keeps rebooting into ColorOS recovery...my PC cant identify the device...how i place a zip file into this phone...i tried using an OTG cable with a thumbdrive and it cant read from the recovery....i am so in bad luck
EDIT: Got my phone recognized by my PC but in adb command..adb devices..it rerturns this 123456789ABCDEF recovery ...seems wrong
Wow the second thread about this now:
http://forum.xda-developers.com/oneplus-one/help/phone-dead-arrival-video-link-post-t2869452
Very strange problem
timmaaa said:
Did you have Xposed Framework installed?
Transmitted via Bacon
Click to expand...
Click to collapse
I've the same problem and I had Xposed Framework on my device. What can I do?:crying:
I have same problem too
I tried to change the boot image on my OnePlus One and accidentally flashed a file called logo.img (I don't know where it came from) instead of the logo.bin using Fastboot ("fastboot flash LOGO logo.img" where it should have been "fastboot flash LOGO logo.bin"). As a result, I can't boot into CyanogenMod, TWRP, or Fastboot.
How might I flash the correct logo.bin file over the corrupted partition if I can't access either of the two methods for flashing?
So the phone won't power on at all? And how do you not know where it came from? How could you possibly flash something to your device without knowing what it is or where it came from?
Transmitted via Bacon
timmaaa said:
So the phone won't power on at all? And how do you not know where it came from? How could you possibly flash something to your device without knowing what it is or where it came from?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, it was hard bricked. I attempted to make my own boot logo.bin file a few months ago and forgot to delete it from my SDK folder when I realized it was screwed up. I had forgotten that that was still there so I accidentally flashed that instead of the correct .bin.
I fixed the hard brick using this: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
asmth00 said:
Yeah, it was hard bricked. I attempted to make my own boot logo.bin file a few months ago and forgot to delete it from my SDK folder when I realized it was screwed up. I had forgotten that that was still there so I accidentally flashed that instead of the correct .bin.
I fixed the hard brick using this: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
It wasn't hard-bricked, it was soft-bricked.
Transmitted via Bacon
timmaaa said:
It wasn't hard-bricked, it was soft-bricked.
Transmitted via Bacon
Click to expand...
Click to collapse
No, it was hard bricked. I've soft bricked my device several times and have easily been able to pull it out. The boot partition was messed up as a result of my trying to fix it. Nothing was working - recovery, fastboot, Cyan, and I was getting QSUSB_BULK in device manager.
asmth00 said:
No, it was hard bricked. I've soft bricked my device several times and have easily been able to pull it out. The boot partition was messed up as a result of my trying to fix it. Nothing was working - recovery, fastboot, Cyan, and I was getting QSUSB_BULK in device manager.
Click to expand...
Click to collapse
That's still a soft-brick, it's just more severe. A hard brick will not power on or respond to any stimulus at all, the only way to fix a hard brick is by soldering onto the main board itself and using jtag to repair it.
Transmitted via Bacon
Hi, my friends, please help me out.
I'm using Temasek v7.8 and want to upgrade the firmware to latest 02_09. But after I flashed the latest firmware_2015_02_09 and rebooted system, the phone just displayed the logo, vibrated twice and entered the fastboot mode. I can't access the system whatever I do.
Also I have tried to clean flashed latest CM12 nightly which contains the latest firmware but the result is the same.
The only way to unbrick it is flashing back to firmware_2015_01_23.
Idk what I did wrong. :crying:
Thanks in advance.
Sorry for my bad English.
Anyone ?　Please help. :crying:
Firstly, the reason the phone is booting into fastboot mode when you use the power + volume up button combination is because that's the button combination to get into fastboot mode. The button combination to get into recovery is power + volume down. At this point I'd be wiping and flashing the stock images with fastboot.
Transmitted via Bacon
timmaaa said:
Firstly, the reason the phone is booting into fastboot mode when you use the power + volume up button combination is because that's the button combination to get into fastboot mode. The button combination to get into recovery is power + volume down. At this point I'd be wiping and flashing the stock images with fastboot.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for your reply.
Sorry for the bad statement and I have re-edited it to make it more clear.
In short, I can only enter fastboot mode after upgrading to the firmware 02_09. please help. :crying:
alpha.shining said:
Thanks for your reply.
Sorry for the bad statement and I have re-edited it to make it more clear.
In short, I can only enter fastboot mode after upgrading to the firmware 02_09. please help. :crying:
Click to expand...
Click to collapse
The very last sentence of my previous post is my advice.
Transmitted via Bacon
timmaaa said:
The very last sentence of my previous post is my advice.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for your reply and help.
Thanks limit reached and will hit thanks for you tomorrow.
alpha.shining said:
Thanks for your reply and help.
Thanks limit reached and will hit thanks for you tomorrow.
Click to expand...
Click to collapse
No need for more thanks, just concentrate on getting your device working again
Transmitted via Bacon
So I got a OnePlus one, yesterday it stuffed up, turned off and wouldn't turn back on., it was stuck in the boot animation. (Made a thread on OnePlus one forums: https://forums.oneplus.net/threads/one-plus-one-not-booting-into-os.285111/ ) so I booted into bootloader, did a wipe to see if that works, wiped my OS and I can't get the device's storage to show up on my PC. In the TWRP now.
How did it "stuff up"? Phones don't usually do this for no reason, what were you doing to it at the time? Put it into fastboot mode and flash the stock images, see section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
How did it "stuff up"? Phones don't usually do this for no reason, what were you doing to it at the time? Put it into fastboot mode and flash the stock images, see section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
I was playing Plants vs zombies and it shut down... Thanks for the help tho.
No problems, the stock images should get you up and running again.
Transmitted via Bacon
Worked, it's up and running Thanks.
You're welcome.
Transmitted via Bacon
I believe I've bricked my OPO. I was trying to flash OxygenOS today and it wasn't flashing completely right. I decided to not try anymore and flash back to 05Q. However, in doing that I bricked my phone. Volume- and power doesn't bring me to recovery, I can't access bootloader. However when I press volume- and power it still sounds the connection and I can see it in my device managers, I just can't do anything. When I try to do anything through ADB it says no fastboot devices found. CUrrently, my phone doesn't have boot.img, recovery.img, and system.img. I do have a latest backup of my 05Q from this morning before I did all of this.
Any help would be great. Thanks!
Try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Try one plus one recovery toolkit 1.0 it will slove ur problem same think happens to me it will help me
timmaaa said:
Try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
Definitely works. Just did the same after I tried to downgrade from OxygenOS and bricked my device.