Related
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
Hey guys,
I just got this phone a day ago and wanted to try out the Cataclysm ROM today.
I was following the following guide on how to root the Nexus 5:
androidrootz.com/2013/11/how-to-root-nexus-5-windowsmaclinuxubun.html
I got up to step 9:
9. Connect your Nexus 5 to your computer and transfer "UPDATE-SuperSU-v1.65.zip". This file is located in "RootNexus5" folder you downloaded earlier.
But it didn't allow me to transfer the file to the phone.
I assume it is unrooted, cause it says unlocked and it has an unlocked photo when I boot up my device. But I don't think it was fully rooted?? (I'm assuming because I wasn't able to complete the final steps).
So I decided that I'm just going to unroot it and stick with the stock ROM.
Any thoughts on how I can unroot it? Would it be okay to use Wugfresh's unrooter? Even though I didn't use it to root the phone?
wugfresh.com/nrt/
Please let me know. Thanks!! :good:
since your bootloader is already unlocked, just fastboot flash a custom recovery and then use adb to push the rom you want to your phone.
there are several threads on how to do this.
Zepius said:
since your bootloader is already unlocked, just fastboot flash a custom recovery and then use adb to push the rom you want to your phone.
there are several threads on how to do this.
Click to expand...
Click to collapse
Thanks for the quick reply; I'm looking to revert back to stock and unrooting my phone.
I tried using wpug's tool, but it says ADB device not found... I'm using windows XP for what it's worth. I'm stuck...
perfectbluelion said:
Thanks for the quick reply; I'm looking to revert back to stock and unrooting my phone.
I tried using wpug's tool, but it says ADB device not found... I'm using windows XP for what it's worth. I'm stuck...
Click to expand...
Click to collapse
if you never rooted your phone, its just unlocked bootloader so its still stock.
Zepius said:
if you never rooted your phone, its just unlocked bootloader so its still stock.
Click to expand...
Click to collapse
Thanks Zep.
I'm not even sure if I rooted the phone or not, but I got up to step 9 of the following guide (did not complete step 9)
androidrootz.com/2013/11/how-to-root-nexus-5-windowsmaclinuxubun.html
Is my phone fully rooted?
I'm attaching two photos of how my phone looks when:
1. I hit both volume and the power buttons:
SECURE BOOT - enabled
LOCK STATE - unlocked
2. When I boot up (picture of unlocked lock)
If only my bootloader is unlocked, how do I lock it back? I want to have it back the way it came from Google incase I need to return for warranty purposes.
Thanks a lot! :good:
1) your phone is not rooted if you did not flash supersu.zip which you said you didnt.
2) to lock your bootloader use: fastboot oem lock.
^ there is a return to stock thread on how to do this.
Those pics won't show if you're rooted. By your description I doubt you are. You never flashed supersu.
To lock the bootloader do
fastboot oem lock.
You should follow this guide to unlock and root http://forum.xda-developers.com/showthread.php?p=47025283
---------- Post added at 09:43 AM ---------- Previous post was at 09:39 AM ----------
Darn,I hate that when it happens. Good thing we have him the same answers
Zepius said:
1) your phone is not rooted if you did not flash supersu.zip which you said you didnt.
2) to lock your bootloader use: fastboot oem lock.
^ there is a return to stock thread on how to do this.
Click to expand...
Click to collapse
jd1639 said:
Those pics won't show if you're rooted. By your description I doubt you are. You never flashed supersu.
To lock the bootloader do
fastboot oem lock.
You should follow this guide to unlock and root http://forum.xda-developers.com/showthread.php?p=47025283
---------- Post added at 09:43 AM ---------- Previous post was at 09:39 AM ----------
Darn,I hate that when it happens. Good thing we have him the same answers
Click to expand...
Click to collapse
Thanks gentlemen. Will read up on fastboot oem lock, try it out, and advise on results. :good: Fingers crossed...
If you are getting device not found when you try to use ADB, that means that you either don't have the right drivers installed, or that you are not using a 'good' USB port. Try a different port.
Zepius, jd1639, All:
Is there a guide to doing a fastboot oem lock?
It's not the following thread right:
http://forum.xda-developers.com/showthread.php?t=2513701
Not sure if there's a specific guide for locking the bootloader, most of them is for unrooting (which I don't need, correct?).
Thanks a lot guys!
perfectbluelion said:
Zepius, jd1639, All:
Is there a guide to doing a fastboot oem lock?
It's not the following thread right:
http://forum.xda-developers.com/showthread.php?t=2513701
Not sure if there's a specific guide for locking the bootloader, most of them is for unrooting (which I don't need, correct?).
Thanks a lot guys!
Click to expand...
Click to collapse
its literally typing the command in the command window: fastboot oem lock
perfectbluelion said:
Zepius, jd1639, All:
Is there a guide to doing a fastboot oem lock?
It's not the following thread right:
http://forum.xda-developers.com/showthread.php?t=2513701
Not sure if there's a specific guide for locking the bootloader, most of them is for unrooting (which I don't need, correct?).
Thanks a lot guys!
Click to expand...
Click to collapse
Yes that one... we assume you fastboot flashed recovery so you need to return that too.
If you don't know what you've done, follow the whole guide and fully return to stock.
Otherwise, cherry pick what you need from the guide
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
zephiK said:
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
Click to expand...
Click to collapse
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Yeah, I'm in the same boat as you. Unfortunately after all my reading, it seems impossible as CM did it as a preventative measure to secure your data.
I'm going to do a back up of everything and then a reflash to 25R where battery life was best, then unlock and reboot.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Well thats the whole point, the OnePlus One is a very developer friendly phone indeed. Thats why you get the "keys" to unlock the phone with a simple command instead of using a exploit to flash a custom recovery.
On 25R bootloader, it was possible but as of now there isn't a way to root without unlocking the bootloader. You can read the thread here, http://forum.xda-developers.com/oneplus-one/help/root-unlocking-bootloader-t2820628
This is why when people just now get a phone that has the ability to fastboot oem unlock, I suggest them to unlock their bootloaders as the first thing to do.
Backup all of your data and move forward. Best of luck.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
if you truly want to restore everything there are apps that will zip up all your data and you can flash in one session after wiping your phone. If you are reloading the exact same software it should not be an issue. check google and playstore for such apps like app2zip
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
therightperson_630 said:
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
Click to expand...
Click to collapse
oh yea my bad I forgot about the root part. I usually root right away so my bad..
Sorry, but the only way is to unlock the bootloader. You could use Helium backup, also some Apps themselves have great backup functionality.
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
timmaaa said:
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
Click to expand...
Click to collapse
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
therightperson_630 said:
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
Click to expand...
Click to collapse
The difference between having a locked and unlocked bootloader is simply flashing custom recoveries or radios/etc. Theres no harm in doing leaving your bootloader unlocked.
The bootloader has to be locked out of the box, I believe its one of the criterias needed to be fulfilled in order to be approved for Google Apps (Play Store,etc). Also, it doesn't make sense to have a bootloader unlocked for average users.
Just unlock the bootloader and learn from your lesson.... either that or stick with stock ROM without root. Yeah it'll set you back because you'll have to redo your phone apps/settings but on the bright side you won't have to do it again because ur bootloader is already unlocked.
You need your bootloader unlocked to obtain root. See http://forum.xda-developers.com/showthread.php?t=2788632 on instructions on how to do so if you're unfamiliar. After once its unlocked, fastboot flash a custom recovery and flash supersu.
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
therightperson_630 said:
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
Click to expand...
Click to collapse
Thats because the G1 had a locked bootloader and the only way to flash a custom recovery was to gain a exploit to push a custom recovery. For the OnePlus/Nexus/HTC, we don't need a exploit because we have the ability to unlock our bootloaders. Think of it as Apple's iOS, in order to gain jailbreak you need a exploit to jailbreak your phone which can take a long time for it to happen. Whereas, on Nexus/OnePlus/HTC, we can simply just obtain access to do changes to the phone without having to wait for a exploit.
You keep mentioning average user but a average user wouldn't be attempting to obtain root access for their phone. The average user would just be using his/her phone as a phone and not tinkering with the deeper innings of the Operating System and if the average user wants to tinker with the deeper innings then they should really do their research and learn. There are a lot of good guides on XDA.
Couldn't agree more. There is no need for any exploit with this phone because you've been handed the keys.
Transmitted via Bacon
therightperson_630 said:
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Click to expand...
Click to collapse
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
ondoy1943 said:
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
But then again,
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to fastboot oem unlock command.
Click to expand...
Click to collapse
A little off topic but I unlock my boot loader and root as soon as I get the phone so I don't have to loose anything.
zephiK said:
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
Click to expand...
Click to collapse
that's what you think, but in my case i was able to unlock the bootloader using the mod, hence rooting was a matter of course. the casual "fastboot oem unlock" command was not effective with my device. so.....
edit: then again, i unlocked the bootloader and rooted my phone while it was still at 30O firmware. i have no idea if the 33R firmware's bootloader is different from that of the 30O or not, that will render the mod ineffective.
It's fine, problem solved, went through the gruelling task of trying to back everything up without root = 40gb of stuff..
Already tried the tamper bit mod...it was stated in the first post (tamper bit mod) and the command screenshot was one of the steps when trying to boot the recovery, it still wouldn't boot because the bootloader wasn't unlocked..so, useless in my case.
Still lost some stuff but I got most of it back. I didn't have this problem on my xperia SP when unlocking the bootloader..if I remember correctly you could root, get recovery and custom rom all without unlocking bootloader. Unlocking the bootloader didn't erase the internal sd either..sure it might have been through an exploit rather than the proper way, but tbh I think I'd rather have that.
I'm not liking this "you've been given the keys" analogy...It's more like you've already settled into your new house and you're given the keys to unlock the front door when you're already inside...it's hassle more than anything.
Hey,
i just re-rooted my One after updating to 38r some days ago, and as it booted up, i got the "audiofx has stopped" bug and the "CM Lockscreen has stopped" bug at the same time. i tried to reset with twrp, reflash the rom and whatnot. I also cant flash roms with toolkits as i can not unlock my Bootloader. Today i finally managed to install a modified 38r via USB Otg after some other rom installations failed (also with USB Otg). I'm all like "Hell Yeah, fvck yeah OnePlus support!" (I wrote to them some days ago but they have not replied). I euphorically booted up my device and waited until the cyanogenmod logo pops up. i waited all the time. And its in a Bootloop now. I tried resetting my device and reflashing the ROM but none works. Can anyone help me please?
Sorry for the typos, i got not much time right now so i had to type fast.
thanks in advance
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
as i can not unlock my Bootloader
Click to expand...
Click to collapse
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
also cant flash roms with toolkits
Click to expand...
Click to collapse
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Transmitted via Bacon
timmaaa said:
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Click to expand...
Click to collapse
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
d4fseeker said:
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
Click to expand...
Click to collapse
Fair enough, although for someone who's inexperienced I think using the flashable version will be an easier and quicker solution.
Transmitted via Bacon
timmaaa said:
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
Click to expand...
Click to collapse
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Crime_Monkey said:
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
Click to expand...
Click to collapse
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
d4fseeker said:
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
Click to expand...
Click to collapse
I installed twrp with the toolkit by @manudroid19 when my phone was still functionable.
And the toolkit says that my bootloader is locked and i cannot unlock it. Every time i try to unlock it with the toolkit when in fastboot mode, the phone just boots up to twrp.
Have you tried the instructions in this thread:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
r0ni3 said:
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I can not find the folder, with and without an OS installed.
Crime_Monkey said:
I can not find the folder, with and without an OS installed.
Click to expand...
Click to collapse
no folder ..
you just have to write that command
r0ni3 said:
no folder ..
you just have to write that command
Click to expand...
Click to collapse
I can't find this option in twrp either.
Crime_Monkey said:
I can't find this option in twrp either.
Click to expand...
Click to collapse
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
r0ni3 said:
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Crime_Monkey said:
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Click to expand...
Click to collapse
installa a nightly...
and gapps
you can adb push roms in twrp, so you dont have to resort to otg.
Hi all,
The bootloader unlocking command "Fastboot oem unlock" did not work for me, because I locked the bootloader when I had installed TWRP recovery. TWRP recovery prevents the command from working. Luckily, timmaaa directed me to a thread which fixed this problem. I flashed a bootloader unlocker zip via TWRP. It worked flawlessly for me.
This is the thread I was directed to:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
your phone still boots into CM11S and TWRP recovery? if yes, then it is not bricked. Unlocking bootloader is only one time process. you do not need to unlock again as it is already unlocked, if you did re-locked bootloader then unlock it. you can flash oxygen OS straight away on twrp recovery.
Parth2187 said:
your phone still boots into CM11S and TWRP recovery? if yes, then it is not bricked. Unlocking bootloader is only one time process. you do not need to unlock again as it is already unlocked, if you did re-locked bootloader then unlock it. you can flash oxygen OS straight away on twrp recovery.
Click to expand...
Click to collapse
Thanks for your reply.
I relocked the device. After that I tried to unlock it again, but when I type the command and hit enter, the device will boot into TWRP recovery.
So what I have now is CM11S with working TWRP recovery.
But if I had installed cm12 or so, I wouldn't be able to flash CM11S, because the bootloader doesn't get unlocked anymore.
I know it's a very strange problem. I don't understand why it doesn't get unlocked anymore..
Luckily, cm11s still works. And I could install Oxygen OS using TWRP. But if something goes wrong, I will not be able to restore my device to stock CM11S, because the bootloader has not been unlocked..
Thanks anyway, I appreciate your help.
danielsinnema said:
Thanks for your reply.
I relocked the device. After that I tried to unlock it again, but when I type the command and hit enter, the device will boot into TWRP recovery.
So what I have now is CM11S with working TWRP recovery.
But if I had installed cm12 or so, I wouldn't be able to flash CM11S, because the bootloader doesn't get unlocked anymore.
I know it's a very strange problem. I don't understand why it doesn't get unlocked anymore..
Luckily, cm11s still works. And I could install Oxygen OS using TWRP. But if something goes wrong, I will not be able to restore my device to stock CM11S, because the bootloader has not been unlocked..
Thanks anyway, I appreciate your help.
Click to expand...
Click to collapse
Well, you can try @manudroid19's Toolkit it has option to unlock/lock bootloader or flash cm11s everything you want to do with toolkit. http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
if this toolkit doesn't work for you. please let me know or pm me
Parth2187 said:
Well, you can try @manudroid19's Toolkit it has option to unlock/lock bootloader or flash cm11s everything you want to do with toolkit. http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
if this toolkit doesn't work for you. please let me know or pm me
Click to expand...
Click to collapse
It did not work ;( It tried to unlock my bootloader. But after I clicked on "unlock bootloader" button, the device rebooted once again in TWRP recovery.
I think the problem is that I have a locked bootloader with a custom recovery. I think stock recovery is used to unlock the bootloader, isn't it?
You should never relock the.bootloader
Its not necessary
Sent from my A0001
There was no point to locking the bootloader again. Go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
That will allow you to unlock again via TWRP. Don't lock your bootloader again.
Transmitted via Bacon
IT WORKED!
timmaaa said:
There was no point to locking the bootloader again. Go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
That will allow you to unlock again via TWRP. Don't lock your bootloader again.
Transmitted via Bacon
Click to expand...
Click to collapse
You are absolutely amazing.
Thank you so much for directing me to that thread.
It unlocked the bootloader via TWRP. I didn't know that was possible.
Again man.. thanks.
Have a great day
Best regards,
Daniel
danielsinnema said:
You are absolutely amazing.
Thank you so much for directing me to that thread.
It unlocked the bootloader via TWRP. I didn't know that was possible.
Again man.. thanks.
Have a great day
Best regards,
Daniel
Click to expand...
Click to collapse
No worries man, glad to be able to help. You have a good day too.
Transmitted via Bacon