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..
Just a background:
This is not my device
This is a stock OS/nonrooted device
I have done some development on Android, so am somewhat experienced
I am helping a friend who just wants it to work again
Kindle Fire HDX 7" model # C9R6QM
What's going on:
Device is stuck on light gray "kindle fire" boot logo.
Device is not showing in device manager on Windows 7 PRO
Device is not showing in adb "adb devices command"
Device seems charged, has been left with cord in for longer than several hours
Tried several different cords to rule out faulty equipment
Tried multiple USB ports including 2.0, 3.0, front and rear ports, even a powered USB hub
Tried hard reset multiple times using power button
Tried power and vol up to go into a recovery, nothing happens.
"fastboot devices" command shows only "waiting for devices"
Help! I just need to get this thing up and running again, no matter the cost to data. Only thing I haven't tried is the bootloop utilities yet, as I am on a work pc and do not have access to download them atm. Will try these later if I need to.
Thanks in advance, and ask any questions if you need more info.
-Tripp
UPDATE 1: Upon further playing with device, I have finally gained access to the "Fire System Recovery" page seen here.
Well I guess since I am a new user still I cannot post the photo, but it is kindlefire recover page with a bunch of E: failed and E:cant mount stuff underneath. If I need to spell it all out I will.
Unfortunatly, neither "reboot your kindle" or "reset to factory defaults" does any good for me. Rebooting just causes it to bootlogo screen again, and Reset to FD fails, getting some weird oldschool tv effect on the screen until it reboots again into recovery and gives me the same two options.
ADB, windows, and fastboot still do not detect the device while in recovery.
Any ideas?
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
EncryptedCurse said:
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
Click to expand...
Click to collapse
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
trippvail said:
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
Click to expand...
Click to collapse
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Davey126 said:
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Click to expand...
Click to collapse
Damn was hoping there was a fix. I am sure that adb was never enabled as they are not tech savvy. Nothing shows in device manager when it is plugged in, ever. No changes.
Update 2:
So I popped in my Ubuntu drive and booted up. After installing adb and fastboot just in case, I tried accessing the kindle in both boot logo and recovery modes. No luck.
Ubuntu doesn't even see it there...
I know I'm not going crazy but it seems like I'm missing something somewhere. I have been through multiple brickings of our developer phones and brought them back to life but they always had adb enabled. Seems like there has to be a work around.
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
trippvail said:
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
Click to expand...
Click to collapse
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Davey126 said:
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Click to expand...
Click to collapse
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
trippvail said:
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
Click to expand...
Click to collapse
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Davey126 said:
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Click to expand...
Click to collapse
Ya I can understand that. I'm actually using an iPhone right now, jailbroken of course lol. But I understand why Amazon did it. Too bad a tablet has to die because of it though. I love the open Android systems but I like apples hardware better. Haven't found an android phone I like better yet. To each his own, right?
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
draxie said:
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
Click to expand...
Click to collapse
I don't and neither does the owner. I would assume the latest if it auto updates, although that may be what bricked it if it didn't have the power to complete the update. Can't confirm any of that though.
I will try both volume buttons in a bit when I get off work. I did the vol up with power to get into recovery, but that did nothing for me as recovery failed every time and rebooting just takes me back to the gray kf logo.
Ok so I tried the vol up and down while powering it on and it just took me to recovery. Same E:failed to mount and E:can't mount/can't open messages below the recovery options in yellow. So I guess I'm screwed then.
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
draxie said:
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
Click to expand...
Click to collapse
I will be trying your methods draxie when I get home and back with the device today if what I am doing now doesn't work. I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
At this point recovering anything from the device is nothing to me, or the owner, as there was nothing important on it. I was hoping to not take the hardware route, but I have the tools, the time, and the hands to do it if necessary. All I need is the knowledge from someone as to what the hell I'm looking for in there.
Just to confirm, after the gray logo of KindleFire comes up, should I be seeing anything else come up while holding buttons for fastboot? <<Just re-read your post and realized it answered this question>>These things are so much easier to use when rooted and TWRP or CWM recoveries are installed. Android makers all over should take note and use the knowledge of the open source community to improve their own devices.
Below is a photo of the recovery screen I see now that I can finally post photos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
trippvail said:
I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
Click to expand...
Click to collapse
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
draxie said:
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
Click to expand...
Click to collapse
Lol thanks. I am sure it will be dead for awhile before I get home, if it's not dead already. But if for some reason it's still alive I will make sure to let it sit for an extra 30 minutes after it goes down.
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
jwcdis said:
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
Click to expand...
Click to collapse
If the bootloader remains locked with no access via tether (or wireless ADB) you are pretty much done. You can attempt the cold start remedy suggested in earlier posts. Long shot at best. Note the device should sit idle for several days after appearing to be depleted as internal circuitry prevents the battery from going completely dead. Even then some charge will remain which is necessary to respond to the power button and protect the battery from permanent damage. Removable primary and backup batteries are the only surefire way to insure a true cold start.
Aight so I have this Samsung Galaxy J7 Max that I've been trying to unlock for more than 2 years now. I of course, don't want to lose the super important data it holds. It got locked out randomly and hasn't been able to take up the pattern I had put on it till date. I'm absolutely sure no one changed its lock screen pattern and its the phone that is unable to recognize the exact same password it had before this happening. I got hold of it today and yet again, started looking for solutions on YouTube and the internet itself. After all of my research, one thing is clear. There is only one way that the pattern lock can be removed in such a condition; by deleting this system folder called gesture.key that lies within the phone itself. I am by no means a nerdy software dev or something but I do have very little knowledge about these workarounds. I used an ADB via a cmd terminal to contact my phone. But it turns out that due to my usb debugging setting not being turned on in my phone, the adb didn't have the required authorization to make any changes to the target. I then got my phone into stock recovery mode and chose the Install through ADB option there. Now when I input the command adb devices, the prompt showed me my device ID, but instead of the "unauthorized" indicator beside it, it now had the indicator "sideload". I had no idea of what had to be done when such happens, so I tried the adb shell > cd data/system > su > rm *.key [taken from an XDA forums thread] commands again. But right on the second step it displayed error this time. I have tried using a key eraser via sd card too, but it just doesn't happen, the sd card folder in the stock mode does not display the contents of the folder.
Now the phone isn't being an obstacle in my life right now, but I really hope there's a way to fix it. Early help would be appreciated. Thank You.
If the data is super important why isn't it redundantly backed up?
Having a set lock screen and storing data on the OS is a sure fire way to lose data, eventually.
Maybe you'll get lucky... is that drive encrypted?
If not it may still be corrupted and unusable.
Don't put yourself in this position again... been there, done that
@blackhawk As I said, this was an absolutely random incident, had never even thought this could've been the case someday. Its not like the phone crashed and then this happened, I turned off my phone's display and the next time I woke it up, the pattern wasn't working anymore. Furthermore, the timed attempts that happen after 5 incorrect tries wasn't existing anymore. Now it could be that someone did get the timed attempts wrong as well [it isn't my own phone]. But I really don't see any other reason to that occurrence.
About the backups, I mean cmon, I was 15 back then, a medico student even more so. I never got my hands around backing up anything. But yes, have been backing up every single bit of data within these two years.
The storage drive shouldn't be encrypted. It was a regular phone bought online that had pdfs, images, recordings and videos stored. The google account was not that of the owner either! It was my uncle's account that was being used ever since he bought it. And since there was never a problem having used his account for quite a while, we never cared to change it to a new google account. Now my uncle's google account itself handles another device, his own phone, exact same model, Galaxy J7 Max. I have tried using his account at the Google Find My Device app to locate and unlock the phone that way [I hope you know it has the three options Ring, Secure and Erase Data]. But it happens so that the Secure phone with password option only for devices that have been lost and don't have a security lock already setup, which wasn't, unfortunately, my case. So that option was greyed out.
For the data corruption, you might be correct. But that phone still does receive SMS texts, calls, whatsapp texts and other notifications. They just don't show up on the lock screen anymore. I honestly had the "Screw the data, I'll erase it anyway" thought yesterday, but during my latest tries, I found the XDA forums website to be quite helpful. Had not it been the damn USB debugging, the solution I approached from this forum would've got the job done in a couple minutes. Again, if the data might've gone corrupted, I will erase the data [I mean I would have to]. But this little glimmer of hope that I experienced yesterday is what is preventing me from doing that. I really hope there is a fix to my situation.
@Chinmay47
a phone can get booted into these modes
Normal ( AKA Android OS )
Recovery
Fastboot
Sideload
EDL
Sideload mode is used to flash OTAs and/or ROMs.
Recovery mode allows you to perform some ADB actions as e.g. pull userdata, but this reqires ADB ( read: USB debug ) got enabled.
So my guess is you can't recover phone's userdata at your own, this would have to be done by an external service who can pull out phone's internal SD-card and has the forensic tools to read it.
@jwoegerbauer Surprisingly the idea of taking the phone to a forensic service struck me yesternight too. As you mentioned, since I can't recover the phone's data myself, all tips and tweaks on the web should now be struck off of my list of solutions. I'll leave the data to some forensic services then. Let's hope the recovery is worth the hassle. The thread is still open to more suggestions though. Thanks for the replies everyone. Really appreciate it!
Chinmay47 said:
@jwoegerbauer Surprisingly the idea of taking the phone to a forensic service struck me yesternight too. As you mentioned, since I can't recover the phone's data myself, all tips and tweaks on the web should now be struck off of my list of solutions. I'll leave the data to some forensic services then. Let's hope the recovery is worth the hassle. The thread is still open to more suggestions though. Thanks for the replies everyone. Really appreciate it!
Click to expand...
Click to collapse
It not a card they can pull. More than likely it's on a BGA chipset, the hardest kind there is to work with.
If they can't access the data on/with the mobo they will have to unsolder the chipset without damaging it then put it into a test jig or another mobo (after pulling that mobo's matching chipset).
If they can access the data on the mobo, not so bad. Otherwise not so good.
Let us know how this plays out for you.
Here's one I found showing you this complex procedure: https://flashfixers.com/recover-data-dead-phone-chip-off-data-recovery/
They may be able to help you, but I have no personal knowledge of this company.
blackhawk said:
If they can't access the data on/with the mobo they will have to unsolder the chipset without damaging it then put it into a test jig or another mobo (after pulling that mobo's matching chipset).
Click to expand...
Click to collapse
Actually thought of this idea right after a couple days from the beginning of the problem. Yes its gonna take loads of precision and patience but it does sound doable. Maybe that's what is gonna be the last option for the forensic service too in case, god forbid, they aren't able to do it the "simple" way. Can't say yet, but I'm gonna keep this thread updated with all the developments that take place.
Chinmay47 said:
Actually thought of this idea right after a couple days from the beginning of the problem. Yes its gonna take loads of precision and patience but it does sound doable. Maybe that's what is gonna be the last option for the forensic service too in case, god forbid, they aren't able to do it the "simple" way. Can't say yet, but I'm gonna keep this thread updated with all the developments that take place.
Click to expand...
Click to collapse
If they need to remove the chipset the chances of failure increase. Flash memory retension is generally good for 10+ years but it may be damaged in the removal process if so, snake eyes.
Get price quotes up front for the whole process.
Once they got the phone, they got you by the balls. Not saying they aren't trustworthy but feel them out. If it's a couple hundred and you get the data back, you did good.
No idea of the cost though, my guess is $400-1000+ especially if they need to pull the chipset.
That's high risk even if they do it by the book.
If their policy is no data, no charge... expect higher rates to cover their loses.
@blackhawk All of that sounds kinda terrifying if you ask me. Well I mean, there is always a first option that can be tried without any mentions of pull-aparts. Yet I will surely judge the person well before I hand my device in his hands. I would try my level best to not take it to the critical stage, but if it needs be and there is a really high chance of losing my data, I can factory reset my data at home by myself too can't I? Future shall tell I suppose.
If you factory reset it all data will be lost.
It will not be recoverable!
If you want the data you will need to use a service like I showed you. They will need physical access to the phone to recovery the data.
The phone may be scrape afterwards
@blackhawk Sure does look like it would be! But paying to get your phone reset for you is way to harsher than doing it yourself. It is only in case the data is nearly impossible to recover that I'll reset the phone myself.
Chinmay47 said:
@blackhawk Sure does look like it would be! But paying to get your phone reset for you is way to harsher than doing it yourself. It is only in case the data is nearly impossible to recover that I'll reset the phone myself.
Click to expand...
Click to collapse
Reset? Most likely destroyed.
Do you really want the data?
blackhawk said:
Reset? Most likely destroyed.
Do you really want the data?
Click to expand...
Click to collapse
I actually do though. But well, if it ain't coming back then why wish for it. Yeah the data was really important.
Chinmay47 said:
I actually do though. But well, if it ain't coming back then why wish for it. Yeah the data was really important.
Click to expand...
Click to collapse
Call them up and see what they say.
Since it's not physically damaged they may be able to access it none invasively.
blackhawk said:
Call them up and see what they say.
Since it's not physically damaged they may be able to access it none invasively.
Click to expand...
Click to collapse
I'll do that and report back ASAP. Thanks for the help sire!