Nougat ota update went wrong? - Nexus 9 Q&A, Help & Troubleshooting

Hi,
Just got the OTA on my stock nexus and did the update. Its on the 4 moving color logos for more than 45 minutes now. Anything I can do?
I advice everyone to wait with the update! Its not ok.

I got the beta program update and it works fine, but your experience isn't unheard of in the OTA upgrade world. First, try to reboot. Report back.
Sent from my Nexus 9 using Tapatalk

So after this time its safe to say its stuck? Before I try to reboot... Its still showing the 4 moving logos.

Yes. You're not a newbie so I think you'll do well to troubleshoot. 45 minutes is much too long. I really don't think waiting will help. If it doesn't reboot into system (google rings again), either 6 or 7, try to boot into bootloader. You could wait about 10 minutes for a reboot if needed.
Sent from my Nexus 9 using Tapatalk

Ok , it still showed the same at this time so I rebooted. Google text, than the 4 moving icons again and now it boots v7! Tnx Ritchea, I was scared there but things like this really shouldnt happen Google!!!

No, they shouldn't! Unfortunately, they do. Do you have adb set up on a computer? If not, consider it if you have one. Even if you never need it, knowing you have it can relieve so much stress because you can use it to get out of tight spots. Also, if you haven't released Developer Options and ticked OEM unlocking and USB debugging, you may want to consider doing so. I'm not saying to unlock your bootloader. Just set the device so you could use ADB and unlock your bl if you get into a real bind.
Glad it worked out for you [emoji3]
Sent from my Nexus 9 using Tapatalk

Yes i have both enabled

Related

[Q] Streak dead?

Evening,
I'd left my Streak off for the most part of two months. Today I turned it on to find it sits on the Dell logo.
I cannot access recovery.
I cannot access fastboot.
I have run streakflash.zip QDL and repairtool.zip QDL - neither have brought it back to life. The latter (repairtool.zip) errors when trying to reboot the device into fastboot, which isn't accessible. So that made sense to me.
I've also swapped out the *internal* SD card with that of another Streak on the off-chance that would help. It didn't.
My thoughts are now swaying towards brick. In a last ditch effort I've come on here to see if other minds may have a solution.
It was working fine as a daily driver but 2 months ago, bizarre.
Thanks
Morning,
Having left the battery out over night, this morning it booted past the dell logo, onto the boot animation and into android. The LEDs flashed continuously the entire time. It will not respond to any input once booted.
Sent from my Dell Streak using Tapatalk 2
Hard to help not knowing what ROM you have on it...
But LEDs flashing means a mismatch of baseband and kernel... get that straightened out... its a common issue... some reading will get you a long way
Sent from my CM9 TouchPad using TapaTalk 2
You're right, reading will get you a long way. If you had, you'd have seen I have no access to recovery or fastboot. Also, that this came on randomly after non-use. Previously it worked fine - no radio issues.
As for the rom, 319.
If you know how to flash radios without fastboot, please do feel free to show me where this has previously been documented. Honestly, that's all I ever see on posts requesting help recently - "read", "search".
Once upon a time, people read the threads thouroughly and tried to help, rather than assuming the OP has done absolutely nothing up until now and suggesting they go away and read.
I shall eat my words if this has been documented. I couldn't find anything on this specific issue.
Sent from my Dell Streak using Tapatalk 2
Bayton said:
You're right, reading will get you a long way. If you had, you'd have seen I have no access to recovery or fastboot. Also, that this came on randomly after non-use. Previously it worked fine - no radio issues.
As for the rom, 319.
If you know how to flash radios without fastboot, please do feel free to show me where this has previously been documented. Honestly, that's all I ever see on posts requesting help recently - "read", "search".
Once upon a time, people read the threads thouroughly and tried to help, rather than assuming the OP has done absolutely nothing up until now and suggesting they go away and read.
I shall eat my words if this has been documented. I couldn't find anything on this specific issue.
Sent from my Dell Streak using Tapatalk 2
Click to expand...
Click to collapse
I read it alright... notice I DIDNT SAY flash anything I said straighten it out... how you end up being able to do it depends on the info YOU find...
If you can't access your DELL recovery you either have an internal memory issue or a hardware issue with your volume buttons (of course we don't know which because you didn't bother to mention WHY you can't access recovery or fastboot... but I'm assuming its a hardware problem
Sent from my CM9 TouchPad using TapaTalk 2
Bayton said:
Evening,
I'd left my Streak off for the most part of two months. Today I turned it on to find it sits on the Dell logo.
I cannot access recovery.
I cannot access fastboot.
I have run streakflash.zip QDL and repairtool.zip QDL - neither have brought it back to life. The latter (repairtool.zip) errors when trying to reboot the device into fastboot, which isn't accessible. So that made sense to me.
I've also swapped out the *internal* SD card with that of another Streak on the off-chance that would help. It didn't.
My thoughts are now swaying towards brick. In a last ditch effort I've come on here to see if other minds may have a solution.
It was working fine as a daily driver but 2 months ago, bizarre.
Thanks
Click to expand...
Click to collapse
you need to do a streakflash my friend...
I've run streakflash qld / vanilla qld but neither resolved the problem. It fails trying to boot to fastboot because fastboot can't be accessed.
The volume buttons work as I can get it to a point of diagnostics to run streakflash.
I made it clear that nothing has been done to prompt this when I stated it didn't turn on after 2 months of non-use. It worked fine before that. So no, you did not read.
Sent from my Dell Streak using Tapatalk 2

VzW Check for Root?

So I finally HAVE to replace my Note 2 via warranty. Power button sticks and will not boot.
At the end of the call to place the warranty order she says "any physical damage, water damage, or software alterations will result in a charge of $290". So I'm rooted and ROM'd and would normally just return to stock. BUT since the phone will not boot, I cannot do this. I realize if it won't boot for me it likely won't boot for Verizon.
My worry is that somehow they will in get it to boot. Do they still check for root? If so is this something I should be worried about? I cannot for the life of me get this thing to turn on it seems like I will not be able to return this to stock with out powering the phone on. Any insight is greatly appreciated.
I have done the warranty replacement game for a long time. Typical the people checking the phone are stupid and dump for checking for root. I havent spoken to or talked to one smart person that would check. Plus the people they hired to make sure the devices comes in probably isn't tech savvy. Just a worker trying to get paid.
Sent from my SCH-I605 using Tapatalk 4
I agree with the above. I guarantee you the people who do the initial evaluation have a 'target' for the number of phones processed. But just the same return your phone to as stock looking as possible. Restore the launcher, use a stock wallpaper and/or boot-ani. Uninstall all apps you got from the store. And run your battery all the way down. It will continue to discharge even though it's off. This means it will need to charge for a few minutes before it will boot again.
And I've never noticed many posts (i can't recall even one) about phones being kicked back for being rooted/flashed.
But with that said isn't there some kind of flash 'counter' on the Note 2?
Sent from my Nexus 7 using XDA Premium 4 mobile app
When I had my DROID X I went into a Verizon store to upgrade to an s3 and the guy who just got done telling me how he "mods" his gnex looked at my X and it was running cm7 themed out the wazoo and he said how plain the stock os is on the Motorola. Haha. So I don't think that 98% of the people who are either in store or at the warranty place have a clue what rooted is let alone able to tell if it is or not.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I think I read somewhere that you can make a powered usb jig the will boot it into download mode. I might be wrong, but you can search around for it.
Sent From My Sticky Note, Too?
Did you even read the op
Sent from my SCH-I605 using xda app-developers app
Yea I can't even get the phone to boot. Which I believe is due to the malfunctioning power button. But I'm still concerned verizon will find some way to get it booted. I'm going to see if I can boot via ADB this evening. Its been quite a while since messing around with ADB so I need to allow myself some time. Hopefully I can boot it and just Odin the factory image via ADB.
I should also try and clear the flash counter right? Does anyone have any tips or know-how on how to do that? I saw somewhere that there is an app. But should that be run before or after running the Odin stock image?
Thanks again guys and gals.
Hey gerg, the app is triangle away, and I would always try to return to stock if possible. I would use it before returning to stock as it needs root privileges. What a great learning experience (better to look at it that way then get angry trying to accomplish your goal). Keep us posted as we are all"rooting" for you....:thumbup:
"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
JeramyEggs said:
Hey gerg, the app is triangle away, and I would always try to return to stock if possible. I would use it before returning to stock as it needs root privileges. What a great learning experience (better to look at it that way then get angry trying to accomplish your goal). Keep us posted as we are all"rooting" for you....:thumbup:
"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
Click to expand...
Click to collapse
Thanks man. Appreciate the positive vibes.
However it seems like I'm stuck. I can't for the life of me get this phone to boot, therefore I can restore the stock image via ADB, because ADB will not recognize the device since it is off. I've tried every trick out there, including the youtube video about pulling the charger and pulling/re-seating the battery as fast as possible. No dice.
I did however receive my warranty device today, and since I have ADB all set up and ready to go, I'll be rooting her and getting back to Trans-Neb ASAP, and of course I'll see you back in that thread.
Again, thanks for the help guys it is appreciated. I'm fairly sure I've tried harder and spent more time to get this phone to boot than Verizon will ( I hope at least). So if they can't get it to turn on, I don't see how they can tell its rooted
Mods can close this thread
Cheers!

[Q] Warning about re-locking the bootloader, AND disabling **Enable OEM unlock**.

Hi, all..
As is probably known, before fastboot commands on the Nexus 9 will work, two things are required...
First, this option, in Developer Options, needs to he checked box ticked...
** Enable OEM Unlock **
...followed by... (with the device booted into it's bootloader)...
Code:
fastboot oem unlock
------
UNDER ABSOLUTELY NO CIRCUMSTANCEs SHOULD THIS PROCEDURE BE REVERSED.... unless you're running 100% stock.
It will very likely cause your Nexus 9 to be become permanently semi-bricked.
The device will boot, and it will charge... However IF YOU CAN'T BOOT ANDROID, AND RE-ENABLE. the ** Enable OEM Unlock ** option in Developer Setting's, then...
Code:
fastboot oem unlock
...will fail.
And you won't even be able to fastboot flash back to factory stock.
You can't even remotely boot a recovery, with...
Code:
fastboot boot recovery
...as this too, also requires an unlocked bootloader.
I know; I've tried.
-----
And this is my current predicament... My Nexus 9 now constantly bootloops into TWRP, with this message, at the top of the screen...
This is a development device not intended for production use..
Bootloader is locked, and I can't unlock it because I can't boot Android in order to set ** Enable OEM Unlock ** in developer options.
Unless anybody has any suggestions, my Nexus 9 is now pretty much useless.
Rgrds,
Ged.
OK.. Anybody know what the setting **Enable OEM Unlock** in Developer Options actually sets.
What flag it sets?
In terms of the underlying operating system, this MUST JUST FLIP some binary state flag, such that...
Code:
fastboot oem unlock
...now works.
There's gotta be some ADB command that will re-enable this, in the absence of a bootable version of Android.
Or some terminal command like a (dd=if>of command).
----
I've been at this for now, for 12 f**king hours...
I've tried everything I know.
At one point, TWRP, didn't bootloop and booted properly. But it was a pyrrhic victory, 'cos I had nothing on the device to restore. That was four hours ago... since then TWRP just bootloops endlessly.
I suspect that when., via the bootloader, I select the FACTORY RESET option, it's looking for the stock recovery... and which of course it doesn't find.... because TWRP is installed.
Indeed, I also suspect because Lollipop now runs encrypted, there are issues with mounting the data partition.
----
Well, I guess, my Nexus 9 is pretty much screwed, I think...
It'll make a nice Christmas decoration though.. It actually lights up!!!))). It's not THAT bricked. It still lights up..
----
In conclusion..
...and for guidance for others...
***
After rooting, and fastboot flashing TWRP...
--do not relock the bootloader.--
--do not disable. ** Enable OEM Unlock ** in Developer Options--
***
If you do both, and Android won't boot, your Nexus 9 is f**cked!!
You won't be able to flash anything; not even with a a toolkit like Wugs. I've tried.
Rgrds,
Ged.
Wow, really sorry to hear about your device! Maybe somebody here can come up with a fix for you...
Thanks for giving the rest of us a heads up!
Sent from my XT1053 using Tapatalk
@GedBlake
If you have time I'm willing to help you out, I've been testing some things and may be able to help, just let me know
Don't worry! Will let demkantor help you. Have you tried fastboot erase recovery and flash stock?
MRobbo80 said:
Don't worry! Will let demkantor help you. Have you tried fastboot erase recovery and flash stock?
Click to expand...
Click to collapse
He can't fastboot because his boot loader is locked. He can't unlock boot loader because he can't check that box. I knew this was gonna be problems as soon as I saw this setting. I guess I get what google was going for, but I still don't like it.
A nexus device should be able to recover from anything short of a hand grenade, for something this simple to semi brick a nexus is ridiculous.
Op, i taje it you can get to an adb shell? Or can you not even access recovery?
di11igaf said:
He can't fastboot because his boot loader is locked. He can't unlock boot loader because he can't check that box. I knew this was gonna be problems as soon as I saw this setting. I guess I get what google was going for, but I still don't like it.
A nexus device should be able to recover from anything short of a hand grenade, for something this simple to semi brick a nexus is ridiculous.
Op, i taje it you can get to an adb shell? Or can you not even access recovery?
Click to expand...
Click to collapse
Hi, di11igaf...
Thanks for your response... And apologies for my late response. I took a few days off from Android; I just needed a break. (And I have a new Nexus 9).
Yep; whilst TWRP was bootlooping, ADB did work... certainly, ADB devices yielded a device serial number... but I had nothing to 'push'.
I had no Nandroid backups on my laptop, and no Custom ROM. zips to 'push'. (I don't even think there are any yet, for the Nexus 9).
And even if I did successfully ADB push something, TWRP was bootlooping.
TWRP was essentially just useless, other than acting as an ADB gateway.
***
demkantor said:
@GedBlake
If you have time I'm willing to help you out, I've been testing some things and may be able to help, just let me know
Click to expand...
Click to collapse
Hi, demkantor...
Thanks for your offer of help... but I now have a new Nexus 9.
Still interested though, in what you have in mind, as I suspect this particular problem is going to rear it's ugly head again sometime in the future. As other Nexus 9 devices will likely befall a similar fate to my Nexus 9....
-----------------------------------------------------------------
Hi, guys...
Thanks for your input, help and advice.
First, apologies for my language in my posts above. It's not often that I resort to expletives, even if disguised with asterisks. It was unbecoming of me, and I hope I didn't cause any offence.
On to the matter in hand...
After three days, I would dearly love to report that 'I fought the good fight', and discovered some ingenious method by which I resolved the problem... but alas I didn't.
The device continued to bootloop TWRP, and fastboot oem unlock continued to fail.
The bootloader itself was still accessible (by pressing & holding vol-down, followed by power on). This button press sequence, interrupted the bootlooping TWRP, and forced a reboot into the bootboader.
But the only real use for this, was to shut down the Nexus 9, as accessing fastboot was a sheer waste of time. With a locked and unlockable bootloader, nothing could be fastboot flashed.
The device was stuck, and with no way out.
A resolution.. but not a solution.
The Nexus 9 in question was actually bought for me, by a very close friend, for my 49th birthday on the 18th November. When she recently enquired how I was doing with it... well, as you can imagine, I was somewhat reluctant to admit that I'd screwed it up.
But eventually, and to my embarrassment, I admitted I'd made a bit of a pig's ear of it.
After she'd given me 'the look', and a sigh of exasperation, she revealed she'd also bought with it, a two year extended, no-quibble, anything-can-happens warranty. I have a similar warranty on my old Nexus 7, though I've never had any cause to avail myself of it on that older device. It adds about £80 to the price of the device. So, this morning, we both headed out to the local PC World from whence she bought the Nexus 9, and got it replaced: no questions asked.
So, I'm currently midway through setting it up again.
Needless to say, I won't be repeating the same mistake!
As it stands, right now, my replacement Nexus 9 is working just fine. And indeed, if it can be said that 'every cloud has a silver lining', it's that the replacement unit is actually 'better'. The original unit had some minor light bleed issues, and the back cover flexed inwards marginally. This new one has no lightbleed at all, and it just feels more robust, with no flexing of the back. Google and HTC really need to get these build quality issues sorted, and quickly. It's really just not good enough on a tablet at this price point.
In conclusion..
After three years of tinkering with Android devices... rooting them, flashing Custom ROMs, etc, this is the first time I've ever rendered one unusable. Not technically hardbricked, in the classical sense, with a black unresponsive screen... but certainly unusable and very likely unrecoverable.
And it's caused me to reconsider the whole point of rooting Android, and unlocking bootloaders.
What are the benefits of doing so? And what are the attendant risks?
And is it worth it?
Of course, it you're rich, and you can afford to replace a bricked device, then maybe it is worth it. Or if you happen to have a no-quibble warranty, (at an additional price), as I did... then perhaps, also it might be worth it.
***
Android today, is a wholly different beast to what it was when I first came to it back in 2011...
...with GingerBread, HoneyComb and, later Ice Cream Sandwich. Then, there where very significant benefits to rooting and flashing Custom ROMs... but today, I'm not so sure it's really worth the hassle, or potential financial cost if things go wrong. And it's been my experience of technology, that things can sometimes go horribly wrong.
***
I rooted my Nexus 9, just so I could run Titanium... A great app, but I feel it's no longer as relevant as once was... and to run Greenify, the power saving app. But if Lollipop delivers on it's promise of improved battery performance, with the so called Project Volta, then maybe even Greenify will become less relevant. And the Greenify app devs. have made great strides forward in making Greenify work in non-rooted mode anyway... I know; I have it running on my unrooted HTC One M8.
Maybe, at some point in the future, I will unlock the bootloader again, and root my Nexus 9 again... but there is going to have to be a pretty compelling reason to do so... And right now, I can't think of one.
I'm just happy to have a Nexus 9 that works one again... and I'm not inclined to take any further chances with it.
Cheers all...
Rgrds,
Ged.
GedBlake said:
Hi, di11igaf...
Thanks for your response... And apologies for my late response. I took a few days off from Android; I just needed a break. (And I have a new Nexus 9).
Yep; whilst TWRP was bootlooping, ADB did work... certainly, ADB devices yielded a device serial number... but I had nothing to 'push'.
I had no Nandroid backups on my laptop, and no Custom ROM. zips to 'push'. (I don't even think there are any yet, for the Nexus 9).
And even if I did successfully ADB push something, TWRP was bootlooping.
TWRP was essentially just useless, other than acting as an ADB gateway.
***
Hi, demkantor...
Thanks for your offer of help... but I now have a new Nexus 9.
Still interested though, in what you have in mind, as I suspect this particular problem is going to rear it's ugly head again sometime in the future. As other Nexus 9 devices will likely befall a similar fate to my Nexus 9....
-----------------------------------------------------------------
Hi, guys...
Thanks for your input, help and advice.
First, apologies for my language in my posts above. It's not often that I resort to expletives, even if disguised with asterisks. It was unbecoming of me, and I hope I didn't cause any offence.
On to the matter in hand...
After three days, I would dearly love to report that 'I fought the good fight', and discovered some ingenious method by which I resolved the problem... but alas I didn't.
The device continued to bootloop TWRP, and fastboot oem unlock continued to fail.
The bootloader itself was still accessible (by pressing & holding vol-down, followed by power on). This button press sequence, interrupted the bootlooping TWRP, and forced a reboot into the bootboader.
But the only real use for this, was to shut down the Nexus 9, as accessing fastboot was a sheer waste of time. With a locked and unlockable bootloader, nothing could be fastboot flashed.
The device was stuck, and with no way out.
A resolution.. but not a solution.
The Nexus 9 in question was actually bought for me, by a very close friend, for my 49th birthday on the 18th November. When she recently enquired how I was doing with it... well, as you can imagine, I was somewhat reluctant to admit that I'd screwed it up.
But eventually, and to my embarrassment, I admitted I'd made a bit of a pig's ear of it.
After she'd given me 'the look', and a sigh of exasperation, she revealed she'd also bought with it, a two year extended, no-quibble, anything-can-happens warranty. I have a similar warranty on my old Nexus 7, though I've never had any cause to avail myself of it on that older device. It adds about £80 to the price of the device. So, this morning, we both headed out to the local PC World from whence she bought the Nexus 9, and got it replaced: no questions asked.
So, I'm currently midway through setting it up again.
Needless to say, I won't be repeating the same mistake!
As it stands, right now, my replacement Nexus 9 is working just fine. And indeed, if it can be said that 'every cloud has a silver lining', it's that the replacement unit is actually 'better'. The original unit had some minor light bleed issues, and the back cover flexed inwards marginally. This new one has no lightbleed at all, and it just feels more robust, with no flexing of the back. Google and HTC really need to get these build quality issues sorted, and quickly. It's really just not good enough on a tablet at this price point.
In conclusion..
After three years of tinkering with Android devices... rooting them, flashing Custom ROMs, etc, this is the first time I've ever rendered one unusable. Not technically hardbricked, in the classical sense, with a black unresponsive screen... but certainly unusable and very likely unrecoverable.
And it's caused me to reconsider the whole point of rooting Android, and unlocking bootloaders.
What are the benefits of doing so? And what are the attendant risks?
And is it worth it?
Of course, it you're rich, and you can afford to replace a bricked device, then maybe it is worth it. Or if you happen to have a no-quibble warranty, (at an additional price), as I did... then perhaps, also it might be worth it.
***
Android today, is a wholly different beast to what it was when I first came to it back in 2011...
...with GingerBread, HoneyComb and, later Ice Cream Sandwich. Then, there where very significant benefits to rooting and flashing Custom ROMs... but today, I'm not so sure it's really worth the hassle, or potential financial cost if things go wrong. And it's been my experience of technology, that things can sometimes go horribly wrong.
***
I rooted my Nexus 9, just so I could run Titanium... A great app, but I feel it's no longer as relevant as once was... and to run Greenify, the power saving app. But if Lollipop delivers on it's promise of improved battery performance, with the so called Project Volta, then maybe even Greenify will become less relevant. And the Greenify app devs. have made great strides forward in making Greenify work in non-rooted mode anyway... I know; I have it running on my unrooted HTC One M8.
Maybe, at some point in the future, I will unlock the bootloader again, and root my Nexus 9 again... but there is going to have to be a pretty compelling reason to do so... And right now, I can't think of one.
I'm just happy to have a Nexus 9 that works one again... and I'm not inclined to take any further chances with it.
Cheers all...
Rgrds,
Ged.
Click to expand...
Click to collapse
As long as you don't make the same 'mistake' again,(admittedly a mistake google should have considered before implementing the 'unlockable' flag) rooting/flashing a nexus is perfectly safe. If you stay unlocked, you can recover from anything. Performance with kernels and roms will continue to get better as the nexus 9s shortcomings are discovered and figured out. (There is a lot of new things with the 9-----lollipop, 64 bit architecture, etc). Personally I need root and an unlocked boot loader, but not everybody does.
Realistically with your device having access to a # adb shell your device was probably recoverable at the very least with 'dd', but you're back up so thats good. You paid for the no questions asked warranty and used it as designed as you should have, as much as it sucks at least you're back up.
Glad everything worked out for you.
GedBlake said:
Hi, di11igaf...
Thanks for your response... And apologies for my late response. I took a few days off from Android; I just needed a break. (And I have a new Nexus 9).
Yep; whilst TWRP was bootlooping, ADB did work... certainly, ADB devices yielded a device serial number... but I had nothing to 'push'.
I had no Nandroid backups on my laptop, and no Custom ROM. zips to 'push'. (I don't even think there are any yet, for the Nexus 9).
And even if I did successfully ADB push something, TWRP was bootlooping.
TWRP was essentially just useless, other than acting as an ADB gateway.
***
Hi, demkantor...
Thanks for your offer of help... but I now have a new Nexus 9.
Still interested though, in what you have in mind, as I suspect this particular problem is going to rear it's ugly head again sometime in the future. As other Nexus 9 devices will likely befall a similar fate to my Nexus 9....
-----------------------------------------------------------------
Hi, guys...
Thanks for your input, help and advice.
First, apologies for my language in my posts above. It's not often that I resort to expletives, even if disguised with asterisks. It was unbecoming of me, and I hope I didn't cause any offence.
On to the matter in hand...
After three days, I would dearly love to report that 'I fought the good fight', and discovered some ingenious method by which I resolved the problem... but alas I didn't.
The device continued to bootloop TWRP, and fastboot oem unlock continued to fail.
The bootloader itself was still accessible (by pressing & holding vol-down, followed by power on). This button press sequence, interrupted the bootlooping TWRP, and forced a reboot into the bootboader.
But the only real use for this, was to shut down the Nexus 9, as accessing fastboot was a sheer waste of time. With a locked and unlockable bootloader, nothing could be fastboot flashed.
The device was stuck, and with no way out.
A resolution.. but not a solution.
The Nexus 9 in question was actually bought for me, by a very close friend, for my 49th birthday on the 18th November. When she recently enquired how I was doing with it... well, as you can imagine, I was somewhat reluctant to admit that I'd screwed it up.
But eventually, and to my embarrassment, I admitted I'd made a bit of a pig's ear of it.
After she'd given me 'the look', and a sigh of exasperation, she revealed she'd also bought with it, a two year extended, no-quibble, anything-can-happens warranty. I have a similar warranty on my old Nexus 7, though I've never had any cause to avail myself of it on that older device. It adds about £80 to the price of the device. So, this morning, we both headed out to the local PC World from whence she bought the Nexus 9, and got it replaced: no questions asked.
So, I'm currently midway through setting it up again.
Needless to say, I won't be repeating the same mistake!
As it stands, right now, my replacement Nexus 9 is working just fine. And indeed, if it can be said that 'every cloud has a silver lining', it's that the replacement unit is actually 'better'. The original unit had some minor light bleed issues, and the back cover flexed inwards marginally. This new one has no lightbleed at all, and it just feels more robust, with no flexing of the back. Google and HTC really need to get these build quality issues sorted, and quickly. It's really just not good enough on a tablet at this price point.
In conclusion..
After three years of tinkering with Android devices... rooting them, flashing Custom ROMs, etc, this is the first time I've ever rendered one unusable. Not technically hardbricked, in the classical sense, with a black unresponsive screen... but certainly unusable and very likely unrecoverable.
And it's caused me to reconsider the whole point of rooting Android, and unlocking bootloaders.
What are the benefits of doing so? And what are the attendant risks?
And is it worth it?
Of course, it you're rich, and you can afford to replace a bricked device, then maybe it is worth it. Or if you happen to have a no-quibble warranty, (at an additional price), as I did... then perhaps, also it might be worth it.
***
Android today, is a wholly different beast to what it was when I first came to it back in 2011...
...with GingerBread, HoneyComb and, later Ice Cream Sandwich. Then, there where very significant benefits to rooting and flashing Custom ROMs... but today, I'm not so sure it's really worth the hassle, or potential financial cost if things go wrong. And it's been my experience of technology, that things can sometimes go horribly wrong.
***
I rooted my Nexus 9, just so I could run Titanium... A great app, but I feel it's no longer as relevant as once was... and to run Greenify, the power saving app. But if Lollipop delivers on it's promise of improved battery performance, with the so called Project Volta, then maybe even Greenify will become less relevant. And the Greenify app devs. have made great strides forward in making Greenify work in non-rooted mode anyway... I know; I have it running on my unrooted HTC One M8.
Maybe, at some point in the future, I will unlock the bootloader again, and root my Nexus 9 again... but there is going to have to be a pretty compelling reason to do so... And right now, I can't think of one.
I'm just happy to have a Nexus 9 that works one again... and I'm not inclined to take any further chances with it.
Cheers all...
Rgrds,
Ged.
Click to expand...
Click to collapse
I think you simply got a good scare off this story, losing a tablet for a checkbox unchecked is quite annoying.
I like to have the bootloader unlocked/s-off as soon as I get a device, so that I can do whatever I like with it the future. I personally couldn't live without root and custom roms, but I guess that my opinion could differ from yours
Sent from my GT-I9100 using XDA Free mobile app
totalnoob34 said:
I think you simply got a good scare off this story, losing a tablet for a checkbox unchecked is quite annoying.
I like to have the bootloader unlocked/s-off as soon as I get a device, so that I can do whatever I like with it the future. I personally couldn't live without root and custom roms, but I guess that my opinion could differ from yours
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
A good 'scare off' story is perhaps sometimes a good thing. It helps keep perspective. A 'chilling' perspective...
Rooting, unlocking bootloaders, and/or flashing custom roms/kernels/recoveries, etc... should, I think, NEVER be considered routine.
We're not talking about installing Angry Birds here... there is always going to be some element of risk to the device.
However, with all that said... I've decided that some valid points have been made... And so I have decided to bite the bullet, and root my replacement Nexus 9.
Currently backing everything up to my laptop...
I'm going to use CF-Auto root... And stay clear of TWRP. I have some suspicions that the presence of TWRP (which endlessly bootlooped), played some part in the previous debacle.
Hope my female friend, who bought me this device, doesn't learn that I'm messing with it again. She'll give me all kinds of hell if I screw it up again!!
Anyhow, signing off for now... progress report later.
Rgrds,
Ged.
Yay!!!! My Nexus 9 bootloader is now unlocked, and successfully rooted... and without problems.
I can now rest easy... .
Thanks once again, for everybodies input, help, advice and guidance.
Kind Rgrds,
Ged.
GedBlake said:
A good 'scare off' story is perhaps sometimes a good thing. It helps keep perspective. A 'chilling' perspective...
Rooting, unlocking bootloaders, and/or flashing custom roms/kernels/recoveries, etc... should, I think, NEVER be considered routine.
We're not talking about installing Angry Birds here... there is always going to be some element of risk to the device.
However, with all that said... I've decided that some valid points have been made... And so I have decided to bite the bullet, and root my replacement Nexus 9.
Currently backing everything up to my laptop...
I'm going to use CF-Auto root... And stay clear of TWRP. I have some suspicions that the presence of TWRP (which endlessly bootlooped), played some part in the previous debacle.
Hope my female friend, who bought me this device, doesn't learn that I'm messing with it again. She'll give me all kinds of hell if I screw it up again!!
Anyhow, signing off for now... progress report later.
Rgrds,
Ged.
Yay!!!! My Nexus 9 bootloader is now unlocked, and successfully rooted... and without problems.
I can now rest easy... .
Thanks once again, for everybodies input, help, advice and guidance.
Kind Rgrds,
Ged.
Click to expand...
Click to collapse
In my opinion, unlocking the bootloader and rooting is routine, on mine and on my close friends' phones. But, as I said, everyone is free to do whatever he likes with their device
I've always had bad luck with TWRP on my devices. I always use ClockworkMod recovery, even if someone specifically recommends TWRP for some task.
But don't be scared by this episode. From your post, you definitely know what you're doing and eventually hit a brick wall. Yeah, **** happens. It's an inherent risk of modding your device.
Just don't give up.
I just relocked mine prior to sending it back, however, I was stock.
I did a full wipe, then did a fastboot oem lock, then booted back into android, re-enabled Developer Options, disabled OEM Unlock option and wiped again - booted into setup screen no problem.
Now packed up ready to send back to Google.
StuMcBill said:
I just relocked mine prior to sending it back, however, I was stock.
I did a full wipe, then did a fastboot oem lock, then booted back into android, re-enabled Developer Options, disabled OEM Unlock option and wiped again - booted into setup screen no problem.
Now packed up ready to send back to Google.
Click to expand...
Click to collapse
that sounds like the logical proper order to do it.
Sent from my Nexus 9 using Tapatalk
Thanks for the warning. So to sum it up, if we need to enable oem unlock, we should be in stock 100%. Right?
albsat said:
Thanks for the warning. So to sum it up, if we need to enable oem unlock, we should be in stock 100%. Right?
Click to expand...
Click to collapse
Hi, albsat...
Apologies it's taken me so long to respond, but with Christmas coming up, and helping out with family related stuff, I've not had much chance this past week to post stuff.
---
Anyhow, to try to answer to your question...
Having thought long and hard about this problem... the problem isn't so much re-locking the bootloader with fastboot oem lock. I suspect this alone, shouldn't cause any problems.
It's the **Enable OEM unlock** setting in Developer Options, that is potentially dangerous.
---
If Android (for whatever reason) won't boot, (bootlooping, for example), and if all other possible remedies fail... you would normally just (re)unlock the bootloader with fastboot oem unlock, and fastboot flash a factory image.
BUT THIS WILL NOT WORK, if the **Enable OEM unlock** setting in Developer Options has also been disabled.
If the device is soft-bricked at this point, and Android won't boot such that you cannot gain access to Developer Options (in order to re-enable that setting), then the device is permanently soft-bricked.
And there is nothing that can be done to rescue the device. And this was my earlier prediciment, as previously described.
---
Let me see of if I can explain why I think this...
In a previous post on this thread, I wrote the following...
GedBlake said:
...anybody know what the setting **Enable OEM Unlock** in Developer Options actually sets.
What flag it sets?
In terms of the underlying operating system, this MUST JUST FLIP some binary state flag, such that...
There's gotta be some ADB command that will re-enable this, in the absence of a bootable version of Android.
Or some terminal command like a (dd=if>of command).
Click to expand...
Click to collapse
This was largely just desperate optimism on my part, in the hope that somebody might know of some ADB or terminal command... but having recently read the OP in this thread, I now know that my attempts to unbrick my previous Nexus 9, was likely a hopeless cause.
If, and as I suspect, the **Enable OEM unlock** setting in Developer Options, is an additional layer of security, then it probably CANNOT be circumvented by some ADB or terminal command.
It wouldn't be much of a security measure if it was that easy!!
Consider the following hypothetical scenario...
"Let's suppose a guy, a regular non-techy kind of guy, buys a brand new Nexus 9 tomorrow. Now, this guy knows nothing about fastboot or factory stock images or any of that stuff. Developer Options, by default, is hidden to him, 'cos he doesn't know you need to tap 7 times on the build number... And so, consequently also, the **Enable OEM unlock** setting is also hidden and by default, it's disabled.
He doesn't know this, and from his point of view, he doesn't want or need to know this. He just wants a nice tablet for browsing the web, checking his emails, posting on Twitter or Facebook, and maybe playing the occasional game. So he takes his new purchase home, and sets it up... with WiFi key and Google Account details, etc. He installs some apps from PlayStore, and copies over his music/pics/documents and other stuff from his laptop.
**But he's a security minded guy, so he decides to set a LOCK PATTERN or PIN NUMBER on his lock screen.**
One day, whilst going to work, he absent mindedly leaves his Nexus 9 on the train... which is then subsequently found by somebody who is not entirely honest. Instead of turning it into the police or the train stations lost property office, this scurrilous individual decides to keep the tablet for himself. He sees the device is PIN or PATTERN locked, but being a bit of an Android expert, he's non too worried about this. All he has to do, is unlock the bootloader and fastboot flash a factory stock image, and the stolen device will be his...
...Or so he thinks!!!
His first stumbling block (and upon which successfully flashing a factory stock image depends), is first unlocking the bootloader... and which of course will fail, because the lawful owner NEVER enabled **Enable OEM unlock** in Developer Options. Indeed, he wasn't even aware that such a setting existed. And our opportunist thief cannot boot Android in order to enable this setting, because he is not in possession of the LOCK PATTERN or PIN CODE required to get past the lock screen.
He is in possession of a useless tablet."
So, in this scenario... the setting **Enable OEM unlock** in Developer Options, has served it's purpose, in rendering the Nexus 9 useless to somebody who has no lawful right to it, and why I think that there was no possible way of salvaging my original Nexus 9. Any such method would undermine the whole point of it.
---
So, in conclusion...
Re-locking the bootloader is probably safe... The danger is ALSO, AND AT THE SAME TIME disabling the **Enable OEM unlock** option in Developer Options... and is risky, as you're potentially disallowing the bootloader from EVER being unlocked again.
And if Android won't boot... FOR WHATEVER REASON, there is NO WAY of re-enabling that setting.
So, once you've enabled it, my advice is to NEVER disable it... regardless of what you do with the bootloader lock state.
---
Anyhow, I hope my lengthy post sheds some light on all of this... And is of assistence to whomever has the patience to read the whole damn thing.
Sorry, but I do tend to waffle on at times.
Kind Rgrds,
Ged.
My case is similar, the only difference is that I never changed the recovery. After a few days of it working ok, at the startup it just stays at the Google logo.
Tried a Factory Reset and Wipe and not yet a single change. Next step would be to just flash the stock ROM, but wait! Developer Options was never enabled nor was Enable OEM Unlock.
I bought this $450 tablet in the US and I live in Brazil and now I cannot even return it. This is how dumb the decision to add this toggle was. And I tought Google made the device for developers.
dirceucorsetti said:
My case is similar, the only difference is that I never changed the recovery. After a few days of it working ok, at the startup it just stays at the Google logo.
Tried a Factory Reset and Wipe and not yet a single change. Next step would be to just flash the stock ROM, but wait! Developer Options was never enabled nor was Enable OEM Unlock.
I bought this $450 tablet in the US and I live in Brazil and now I cannot even return it. This is how dumb the decision to add this toggle was. And I tought Google made the device for developers.
Click to expand...
Click to collapse
You're fine. Just find the factory update.zip and install it via factory recovery, along with a userdata wipe.
After a few tries the factory reset was well succeeded. Thanks for the info though. I had no knowledge that I could flash the stock version via factory recovery. I guess I'm back to the noob pack.
Same just happened to me and I'm stuck. Is there any way to even use TWRP? I can boot into it but it can't mount storage which makes it useless afaik. I was running stock rom and everything except recovery..
You still have no answer to your problem?
Edit: after trying factory reset through the bootloader the recovery won't boot anymore..

Jan2017 - [Root Unlock S-OFF] Verizon HTC 10 1.85.605.9

Verizon & HTC patched the current SunShine temproot with this update, however we have a downgrade path.
If you are on 1.85.605.9 you can downgrade to 1.85.605.8
If you need this RUU from @dottat - https://www.androidfilehost.com/?fid=529152257862670562
To flash the RUU, two methods exist. This should not wipe data, but always backup your data just in case. Again back up your data.
Method 1: (preferred)
Rename the file 2PS6IMG.zip (it is .zip, not .zip.zip, check to see if your os hides the file extension).
place the file on a sdcard, put sdcard into the follow and reboot to download mode using adb (adb reboot download) and follow on screen directions
Method 2:
Reboot the phone into download mode with "adb reboot download"
Use htc_fastboot (not the google version of fastboot) reboot the phone to RUU mode "htc_fastboot oem rebootRUU"
Then flash the zip
"htc_fastboot flash zip 2PS6IMG_PERFUME[email protected]60722.2_CNV_0.93_002_release_486126_signed_1.zip"
Thanks
-Patient Zero
htc_fastboot is not recognized as in internal or external command. im in download mode and trying to enter into fastboot
Thank you for your help i am Very new to this and trying to s-off so i can play around with some roms
stanfiem513 said:
htc_fastboot is not recognized as in internal or external command. im in download mode and trying to enter into fastboot
Thank you for your help i am Very new to this and trying to s-off so i can play around with some roms
Click to expand...
Click to collapse
Do you have the working fast boot files on your computer?
https://www.androidfilehost.com/?fid=24588212152305887
Open cmd from your fast boot folder, then enter commands
afuller42 said:
Do you have the working fast boot files on your computer?
Open cmd from your fast boot folder, then enter commands
Click to expand...
Click to collapse
Thanks man those files were what i needed. I also had something wrong either the name when flashing or the file was not in the right location. I added the .zip to the command and also moved the file into the fastboot folder not sure which one worked but i am currently "optimizing apps" and ill let you know what version it is when the phone finishes.
HA! you guys rock 1.85.605.8. Thanks to both of you sunshine passed when it used to fail. Thanks man for the help.
For some reason the advanced calling features no longer work every time I am on a call it drops to 1x
Edit:I swear I'm not a complete idiot but the advanced calling seems to work fine earlier today it was not working but I just checked in the exact same place and it is working now so I do not know exactly what was going on but it seems to be working now I'm going to S off when I get home. Thanks again for this downgrade
I currently need to send my HTC 10 in for repairs on the charging port/battery charging issues I'm having and I have a concern. I'm currently unlocked and S-OFF and if I RUU back to factory settings I will remain S-OFF regardless. When HTC gets my device they (I assume) will relock it and return it to S-ON status or shoot me a new/like new device. If they do return my device will I need to re purchase sunshine considering I sent my phone directly to u guys to have it S-OFF'd I'm just curious as to what my options will be. Thanks
eriknors said:
I currently need to send my HTC 10 in for repairs on the charging port/battery charging issues I'm having and I have a concern. I'm currently unlocked and S-OFF and if I RUU back to factory settings I will remain S-OFF regardless. When HTC gets my device they (I assume) will relock it and return it to S-ON status or shoot me a new/like new device. If they do return my device will I need to re purchase sunshine considering I sent my phone directly to u guys to have it S-OFF'd I'm just curious as to what my options will be. Thanks
Click to expand...
Click to collapse
Second guy this week? Sure it's a physical issue?
Sent from my SM-T810 using Tapatalk
dottat said:
Second guy this week? Sure it's a physical issue?
Click to expand...
Click to collapse
Yep I've done everything I can think of to try to get my phone to start charging, got a new cord, used 5 different chargers, did the whole factory reset/RUU (that worked for about a day and I got it to charge to 84%, held down vol+ and - and power for 2 mins nothing is working
eriknors said:
Yep I've done everything I can think of to try to get my phone to start charging, got a new cord, used 5 different chargers, did the whole factory reset/RUU (that worked for about a day and I got it to charge to 84%, held down vol+ and - and power for 2 mins nothing is working
Click to expand...
Click to collapse
Cleaned out the port?
Sent from my SM-T810 using Tapatalk
dottat said:
Cleaned out the port?
Click to expand...
Click to collapse
To the best of my ability with some cotton and alcohol
I also have lots of battery charging issues. Mine will not charge unless I reboot while plugged in. Tried multiple chargers, cables, Roms, full whipes, formatted data, stock rom, ruu, everything. Just when I get frustrated enough to do something if starts charging again.
Quick and yes maybe for sure "noobish" question.. Feb 17th VZW is disconnecting this line. (unlimited data plan) and my htc 10 is only 17% paid off. Obviously the first thing I did when I got this phone as well as my M8 was you sunshine. (unlocked/s-off) Now for noobish sake does this mean VZW cannot possibly anyway block my phone or IMEI or Blacklist so I would be unable to stick another carrier SIM card in and use my device with them? You know, bring your own device, byod? I never thought I'd be in this situation but I'm kind of freaking out so thanks for your understanding, thank you..
Sent from my HTC6545LVW using Tapatalk 2
I put it in these words because when I add up to the HTC 10 nothing at all was ever mentioned about ganking my account and leaving me with an unpaid device that I could not use unless I surrender to them and use the limited g*y data plans. So I just figured if they wanted to be bullies it would be pretty sweet for me if they try to lock my phone or Blacklist it and they couldn't. Thanks again
1droidmod said:
Quick and yes maybe for sure "noobish" question.. Feb 17th VZW is disconnecting this line. (unlimited data plan) and my htc 10 is only 17% paid off. Obviously the first thing I did when I got this phone as well as my M8 was you sunshine. (unlocked/s-off) Now for noobish sake does this mean VZW cannot possibly anyway block my phone or IMEI or Blacklist so I would be unable to stick another carrier SIM card in and use my device with them? You know, bring your own device, byod? I never thought I'd be in this situation but I'm kind of freaking out so thanks for your understanding, thank you..
Sent from my HTC6545LVW using Tapatalk 2
I put it in these words because when I add up to the HTC 10 nothing at all was ever mentioned about ganking my account and leaving me with an unpaid device that I could not use unless I surrender to them and use the limited g*y data plans. So I just figured if they wanted to be bullies it would be pretty sweet for me if they try to lock my phone or Blacklist it and they couldn't. Thanks again
Click to expand...
Click to collapse
They can't do that to your device, it would be illegal. You can bring it to any carrier also. Sticking to stock Verizon rom will get you a pop up saying sim is not from Verizon but everything should function.
You could really stick it to them and fully convert your phone to us unlocked after you switch and no more sim pop up and completely Verizon-less system/firmware, that's probably way to go anyways if switch carriers
afuller42 said:
They can't do that to your device, it would be illegal. You can bring it to any carrier also. Sticking to stock Verizon rom will get you a pop up saying sim is not from Verizon but everything should function.
You could really stick it to them and fully convert your phone to us unlocked after you switch and no more sim pop up and completely Verizon-less system/firmware, that's probably way to go anyways if switch carriers
Click to expand...
Click to collapse
Cool, thank you for the confirmation. Tomorrow I am speaking with Stephanie B. A supposed VZW executive. I only average to 241 gigabytes a month, I was never made aware of a 200 gigabyte cap so I'm going to see what I can do about keeping it open but I also have a second line that is also unlimited data which they don't care about at this time because it doesn't come close to 200 gigabytes a month so I think I might have some wiggle room but I don't know. I just wanted to express to her my main concern is the fact I was never made aware about what happened over 200 gigabyte cap and also we as their customers we're never given a questionnaire or survey as far as the 1% of their customers who have unlimited data goes what should happen to us as far as going over 200 gigabytes is concerned. I doubt anything will happen that's not going to already but I'll let you know if I get to keep my line. Thanks again
Sent from my HTC6545LVW using Tapatalk 2
delete
dottat said:
Second guy this week? Sure it's a physical issue?
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I just got mine back. Took to Verizon a complete brick. I've only had 4 months. Finally got the new one in mail
About to downgrade and use sunshine and yes it has to be paid for again. Geesh these 10's are much more fragile than my old m8 . First device I've ever bricked. Now I didn't have to pay anything for replacement to be sent. I know people personally there though
Good luck and happy flashing
10
Just wanted to say thanks for this. Got my replacement in the mail after a brick. Immediately before reading the latest ota blocked sunshine from working. I took ota and set up device. Searched & downloaded your linked file : renamed and moved to SD card. Here is where it got strange. Battery over 50% mind u. Ran first time failed near the end. Left device useless. Tried to run again after booting back to download mode. Failed again. Only to boot device into white HTC screen. Well after about an hour of trying to figure out a way out the hole I've dug again, because PC will not recognize phone like this. And I could not fastboot said file. Anyhow after about another hour I tried again. And finally the same thing loaded everything properly and finished without an error. So successfully downgraded firmware so I could run ☀ . Ran sunshine and am s-off,now.and all is well. Any understanding why it would fail twice then work. Same method.?
Sent from my HTC6545LVW using XDA-Developers Legacy app
mattie_49 said:
Just wanted to say thanks for this. Got my replacement in the mail after a brick. Immediately before reading the latest ota blocked sunshine from working. I took ota and set up device. Searched & downloaded your linked file : renamed and moved to SD card. Here is where it got strange. Battery over 50% mind u. Ran first time failed near the end. Left device useless. Tried to run again after booting back to download mode. Failed again. Only to boot device into white HTC screen. Well after about an hour of trying to figure out a way out the hole I've dug again, because PC will not recognize phone like this. And I could not fastboot said file. Anyhow after about another hour I tried again. And finally the same thing loaded everything properly and finished without an error. So successfully downgraded firmware so I could run ☀ . Ran sunshine and am s-off,now.and all is well. Any understanding why it would fail twice then work. Same method.?
Sent from my HTC6545LVW using XDA-Developers Legacy app
Click to expand...
Click to collapse
Same situation but different device.. Samsung s4 or s5 nt sure anymore but downloaded stock firmware and used correct drivers/ODIN, flashed atleast 3 hrs straight always failed, finally it worked, dont know what/why it took so many tries but I was not quiting until something gave... Was very strange, like ur deal.
Sent from my HTC6545LVW using Tapatalk 2

7 Days OEM unlock requirements ? exactly what is required

so about 8 days ago i saw there were updates for my S9 software available , at this time i was about to root and had oem unlock visible. anyway i thought it would be good to do the updates first as it said something about improving the camera stability which i thought would be worthwhile to do before root ( and then cant do OTA updates)
anyway after the updates the phone restarted and said something about security issue and restarted again. after that no OEM unlock available. i just waited 7 days with no restart and no OEM unlock is still not visible.
so yesterday i did full reset of device and will wait another 7 days, phone has no sim in it as im not using it. but it is signed into google but not samsung account. do we know if this good enough to get the OEM unlock after 7 days ?
its a long time to wait each time... had the phone over 2 weeks now and still using my s8 as i cant root this new one yet...
please can we confirm what exactly is required to make sure that after 7 days we see the unlock ?
insert sim card ?
google account sign in
Samsung account sign in
don't power off or reboot
i didn't insert sim or sign into Samsung last time.. not sure if necessary ?
would be good to make sure what is needed for sure.
I saw this on this forum, but my phone had OEM unlocking even on the first days of purchase.
I have the same problem with my s9+ have been waiting for 7 days since first start the phone but I did factory reset few times trying to get OEM but still no luck.
My wife s8 had the Oreo update this morning then I checked the dev mode after it completed and fuss what OEM is fine too arrrrrr
I believe you need a SIM.
Also factory reset will reset the timer. So dont do that!
Hi, any update in this. I'm currently experiencing the same thing. Did the OEM unlock eventually show up?
Samik7 said:
I have the same problem with my s9+ have been waiting for 7 days since first start the phone but I did factory reset few times trying to get OEM but still no luck.
My wife s8 had the Oreo update this morning then I checked the dev mode after it completed and fuss what OEM is fine too arrrrrr
Click to expand...
Click to collapse
Lol everytime you factory reset you reset the counter, so your actually making it harder on yourself. Guys there is a ton of info out there on the 7 day wait, is suggest get to reading instead of everyone posting the same silly questions
sent from my S9 plus, Pixel 2 XL or Note FE
force70 said:
Lol everytime you factory reset you reset the counter, so your actually making it harder on yourself. Guys there is a ton of info out there on the 7 day wait, is suggest get to reading instead of everyone posting the same silly questions
sent from my S9 plus, Pixel 2 XL or Note FE
Click to expand...
Click to collapse
I haven't factory reset or anything and still hasn't showed up after 11 days. Any ideas?
Logan0829 said:
I haven't factory reset or anything and still hasn't showed up after 11 days. Any ideas?
Click to expand...
Click to collapse
Unfortunately you just have to wait it out, there have been cases where weeks went by and then it just pops up.
Some people have had luck changing csc but doing that has caused others issues.
Even since the note 8 came out last year this isnt fully understood sadly
sent from my S9 plus, Pixel 2 XL or Note FE
force70 said:
Unfortunately you just have to wait it out, there have been cases where weeks went by and then it just pops up.
Some people have had luck changing csc but doing that has caused others issues.
Even since the note 8 came out last year this isnt fully understood sadly
sent from my S9 plus, Pixel 2 XL or Note FE
Click to expand...
Click to collapse
Well damn this sucks. Might just sell it for op6 or something then. Thanks tho.

Categories

Resources