Database Users

Flashed custom recovery, WiFi broken

I have an SGH-I337 with Android version 4.4. I have the Knox bootloader (sadface). I attempted to root this phone previously using Saferoot but this caused problems (relevant thread).
I can connect to the data network but I can't get the wifi to work. It won't even turn on. As soon as I tap the switch it goes back off.
Please help.

You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app

DeadlySin9 said:
You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.

goose90proof said:
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.
Click to expand...
Click to collapse
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).

DeadlySin9 said:
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).
Click to expand...
Click to collapse
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:

WiFi issues with OTA firmware too
Just thought I'd add that the OFW has WiFi issues as well, at least for a few if us. When I updated OTA to 4.4 the WiFi worked for a couple of weeks then stopped working (reboot will allow it to work for a while until the unit sleeps, then it won't toggle). I tried the Odin tar.md5 image and the same thing crops up. This thread is relevant: [Q] OFW 4.4.2 WiFi Not Turning On. I like KitKat, hopefully we can figure out what the problem is.

goose90proof said:
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:
Click to expand...
Click to collapse
You likely overwrote the stock recovery. Here is the NB! stock recovery. Flash in PDA slot in Odin:https://mega.co.nz/#!M9EQBT5A!ri4QeMYpgi-JjmUGZ3FY2gtogDBWPEL7zRCjASIcVe8
If you need the NB1 stock modem here it is. Also flash in PDA slot in odin: https://mega.co.nz/#!sstkFRiJ!d9zTRte0KcVFv7o-bjKFuFMM1Q9ivzDlqJKy2OlP_7o

Excellent thank you.

goose90proof said:
Excellent thank you.
Click to expand...
Click to collapse
did it work for you?

I haven't gotten around to trying it. The phone is working now so I'm a bit reluctant to do anything to it until future developments bear fruit.

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.

Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.

So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app

rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.

JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app

http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app

I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.

Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.

JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)

Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.

JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far

Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.

joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf

Can't sideload the OTA

Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it

Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?

Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands

I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...

DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site

brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.

Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.

Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.

Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!

Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.

Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.

billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.

Panic - plz help! applied the wrong ota file from adb by mistake, now bootloop

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 :/

Bootloop Photo Recovery

Hello everybody!
I guess there are hundreds of threads out there about this topic, however, I could not find a clear answer to my question.
One week ago my Nexus 6p decided to go into a bootloop... I got a refurbished replacement by google because I am still in warranty.
However, I did not do a backup for a loooooong time (one year :/ ) and my photos are on the bootlooping phone.
Some of them are very dear to me.
No, I did not use google photos for backup, as I don't like google having rights to use my photos.
So, my phone is bootlooping. No, the bootloader is not unlocked. I am not sure if USB debugging is enabled or not.
If I go into fastboot i can identify my phone via terminal (fastboot devices).
If I go into recovery and enter adb devices nothing showes up. However, if i go into sideload via adb i can find my phone (adb devices), but not pull any data (adb pull does not work).
My question: Is there any possibility to get my pictures off that phone? If yes, what can I do.
If not, then thats it.
I am looking forward to some good advice! I hope someone might be able to help me
Thank you all!

@mori88 If you have already tried sideloading a full OTA in recovery mode, then you are done. Sideloading via ADB in recovery works because it is a different mode.

v12xke said:
@mori88 If you have already tried sideloading a full OTA in recovery mode, then you are done. Sideloading via ADB in recovery works because it is a different mode.
Click to expand...
Click to collapse
Well, I did not try to sideload a full OTA yet. I was not sure if it would delete all my data on the phone. But I am not sure it would let me access my data either...?

mori88 said:
Well, I did not try to sideload a full OTA yet. I was not sure if it would delete all my data on the phone. But I am not sure it would let me access my data either...?
Click to expand...
Click to collapse
OTA will not delete your data and is your last chance that I am aware of. The OTA needs to be newer than your current build. If it completes successfully you may be able to boot the phone... but you may not. You are just eliminating a software issue as being at fault (rather than the more likely hardware defect). If after flashing the OTA the OS won't load then "that's it".

v12xke said:
OTA will not delete your data and is your last chance that I am aware of. The OTA needs to be newer than your current build. If it completes successfully you may be able to boot the phone... but you may not. You are just eliminating a software issue as being at fault (rather than the more likely hardware defect). If after flashing the OTA the OS won't load then "that's it".
Click to expand...
Click to collapse
Well... nothing newer than Android O out there yet, so I guess I'm not lucky... :/

mori88 said:
Well... nothing newer than Android O out there yet, so I guess I'm not lucky... :/
Click to expand...
Click to collapse
Oh, so you are on OPR6.170623.019 ? It was the second September image that came out a week ago right after OPR6.170623.017 which was late. Usually there is only one image per month, but this month there were two because of the Android Pay issue. Go get the full OTA and sideload it from stock Recovery.