Database Info

[Q] Locked Bootloader and no recovery =No hope??

G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers

U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305

ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon

timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.

Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon

Cheers mate.

What build of CM11S are/were you on?
Transmitted via Bacon

timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.

Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon

Will have a crack when i get home, thanks for your help.

No good mate as you said.

Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon

Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.

[Q] help with color os, driving me crazy :(

Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!

METAL66 said:
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow Sections 1-4 and then Section 8.
Transmitted via Bacon

Dear Timmaa
after Code:
fastboot oem device-info
It should have a couple of lines there, both with the flag set to true.
Please note: this will erase all user data from your device, it is best to do this before turning your phone on for the first time, otherwise make sure you backup anything important.
the fastboot is still on the screen, how do i move to step 2 ? just remove the cable? force restart or how ?

Are you saying that fastboot isn't working?
Transmitted via Bacon

timmaaa said:
Are you saying that fastboot isn't working?
Transmitted via Bacon
Click to expand...
Click to collapse
i see fastboot in english and chinese on the phone, i do the commands on cmd prompt, but nothing happens to the phone when i finish the steps.

You didn't answer my question though, is fastboot working? Are you getting a response in your command prompt when you enter commands? Try this:
Code:
fastboot devices
What's the result?
Transmitted via Bacon

yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.

METAL66 said:
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
Click to expand...
Click to collapse
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon

ok i will try to make a very detailed answer, sorry. await the answer in few hours.

detailed video of how i did it
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=4N0evbwCNgI&feature=youtu.be
hope this works better ?

timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
did you see my video ?

METAL66 said:
did you see my video ?
Click to expand...
Click to collapse
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon

timmaaa said:
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.

METAL66 said:
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
Click to expand...
Click to collapse
Cool, glad you got it sorted out. If you have any questions in future please don't hesitate to ask here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon

Thanks, now there are some problems with the network, is this normal? can it be solved?

METAL66 said:
Thanks, now there are some problems with the network, is this normal? can it be solved?
Click to expand...
Click to collapse
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon

timmaaa said:
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
Click to expand...
Click to collapse
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine

METAL66 said:
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
Click to expand...
Click to collapse
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon

timmaaa said:
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, it worked perfectly, i dont know why the APN settings were empty, but now it works.
perfect, thanks a lot timmaaa

No problems [emoji3]
Transmitted via Bacon

[Q] Bootunlocker / locker on the fly after oem unlock

Hello,
On the Nexus, there is https://play.google.com/store/apps/details?id=net.segv11.bootunlocker that allow to lock/unlock on the fly the bootloader. Is there an equivalent app on the OnePlus One ?
Edit: Support of the OPO in the app added on 09/01/2015.

Why? There's no point in having the bootloader locked on this device.

timmaaa said:
Why? There's no point in having the bootloader locked on this device.
Click to expand...
Click to collapse
Well if you want me to justify, I will say it this way : think about what you can do when the device is unlocked, now what if your device is stollen...

If phone is stolen with bootloader locked, the thief can still unlock and do everything as per normal lol. Only thing is your info will be wiped. Which probably doesn't matter to thief anyways. But no I have seen such app for this phone
Sent From Lollipopified Bacon Goodness!

Xoib said:
Well if you want me to justify, I will say it this way : think about what you can do when the device is unlocked, now what if your device is stollen...
Click to expand...
Click to collapse
So take better care of your phone. It's a moot point anyway because anybody who steals your phone who actually knows what to do with an unlocked device will equally know how to unlock that device anyway. They steal the phone, see bootloader is locked, unlock bootloader with a single fastboot command, have their way with your phone. Which brings me back to my initial statement, the only thing you can do is take better care of your device. Honestly, I have no idea how people get their phones stolen, it simply means they're not taking enough care with it.
---------- Post added at 07:50 AM ---------- Previous post was at 07:49 AM ----------
ek69 said:
If phone is stolen with bootloader locked, the thief can still unlock and do everything as per normal lol. Only thing is your info will be wiped. Which probably doesn't matter to thief anyways. But no I have seen such app for this phone
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
My point exactly.

Well, I know all that, it's just a "feeling" of counter forensic to know that they will have to oem unlock (so wipe) to put a custom recovery to hope hacking into my datas...

Xoib said:
Well, I know all that, it's just a "feeling" of counter forensic to know that they will have to oem unlock (so wipe) to put a custom recovery to hope hacking into my datas...
Click to expand...
Click to collapse
That's not necessarily true, as after the oneplus has been unlocked once it's possible to unlock it again without wiping userdata - if you have a custom recovery installed any way.
But to provide an answer to your question, the closest I've seen is if you install AK kernel with UKM the kernel settings app (Synapse) has an option to toggle the bootloader lock status as well as the tamper flag status.

Of course that was the scenario if you put back the original recovery.
Thanks for AK Kernel suggestion, I will have a look.
Edit: Found http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

readers here might be interested in this...
The TWRP Password Protection Thread
http://forum.xda-developers.com/android/software-hacking/twrp-password-protection-thread-t2990816​

Lanchon said:
readers here might be interested in this...
The TWRP Password Protection Thread
http://forum.xda-developers.com/android/software-hacking/twrp-password-protection-thread-t2990816​
Click to expand...
Click to collapse
Hello @Lanchon, the case you describe in your point 2) is exactly what I had on my Nexus 4.
That's what I was looking for a on the fly bootlocker/unlocker in combination of putting only the custom recovery when needing to flash something.
I will also follow your thread.

Rkr87 said:
That's not necessarily true, as after the oneplus has been unlocked once it's possible to unlock it again without wiping userdata - if you have a custom recovery installed any way.
But to provide an answer to your question, the closest I've seen is if you install AK kernel with UKM the kernel settings app (Synapse) has an option to toggle the bootloader lock status as well as the tamper flag status.
Click to expand...
Click to collapse
I just noticed that option I normally just skip over that page lol. Dunno if it actually works though.
See screenshot
Sent From Lollipopified Bacon Goodness!

Rkr87 said:
That's not necessarily true, as after the oneplus has been unlocked once it's possible to unlock it again without wiping userdata - if you have a custom recovery installed any way.
Click to expand...
Click to collapse
Xoib said:
Edit: Found http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
That script is what I was referring to when I said it's possible to unlock without wiping user data if you have a custom recovery installed
Powered by Bacon

Follow up: Support of the OPO has been aded to BootUnlocker (https://play.google.com/store/apps/details?id=net.segv11.bootunlocker)

Really Hard Brick!!

Hello my friends,
now it happened to me. My OPO bricked after I installed the ColorOS port. I wanted to restart it after a succesful installation of the 2.06 port in TWRP. Now it doesn't start, neither gets recognized by windows as QHSUSB or something like that. Any ideas what I can do? It doesn't vibrate even if I hold the power button for 2 minutes.
Please help!
Thanks in advance,
Felix

Try these:
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon

Thanks, but the problem is that the device doesn't get listed at all in the device manager. There isn't even a "usb connect/disconnect"-sound in windows, like the device is totally dead.

Nothing you can do. Sell it at a junkyard or try to get it warranty swapped.

oneplus said:
Nothing you can do. Sell it at a junkyard or try to get it warranty swapped.
Click to expand...
Click to collapse
What are you talking about? Plenty of devices in this situation have been revived. Unless you're actually knowledgeable about something, maybe don't comment.
Transmitted via Bacon
---------- Post added at 10:51 AM ---------- Previous post was at 10:51 AM ----------
felix297 said:
Thanks, but the problem is that the device doesn't get listed at all in the device manager. There isn't even a "usb connect/disconnect"-sound in windows, like the device is totally dead.
Click to expand...
Click to collapse
So you attempted both?
Transmitted via Bacon

timmaaa said:
So you attempted both?
Transmitted via Bacon
Click to expand...
Click to collapse
No, because they're based on the same method. I can't install any drivers because there is no device listed in the device manager.
I've tried 3 different USB cables, still no luck.
But I stumbled on this:
3) If drivers dont work or your device is not detected for whatever reason install the QPST tool.
Click to expand...
Click to collapse
I installed it but don't know what to do. Its not just a single tool, its a toolkit.

felix297 said:
No, because they're based on the same method. I can't install any drivers because there is no device listed in the device manager.
I've tried 3 different USB cables, still no luck.
But I stumbled on this:
I installed it but don't know what to do. Its not just a single tool, its a toolkit.
Click to expand...
Click to collapse
Ok, but many other people in your exact situation have recovered by using those methods, you can't say it doesn't work until you actually attempt it.
Transmitted via Bacon

timmaaa said:
What are you talking about? Plenty of devices in this situation have been revived. Unless you're actually knowledgeable about something, maybe don't comment.
Transmitted via Bacon
---------- Post added at 10:51 AM ---------- Previous post was at 10:51 AM ----------
So you attempted both?
Transmitted via Bacon
Click to expand...
Click to collapse
What knowledge do you have except copy pasting some random link? The guy got hard brick. What you talk about is soft brick. Read what he says in the post then copy paste links.

The problem is that I cant attempt it because im not able to do the first step.
I think there is a misunderstanding here.
To follow these instructions the device has to be recognized by the pc, which in my special case isn't.
So I think thats it with my OPO.. Very sad

You have to turn off windows driver signing before installing the drivers otherwise it might install the drivers correctly. Did you try install the drivers with driver signing off?

No, because they're based on the same method. I can't install any drivers because there is no device listed in the device manager.
I've tried 3 different USB cables, still no luck.
But I stumbled on this:
Quote:
3) If drivers dont work or your device is not detected for whatever reason install the QPST tool.
Click to expand...
Click to collapse

oneplus said:
What knowledge do you have except copy pasting some random link? The guy got hard brick. What you talk about is soft brick. Read what he says in the post then copy paste links.
Click to expand...
Click to collapse
Exactly what I thought. You might want to brush up a bit, he is not experiencing a proper hard brick. Do some reading before you claim to know something, as I said, many people in the exact same situation have brought their phones back to life.
Transmitted via Bacon

Hey timmaaa, i don't want to speak against you, but its not the exact same situation. I think I have a proper hard brick, because the device isn't showing any sign of life
These tutorials have no use in my case until now.

felix297 said:
Hey timmaaa, i don't want to speak against you, but its not the exact same situation. I think I have a proper hard brick, because the device isn't showing any sign of life
These tutorials have no use in my case until now.
Click to expand...
Click to collapse
I understand what you're saying, but I'm telling you that several devices that were just like yours is now have been revived.
Transmitted via Bacon

timmaaa said:
Exactly what I thought. You might want to brush up a bit, he is not experiencing a proper hard brick. Do some reading before you claim to know something, as I said, many people in the exact same situation have brought their phones back to life.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok lmk how it goes.

Won't turn on at all

12S came out today, and since this phone isn't my daily driver right now, I figured I would fastboot 11S back on my phone, then put TWRP on it so I can flash the update from scratch etc, and about half way through installing 11S through fastboot, the screen turns off and won't turn back on. I was at more than 50% when I was flashing 11S. I have been doing this stuff for a while with a bunch of different phones. I know it's not something I did. I tried hard rebooting on and off of the charger, trying it regularly on and off the charger. I have no idea why it won't power on. Anyone experience this and know how to fix it?

This is the only thing that has a chance of saving your phone:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon

timmaaa said:
This is the only thing that has a chance of saving your phone:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks!! I'm going to try this tomorrow after work.

timmaaa said:
This is the only thing that has a chance of saving your phone:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
Tried it this morning. You are a life saver. My phone is now running 12S.

godraistlin said:
Tried it this morning. You are a life saver. My phone is now running 12S.
Click to expand...
Click to collapse
Good news!
Transmitted via Bacon