Database Users

[Q] I need I337UCUAMF3 official firmware

I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]

chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.

If you repeat three times "owaa tagoo siam" it might magically appear.

Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)

agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless

So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app

You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2

chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT

salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.

scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ

salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.

scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.

salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.

scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:

add myself to the thread for future fixes...

Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app

agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.

Thank you! I knew that little bit of advice would help somebody one day.

[Q] How to unlock rooted i9505 from EE network

Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!

intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
I don't think so if you had android 4.4.2 before flash the custom ROM. You will have to buy a unlock code.

How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!

intacto said:
How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!
Click to expand...
Click to collapse
I don't know if is legal or no. All depends of the little letter of the contract. Did you read the contract when you signed it?

intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.

Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.

intacto said:
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.
Click to expand...
Click to collapse
I hope he explain you too the PROS and CONS about that process :highfive:

I know the pross, what are the cons?

The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.

Strephon Alkhalikoi said:
The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.
Click to expand...
Click to collapse
Well I have tried that service menu trick while on kitkat, but that didnt go pass step 2, it didnt even show me the menu, but I am fine with downgrading to 4.2.2 and giving it a try....I also tried ragionaway app 2 days ago, that was a no-go

Because the exploits that allowed both to work were patched in versions later than 4.2.2. Downgrading the modem at minimum is a requirement for either to work.

Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
Well it didnt go well with this 4.2.2 rom i must said, i got this in Odin:
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
I then tried to do the stock of 4.4.2, that resorted fine but it wiped my IMEI and now phone doesnt connect to mobile network...help...:crying:

What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.

Strephon Alkhalikoi said:
What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.
Click to expand...
Click to collapse
I have managed to revert back to lollipop from hte backup and it works fine but I am still in the square one. I do use the original cable, direct to my PC drivers are there, kies isnt running. It did a proper flashing to 4.4.2 but it refuses to have that 4.2.2, is there anyway to downgrade the modem only from 4.4.2 to see if that will work for me? also my phone is i9505xxugni2, the rome u gave me the link to has a different PDA, would that prevent the flashing of my handset?
Cheers!

Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.

Strephon Alkhalikoi said:
Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.
Click to expand...
Click to collapse
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:

intacto said:
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:
Click to expand...
Click to collapse
:good:

RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.

Strephon Alkhalikoi said:
RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.
Click to expand...
Click to collapse
Yes region away always ask for root so I have to re-do it every time after the flash. But seriously EE is the worst provider and one of the most hated companies in UK. I would rather pay someone on the street with z3x box than them

in our country we can get unlock code for free, but only till one month from end of contract. later they ask money.
i hate them too for asking money, but on other hand: why they should do anything for free if phone is yours and not their.

Nexus 6P on boot loop after an OTA update

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.

Bricked?

Hi,
I have the OnePlus 5 8GB.
I unlocked my bootload, rooted my phone, all good.
But then I realized android pay is not working with rooted phones, so i wanted to undo it.
for some reason i ran this because i found it in a guide to lock the bootloader again (yes, it was was stupid):
./fastboot flashing lock
After that i got the message that my device is corrupt and cant boot. So i ran ./fastboot oem unlock and that message disappeard.
I tried booting, but nothing happend for 10 minutes, still boot animation. so i went into fastboot, flashed twrp and tried doing a factory reset, but whatever i do, I get tons of these error messages:
Updating partition details...
Error opening: '/data/misc/[...]
Error opening: '/data/user_de/0/[...['
(No such file or directory)
What can I do?
I can even ADB sideload because of those errors.
edit:
also it shows nothing for bootloader version or baseband version in the fastboot screen.
https://imgur.com/a/z2KN3
doesnt look good. cant copy anything to device or from device

Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted

Eric214 said:
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Click to expand...
Click to collapse
Anything I should do to have them not reject the RMA?
thx for the Magisk advice, using it now.

Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!

TheCorax said:
Anything I should do to have them not reject the RMA?
Click to expand...
Click to collapse
Since it's obvious someone tampered with the software, they may reject it.
You don't lose warranty if you root, but they won't cover the cost if anything happens to it due to the user's intervention.
If you manage to get the stock ROM onto the phone, you may be able to flash it from TWRP.

TheCorax said:
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
Click to expand...
Click to collapse
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs

elbuenzurdo said:
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Yes it works again. That what I meant by android is launching.

TheCorax said:
Yes it works again. That what I meant by android is launching.
Click to expand...
Click to collapse
How do you do to get your device recognized? I have a similar problem for that command. But muy device just turned off and doesnt do nothing, Im trying flash it but nothing atm.
I have a leeco le s3 x626

Question about custom boot logo on my phone ..

First let me apologize if this is a stupid question ...
I got a Galaxy s7 edge Verizon version from eBay ..
After getting and booting up right under de Samsung boot logo and stuff it said CUSTOM .. after I contact de seller he reply .." I buy phones on bulks and some of them come with Google Lock on it and have to get it remove with a custom patch " I say ok no problem since it was a good price and all and them phone works fine with issues I guess I can deal with that ..
Now my question is : IF I ROOTED AMD FLASH A CUSTOM ROM ON IT AND IF I FLASH IT BACK TO VERIZON STOCK WILL GET LOCK AGAIN ? After trying to get activated on the network ?
Maybe a stupid and silly question but just what to make sure I don't end up with a paper weight after trying rooted and stuff ...
Thanks ..

honestly with that custom lock on the boot up that means the seller probably already rooted it previously to install the patch haha and l can only guess by google lock he is talking about the factory reset protection on it??? so before you flash anything onto it i would make sure that is turned off just in case. Otherwise you never know until try and if youre going to flash anything i would say completely wipe the phone too.

gurnsey101 said:
honestly with that custom lock on the boot up that means the seller probably already rooted it previously to install the patch haha and l can only guess by google lock he is talking about the factory reset protection on it??? so before you flash anything onto it i would make sure that is turned off just in case. Otherwise you never know until try and if youre going to flash anything i would say completely wipe the phone too.
Click to expand...
Click to collapse
Thanks for the reply ... yes he said it had the google Lock protection ... I don't think is rooter but I'm going to try to install superU and see ... thanks again

DRpesao said:
First let me apologize if this is a stupid question ...
I got a Galaxy s7 edge Verizon version from eBay ..
After getting and booting up right under de Samsung boot logo and stuff it said CUSTOM .. after I contact de seller he reply .." I buy phones on bulks and some of them come with Google Lock on it and have to get it remove with a custom patch " I say ok no problem since it was a good price and all and them phone works fine with issues I guess I can deal with that ..
Now my question is : IF I ROOTED AMD FLASH A CUSTOM ROM ON IT AND IF I FLASH IT BACK TO VERIZON STOCK WILL GET LOCK AGAIN ? After trying to get activated on the network ?
Maybe a stupid and silly question but just what to make sure I don't end up with a paper weight after trying rooted and stuff ...
Thanks ..
Click to expand...
Click to collapse
If the phone has the unlock icon on the boot, its probably rooted. you can go to the play store and look for a root checker if you want to make sure. If you want to change the root and rom it shouldn't be an issue, but it may require a data wipe on the phone. If you flash it back to verizon stock rom, yes it will "relock" the bootloader (you can't really unlock a US bootloader, you just get root). I got two phones from an amazon owned company and one came fully stocked with all the apps like what you get fresh from box. The second one came debloated, so you don't really know what you are going to get.