After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption
Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked
Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?
DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow
Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.
-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone
Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming
Related
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things
jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.
The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App
xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App
Thanks for the clarification. I'll do some more reading in the dev section
Thanks a lot, this really helped me out a lot. I will proceed to rooting
So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
badboy47 said:
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
Click to expand...
Click to collapse
I mean People have had trouble when they have been at a Official Servicecenter.
Apparently the servicecenter said that the customer have had a open bootloader then locked it before going to repair, so the Servicecenter refused to repair the phone.
I dont know if its a myth or not?
so its 100 % secure not damaging any hardware just unlocking the bootloader with nexus toolkit.
Eastliin said:
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Click to expand...
Click to collapse
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data, again.
iowabeakster said:
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data when you unlock in the future.
Click to expand...
Click to collapse
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Eastliin said:
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Click to expand...
Click to collapse
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
iowabeakster said:
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
Click to expand...
Click to collapse
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Eastliin said:
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Click to expand...
Click to collapse
actualy google says to unlock,flash and then relock for"security purposes".
opssemnik said:
actualy google says to unlock,flash and then relock for"security purposes".
Click to expand...
Click to collapse
Thats fun haha, you got a link of where they state that?
Eastliin said:
Thats fun haha, you got a link of where they state that?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
opssemnik said:
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
Click to expand...
Click to collapse
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Eastliin said:
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Click to expand...
Click to collapse
^, they tried to screw with me, but as i know lg here in brasil, i carried a book of "consumers defense code", i showed them the link,and the guy from the service center had to get my n4 and fix for no fee (my screen was broken, and no touch, but the screen broke because of overheating).
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
sumit29 said:
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
Click to expand...
Click to collapse
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
gasparzim said:
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
Click to expand...
Click to collapse
No, as per the instructions in my guide you can only install a newer build. I wasn't aware that full OTA zips were even available for the Developer Previews.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Have already tried doing this...this also gets interrupted mid-way, with the command terminal showing - "connection reset by peer". these are the same OTA files available on the google developers website.
and for some reason, it worked this time around!!!
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
Same problem have you been able to sort it out yet?
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Heisenberg said:
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Click to expand...
Click to collapse
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
no.:crying::crying:
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Heisenberg said:
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Click to expand...
Click to collapse
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
Mine is also still messed up I'm calling the store where I bought it to see if they can do anything highly doubt they will though
Ame123 said:
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Click to expand...
Click to collapse
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Heisenberg said:
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Click to expand...
Click to collapse
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
An accredited repair centre should have access to software tools that can do it.
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
did not understood what you said. can you explain a little bit more?
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Ame123 said:
did not understood what you said. can you explain a little bit more?
Click to expand...
Click to collapse
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've tried sideloading multiple times and they succeeded however my phone is still not booting :/
Hey, is it possible to get rid of this message when booting?
Would be nice
Sure, just re-lock your bootloader. Presto. ?
thedrizzle said:
Sure, just re-lock your bootloader. Presto. ?
Click to expand...
Click to collapse
Probably a stupid question but im rooted, will it still boot up?
Macblack1991 said:
Probably a stupid question but im rooted, will it still boot up?
Click to expand...
Click to collapse
No, it's likely that your device will brick. Please don't do so
veatesia said:
No, it's likely that your device will brick. Please don't do so
Click to expand...
Click to collapse
Okay thanks for the reply
Dead end thread, there have been many many many many many posts about that since oneplus introduced that a couple of years ago
THERE IS NO WAY TO GET RID OF THAT WHILE UNLOCKED
period
and there's a thread about it here. been following this from the start and apparently it's next to impossible to achieve.
https://forum.xda-developers.com/oneplus-6t/development/wip-dissecting-bootloader-aka-rid-t3878470
veatesia said:
No, it's likely that your device will brick. Please don't do so
Click to expand...
Click to collapse
I have experience doing that. Yes your device will definitely get BRICKED!!! Just ignore that boot screen, do not attempt to do anything to get rid of it. It just takes time to accept it. I use to think about getting rid of it as well when i was using my Oneplus 3. I re-locked the bootloader and got bricked. I couldn't do anything and had to send it back to Oneplus to fix it.
There have been other devices where they are able to replace the image with another, such as a blank image to hide the warning. I've also seen people load custom ROMs signed with their own signature so they can relock their bootloader after loading a custom OS. So there are things that can be done, but it's not something to just play around with, as mentioned, mess it up, and you'll brick something.
Thanks for the replies. Well I guess its just how it is, nit a big issue, was just wondering because most videos of custom roms I saw this part was cut out lol.