I recently purchased a used Nexus 4, Factory unlocked and sim free 16gb. Android v4.2.2
I unlocked the bootloader, rooted it and installed TWRP however i left it at that, i did not change ROM's or kernels.
After noticing that the phone did not function correctly i decided to return it to its factory state and return it to the store.
This is where my problems began....
As i had used a toolkit to unlock bootloader, root... etc.. i used the same one to undo the things i had done.
First i relocked the bootloader.
Then i tried to unroot but came across an error that i had to have bootloader unlocked to unroot.
so i unlocked the bootloader again.- it wiped the system
Then i tried to unroot,
but i had to have usb debugging enabled which meant i had to boot into the freshly wiped system.
So i went ahead and attempted to start the phone normally.
After about 5-10 mins on the Google screen it would finally move onto the X slash screen.
after 20 or so minuted the on that screen the phone would get extremely hot and still wouldn't boot.
I looked up online for solutions and one said to wipe dalvik cache in recovery
Did that- No luck
Another said to wipe cache
Tried to do that:
Cannot mount cache error message in TWRP
I then tried to restore a nandroid backup from TWRP, Still the same problem.
I even resset factory settings, nothing.
So i figure that the cache partition became messed up and therefore the phone couldnt boot into OS.
Luckily the store had given me a warranty which apparently covered whatever was wrong with the phone.
However, this time i am planning on purchasing a new nexus 4 this time strait from Google and am wondering:
What could have caused this problem? - Could it have been the fact that for a brief moment the phone was rooted while having a locked bootloader, messing something up (the cache partition maybe)?
Is/Has anyone ever experienced a similar problem?
How can people ( like me) avoid this problem/ issue?
Also as i mentioned the phone itself had several minor faults which was the reason i decided to return it to its original state, could this have been another hidden fault that particular phone?
One of the very reason why toolkit is not recommended for people who are not familiar with the process. When the toolkit decides to mess up, it leaves behind a bricked phone with no obvious function to undo the mistake.
Q. What could have caused this problem?
A. I don't know what the toolkit does to unroot your phone, technically "unroot" is to remove the superuser/supersu apk and su binary from your phone. This process can be done with a locked or unlocked bootloader.
Why? Because a locked bootloader only prevent anything to be written to your emmc block in the bootloader mode. However when you have custom recovery installed, you can do these modification in recovery mode even with a locked bootloader.
All process that you have described above will not brick your phone, some commands that you use with the toolkit unknowingly bricked it.
For Nexus devices, you can always go to this website to download the factory image for Nexus 4 and flash it with fastboot. Or flash with the toolkit, if you absolutely have to use it.
https://developers.google.com/android/nexus/images
Q. Is/Has anyone ever experienced a similar problem?
A. There are people bricking their phone with toolkit everyday, so your answer is yes.
Q. How can people ( like me) avoid this problem/ issue?
A. Learn the fastboot and adb command, it's not a lot to learn, might only take 5 minutes, or 1 hour in worst case. I don't blame toolkits, because I believe the toolkit is made for good purpose, to simplify the process, to speed things up. But certainly not made for noobs.
Thank you for your very quick and detailed response. I have used fast boot commands on my previous Android, so I know the basics, just need to adapt my knowledge to the nexus. Will have to brush up on fast boot and read up on adb.
If this was to have happened on a phone that I had brought directly from google would it have been replaced by google?
Also if I was to send back a phone to google for what ever reason, would I need to unroot and uninstall custom recovery as well as locked the boot loader or would it be enough to only lock the boot loader?
Use the tool here: https://developers.google.com/android/nexus/images#occamjwr66v
Put your device into the bootloader and flash.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Use the tool here: https://developers.google.com/android/nexus/images#occamjwr66v
Put your device into the bootloader and flash.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thank You
ksilver89 said:
One of the very reason why toolkit is not recommended for people who are not familiar with the process. When the toolkit decides to mess up, it leaves behind a bricked phone with no obvious function to undo the mistake.
Q. What could have caused this problem?
A. I don't know what the toolkit does to unroot your phone, technically "unroot" is to remove the superuser/supersu apk and su binary from your phone. This process can be done with a locked or unlocked bootloader.
Why? Because a locked bootloader only prevent anything to be written to your emmc block in the bootloader mode. However when you have custom recovery installed, you can do these modification in recovery mode even with a locked bootloader.
All process that you have described above will not brick your phone, some commands that you use with the toolkit unknowingly bricked it.
For Nexus devices, you can always go to this website to download the factory image for Nexus 4 and flash it with fastboot. Or flash with the toolkit, if you absolutely have to use it.
https://developers.google.com/android/nexus/images
Q. Is/Has anyone ever experienced a similar problem?
A. There are people bricking their phone with toolkit everyday, so your answer is yes.
Q. How can people ( like me) avoid this problem/ issue?
A. Learn the fastboot and adb command, it's not a lot to learn, might only take 5 minutes, or 1 hour in worst case. I don't blame toolkits, because I believe the toolkit is made for good purpose, to simplify the process, to speed things up. But certainly not made for noobs.
Click to expand...
Click to collapse
It is soft-bricked, not bricked.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
It is soft-bricked, not bricked.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thanks, it helped so much that the whole world is gonna come here and click your thanks button.
Related
So I am going to be getting a N7 for Christmas, and I was wondering, should I root and unlock the tab before even setting it up? And should I accept the 4.2.1 update before or after doing all this?
Outdated yet young Motorola Photon 4G
I just did mine today on nexus 4 and 7. I had to read everything carefully to find out this was the method that I find it was easy. Make sure you read everything first. Look at the video for 4 and it should be similar to 7 and instructions are provided in link as well. btw I rooted it on 4.2.1.
As rooting will factory reset your device, it will delete all your data. Make sure you backup first.
http://forum.xda-developers.com/showthread.php?t=1766475
Do yourself a favor and learn to do it manually first before using toolkits. There is a lot of tutorials on doing so.http://forum.xda-developers.com/showthread.php?t=1741395 Use fastboot to unlock device:
Command= fastboot OEM unlock
Select yes on your device to unlock boooader.
Install a custom recovery( I would reccomend twrp) and flash supersu zip and you are now rooted.
Need to go back to stock then this is great http://forum.xda-developers.com/showthread.php?t=1907796
Yes toolkits do work but if things go wrong its good to know what to do.
Travisdroidx2 said:
Do yourself a favor and learn to do it manually first before using toolkits. There is a lot of tutorials on doing so. Use adb to unlock device:
Command= adb OEM unlock
Select yes on your device to unlock boooader.
Install a custom recovery and flash supersu zip and you are now rooted.
Need to go back to stock then this is great http://forum.xda-developers.com/showthread.php?t=1907796
Yes toolkits do work but if things go wrong its good to know what to do.
Click to expand...
Click to collapse
I had no intention of using a toolkit lol. Link to the best method to root/unlock?
Outdated yet young Motorola Photon 4G
Lol good deal added another link that you are looking for.
http://forum.xda-developers.com/showthread.php?t=1741395
Travisdroidx2 said:
Lol good deal added another link that you are looking for.
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
Answered my edit before I could post it. You read my mind!
Outdated yet young Motorola Photon 4G
Nexus 7 root and unlock.
Slender Troll said:
So I am going to be getting a N7 for Christmas, and I was wondering, should I root and unlock the tab before even setting it up? And should I accept the 4.2.1 update before or after doing all this?
Outdated yet young Motorola Photon 4G
Click to expand...
Click to collapse
I bought my Nexus 7 about 2 weeks ago. I set it up then downloaded the jb 4.2.1 update. You will have to unlock before you root. I then downloaded Wugfresh Nexus 7 Tool kit to my computer. Very easy to follow instructions. The kit will take you through the steps on unlocking and rooting. There are videos on this procedure. I did not flash CWM and opted to flash TWRP. Excellent recovery system. I downloaded Goo manager app and you can install TWRP within the app. Very easy. You can then make nandroid backups and install custom roms. I am currently on Cyanogenmod 10.1 nightly.Cyanogenmod now has an updater within and it will search for new nightlys and also install them. Very easy. Hope this helps.
I do prefer twrp over cwm. And I was a long time cwm user before. You can fastboot the twrp.IMG file. And if you Fastboot twrp you will not have to rename .bak the stock recovery.
And yes you will want to unlock it and root it first thing since the unlock wipes the entire device.
What's the difference between CWM and TWRP?
Edit: Swipe was acting up.
Outdated yet young Motorola Photon 4G
In my opinion twrp gets more support and updates. Is way faster than cwm and you will never look back. Twrp is a great recovery.
Ok. So if/when I root the 7, I will be using a computer running windows xp, and I don't know how to install the correct files and where.
Outdated yet young Motorola Photon 4G
Hey, I'd like you to help me decide whether I should root my Nexus 7 or not. This is my first android device and I'm a complete 'noob.' Since then I've been reading about rooting continuously and I would've done it already but I'm a bit concerned. I don't want to lose my warranty and I'm aware that I can unroot the device to get my warranty back but what if something happens to the screen or the power button, or what if it bricks after losing battery power? (I read somewhere that this happened to him during night, the device ran out of juice and he couldn't turn it on ever again) Would I still be able to unroot it so I could return it for repair?
My other concern is about the rooting process itself. I've read that it's 99% safe with a toolkit but anything can go wrong. Is this 1% a big risk? Would I be able to unbrick it if something happened? Since I'm a noob my only reason to root my device is to be able to run memory editors like gamecih or something like that. Are the risks worth it?
Thank you for your answers.
BenFuF said:
Hey, I'd like you to help me decide whether I should root my Nexus 7 or not. This is my first android device and I'm a complete 'noob.' Since then I've been reading about rooting continuously and I would've done it already but I'm a bit concerned. I don't want to lose my warranty and I'm aware that I can unroot the device to get my warranty back but what if something happens to the screen or the power button, or what if it bricks after losing battery power? (I read somewhere that this happened to him during night, the device ran out of juice and he couldn't turn it on ever again) Would I still be able to unroot it so I could return it for repair?
My other concern is about the rooting process itself. I've read that it's 99% safe with a toolkit but anything can go wrong. Is this 1% a big risk? Would I be able to unbrick it if something happened? Since I'm a noob my only reason to root my device is to be able to run memory editors like gamecih or something like that. Are the risks worth it?
Thank you for your answers.
Click to expand...
Click to collapse
In all honesty, a toolkit is almost completely unnecessary for the Nexus 7. You can do everything yourself in about 5 minutes. The thing about the Nexus 7 is that Google knew that people would try and do things with it, so they made it easy (How it should be with every device). One thing you should take into consideration when unlocking/rooting any device is "Why am I doing this?" If the answer is "Cuz I can!", you probably shouldn't. If you want to be able to use advanced apps that require root, go right ahead. Even if you are having performance problems, and just want to fix them by installing a new ROM after you unlock, go for it. If not, don't worry about it.
Hi! I was using my N7 3G reading the news and suddenly it became unresponsive. It took about 2 seconds to recognize my touch. So i decided to turn it off and turn it back on. But after it turned back on the touch screen is completely dead. I can't even unlock it. Power and volume buttons still work. I'm on CM 10.1.3
I even forced reboot it many times by holding the power button for about 20s but that didn't help. Anyone ever had this issue too? It seems like a hardware problem. If that's the case i would have it repaired by ASUS but I'm afraid that I won't get warranty because I'm not on stock ROM+rooted+unlocked bootloader
Can you get into recovery? If so, try wiping the cache partition first to see if that helps.
If that doesn't help, do you have usb debugging enabled? If so,
should be able to use the Nexus 7 toolkit. Just boot your tablet, plug it in your machine, fire up the Nexus 7 toolkit and have it unroot and relock your BL.
You might also want to try and see if you can backup your data partition and your internal storage with the N7 toolkit. If you can do that, then you won't lose any of your data or application settings.
You should also be able to flash it back to stock as well via the toolkit and have it erase the user data.
If usb debugging is NOT enabled, then you might be hosed. You could at least do a factory reset in the main recovery.
Other than that, not much else can probably be done unless you want to open your tablet yourself and ensure all the connections are tight. There might be a lose connection for the digitizer and that's all you would need to do to fix it. Of course, that voids your warranty if you open it yourself. I don't know exactly where the hook up is. I'm sure a quick Google will tell you how to fix this if it's possible.
It definitely sounds like either your digitizer is bad or it's got a lose connection.
Good luck!
Sent from my Nexus 7 using Tapatalk 4
thanks for your help. I was going to plug it in my PC BUT IT'S WORKING AGAIN. I was like WTF lol :laugh: . So it must be a lose connection i guess .
By the way, I'm planning to go back to stock in case it happen again so that i can get my warranty at ASUS. And I don't know much about rooting/ flashing so I want to ask some questions .
1. Can I flash google's stock ROM just like flashing other ROMs like CM with bootloader unlocked?
2. Have you tried KitKat. If so have you experienced battery drain? The only reason I rooted and installed CM is that I hate the battery draining issue. I had it since I updated my N7 3G to 4.2.2 and it kept happenings in 4.3
Anyway thanks a lot :good:
So far no major issue with battery and yes flashing process is the same just be careful u need to update ur bootloader to go to 4.4 and flashing wrong bootloader will brick ur device to be careful and read every thing.
Please ignore my spelling mistakes. English is not my native language.
xateeq said:
So far no major issue with battery and yes flashing process is the same just be careful u need to update ur bootloader to go to 4.4 and flashing wrong bootloader will brick ur device to be careful and read every thing.
Please ignore my spelling mistakes. English is not my native language.
Click to expand...
Click to collapse
Well, I used wug's nexus root toolkit to root and unlock bootloader. If I use the option:"go back to stock lock bootloader and flash stock", can I install update from OTA like normal again?
Choriandus said:
Well, I used wug's nexus root toolkit to root and unlock bootloader. If I use the option:"go back to stock lock bootloader and flash stock", can I install update from OTA like normal again?
Click to expand...
Click to collapse
YES
my nexus 7 with jwr66y has struck on the screen boot failed
I tried to relock using nexus tool kit and then tried to flash stock rom and relock but unfortunately nexus root kit dint woed boot locker locked rk well and it displayed bootloader locked and failoed to flash stock rom and now all i got was a bootloader screen with locked state..help me
Hey, try to do the same procedure again.
Sent from my LG-D802 using Tapatalk
federer123 said:
but unfortunately nexus root kit dint woed boot locker locked rk well
Click to expand...
Click to collapse
Easy for you to say.
I don't know what the point of locking your bootloader would be - especially if you don't have a working ROM on the tablet (stock or otherwise).
If you are trying to go back to stock and never root again, well then: unlock your bootloader, get stock running on your tablet FIRST and only then lock the bootloader after everything else is working.
So, for the moment, unlock the bootloader and get a ROM installed. You can use a toolkit if you want, but using fastboot manually will avoid the "hiding" of any error messages. There are a TON of threads in here on how to do that.
And if you want any kind of decent help, don't use the phrase "it didn't work". That's totally ambiguous - it sort of implies that there is only one possible reason why something went wrong on your tablet, and we all know exactly what that one thing is. Not even close; there are hundreds of things that could have gone wrong.
A far better approach is to detail exactly what you were attempting, and then cut and paste any error messages you observed into your post here on XDA.
This guide is for the safe procedure for re-locking your bootloader with the new security features of Android 5.1 on the Nexus 6
The purpose of re-locking your bootloader should solely be used for RMA or resale of your device. Also if you have flashed a factory image and want the added security of a locked bootloader. Or possibly it is required by your employer. If you're required by your employer, then I suggest you reconsider unlocking in the first place. If you're returning to stock, to simply fix problems on your device, then I also strongly suggest leaving the bootloader unlocked. To put it in simple terms, if you want to keep a custom recovery and ROM, mod, root, etc, then leave your bootloader unlocked. Re-locking the bootloader on the Nexus 6 will cause your device to be wiped.
Please read this post by @efrant for more clarification:
http://forum.xda-developers.com/showthread.php?p=60128929
Thanks @efrant @cam30era @rootSU @clairez for collaboration and advice.
This is based on a 100% stock, encrypted, un-modded Nexus 6
Due to significant security changes in Android 5.1, there are some specific steps that must be taken in order to safely re-lock your bootloader during and after installing a factory image.
WARNING! These steps are confirmed working but there is still risk involved. If you do not ABSOLUTELY need to re-lock then I strongly suggest leaving the bootloader unlocked.
FOLLOWING THESE STEPS WILL WIPE YOUR DEVICE SO BACKUP YOUR DATA!
This is based on you (the user) having already read and followed instructions on downloading the factory image and having it ready to install.
STEP 1
Disable all security locks on your phone.
On your phone, go into your settings, click Security. In Screen security, click on Screen lock, enter your passcode/pin/pattern then select none.
You will get a prompt that Device protection features will no longer work. Click OK.
STEP 2
**OPTIONAL**
Thanks @gee2012
This step is optional because successful installation of the factory image will remove this info anyway.
Remove your Google account.
In settings, click Accounts, click Google then click on your account name. (your gmail address)
Click the 3 dot menu button in top right of screen and select Remove account. You will get a prompt That this will delete all messages, contacts and other data from your phone. Click REMOVE ACCOUNT.
STEP 3
This step is optional and may or may not be needed but I recommend doing this.
Preform a factory reset from your phone settings.
Open settings and click on Backup & reset. Click Factory data reset.
You will receive a prompt stating that this will erase all data from your phone's internal storage, click RESET PHONE.
The reset takes quite a while to complete, approximately 10 to 15 or more minutes for a 32gb model and 20 minutes or more for a 64gb model, so BE PATIENT!
Your phone will reboot when completed.
STEP 4
IMPORTANT!!
When your phone reboots, you will have to skip all account set up and ABSOLUTELY do not set any security features up. Skip EVERYTHING!
Go to settings and enable Developer options. (About phone>tap build number 7 times)
Once you have developer options enabled, enable USB Debugging and tick the box to allow OEM unlock.
I suggest preforming a reboot here to verify that OEM unlock sticks. After the reboot enter developer options to verify OEM unlock is still ticked.
If it is, we will proceed. If not, ensure you have followed the previous steps correctly. If you have and for some reason the setting won't stick, DO NOT PROCEED OR YOU MAY END UP STUCK IN A BOOT LOOP WITH NO CURRENT WAY TO FIX!
STEP 5
If setting has stuck, you are ready to unlock your bootloader and install the factory image using one of the ways outlined elsewhere in this forum.
After installation is complete, reboot to recovery and again preform a factory reset. Reboot to Android.
STEP 6
IMPORTANT!
Upon completion of factory reset from recovery and reboot to Android, it is important to follow this procedure so you may now safely lock your bootloader.
SKIP ALL ACCOUNT AND SECURITY SET UP AGAIN! Go to settings and enable developer options again. Enable USB debugging and tick allow OEM unlock.
Again, I recommend a reboot at this point to verify the settings stick.
Use the button combo or ADB to reboot to bootloader.
Use the command fastboot oem lock
Your device will wipe again and reboot.
CONGRATULATIONS! You now have a locked bootloader and you may proceed to restore your phone.
See here for info from Google about the new security features:
https://support.google.com/nexus/answer/6172890?hl=en
Thanks @efrant for finding this link.
Thanks also to all of those who helped to confirm this process works consistently.
Thanks to @clairez for this thread: http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
*Disclamer*
I am not responsible if your device bricks, loops or causes mass world hysteria.
*How to prepare your Nexus 6 for resale*
Since the onset of Android 5.1, there are some specific steps needed to ensure you can sell your device and not have the seller need your Google password when they receive your device. Please read this guide provided by @PatimusXPrime
http://forum.xda-developers.com/showpost.php?p=60455167&postcount=43
TWRP RECOVERY INSTALLED ONLY
The following info is for users who have TWRP installed and are stuck in bootloop (soft brick) after wiping OS with a locked bootloader.
Credit to this thread:
Thanks @ixa20
http://forum.xda-developers.com/showthread.php?t=3053783
STEP 1
Boot into bootloader.
STEP 2
Use fastboot and issue the commands:
fastboot format userdata
fastboot format cache
This should allow you to boot back into TWRP.
Flash a ROM and get up and running.
Unlock your bootloader and leave it that way.
Thanks also to @rootSU for posting this solution many, MANY times.
I hear a lot about locking the boot loader, but what exactly am I missing out on in terms of security with an unlocked boot loader, and rooted
productofusa said:
I hear a lot about locking the boot loader, but what exactly am I missing out on in terms of security with an unlocked boot loader, and rooted
Click to expand...
Click to collapse
I think, primarily, if you are unencrypted you run the risk of your data being compromised if your phone is lost or stolen. Plus, the new security features are not proven to work 100% when bootloader is unlocked. Simply by rooting, you've opened your device to be more vulnerable to malicious attacks. I'm sure you already know that.
Evolution_Freak said:
I think, primarily, if you are unencrypted you run the risk of your data being compromised if your phone is lost or stolen. Plus, the new security features are not proven to work 100% when bootloader is unlocked. Simply by rooting, you've opened your device to be more vulnerable to malicious attacks. I'm sure you already know that.
Click to expand...
Click to collapse
I see, nothing I wasn't already aware of! It seems that a significant amount of people that are used to an unlocked rooted handset are quick to jump on the relock the bootloader omg security bandwagon regardless of the consequences. Having said that thanks to folks such as yourself most of the kinks seem to be worked out at this point.
Thanks
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Cannibal Oxen said:
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
The first post explains how to lock the bootloader safely. If you're going g back to stock, simply follow the steps
Cannibal Oxen said:
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
No, not at all. You can flash a factory image and return to stock at anytime. However, if you plan on flashing ROMs again, there's no need to relock the bootloader. For instance, if you wanted to return to stock to say, get an OTA, the bootloader being unlocked wouldn't affect that negatively.
If you did desire to relock, following this guide, as far as disabling the security and Google account, you should be able to relock. The important thing is making sure that pesky "allow OEM unlock" option remains checked after a reboot.
Cannibal Oxen said:
Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
You can go back to stock. And then, subsequently relock the bootloader.
And the question is not "stupid". Noob questions are encouraged here. That's how you learn.
rootSU said:
The first post explains how to lock the bootloader safely. If you're going g back to stock, simply follow the steps
Click to expand...
Click to collapse
Fair enough. The part that confused me was the first five steps appear to address steps required to unlock the bootloader. I was afraid since I already unlocked mine without first disabling security and removing my account that it would somehow preclude me from ever being able to relock the bootloader should that need ever arise in the future.
I really appreciate the help!
Yeah, I learned my lesson, DON'T PLAY WITH LOCKED BOOTLOADERS ON THIS DEVICE, EVER!
I had a locked bootloader, and no System (I had wiped it accidentally).
Luckily though I had the sense to keep TWRP installed, but I couldn't boot to it, it was just bootlooping to the TWRP splash screen.
I thought I had just lost a $650 investment, but here's what I did:
Boot to bootloader, then
Code:
fastboot erase cache
fastboot erase userdata
Then I could boot to TWRP! So I
Code:
adb push (ChromaOS zip here) /sdcard/
But when I tried to flash the Data and Cache partitions kept giving me errors, I couldn't flash anything!
I went to sleep (or tried to sleep, but couldn't) I was panicking!
When I woke up I tried one more thing:
From bootloader I did
Code:
fastboot format cache
fastboot format userdata
(Notice FORMAT instead of erase!)
I booted into TWRP and was able to flash ChromaOS, I was able to enable OEM Unlock, and flashed the full Factory Image, completely back to stock.
I booted once with unlocked bootloader to verify it was working, then locked it.
If I had the stock recovery, I would've had a $650 paperweight.
DO NOT MESS AROUND WITH LOCKED BOOTLOADERS! DON'T RISK IT!
gorei23 said:
Yeah, I learned my lesson, DON'T PLAY WITH LOCKED BOOTLOADERS ON THIS DEVICE, EVER!
I had a locked bootloader, and no System (I had wiped it accidentally).
Luckily though I had the sense to keep TWRP installed, but I couldn't boot to it, it was just bootlooping to the TWRP splash screen.
I thought I had just lost a $650 investment, but here's what I did:
Boot to bootloader, then
Code:
fastboot erase cache
fastboot erase userdata
Then I could boot to TWRP! So I
Code:
adb push (ChromaOS zip here) /sdcard/
But when I tried to flash the Data and Cache partitions kept giving me errors, I couldn't flash anything!
I went to sleep (or tried to sleep, but couldn't) I was panicking!
When I woke up I tried one more thing:
From bootloader I did
Code:
fastboot format cache
fastboot format userdata
(Notice FORMAT instead of erase!)
I booted into TWRP and was able to flash ChromaOS, I was able to enable OEM Unlock, and flashed the full Factory Image, completely back to stock.
I booted once with unlocked bootloader to verify it was working, then locked it.
If I had the stock recovery, I would've had a $650 paperweight.
DO NOT MESS AROUND WITH LOCKED BOOTLOADERS! DON'T RISK IT!
Click to expand...
Click to collapse
With the method I've outlined and personally tried, it can be safely done. The security settings are the issue and a safe way around that has been found.
Evolution_Freak said:
With the method I've outlined and personally tried, it can be safely done. The security settings are the issue and a safe way around that has been found.
Click to expand...
Click to collapse
I know, I'm just saying don't play around with it, if you're going to relock make sure that you KNOW it will work.
Can confirm that the outlined info here works flawlessly
I used this process to re-lock my phone after unlocking in the fastboot-enabled upgrade from OTA 5.1 "D" to stock 5.1 "E" an hour ago.
The easy part was unlocking/locking/rebooting in the correct order - the harrowing part was when my fastboot update of the radio failed, after which I figured out it was a transient USB issue with my system, so rebooted Windows and then everything went reasonably close to plan.
So, now I'm on "E" and with a locked bootloader (i.e., stock for Verizon). I'll be experimenting with custom ROMs after settling in with this for a bit, but wanted to test out VoLTE and other things before going the custom route.
Thanks again for this guide.
- ooofest
ooofest said:
I used this process to re-lock my phone after unlocking in the fastboot-enabled upgrade from OTA 5.1 "D" to stock 5.1 "E" an hour ago.
The easy part was unlocking/locking/rebooting in the correct order - the harrowing part was when my fastboot update of the radio failed, after which I figured out it was a transient USB issue with my system, so rebooted Windows and then everything went reasonably close to plan.
So, now I'm on "E" and with a locked bootloader (i.e., stock for Verizon). I'll be experimenting with custom ROMs after settling in with this for a bit, but wanted to test out VoLTE and other things before going the custom route.
Thanks again for this guide.
- ooofest
Click to expand...
Click to collapse
Word of caution, don't flash stuff with a locked bootloader. If you get a bad flash and you can't boot, you'll be screwed.
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
pwned3 said:
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes
pwned3 said:
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It does if you have "Device protection" enabled. If you do a factory reset and, while you are running through the set up wizard, do not enable "Device protection", then the " Allow OEM unlock" setting should stick.
Sent from my Nexus 6 using Tapatalk
rootSU said:
Word of caution, don't flash stuff with a locked bootloader. If you get a bad flash and you can't boot, you'll be screwed.
Click to expand...
Click to collapse
Before attempting to upgrade the stock level or going custom, I was planning to run through at least steps 1-4 again to enable me to safely unlock.
Or, do I only need to tick OEM Unlock, adb into stock recovery and then fastboot oem unlock without going through the suggested factory data reset step?
- ooofest
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.