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
Hello all
I have a baaaaad situation going on!
I have been trying to delete me superuser in twrp, but something terrible happened....
1) When i boot my 1+ it just stays black.
2) When i boot into fastboot it just shows a linux penguin logo and noting else.
3) When i go to twrp i can do multiple things like adb sideload, and i can push a rom to my phone.
-> but everytime i do this and try to install it, it just fails and says i have no OS installed when i want to reboot.
I've contacted support from 1+ but nothing yet so far...
Anyone here who can help me? (i'm open for teamviewer and even want to pay the person who can fix my Oneplus)
Hoping one of you can help me!
Greetz
Michel
(I have a picture of the logo but i can't post i due to beiing a new member here )
You can't communicate with your phone through fastboot and ADB? Oh ****...
How did you manage to replace the bootloader with a Linux penguin? When you go into fast boot and type does fast boot devices does the pc recognize the phone?
Sent from my One A0001 using Tapatalk
The thing is, i was rooting my device and after i've done that my rootchecker told me the root was incomplete...
So smart as i was i started a complete unroot, to do it all over again...
In this process my device got stuck... so i booted in TWRP recovery to uninstall everything from the root over there..
Here i managed to delete my complete OS.... 8-|
After reading every tutorial and guide i figured out that on my phone my developper otions were NOT enabled...
So i contacted the oneplus support, who even remotely connected to my computer from Beijing to Belgium.. but never the less my problem was not solved and i was still stuck on the f*cking Linux logo...
So i started searching for a flashable ROM (in this case i found Pacman Nightly Signed) to flash on my phone through command on Windows.
After many hours and even more attempts i managed to go in adb en flash it by the sideload way.
So not through "adb push romname.zip /sdcard...." but by "adb sideload romname.zip /sdcard...."
And the pacman rom started to install and booted my phone to language selection...
PS: i cried :cyclops:
Glad to hear that you fixed your phone. I wouldn't contact oneplus support for things like this, chances are you'll get a reply back from xda faster as well as searching on your own to resolve the issue.
Sent from my One A0001 using Tapatalk
OnePlus One no OS, no Charge and that stupid lunix penguin
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
timmaaa said:
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
---------- Post added at 10:09 AM ---------- Previous post was at 09:58 AM ----------
Coug76 said:
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I'm having an issue gettjngit into fastboot its died and all I'm getting is a black flashing screen!
Any tips on how to get it to charge?
Ashleigh.17 said:
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
Click to expand...
Click to collapse
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
timmaaa said:
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Ashleigh.17 said:
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Click to expand...
Click to collapse
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
timmaaa said:
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
Click to expand...
Click to collapse
okay
thank you for all your help hopefully I'll be posting later with some good news
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Ashleigh.17 said:
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Click to expand...
Click to collapse
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Ashleigh.17 said:
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Click to expand...
Click to collapse
Lol, no worries, glad to help.
timmaaa said:
Lol, no worries, glad to help.
Click to expand...
Click to collapse
This is better than the best soapserie
....
Is he going to make it?
Yes
Great! :good:
Oooooh nooooo!!!
He's got a locked bootloader
Damn F*ING
This will never turn out right
OH, look here comes @timmaaa again
He says what? :silly:Really is it possible
Yes YES YYEEEEESSS
I did it, it's working again
I loooove you
:highfive::highfive::highfive:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
ElmoRapz said:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
Click to expand...
Click to collapse
It looks like you did the same thing that I did.
Its a pretty easy fix your going to be able to avoid all of the unlocking boot loader issues I had.
To begin with when your try an turn the device on is the screen flashing black?
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
Need some help.
I am usually pretty good with working with firmware and software issues.
I have a friends OPO which they had issues with and somehow got it into a state where the only thing it seems I can possible do is get it into the stock Cyanogen Recovery.
I tried going into fastboot (Vol Up. + Power) but this yields no result it always ends up booting into cyanogen recovery.
As far as I know (with this friend not being very technical) i doubt it had an unlocked bootloader, or even USB debugging on prior to the crash.
The only way I can get the PC to recognize the phone in ADB mode is to enter the Apply update section and hit apply from ADB which puts me into ADB for sideloading.
If I could get it into Fastboot I would be able to move forward.
When it boots, I see a quick flash of some sort of error/failure screen but it is so quick I cannot identify the image.
Try this:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
I actually came across that thread while waiting for a reply to my own. In the state that it is in the msm tool is the only thing that can help me?
Well without fastboot you're going to find it very difficult to get anything done. CM recovery isn't really of any help because it can't actually flash anything that you need it to flash. I find it very odd that you can't get to fastboot. Have you tried adb commands while in recovery?
Transmitted via Bacon
I tried the button configurations to get into fastboot to no avail, it just boots into cyanogen recovery. As for adb while connected, only way I can use it is by going into the section to sideload an update. Within there I can adb, but most commands give me "error: closed".
Adb reboot bootloader doesn't work?
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
Sent From Lollipopified Bacon Goodness!
I am in the same state, my phone always boots to Cyanogen Recovery and no fastboot and even adb side load says closed. I am stuck here. Any help is greatly appreciated.
androidmah said:
I am in the same state, my phone always boots to Cyanogen Recovery and no fastboot and even adb side load says closed. I am stuck here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Has anyone made any progress on this issue?
androidmah said:
I am in the same state, my phone always boots to Cyanogen Recovery and no fastboot and even adb side load says closed. I am stuck here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Tried flahsing the stock rom? Or just the bootloader?
Sent from my Xiaomi Mi 5 using XDA Labs
i've got the same problem, did you manage to solve it?
Thank you
I am not able to flash TWRP recovery after updating my OPO to CM OS 12 via OTA.
I have tried everything and followed every step precisely.
After enabling USB debugging & turning off update recovery in Developer Options.
I used command prompt and flashed the recovery image.
Everything happens smoothly and the command prompt shows flashing successful.
But after rebooting the phone and going to recovery. I get Cyanogen Recovery again and again.
I even tried "fastboot erase recovery" before "fastboot flash recovery recovery.img"
Even then nothing happens. Cynogen Recovery comes again and again.
I have two OPO and another one is running CM11s.
I flashed TWRP without any problem in my old OPO.
If anyone knows the solution, please help.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon
I've read the FAQ and am having exactly the same problem as the orignal poster.
Additionally, I also tried to "erase" boot via flash, got a successful and then reflashed twrp again. It just doesn't work. Has something changed?
Thanks,
/geir
gsjurseth said:
I've read the FAQ and am having exactly the same problem as the orignal poster.
Additionally, I also tried to "erase" boot via flash, got a successful and then reflashed twrp again. It just doesn't work. Has something changed?
Thanks,
/geir
Click to expand...
Click to collapse
Nothing has changed, try powering off your phone completely after flashing, and then using the power + volume down combo to get to recovery.
XDA Moderator
Transmitted via Bacon