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..
Related
I was fiddling with adb after work and out of curiosity I tried following the unlock procedure that I used on a Xoom before. This has probably been tried so thats why Im asking. When I issue reboot bootloader and then fasboot oem unlock through adb, it says "If you wish to proceed please re-enter the command containing the unique ID of your device: "Then it lists an ID." Its 16 characters long. Is this echo normal? I did get my fastboot.exe from the internet somewhere because the SDK I got didnt have it.
I looked online and the way you unlock the bootloader on an Atrix is by doing the same steps so that leads me to my question: What happens if I re-enter the command with the unique ID? Im just afraid to screw something up. That is according to this link: http://mobilegeeky.com/hack-unlock-the-atrix-4g-bootloader/
I find it hard to believe that unlocking the bootloader is that easy but I just dont want to end up in a "curiosity killed the cat" kind of scenario and brick my phone.
Thanks guys!
I tried it for you . It just returns a message that says "OEM unlock is not implemented".
robocuff said:
I tried it for you . It just returns a message that says "OEM unlock is not implemented".
Click to expand...
Click to collapse
Thanks man. Im kinda skittish with my phone. Thats disappointing it doesnt do anything but what else could we expect haha.
Well, I figure I don't have much to lose. I can upgrade at a discounted price if I want so I figured what the heck. Worst case, if for some reason I couldn't sbf my way out of a jam I'd have to use the upgrade. That wouldn't be all bad though.
robocuff said:
Well, I figure I don't have much to lose. I can upgrade at a discounted price if I want so I figured what the heck. Worst case, if for some reason I couldn't sbf my way out of a jam I'd have to use the upgrade. That wouldn't be all bad though.
Click to expand...
Click to collapse
what are you looking at for your upgrade. I'm due an upgrade also n have done allot to this x2
But don't really know where to go from here. A razor? was suggested a galaxy nexus but know absolutely nothing about that.
Get the galaxy nexus. Its completely stock android. It gets tons of updates because it runs pure android.
Sent from my MB870 using XDA App
Well, I've done a limited amount of reading on the nexus. If I was looking to upgrade, I'd be tempted to get one except for one thing. No sd card. Don't think I want a phone without support for a sd card. I also did some reading in the nexus forum here. The phone isn't without it's faults. For one thing, it looks like there's a fair amount of people who aren't happy with the glass on it. The say it scratches easy. That can be remedied with a screen protector of course, but, if you happen to be one (like me) who doesn't care for screen protectors, well, it's a negative too.
Anyway, I haven't done enough reading to come to a final conclusion on what phone I'd get. I'm not really looking to upgrade at the moment. Things are just getting interesting with this one.
I imagine that the obvious answer is also the correct one, meaning this is not going to be an option. In a way, it's just as frustrating as before Asus provided an Unlock tool (which they did, on schedule at least on the schedule they committed to.) For all of the blunders that occurred around and with the Transformer Prime, they have work like hell to overcome a lot of the issues. They haven't been entirely succesfull on all fronts, such as the reboots that keep recurring for some, but not for others with each succesive update, but you cannot fault Asus for failing to try.
I guess why I asked will be a common point of contention for a lot of us. It can be agonizing to see sweet looking ROMs showing up, and wanting to enjoy that on the Prime, but unfortunately the Bootloader Lock/Unlock is not like rooting, S-On and all the rest because just about all of those changes are undo-able.
I know personally that every device I root, I look at the tool or method to see how difficult (or possible even) un-rooting is. As long as I now I can put the device n a returnable state for warranty coverage, I am the bravest ROM Flasher in the world! LOL
Because $500-800 is a lot of money to have tied up in a device, one that has had more that a fair amount of issues, including issues that require RMA, it is just too risky for the average Prime owner to unlock the Bootloader.... MAJOR BUMMER!
A really awesome option would have been, or could be if Asus said: "Unlocked bootloader devices lose warranty, BUT, if you are able to restore the device to factory spec (including re-locking the bootloader, a tool that does not presently exist) we will honor the remaining portion of the warranty"
And yes, I am aware that the serial number is recorded by Asus during the unlock process.
That would be the ultimate option. The chance of it happening?About as likely as a new update arriving that fixes GPS completely and permanently. Oh well. One can dream, right?
Sigh.
Prior to owning the TF201, I owned the TF101 which was flawless for the first 4 months of owning it, and then one day it developed this strange off-white splotchy area on the screen, it was pretty big too... way more noticeable than a dead pixel. If I couldn't have RMA'd it, then the value of the tablet would've gone down significantly.
I'm a little more worried about the TF201 developing issues later in it's life, so I probably wont be unlocking my device until there's a way around the warranty void. A $500 gamble is not worth a minor performance boost you might get from using a custom rom (IMO).
Edit: Just noticed you live about 30-40 minutes from me, Raleigh NC here.
SmartAs$Phone said:
I imagine that the obvious answer is also the correct one, meaning this is not going to be an option. In a way, it's just as frustrating as before Asus provided an Unlock tool (which they did, on schedule at least on the schedule they committed to.) For all of the blunders that occurred around and with the Transformer Prime, they have work like hell to overcome a lot of the issues. They haven't been entirely succesfull on all fronts, such as the reboots that keep recurring for some, but not for others with each succesive update, but you cannot fault Asus for failing to try.
I guess why I asked will be a common point of contention for a lot of us. It can be agonizing to see sweet looking ROMs showing up, and wanting to enjoy that on the Prime, but unfortunately the Bootloader Lock/Unlock is not like rooting, S-On and all the rest because just about all of those changes are undo-able.
I know personally that every device I root, I look at the tool or method to see how difficult (or possible even) un-rooting is. As long as I now I can put the device n a returnable state for warranty coverage, I am the bravest ROM Flasher in the world! LOL
Because $500-800 is a lot of money to have tied up in a device, one that has had more that a fair amount of issues, incuding issues that require RMA, it is just too risky for the avarage Prime owner to unlock the Bootloader.... MAJOR BUMMER!
A really awesome option would have been, or could be if Asus said: "Unlocked bootloader devices lose warranty, BUT, if you are able to restore the device to factory spec (including re-locking the bootloader, a tool that does not presently exist) we will honor the remaining portion of the warranty"
That would be the ultimate option. The chance of it happening?About as likely as a new update arriving that fixes GPS completely and permanently. Oh well. One can dream, right?
Sigh.
Click to expand...
Click to collapse
Even if you are able to lock i it wont matter. The bootloader unlock tool provided by ASUS reports your serial number when you unlock kinda like a phone home mode. Using this serial hey generate some kinds of unlock code. This is the finding thus so far from the development forum and reviviewing the decompile apk file.
MasterZen88 said:
Even if you are able to lock i it wont matter. The bootloader unlock tool provided by ASUS reports your serial number when you unlock kinda like a phone home mode. Using this serial hey generate some kinds of unlock code. This is the finding thus so far from the development forum and reviviewing the decompile apk file.
Click to expand...
Click to collapse
This. If you relock your bootloader you only limit what you yourself can do with the tablet. The damage has already been done as far as Asus is concerned
if I had 2 primes stuck the serial number of the other prime on mine (unlocked and rooted) then unrooted and flashed back to stock would an RMA work? I don't see why it wouldn't I'm just a little curious?
Sent from my Transformer Prime TF201 using xda premium
I hope dev will find a way to stop the apk to send our information to Asus..
Inviato dal mio Transformer Prime TF201 usando Tapatalk
Voiding the warranty by rooting is nothing new.
It has always been that way since day one.
Only difference is that now ASUS has figured a way to know which units have been unlocked.
I wouldn't be surprised if other companies start doing the same thing.
MasterZen88 said:
Even if you are able to lock i it wont matter. The bootloader unlock tool provided by ASUS reports your serial number when you unlock kinda like a phone home mode. Using this serial hey generate some kinds of unlock code. This is the finding thus so far from the development forum and reviviewing the decompile apk file.
Click to expand...
Click to collapse
Cant you use multiple unlock codes to make your own decrypter, that way asus never knows and you can re-encrypt it if you need to send it in for warranty
Dnakaman said:
Voiding the warranty by rooting is nothing new.
It has always been that way since day one.
official unlocks, not developer made one clicks
I wouldn't be surprised if other companies start doing the same thing.
Click to expand...
Click to collapse
Others companies already do the same thing.
Only difference is that now ASUS has figured a way to know which units have been unlocked. Asus are just the first ones to package it into an easy to use apk. Usually they make it hard so that only people with some adb/dev knowledge can do it. Were talking about
Sent from my Transformer Prime TF201 using xda premium
foxtrot16m said:
Cant you use multiple unlock codes to make your own decrypter, that way asus never knows and you can re-encrypt it if you need to send it in for warranty
Click to expand...
Click to collapse
I am not sure this is feasible, An "un official" unlocker would of course get us half way there. Then we just need a way to properly re-encrypt that mimics the stock 128 bit encryption. It would be risky either way, and as we have seen, people are bricking devices already in the earliest stages of learning what works and what doesn't. I think that I even saw that Diamondback bricked his Prime, because Asus does not give us access to NVFlash ! (Virtuous ROM chef for Prime, our first non-Asus ROM)
So I think we are going to see a slowing of the initial rush out the gate to mod and develop for this.
SmartAs$Phone said:
I am not sure this is feasible, An "un official" unlocker would of course get us half way there. Then we just need a way to properly re-encrypt that mimics the stock 128 bit encryption. It would be risky either way, and as we have seen, people are bricking devices already in the earliest stages of learning what works and what doesn't. I think that I even saw that Diamondback bricked his Prime, because Asus does not give us access to NVFlash ! (Virtuous ROM chef for Prime, our first non-Asus ROM)
So I think we are going to see a slowing of the initial rush out the gate to mod and develop for this.
Click to expand...
Click to collapse
How exactly do they block it? It doesn't exist? There is a software block?
Sent from my Transformer Prime TF201 using xda premium
Whatever the case, atleast asus has allowed us to unlock it with this simple to use apk.
Eitherway, the future for any android device (esp for people on this forum) is to go the custom rom way!
From what i heard, CM9 is already in the works and a beta is soon to follow!
hxxp://androidroot.mobi/2012/02/22/cyanogenmod-9-for-asus-transformer-prime/
Being able to block ASUS from knowing you have unlocked your bootloader using their tool would depend on the following:
Option A: is the package unlocks the bootloader and then sends a beacon home with your device information and ASUS then voids your warranty and blocks OTA. This could be resolved by blocking the call home.
Option B: which is more likely is the tool FIRST sends a call to ASUS with your device info, voids your warranty, and THEN returns the actual unlock code.
Option C: A dev develops a aftermarket unlocking tool.
The only way to beat option B would be to decrypt the encryption and generate your own code by inserting it in a custom installer or modifying the homebeacons dns and making a server to intercept the original message and respond with the correct code etc.
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
From what I understand...
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
zomblitous said:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
Click to expand...
Click to collapse
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
I am sure that there is a way to restore through QPST:
http://forum.xda-developers.com/showthread.php?p=49862146
but I lack the skills to complete this process
Thanks
Thanks for the speedey responses guys, I'll try the QTSP method when I have time, but still thanks. Any other help is good to.
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Really!?!?
squee9 said:
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Click to expand...
Click to collapse
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
zomblitous said:
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
Click to expand...
Click to collapse
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Fastboot & the system
lawnnewm said:
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
Click to expand...
Click to collapse
Well I did the advanced system wipe, I think I may have just wiped off all traces of a rom by formatting the system, I havent touched the build.prop or any file like that, only format. Also I'll grab a fastboot cable off ebay and give tinkering a try,
Thanks
zXiC said:
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Click to expand...
Click to collapse
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
GSLEON3 said:
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
Click to expand...
Click to collapse
Thanks for the pep-talk, I haven't even thought about giving up, and I don't really want to just get out the easy lying way. But sadly my problem is one of few and will take time even with the help of power techies. I really only have one option at the moment and that is to continue troubleshooting and ignore everyone who just says that i have acquired a taste in paperweights. And Thanks anyway, means alot when a member takes time just to cheer ya on.
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
1 year then...
zXiC said:
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
Click to expand...
Click to collapse
Well I have about a year then.
Today I went to update my rooted/bootstrapped HDX to [ROM] [4.4.4] [STABLE] HDX Nexus v4.0.5, it was currently running an older version of an HDX Nexus ROM, no problems. Not sure exactly where I went wrong, but, this thing is in a nasty boot loop now. Before I'd had the chance to read not to, I attempted the "Reset to Factory Defaults" at the Kindle Fire System Recovery prompt. So...still looping.
Here's the deal, I am on Mac OS X, am capable of getting into terminal, and poking around. It's all a bit foreign to me, tho. I was raised a PC guy. I just downloaded Android Studio, in anticipation that this will contain the tools I need to roll this back. I am hoping I can get some folks who wouldn't mind helping to walk me through this deal. I have been Googling a bunch, have been having a heck of a time finding tutorials with information that pertains to fixing things in a Mac environment.
Any consideration anyone with more experience and wisdom can afford me would be very much appreciated.
zerawkid said:
Today I went to update my rooted/bootstrapped HDX to [ROM] [4.4.4] [STABLE] HDX Nexus v4.0.5, it was currently running an older version of an HDX Nexus ROM, no problems. Not sure exactly where I went wrong, but, this thing is in a nasty boot loop now. Before I'd had the chance to read not to, I attempted the "Reset to Factory Defaults" at the Kindle Fire System Recovery prompt. So...still looping.
Here's the deal, I am on Mac OS X, am capable of getting into terminal, and poking around. It's all a bit foreign to me, tho. I was raised a PC guy. I just downloaded Android Studio, in anticipation that this will contain the tools I need to roll this back. I am hoping I can get some folks who wouldn't mind helping to walk me through this deal. I have been Googling a bunch, have been having a heck of a time finding tutorials with information that pertains to fixing things in a Mac environment.
Any consideration anyone with more experience and wisdom can afford me would be very much appreciated.
Click to expand...
Click to collapse
Were you previously running Safestrap v3 and Nexus v2.0.5? If so what steps had you taken prior to the factory reset? Finally, is the device stuck at grey Kindle Fire logo or looping in some other way. Responses will determine if your HDX is recoverable.
(assuming you did not have 'native' twrp or unlocked bootloader).
Davey126 said:
Were you previously running Safestrap v3 and Nexus v2.0.5? If so what steps had you taken prior to the factory reset? Finally, is the device stuck at grey Kindle Fire logo or looping in some other way. Responses will determine if your HDX is recoverable.
(assuming you did not have 'native' twrp or unlocked bootloader).
Click to expand...
Click to collapse
Because I only tinkered with it once, to get it bootstrapped and to flash the Nexus ROM + GApps on the device, I am going to go ahead and admit I don't remember precisely the versions of the strap and ROM. I do know that I used KFHDX+ToolKit+v0.95. Hopefully that narrows things down enough.
The device is looping with the grey Kindle Fire logo on screen approximately one minute, then cycles. Volume down+power can get me to the Kindle Fire System Recovery screen.
Thanks for the response.
zerawkid said:
Because I only tinkered with it once, to get it bootstrapped and to flash the Nexus ROM + GApps on the device, I am going to go ahead and admit I don't remember precisely the versions of the strap and ROM. I do know that I used KFHDX+ToolKit+v0.95. Hopefully that narrows things down enough.
The device is looping with the grey Kindle Fire logo on screen approximately one minute, then cycles. Volume down+power can get me to the Kindle Fire System Recovery screen.
Thanks for the response.
Click to expand...
Click to collapse
Unfortunately, your device is likely bricked. A factory reset with Safestrap installed is typically fatal. Even if you are able to secure adb access not much can be done with a locked bootloader. That's true for any device but Kindles (especially HDX models) present an additional challenge due to aggressive lockdown steps taken by Amazon. Typical recovery techniques simply don't work as the fastboot environment is severely crippled. 'Factory cables' are also useless the device lacks hardware support.
Feel free to share further detail regarding actions taken just prior to performing a factory reset (unless that was your first step). Unlikely there will be a resolution but can't hurt as, regrettably, you now own a paper weight.
Davey126 said:
Unfortunately, your device is likely bricked. A factory reset with Safestrap installed is typically fatal. Even if you are able to secure adb access not much can be done with a locked bootloader. That's true for any device but Kindles (especially HDX models) present an additional challenge due to aggressive lockdown steps taken by Amazon. Typical recovery techniques simply don't work as the fastboot environment is severely crippled. 'Factory cables' are also useless the device lacks hardware support.
Feel free to share further detail regarding actions taken just prior to performing a factory reset (unless that was your first step). Unlikely there will be a resolution but can't hurt as, regrettably, you now own a paper weight.
Click to expand...
Click to collapse
This was my fear. Unfortunately, this is a lesson learned the hard way.
Not that anyone here need to weigh in on this idea, but I have read where more than a few people have been able to simply report the locked condition of the device to Amazon and have a replacement device sent out, without much issue. I know its not exactly ethical, based on the terms of warranty, but then, I don't really agree with manufacturers telling consumers they cannot effect changes to the environment of their personal computing devices to begin with. I mean, it's not like I don't do plenty of business with Amazon.
zerawkid said:
This was my fear. Unfortunately, this is a lesson learned the hard way.
Not that anyone here need to weigh in on this idea, but I have read where more than a few people have been able to simply report the locked condition of the device to Amazon and have a replacement device sent out, without much issue. I know its not exactly ethical, based on the terms of warranty, but then, I don't really agree with manufacturers telling consumers they cannot effect changes to the environment of their personal computing devices to begin with. I mean, it's not like I don't do plenty of business with Amazon.
Click to expand...
Click to collapse
If the device is under warranty (typically 12 months) and physically undamaged Amazon will typically off a one-time exchange for a refurbished unit. Simply state it locked up following a factory reset which is technically correct; no need to go into further detail. Suggest reaching out via phone/chat/email to determine eligibility.
Davey126 said:
If the device is under warranty (typically 12 months) and physically undamaged Amazon will typically off a one-time exchange for a refurbished unit. Simply state it locked up following a factory reset which is technically correct; no need to go into further detail. Suggest reaching out via phone/chat/email to determine eligibility.
Click to expand...
Click to collapse
Just got done with Amazon. Everything's all good.
Thanks for your time, Davey.
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
notstevek said:
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
Click to expand...
Click to collapse
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
notstevek said:
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
Click to expand...
Click to collapse
Sorry I don't have the URL handy but it's in here just search in the 6p forums and you should easily find it as there has been a lot of chatter about it
Sent from my Nexus 6P using Tapatalk
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
ksaves2 said:
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
Click to expand...
Click to collapse
Hi Kurt,
Wow, first off thanks for the indepth response. My Nexus 5x was unlocked, rooted with Magisk, allowed unlocking, usb debugging etc. Still can't fix it. I put it in the freezer and got it to boot into TWRP for 30 seconds before it boot looped. Bootloader always works, and can flash, but cannot boot into the rom or recovery. Anyway, I bought this 6P (128gb for $170, perfect condition with a Spigen case and glass screen protector.) because the Nexus 5x is dead, but wasn't aware this also has the same issue which sucks. I run Debian 32bit on my laptop, and it's a breeze compared to windows. Just had to grab the binaries for adb and fastboot, unlike windows where you gotta install crazy large sdk packs, make sure you got the correct drivers, etc. I unlocked the 6P, oem unlocking & usb debugging is checked on developer options. I flashed TWRP, and I'm on 8.1 OPM3.171019.014 (Feb 5th) because the newest one (8.1.0 OPM5.171019.015) won't pick up my Verizon simcard. I flashed Elemental X so I can underclock it, I'm running 4 cores at 1,200mhz and it still runs flawlessly. Any reason I should be using the LineageOS 15.1 kernel? I don't ever plan on using LineageOS or a custom rom. Just stock rooted for me. The battery life is kind of poor compared to the Nexus 5x. I'm a little confused, what do you mean by "Battery swaps are a bear"? If it's worth it, maybe I will put in a new battery. Lithiums life are extended if you don't charge 100% and don't let it die. If you keep it above 20% and charge to 90% max, you'll extend the lifespan by a lot. Some phone companies like Samsung already do this. Your 100% charge is actually only 95% or so in reality. Other things like Telsa cars also do this. I wouldn't have upgraded for a few years if my Nexus 5x didn't die, and honestly if I wasn't afraid of another bootloop, I would have gotten another, I loved that phone. The pixel 2 is great, my brother has one, but I'm not spending more than 250 on a phone ever again in my life, and 250 being the absolute max. I also don't want to sign a contract and do a device payment, I want to own it in full. I will upgrade to the pixel 1 XL when this phone requires me to do so, and hopefully that's at least 2 years from now. Thanks in advance!
Cheers.
Tore open the 128gb "bootloop" special using the variety of videos out there. Heated the CPU's directly although the battery
was I believe fully charged. No dice of breaking the bootloop to have it boot to a "clean" system and unlock the bootloader.
There were no anti tamper seals on this thing so I thing someone threw it out there for $94.00 and I stupidly bit. I caution
folks that unless one can buy a "bootloop" special for less than $20.00 and they have a "good" 6P they want to replace a battery on, don't buy a bootloop special unless it is dirt cheap. Use it to practice on for battery replacement before using
it on a "good" 6p.
I heated the CPU, case off while in a bootloop and no magic restoration was seen. The battery was from October 2015.
I dinged the edges of the glass but got the back half off pretty decently. If the thing booted up and I were able to restore it, I would have been happy with it as the dings aren't really noticeable.. I need to get some guitar opening picks without a lip on them as they are better to work with.
Last ditch attempt will be to drain it down to el "zippo" percent left, put it on a charger and see if I can make the $94.00 evaporate under the auspices of a 1000 watt heat gun with the back case off. Again, don't buy a "bootloop" special of a 6p unless it's dirt cheap. Kurt