Phone booting only into Fastboot mode! HELP! - ONE Q&A, Help & Troubleshooting

Desperately need help guys, I was running on a Custom ROM since the past few months and using AK kernel with UKM and synapse. No problems whatsoever with that but today I set my bootloader status to "locked" and tamper flag to "true" with synapse which locked my bootloader.
Problem is I installed xposed modules for Lollipop on cm12 nightlies running on temasek rom, but after i had to reboot for changes to take place , my phone BOOTS ONLY INTO FASTBOOT MODE and nothing else.
>I can't access my recovery either as phone does not boot into system or recovery, but recognises only as Fastboot Mode.
>I'm guessing this is because my bootloader is set to locked, but is there any way I can access my phone again?
>I don't want to "fastboot OEM unlock" through Fastboot mode because this WILL WIPE ALL MY DATA and I have some really important pictures and files on it which I can't lose :/
Please help :crying:

Why did you lock your bootloader? Now you're in a position where you might have no choice but to unlock it again, therefore losing all data on your phone. But, hopefully not getting into recovery is just a case of not getting the button combo right. Try this: hold volume down button and then hold the power button (so you're now holding them together), when the phone starts to reboot let go of the power button (if you keep holding power the phone will just try to reboot normally) but keep holding the volume down button until it reaches recovery, hopefully you'll get to recovery ok, if not you'll need to unlock your bootloader.
Transmitted via Bacon

timmaaa said:
Why did you lock your bootloader? Now you're in a position where you might have no choice but to unlock it again, therefore losing all data on your phone. But, hopefully not getting into recovery is just a case of not getting the button combo right. Try this: hold volume down button and then hold the power button (so you're now holding them together), when the phone starts to reboot let go of the power button (if you keep holding power the phone will just try to reboot normally) but keep holding the volume down button until it reaches recovery, hopefully you'll get to recovery ok, if not you'll need to unlock your bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Yes now I realise it was really stupid to lock the bootloader >.>
I tried but as soon as phone powers on, it vibrates once, the 1+ logo is displayed and it boots into fastboot ! Same result if I keep holding down the volume down , but only this time, it vibrates twice and and then goes into fastboot mode T_T
Thanks for the help!

Aditya Srinidhi said:
Yes now I realise it was really stupid to lock the bootloader >.>
I tried but as soon as phone powers on, it vibrates once, the 1+ logo is displayed and it boots into fastboot ! Same result if I keep holding down the volume down , but only this time, it vibrates twice and and then goes into fastboot mode T_T
Thanks for the help!
Click to expand...
Click to collapse
Are you letting go of power as soon as it vibrates?
Transmitted via Bacon

timmaaa said:
Are you letting go of power as soon as it vibrates?
Transmitted via Bacon
Click to expand...
Click to collapse
Yup, if I continue holding Vol Down, it just keeps vibrating and displaying the 1+ logo over and over again and stops me from entering recovery :/

Aditya Srinidhi said:
Yup, if I continue holding Vol Down, it just keeps vibrating and displaying the 1+ logo over and over again and stops me from entering recovery :/
Click to expand...
Click to collapse
If you can't get into recovery you have no choice but to unlock the bootloader.
Transmitted via Bacon

timmaaa said:
If you can't get into recovery you have no choice but to unlock the bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Ahhh I see :/
Is there any way that I can use fastboot to pull files from my phone?

timmaaa said:
If you can't get into recovery you have no choice but to unlock the bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Just one last question, is there any possible way for me to flash an unlocked state of boot.img which unlocks my bootloader?

Aditya Srinidhi said:
Ahhh I see :/
Is there any way that I can use fastboot to pull files from my phone?
Click to expand...
Click to collapse
Only adb can pull files from your phone, and adb only works in the OS or in recovery, not in fastboot.
Aditya Srinidhi said:
Just one last question, is there any possible way for me to flash an unlocked state of boot.img which unlocks my bootloader?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader. You need to unlock it mate, it hurts, but you need to. And don't lock it again.
Transmitted via Bacon

timmaaa said:
Only adb can pull files from your phone, and adb only works in the OS or in recovery, not in fastboot.
You can't flash anything with a locked bootloader. You need to unlock it mate, it hurts, but you need to. And don't lock it again.
Transmitted via Bacon
Click to expand...
Click to collapse
This blows, but least lesson learnt! T_T
Thanks a lot for your help!

timmaaa said:
Only adb can pull files from your phone, and adb only works in the OS or in recovery, not in fastboot.
You can't flash anything with a locked bootloader. You need to unlock it mate, it hurts, but you need to. And don't lock it again.
Transmitted via Bacon
Click to expand...
Click to collapse
Hey, so I tried flashing twrp again with the locked state and it worked
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openreco
very-twrp-2.8.5.1-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10106 KB)...
OKAY [ 0.320s]
writing 'recovery'...
OKAY [ 0.132s]
finished. total time: 0.454s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Seeing it does allow to flash, is there a way to flash an unlocked state of the bootloader with boot.img?
I tried remote booting into twrp with fastboot, but that didnt work
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot openrecovery-twrp-
2.8.5.1-bacon.img
downloading 'boot.img'...
OKAY [ 0.319s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.324s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

Aditya Srinidhi said:
Hey, so I tried flashing twrp again with the locked state and it worked
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openreco
very-twrp-2.8.5.1-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10106 KB)...
OKAY [ 0.320s]
writing 'recovery'...
OKAY [ 0.132s]
finished. total time: 0.454s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Seeing it does allow to flash, is there a way to flash an unlocked state of the bootloader with boot.img?
I tried remote booting into twrp with fastboot, but that didnt work
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot openrecovery-twrp-
2.8.5.1-bacon.img
downloading 'boot.img'...
OKAY [ 0.319s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.324s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Click to expand...
Click to collapse
That means it wasn't/isn't locked. Did you actually check the status of the bootloader with this command?
Code:
fastboot oem device-info
What does that return?
Transmitted via Bacon

timmaaa said:
That means it wasn't/isn't locked. Did you actually check the status of the bootloader with this command?
Code:
fastboot oem device-info
What does that return?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes I did, it returns an "unknown" state for all commands

Can you please post an image of the result of that command so I can see?

timmaaa said:
Can you please post an image of the result of that command so I can see?
Click to expand...
Click to collapse
This is what it returned
_________________________________________
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
262748c5 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
__________________________________________________________

Aditya Srinidhi said:
This is what it returned
_________________________________________
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
262748c5 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
__________________________________________________________
Click to expand...
Click to collapse
So which part is unknown? Anyway, can you boot into TWRP recovery now?
Transmitted via Bacon

timmaaa said:
So which part is unknown? Anyway, can you boot into TWRP recovery now?
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry got confused with another command I ran. And nope, still unable to boot into recovery or system :/ if this helps the reason I rebooted was because I activated an xposed module, but not sure if that could've caused this at all . Is there a way to get an unlocked state of the bootloader which I can try to flash ? And brb in some hours since I'm I'm at work
Thanks for your help!

Aditya Srinidhi said:
Sorry got confused with another command I ran. And nope, still unable to boot into recovery or system :/ if this helps the reason I rebooted was because I activated an xposed module, but not sure if that could've caused this at all . Is there a way to get an unlocked state of the bootloader which I can try to flash ? And brb in some hours since I'm I'm at work
Thanks for your help!
Click to expand...
Click to collapse
If you could get into recovery there's a script that alters the bootloader state to unlock it without losing data, that's the only way, but if you can't get into recovery you can't do that. And yes, the Xposed module probably caused all this, it probably wasn't compatible with Lollipop. KitKat modules and Lollipop modules are different so you need to be very careful about what you install.
Transmitted via Bacon

timmaaa said:
If you could get into recovery there's a script that alters the bootloader state to unlock it without losing data, that's the only way, but if you can't get into recovery you can't do that. And yes, the Xposed module probably caused all this, it probably wasn't compatible with Lollipop. KitKat modules and Lollipop modules are different so you need to be very careful about what you install.
Transmitted via Bacon
Click to expand...
Click to collapse
Ahh I see :/ And phone doesnt charge either, if i power it off and connect to a wall charger, it automatically switches on and goes into fastboot mode ;_;

Aditya Srinidhi said:
Ahh I see :/ And phone doesnt charge either, if i power it off and connect to a wall charger, it automatically switches on and goes into fastboot mode ;_;
Click to expand...
Click to collapse
If it isn't charging you want to unlock the bootloader as soon as possible so you can flash the stock images to get it working again.
Transmitted via Bacon

Related

Cannot flash another recovery please help

BACKGROUND INFO: I am trying to install color os rom using twrp recovery and it gives me "failed" when i flash it. I have heard that if you use CWM recovery it will work. i have installed TWRP recovery using toolbox that i downloaded from XDA. when i went back to toolbox to install CWM recovery it told me to boot into fastboot mode and I did. i also clicked attached devices under adb options and it gives my device number in CMD. when i select CWM recovery in toolbox and i hit flash it says make sure your device is in fastboot mode and i clicked ok. then it said within a few seconds your device will boot selected recovery and CMD pops up and it says FAILED. DEVICE NOT UNLOCKED CANNOT FLASH OR ERASE. i think this is because bootloader is locked but when i hit unlock boot loader in toolbox it says make sure your device is in fastboot mode and when i click ok, CMD pops for a second, then it closes and my device reboots immediately to TWRP recovery. also my device is ROOTED. i am able to install other ROMS such as mahdi and rom from OP. someone said that if i flash philz recovery.zip using TWRP recovery i will be able to install color os but still the same error. now i am stuck with philz recovery and i am unable to flash other recoveries. someone said that it is the oem lock and i went to CMD and typed fastoot oem unlock while my device was in fastboot mode and it said OK in cmd and the device booted right into philz recovery and still i am not able to flash another recovery. i went to CMD and typed fastboot oem device-info and it said device tempered- true, bootloader unlocked- false, charger screen enabled- false. I DONT KNOW IF ITS LOCKED BOOTLOADER, THAT I AM NOT ABLE TO UNLOCK, OR OEM LOCK, WHICH I TRIED TO UNLOCK AND IT SAID OK IN CMD, THAT IS NOT ENABLING ME TO FLASH BACK TO TWRP OR STOCK RECOVERY BECAUSE I HAVE MY ROM BACKUPS IN TWRP. PLEASE HELP ME TO GO BACK TO TWRP RECOVERY OR ANY RECOVERY.
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
timmaaa said:
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
Click to expand...
Click to collapse
device tempered- true, bootloader unlocked- false, charger screen enabled- false
Your bootloader is indeed locked. You can unlock it:
Code:
fastboot oem unlock
This will erase all user data on the device.
Transmitted via Bacon
timmaaa said:
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
Click to expand...
Click to collapse
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
timmaaa said:
Your bootloader is indeed locked. You can unlock it:
Code:
fastboot oem unlock
This will erase all user data on the device.
Transmitted via Bacon
Click to expand...
Click to collapse
i tried it nothing happens. the phone reboots into recovery and nothing erases. read my issue first. i already mentioned this. NOTHING HAPPENS WHEN I TYPE FASTBOOT OEM UNLOCK. IT SAYS OK. THEN THE PHONE BOOTS INTO RECOVERY AND NOTHING IS DELETED.
zephiK said:
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
Click to expand...
Click to collapse
when i flashed fastboot boot openrecovery-twrp-2.7.1.1-bacon.img it said ok in cmd and the device is still in fastboot mode and the logo of fastboot got more brighter. also what timaaaa said did not work. it said ok when i typed fastboot oem unlock in cmd and the device booted right to philz recovery and nothing got deleted.
zephiK said:
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
Click to expand...
Click to collapse
can you please explain me the steps in details. i downloaded 3 zip files that were in the link that you gave me. what should i do next? i found the steps confusing in the link.
My output is: device tempered- true, bootloader unlocked- true, charger screen enabled- false. Is it right? Thank you
MAX 94 said:
My output is: device tempered- true, bootloader unlocked- true, charger screen enabled- false. Is it right? Thank you
Click to expand...
Click to collapse
Yes. You are lucky dude. I can't unlock my bootloader.
So, I am the "lucky" one too
I did facktory reset and full wipe as I wanted to install back the CM11s, but I ended up in the "bricked" One :crying:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
The command: fastboot oem unlock
Reset One to the TWRP, but it does not unlock it
Any falstboot command ends up with: Device not unlocked cannot flash or erase
I already playing with it over 20 hours, but I didnt find how to fix it
I had the same issue that could not unlock bootloader neither flash any room after brick. I used the computer downloaded color os and pushed it to my oneplus SD memory with cmd. But before that I installed twrp 2.7.1 in order to be able to flash os. The only rom was color os that I had success to install. Still bootloader not unlocked but color os rom has root privileged. But at least I have working phone. I installed twrp temporarily with toolkit from xda.
I succeeded to install the latest CyanogenMod 4.4.4. It is pain in the ass. But did it. Most implant is to unlock boot loader with flashing files from twrp. Then used toolkit and installed the rom and Chinese fastboot is gone.
[email protected] said:
I succeeded to install the latest CyanogenMod 4.4.4. It is pain in the ass. But did it. Most implant is to unlock boot loader with flashing files from twrp. Then used toolkit and installed the rom and Chinese fastboot is gone.
Click to expand...
Click to collapse
I have same problem as OP.
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.019s]
finished. total time: 0.019s
When i do "fastboot oem unlock" when my phone is in fastboot mode, the CMD tells me
Code:
E:\adt-bundle-windows\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
E:\adt-bundle-windows\sdk\platform-tools>
Than he auto reboots into TWRP. I don't do anything there. I boot to android. I shut down. And I Boot to fastboot again. Than when i try to do a fastboot flash or boot he tells me "DEVICE NOT UNLOCKED cannot BOOT"
So every time i unlock it, he puts it immediatly in lock.
What to do?
Search for my post on the OnePlus.net forum...
And welcome to my 28 hours nightmare
djha53k said:
Search for my post on the OnePlus.net forum...
And welcome to my 28 hours nightmare
Click to expand...
Click to collapse
That's incredibly vague. If you really want to help you should provide a link.
Transmitted via Bacon
Sorry... the search for my nick on OnePlus forum gives you 5 results: https://forums.oneplus.net/search/2437238/?q=djha53k&o=relevance&c[node]=26
anyway here we go: https://forums.oneplus.net/threads/recovery.82350/page-8#post-6054985
edit: I wrote that post from bed at 12:55 AM on Tapatalk... and OnePlus forum is not there...
ever figured out how to fix this problem?
djha53k said:
So, I am the "lucky" one too
I did facktory reset and full wipe as I wanted to install back the CM11s, but I ended up in the "bricked" One :crying:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
The command: fastboot oem unlock
Reset One to the TWRP, but it does not unlock it
Any falstboot command ends up with: Device not unlocked cannot flash or erase
I already playing with it over 20 hours, but I didnt find how to fix it
Click to expand...
Click to collapse
quackoman said:
ever figured out how to fix this problem?
Click to expand...
Click to collapse
Yes, long long loooooooooooooooooooooong time ago...
Suddenly the engl version of my post was already removed :crying:
I have only the czech version now
http://androidforum.cz/jak-opravit-chybu-device-not-unlocked-cannot-flash-or-erase-t59365.html
use google translator then :angel:
I fixed it by :starting up twrp... then I went to install and searched for the recovery (for me i had to go up a lvl and go to sdcard and it was the stock recovery.img)i wanted to flash but you have to chanege to images at the bottom left then I flashed it as recovery .. it failed then i flashed it as boot and then again as recovery and it worked then i reboted it i was promted with the normal recovery .. wiped data and applyd the oneplus ota update .. now it works grat and is fully unlocked IDK IF THAT WILL WORK FOR U OR EVEN HELP.... not responsible..

[Q] OnePlus One - Unable to unlock bootloader again after relocking

Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..
YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.
zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.
Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:
lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s
That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Im have the same issue but I have no recovery installed..Anyway to do this
i have same issue plz give me any solution if you found any???plz let me know plzzzzz
​
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue

Can't unlock bootloader

I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?
Any ideas guys?
aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.

Bricked for life? Partition error?

Hello!
I have a small problem. A week ago died my phone when i unlocked the lockscreen one evening. Thought that the battery was empty, i put it on the charger and started up the phone a few hours later and the only thing that happens is that Google logo is displayed, then it starts over again. I can go into recovery and fastboot, but it does not matter what i do there. Managed to get it to be connected as a USB drive so I got out the pictures from it. But if you make a complete factory reset including data and restarts there everything left! Tried to run "fastboot format cashe" but it only return "FAILED (remote: flash write failure) "
The phone is rooted and bootloader is unlocked, i had a custom rom installed, and it had worked since beginning of summer.
Have you already tried to reflash stock rom with fastboot? Maybe that will help to get your partitions working properly...
i followed a guide on androidrootz dot com, "how-to-unroot-nexus-5-complete-stock" but directly when i try to flash bootloader i get a error message.
Does the bootloader remain unlocked? What error are you getting when flashing stock?
audit13 said:
Does the bootloader remain unlocked? What error are you getting when flashing stock?
Click to expand...
Click to collapse
Yes! It remains unlocked! Heres the "print screen"
C:\UnrootNexus5>fastboot flash bootloader-hammerhead-HHZ11d.img
unknown partition 'bootloader-hammerhead-HHZ11d.img'
error: cannot determine image filename for 'bootloader-hammerhead-HHZ11d.img'
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
g90814 said:
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
Click to expand...
Click to collapse
I Have tried that also, here is the print from that:
Connectivity Status: Fastboot Device Connected
Flashing bootloader-hammerhead-HHZ11d.img to BOOTLOADER partition...
fastboot flash bootloader "C:\UnrootNexus5\bootloader-hammerhead-HHZ11d.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
But when it boots up again its still unlocked...
fastboot flash bootloader bootloader.img
Oh! I missed one word. Will try it tonight!
Nope.... Doesnt work either....
C:\UnrootNexus5>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.256s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.457s
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
audit13 said:
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
Click to expand...
Click to collapse
Damn! thats what im afraid of....
ChocholateMaster said:
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
Click to expand...
Click to collapse
The telephone is unlocked, the lock is open when i reboot the phone.
C:\UnrootNexus5>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
I don't know how it got damaged. One day, ti started bootlooping and the bootloader had re-locked on its own even though I unlocked it straight out of the box. I booted into fastboot, unlocked the bootloader, and it only too a few seconds to erase everything. I immediately rebooted in fastboot and the bootloader was locked again. This unlock/relock happened over and over.
I booted into recovery and tried a factory reset but recovery could not mount cache or data to perform the erase.
My phone just kept getting stuck at the Google logo or bootlooping.
ChocholateMaster said:
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
Click to expand...
Click to collapse
I have tried that also, when im just type "FASTBOOT OEM LOCK" it lookes like this:
C:\UnrootNexus5>fastboot oem lock
...
OKAY [ 0.054s]
finished. total time: 0.054s
PERFECT!?!? But when i reboot its still unlocked.... if i do first lock, then unlock without rebooting, i get a new meny on the phone where i have to chose if i want to unlock my device. and if i chose yes it will reboot and its the same again....
How do i download that file??? I just got an EXE file, and i dont want to run that!
If it's not sticking on a reboot, that means the memory is most likely gone bad. I guess you could try using the diagnostic tool, which would confirm if the memory is bad.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
ChocholateMaster said:
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
Click to expand...
Click to collapse
after flashing it can take up to 15 mins to turn on because of first boot
@kardanmannen any news?
I'm getting more and more sure that the memorymodule is faulty in the phone. If you reboot in Recovery and select filemanager, for example you remove a directory with files, if you restart the phone, the directory is there again! And when you start it up in recovery and connect it to the computer, theres a few directorys you can write/delete/. Similarly, if you run "fastboot oem lock" and reboot it, its locked the first time it is started up and then the second time it is unlocked again.
Lost hope a little there and went off and ordered a Nexus 6P, hoping it will arrive on Wednesday.

Softbrick, can't unlock bootloader, that's why I cant unbrick it, pls help!

So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i
GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.
meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?
I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/
Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )
Go to an independent repair shop. They have the equipment to flash on the motherboard.

Categories

Resources