Related
I am blind. Figuratively, anyway. I have been looking for the past couple of hours on what flashing exactly is.. and how the heck to do it. To start, I'm rooted on 4.1.1, locked bootloader, stock rom. There are tons of posts about flashing this and that. Installing I'm guessing that's what that means. But today I decided I would try to specifically "flash" a custom bootscreen.
THIS THREAD: http://forum.xda-developers.com/showthread.php?p=43161125#post43161125
So the instructions seem simple.. I'm able to get to a screen where I have a menu with one of the options to boot into "recovery".. but then how do I "Flash" something? I may be missing a number of things here but I'm just trying to figure this out. Does my bootloader need to be unlocked to simply change my boot screen? Do I need something additional to root? Am I pressing the wrong buttons when navigating the menu? I can get to the menu and I can get to a screen with the android is laying down with a red triangle. I sound like I have zero experience, and I basically do. I want to be able to "flash" this boot screen to become comfortable enough to figure out how to "flash" other things like custom roms. I'm just lost here. Anybody in the mood for noob charity?
Unlock your bootlader, install a custom recovery, create a backup of your current rom and then start flashing (installing) to your heats content. The flashing of roms and boot logo/animations that everyone is referring to is simply installing zips from your internal storage or SD card though the custom recovery.
Thanks for the rundown. I'll work on unlocking the bootloader then. Very carefully.
Sent from my XT907 using xda app-developers app
its very easy just follow the guide in post #2
http://forum.xda-developers.com/showthread.php?t=2345558
I've successfully unlocked the bootloader and installed TWRP. Thanks for the help! Is there any way to remove that warning screen about my bootloader being unlocked?
Jersey846 said:
I've successfully unlocked the bootloader and installed TWRP. Thanks for the help! Is there any way to remove that warning screen about my bootloader being unlocked?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1901444
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.
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.
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.
Hey all.
So I've installed LineageOS just fine - the unlocking guides around here are mostly clear enough. Certainly not as easy as I've been used to for Nexus and OnePlus devices though! I've been using the 'official' TWRP 3.0.4.1 and not any of the other (now often links removed) unofficial versions.
I've also got my hands dirty with EDL mode and have totally reflashed a couple of times while playing around.
So on to my question. Basically I have an email client for work (Good for Enterprise) that detects unlocked bootloaders as 'root' (even though I'm not rooted), so I would like to relock my bootloader.
However, as soon as I use 'fastboot oem lock' it instantly bricks my phone. It goes straight into EDL mode, from which it cannot return. No bootloader, no recovery mode, no booting of system. Completely dead. All button combos attempted etc.. The only way back that I've found is to flash a whole new system image in EDL, and start over.
So, have I missed something (a signed recovery?) that makes this happen? Are there some verifications that the bootloader does while locked that fails because there's a custom system and recovery in place?
Is there anything I can do about this? Am I doomed to use stock for as long as I need to use this darned app?
Thanks very much!
Yes you need to be completely stock to lock BL.
Also if you want to stay unlocked, you can use MAGISK to hide root for your mailing app.
Thanks for the replies. I actually don't have, and never have had, root. So the only thing it can possibly be detecting is either the custom ROM itself (or rather, not a factory one from some list they maintain) or the unlocked bootloader. So I doubt MAGISK will work, because there's no root there to hide in the first place
(In case it wasn't obvious, we're talking about Good for Enterprise here).
The blackberry mobile device management system (earlier called GFE) doesnt care if bootloader is unlocked, it just checks whether you have a custom recovery (twrp) and that is enough to flag your system as rooted.