Related
How do I root an HTC One GE on a Mac? I'd like to do so before I set up the phone tomorrow. Done some googling and couldn't find an answer. Did my N4. Is it the same files/procedure?
Sorry for the duplicate post, but I realized I had entered the title in correctly.
mdandashly said:
How do I root an HTC One GE on a Mac? I'd like to do so before I set up the phone tomorrow. Done some googling and couldn't find an answer. Did my N4. Is it the same files/procedure?
Sorry for the duplicate post, but I realized I had entered the title in correctly.
Click to expand...
Click to collapse
yes.
fastboot oem unlock
push recovery
install supersuer.zip
gunnyman said:
yes.
fastboot oem unlock
push recovery
install supersuer.zip
Click to expand...
Click to collapse
I'm a noobie. Need more direction than that.
you just said you did your N4.
procedure is exactly the same
or after you do fastboot oem unlock from the bootloader screen you can follow my tutorial for recovery and root.
It's in my signature
gunnyman said:
you just said you did your N4.
procedure is exactly the same
or after you do fastboot oem unlock from the bootloader screen you can follow my tutorial for recovery and root.
It's in my signature
Click to expand...
Click to collapse
Are the files universal? Not custom?
mdandashly said:
Are the files universal? Not custom?
Click to expand...
Click to collapse
correct
gunnyman said:
correct
Click to expand...
Click to collapse
I was under the impression there were specific drivers for the devices. So if I follow the tutorial on the website I post below it will work?
http://www.cultofandroid.com/23782/rooting-the-google-nexus-4-the-right-way-how-to/
Follow the link in my signature.
gunnyman said:
Follow the link in my signature.
Click to expand...
Click to collapse
I'll keep you updated.
mdandashly said:
Are the files universal? Not custom?
Click to expand...
Click to collapse
Just make sure you get the HTC One recovery and not the N4.. based on your lack of knowledge, based on your multiple questions, I would hold off a bit though.. as far as I know there isn't a confirmation as to if the recovery from the normal One is compatible with the GE One. I could be wrong though
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Just make sure you get the HTC One recovery and not the N4.. based on your lack of knowledge, based on your multiple questions, I would hold off a bit though.. as far as I know there isn't a confirmation as to if the recovery from the normal One is compatible with the GE One. I could be wrong though
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thanks. I guess I'll hold off. I figured there had to be some custom files and that they arent all plug and play. Thanks for your help. I'll prob wait a couple weeks. I just wanted to do it immediately to avoid having to wipe again.
mdandashly said:
Thanks. I guess I'll hold off. I figured there had to be some custom files and that they arent all plug and play. Thanks for your help. I'll prob wait a couple weeks. I just wanted to do it immediately to avoid having to wipe again.
Click to expand...
Click to collapse
You don't need to wipe for a recovery. When you get the device and its good to go, go into fastboot and type
"fastboot oem unlock"
Then after you unlock it reboot into the stock recovery and do a factory reset.. then hold off for recovery. Once your unlocked you no longer are required to wipe for anything
Sent from my Nexus 10 using Tapatalk HD
mdandashly said:
Thanks. I guess I'll hold off. I figured there had to be some custom files and that they arent all plug and play. Thanks for your help. I'll prob wait a couple weeks. I just wanted to do it immediately to avoid having to wipe again.
Click to expand...
Click to collapse
you can unlock the bootloader first thing then do the rest later only wipe happens when you unlock bootloader
gunnyman said:
you can unlock the bootloader first thing then do the rest later only wipe happens when you unlock bootloader
Click to expand...
Click to collapse
Aaah. Didn't think of that. Which files do I need for that?
On a mac? Just fastboot
Rooted using a combination of instructions. Pleased to say it worked. Only problem I have had so far is that on one occasion it told me I was not rooted, when in fact I was. A reboot fixed that problem.
mdandashly said:
Rooted using a combination of instructions. Pleased to say it worked. Only problem I have had so far is that on one occasion it told me I was not rooted, when in fact I was. A reboot fixed that problem.
Click to expand...
Click to collapse
Looks like I have root, but it seems like after some time of the phone being on, it loses root access and I have to reboot in order to regain root access. Any ideas?
The first S6 Edge roots are available from the repository: http://autoroot.chainfire.eu/ !
Note that the stock kernel currently has an issue preventing the device from going into "deep sleep" if a custom recovery is flashed (which is what this does). A fix for this issue can be found here: http://forum.xda-developers.com/showpost.php?p=60383471&postcount=49. This fix will also work if you replace the recovery with for example TWRP.
im trying to root my tmobile sm-g925t s6 edge and in odin it is stuck on nand write start.. what should i do?
yubby said:
im trying to root my tmobile sm-g925t s6 edge and in odin it is stuck on nand write start.. what should i do?
Click to expand...
Click to collapse
is your bootloader unlocked..?
yubby said:
im trying to root my tmobile sm-g925t s6 edge and in odin it is stuck on nand write start.. what should i do?
Click to expand...
Click to collapse
Same issue here. I've tried all the "Odin" tricks.. different cables, different PCs, latest drivers, several reboots, different Odin versions, etc.... All the same, stuck on "NAND Write Start". Hoping for a fix soon.
Yes the sm-g925t is on the list
From looking at the other threads, specifically the non-edge S6 auto root thread, everyone is in the same boat. We just need to wait for Chainfire to update. Like an idiot, I accepted the out-of-the-box OTA although others are saying they are having the same issue without the OTA update.
Alex-V said:
is your bootloader unlocked..?
Click to expand...
Click to collapse
All t-mobile phones have unlocked bootloaders
mmayhew said:
From looking at the other threads, specifically the non-edge S6 auto root thread, everyone is in the same boat. We just need to wait for Chainfire to update. Like an idiot, I accepted the out-of-the-box OTA although others are saying they are having the same issue without the OTA update.
Click to expand...
Click to collapse
mine is bricked. i tried to root and it wont get passed the first screen. cant even access recovery. i cant even get the phone to turn off
Damn I bricked mine too. Used Odin 3.10.6, got a successful flash but it won't get past the booting screen, won't shut off, can only really access Download Mode. Which I've tried using different suggestions but still failed to get it to boot up or put into recovery to complete the root process.
shadowk91 said:
Damn I bricked mine too. Used Odin 3.10.6, got a successful flash but it won't get past the booting screen, won't shut off, can only really access Download Mode. Which I've tried using different suggestions but still failed to get it to boot up or put into recovery to complete the root process.
Click to expand...
Click to collapse
I would be really pissed if my new edge will be stuck before i even got to play with it...... Hope you guys get it working back asap
How did you get it to be successful flash? I tried ODIN 3.10.6 with the available CF-Auto_root and continue to get stuck at NANO WRITE! Of course i accepted the OTA right out of box also.
Wonder why we have different results of "same task"
FieldsInc said:
How did you get it to be successful flash? I tried ODIN 3.10.6 with the available CF-Auto_root and continue to get stuck at NANO WRITE! Of course i accepted the OTA right out of box also.
Wonder why we have different results of "same task"
Click to expand...
Click to collapse
I didn't actually take the OTA, because I wanted to be sure that I would be able to root the phone for sure without needing to wait too long for an update to the Auto Root Utility that would work with the newer version.
shadowk91 said:
Damn I bricked mine too. Used Odin 3.10.6, got a successful flash but it won't get past the booting screen, won't shut off, can only really access Download Mode. Which I've tried using different suggestions but still failed to get it to boot up or put into recovery to complete the root process.
Click to expand...
Click to collapse
I had the same problem but then I flashed the non-edge S6 auto root (SM-G920T) and it worked flawlessly. Good luck.
mmayhew said:
I had the same problem but then I flashed the non-edge S6 auto root (SM-G920T) and it worked flawlessly. Good luck.
Click to expand...
Click to collapse
OMG! THAT'S IT!, IT WORKED!!! YOU SAVED MY STUPIDLY EXPENSIVE PHONE (and from some seriously painful beatings from the wife had she found out the $1100+ phone died).
Okay enough of my excitement. Thanks for the advice, and helping me revive my phone. I hope Chainfire updates his first page post to ensure other people don't accidentally semi-brick their phones.
shadowk91 said:
OMG! THAT'S IT!, IT WORKED!!! YOU SAVED MY STUPIDLY EXPENSIVE PHONE (and from some seriously painful beatings from the wife had she found out the $1100+ phone died).
Okay enough of my excitement. Thanks for the advice, and helping me revive my phone. I hope Chainfire updates his first page post to ensure other people don't accidentally semi-brick their phones.
Click to expand...
Click to collapse
and after this you installed the OTA..?
mmayhew said:
I had the same problem but then I flashed the non-edge S6 auto root (SM-G920T) and it worked flawlessly. Good luck.
Click to expand...
Click to collapse
Alex-V said:
and after this you installed the OTA..?
Click to expand...
Click to collapse
Yes, I installed the OTA and successfully rooted the S6 Edge (SM-925T) by using Odin 3.10.6 and the non-edge auto root (SM-G920T). It will trip KNOX as expected.
Alex-V said:
and after this you installed the OTA..?
Click to expand...
Click to collapse
The Updater recognizes that my phone has been modified so it won't even allow me to download the OTA.
shadowk91 said:
The Updater recognizes that my phone has been modified so it won't even allow me to download the OTA.
Click to expand...
Click to collapse
Has anyone successfully updated OTA first and then flashed AutoRoot?
martinezma99 said:
Has anyone successfully updated OTA first and then flashed AutoRoot?
Click to expand...
Click to collapse
Yes, several of us have had success flashing Auto Root after installing the OTA.
I have took OTA and rooted, using the 920t auto root.
Sent from my SM-G925T using XDA Free mobile app
OK so i was going to flash back to a factory rom from CYANOGEN, but got bricked and it says I need to check the OEM UNLOCK option in developer options. the problem is, no matter what I try when I reboot I ALWAYS end up at the screen pictured below.
Have tried Wugfresh have tried SDK
cant even boot into recovery
please someone tell me there is a way to save this phone...
you might be screwed if you dont have twrp installed. try this..
fastboot format cache
fastboot format userdata
try booting first thing after, if not then try flashing twrp.
Maybe some more information too, like what EXACTLY you were trying to do. How did you end up with a locked bootloader? If the advice given previously didn't work, you are most likely bricked.
EDGRAHAM2.0 said:
OK so i was going to flash back to a factory rom from CYANOGEN, but got bricked and it says I need to check the OEM UNLOCK option in developer options. the problem is, no matter what I try when I reboot I ALWAYS end up at the screen pictured below.
Have tried Wugfresh have tried SDK
cant even boot into recovery
please someone tell me there is a way to save this phone...
Click to expand...
Click to collapse
It's f...ing unbelievable that people still lock their bootloader while having a custom ROM. Just turn it in for repair and blame yourself on this one.
Verstuurd vanaf mijn Nexus 6 met Tapatalk
gee2012 said:
It's f...ing unbelievable that people still lock their bootloader while having a custom ROM. Just turn it in for repair and blame yourself on this one.
Verstuurd vanaf mijn Nexus 6 met Tapatalk[/QUO
Look, not everyone is a savvy as you. I wasn't looking for criticism, I was looking for assistance..
Click to expand...
Click to collapse
EDGRAHAM2.0 said:
Look, not everyone is a savvy as you. I wasn't looking for criticism, I was looking for assistance..
Click to expand...
Click to collapse
If yuour bootloader is locked and you don't have TWRP, there is nothing you can do.
EDGRAHAM2.0 said:
gee2012 said:
It's f...ing unbelievable that people still lock their bootloader while having a custom ROM. Just turn it in for repair and blame yourself on this one.
Verstuurd vanaf mijn Nexus 6 met Tapatalk[/QUO
Look, not everyone is a savvy as you. I wasn't looking for criticism, I was looking for assistance..
Click to expand...
Click to collapse
This is rule no. 1 mate, if you want to be angry be it at yourself.
Verstuurd vanaf mijn Nexus 6 met Tapatalk
Click to expand...
Click to collapse
EDGRAHAM2.0 said:
Look, not everyone is a savvy as you. I wasn't looking for criticism, I was looking for assistance..
Click to expand...
Click to collapse
OK, here's the assistance you're looking for:
Request an RMA from Google, Motorola, or whomever you bought it from. That is your only option.
In wugfresh click return to stock, then click preferences button on bottom make sure to check all 3 boxes to force flash, when finished reboot phone and you should be able to go into settings to check the unlock option.
Tdeljr said:
In wugfresh click return to stock, then click preferences button on bottom make sure to check all 3 boxes to force flash, when finished reboot phone and you should be able to go into settings to check the unlock option.
Click to expand...
Click to collapse
Are you sure you'e understood the problem? You cannot unlock because you need Android to boot to unlock? Or is this a new magic function that none of us know about?
rootSU said:
Are you sure you'e understood the problem? You cannot unlock because you need Android to boot to unlock? Or is this a new magic function that none of us know about?
Click to expand...
Click to collapse
Yes I understand what the op is talking about, I just went through it yesterday. Was rooted and I relocked my boot loader by mistake while trying to flash back to stock. And right now I am responding by using my nexus that has been fully restored back to stock.
Tdeljr said:
Yes I understand what the op is talking about, I just went through it yesterday. Was rooted and I relocked my boot loader by mistake while trying to flash back to stock. And right now I am responding by using my nexus that has been fully restored back to stock.
Click to expand...
Click to collapse
did you have twrp installed still?
simms22 said:
did you have twrp installed still?
Click to expand...
Click to collapse
When I first did it yes. After I was able to get into android I did the steps used wugs unlocked boot loader again and then from there I just fully unroofed and relocked.
Tdeljr said:
When I first did it yes. After I was able to get into android I did the steps used wugs unlocked boot loader again and then from there I just fully unroofed and relocked.
Click to expand...
Click to collapse
yea, if you have twrp installed, its easy to get out of this situation. all you have to do is is format userdata and cache with fastboot(or use the toolkit). but without having twrp installed, i dont see a way out.
The op never said whether he has twrp installed or not. I was sharing my experience but I was in the same boat.
Tdeljr said:
The op never said whether he has twrp installed or not. I was sharing my experience but I was in the same boat.
Click to expand...
Click to collapse
right.
look at post #2
simms22 said:
right.
look at post #2
Click to expand...
Click to collapse
Post #2 isn't the op. But anyway as I said I was just trying to help.
Tdeljr said:
Post #2 isn't the op. But anyway as I said I was just trying to help.
Click to expand...
Click to collapse
absolutely. and as im not with the issue, i still appreciate it
How does one re-lock their bootloader "by mistake"? I'm very curious.
Evolution_Freak said:
How does one re-lock their bootloader "by mistake"? I'm very curious.
Click to expand...
Click to collapse
type in fastboot oem lock "accidentally"
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
FireMedic1234 said:
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
Click to expand...
Click to collapse
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
simms22 said:
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
Click to expand...
Click to collapse
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
FireMedic1234 said:
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
Click to expand...
Click to collapse
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
simms22 said:
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
Click to expand...
Click to collapse
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
FireMedic1234 said:
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
Click to expand...
Click to collapse
ok, boot into the bootloader, connwct via usb to your computer, the type fastboot devices. at that point, it should list your phone via a number. if it does, then its all connected right. then you can flash the factory image, but do not use the flash-all script, flash them all individually.
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
FireMedic1234 said:
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
Click to expand...
Click to collapse
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
I concur. I have used "the" toolkit to see what happens. Have had multiple failures using toolkit and always had to revert to fastboot to fix. Might as well use fastboot up front. Saves a lot of time and headaches.
simms22 said:
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
Click to expand...
Click to collapse
Gotcha thanks again!
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You can drag and drop or copy/paste the image into the command line.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
are you flashing with flash-all or are you flashing each image individually. dont use flash-all, flash them individually.
Share a screen print of the command prompt, with the command you executed, and the error message?
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
FireMedic1234 said:
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
Click to expand...
Click to collapse
Yes.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You don't need to put the system.img there. Please do read general > sticky roll-up thread > adb and fastboot...
...some time.
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
FireMedic1234 said:
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
Click to expand...
Click to collapse
Yes the flash-all.bat can't break up the image. Has something to do with how it sees the partition. Have heard that fastboot in SDK 23+ has fixed this problem. Have not confirmed as I do each individually anyway depending on what I want to do.
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Only way you're gonna possibly brick is flash wrong image to wrong partition. Not sure that even that can be corrected with fastboot as long as the one you bork isn't the bootloader.
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
ChiefEli said:
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
Click to expand...
Click to collapse
do you have twrp recovery, or the stock recovery?
i have stock recovery
linezero said:
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
ChiefEli said:
i have stock recovery
Click to expand...
Click to collapse
The only option is try and fastboot format userdata and fastboot format cache.
If they don't work, there is no fix. Nothing a toolkit can do.
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
simms22 said:
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
Click to expand...
Click to collapse
damn, well i will try it using the toolkit and let you know how it goes.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
good luck!
at the very least, it might help you fix the bootloop.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
Has to have unlocked bootloader for that toolkit option to work.
prdog1 said:
Has to have unlocked bootloader for that toolkit option to work.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
prdog1 said:
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
Click to expand...
Click to collapse
oh well, another "brick"..
simms22 said:
oh well, another "brick"..
Click to expand...
Click to collapse
Pretty much. I have to concur.
prdog1 said:
Pretty much. I have to concur.
Click to expand...
Click to collapse
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
simms22 said:
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
Click to expand...
Click to collapse
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
We don't know but this sucker likes to bootloop. Never relock the device till after it boots and running. Concerning relocking non-stock have seen it bork TWRP and kernel.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
because many people dont read and educate themselves beforehand.
I don't understand why people are re-locking their boot loader. Unless you are returning the device, what is the purpose of re-locking it? I don't get, in this particular thread, why or how the boot loader got locked?
BladeRunner said:
I don't get, in this particular thread, why or how the boot loader got locked?
Click to expand...
Click to collapse
And that is a key question.
I was trying to get ready to turn in my nexus 6 and so I flashed a stock rom (apparently minus the recovery) and relocked my device. I now have twrp but stock 5.1 installed. twrp boots okay but internal storage is 0mb and it appears unable to format partitions. any ideas on a resolution? very comfortable with fastboot (bootloader loads normally) but can't seem to get anything working otherwise.