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..
I just bought this phone about 2wo weeks ago, & it's actually not a bad for a Tracfone. It runs on version 5.1.1. But forget specs lol. It's currently not activated, & I'm not so sure if that matters when it comes to the actual process of Rooting. I downloaded KingRoot, but I seen that before Rooting I would have to unlock the bootloader. So I followed the procedures only to stumble upon something wasn't right.. I couldn't put my phone in either fastboot, download, or recovery mode.. No matter what I did. I've tried every guide & forum, but nothing. I finally called my service provider to see if they could figure out what the problem was. They came to tell me that I wasn't going to be able to access those features until I activate the phone. (which sounds really suspicious & stupid) I noticed I can access safe mode. What sounds more suspect is that I have to pay for a plan just to activate it, which I never had to do with a phone before. Nevertheless, to sum it all up.. Is there an actual way around this craziness? I never had to go thru this much to root a phone. I honestly feel like there is no point of having an android without unleashing it's true potential. Please, any help would be great. :fingers-crossed:
I have the same phone and the same problem. Still have yet to find a way. anybody?
Looks as though Straight Talk (ST) sets it up that way. I have had other straight talk phones and have always had issues rooting their phones. In fact I have never been able to root their phones. Please someone, show us a work around solution these ST phones.
Same on net 10. Think its an lg thang...
activated my phone and have same prob...help
Funny how I have a LG Optimus Fuel that has really crappy specs and can root easily with android kitkat but this phone is lollipop and better specs and newer can't root at all. I think it is more bootloader locked and only ones that are not locked are mediocre to expensive phones from the manufacturer now. My Optimus Fuel is a Tracfone too, just like the Rebel. I doubt anyone is interested in getting this one rooted. I would not mind because when I rooted my Optimus Fuel it let me put my Micro SD Card into exfat instead of fat32, which exfat sound quality is better and boosted volume a couple db. Only thing with Optimus one is that 512mb makes the music randomly skip. So that is one reason to get the Rebel rooted but we are SOL with this device.
Straight Talk is newer than Tracfone, because Tracfone created Straight Talk. Not the other way around. Tracfone has been around the longest.
TrillzUpTheBlock said:
I just bought this phone about 2wo weeks ago, & it's actually not a bad for a Tracfone. It runs on version 5.1.1. But forget specs lol. It's currently not activated, & I'm not so sure if that matters when it comes to the actual process of Rooting. I downloaded KingRoot, but I seen that before Rooting I would have to unlock the bootloader. So I followed the procedures only to stumble upon something wasn't right.. I couldn't put my phone in either fastboot, download, or recovery mode.. No matter what I did. I've tried every guide & forum, but nothing. I finally called my service provider to see if they could figure out what the problem was. They came to tell me that I wasn't going to be able to access those features until I activate the phone. (which sounds really suspicious & stupid) I noticed I can access safe mode. What sounds more suspect is that I have to pay for a plan just to activate it, which I never had to do with a phone before. Nevertheless, to sum it all up.. Is there an actual way around this craziness? I never had to go thru this much to root a phone. I honestly feel like there is no point of having an android without unleashing it's true potential. Please, any help would be great. :fingers-crossed:
Click to expand...
Click to collapse
Have you tried shutting the phone off, and pressing the buttons after connecting to pc. I don't remember the exact buttons you press. I have worked on a few lg phones before and that was the only way i was able to obtain the mode i needed.
Cannot Root my LG Rebel LTE (L44VL)
I am also having problems trying to Root my my LG Rebel LTE (L44VL) too. My Backup&Restore program of choice is Titanium, but it requires that my system needs to be "Rooted" first. I couldn't find any settings to do this (even when I enter 'Developer Mode'). I've even tried several popular Rooting app tools, including RootKing and Kingo Root (Mobile Version), but they all were not able to Root my system. Please help me with this problem...thank you very much.
At the moment I really only need to backup the critical *system* files, any recommendations?
Looks like this phone is never going to get the root attention it needs. It been out about a year now since release and nothing at all. No one cares about this phone.
Have any of you tried going into developer options and turning on the oem unlock option before trying to get into download mode or anything? Just a thought guys...
As for the optimus fuel,install towelroot. open it, tap the title/symbol 3x, change the 2nd from last digit to "zero". Tap "make it rain". Should root it in literally like 3secs...
---------- Post added at 11:46 AM ---------- Previous post was at 11:43 AM ----------
Worx exactly the same for the lg l41c ultimate 2...
so anybody with this device is jst boned or what?
Is this place dead
Skunkser said:
Is this place dead
Click to expand...
Click to collapse
No this phone sucks without root though lol.
I've been fiddling with this phone for months, the farthest I've managed to get was a temp root, which is undone when the phone is reset. My theory is that it's possible, if done within the timeframe before the phone resets itself, whether that means pushing files through adb or shell, or flashing a custom Rom. My phone has been through a number of battles, and has seen more bricks than a brick wall..but, I'm still at it.
BlindReaperz0rz said:
I've been fiddling with this phone for months, the farthest I've managed to get was a temp root, which is undone when the phone is reset. My theory is that it's possible, if done within the timeframe before the phone resets itself, whether that means pushing files through adb or shell, or flashing a custom Rom. My phone has been through a number of battles, and has seen more bricks than a brick wall..but, I'm still at it.
Click to expand...
Click to collapse
Care to Share what You did to get temp root ? that may be enough to dump a partition...
Astr4y4L said:
Care to Share what You did to get temp root ? that may be enough to dump a partition...
Click to expand...
Click to collapse
This phone is the same as the Optimus Zone 3, or the LG Leon, or the LG K4, however the Optimus Zone 3 seems to be its direct ancestor.
I have successfully temp rooted with kingroot 5.2.2 and oem unlock, problem is a random crash/reboot soon follows which of course flushes all the root.
We worked on this phone and the zone 3 a few years back. Never had any luck with this handset. It's another cheap undesirable that will most likely not see any development for itself any time soon.
_360Root 8.1.1.3
_In Chinese but worked on first try
_360_Root_v8.1.1.3.apk - Android Data Host
My wife Karen gets credit for this find.
360_Root_v8.1.1.3.apk - Android Data Host
You are about to download the 360_Root_v8.1.1.3.apk file on your computer. The file comes as an apk application and the file size is approximately 8.14 MB only. ADH Editorial Staff uploaded this file from Spain on 18/07/2018. The registered Editorial Staff uploaded this file under the Public...
androiddatahost.com
I cannot even find any information on this device let alone a root method. Apparently from my searches methods for the zenphone may work but im not sure if I want to risk bricking this device, but verizon would just replace it anyway. I guess its fairly new? It came with MM and already has an OTA which i keep putting off while I am going to try out various methods to get this one rooted and unleashed since one verizon store essentially scammed me over my new s7 edge so another store refunded everything for me. Now I got this 4g tablet I want to fasten in my car and it would be nice to root or unlock and put some custom vehicle firmware on it or something like that.
I have the same issue with my new Zenpad 3 8.0 . KingRoot and some other rooting apps didn't work for me.
At least someone finally replies.... I am still stuck trying to root this thing. I've tried nearly everything to no success. Even the temporary cwm wouldn't work for me
Same here buddy. Why did ASUS remove such features as App to SD and multi user support?
Anyone found anything? I have the tablet too...
Well damn this sux, Verizon stuck me with another unrootable device, at least I can say I got my pixel in time to unlock the bootloader and route it but not much activity for it since decided to lock them down. I thought I learned with my G4 that's why I got the pixel got home just to find out they're going to be locked down too lol Oh God how I loath Verizon
dadrumgod said:
Well damn this sux, Verizon stuck me with another unrootable device, at least I can say I got my pixel in time to unlock the bootloader and route it but not much activity for it since decided to lock them down. I thought I learned with my G4 that's why I got the pixel got home just to find out they're going to be locked down too lol Oh God how I loath Verizon
Click to expand...
Click to collapse
I hear ya. I have this tablet too: Asus Verizon Zenpad Z8 ZT581KL with V.3.4.23. Despite my best efforts, the damn system update notification keeps coming up telling me to update to Android 7--which I DO NOT want to do since doing that very well could kill any small hope I have on rooting the device. Since this is a Verizon branded tablet, they made an agreement with Asus to lock it down like Gitmo, so any official bootloader unlocker will not work with Verizon. Maybe one day when Verizon get's their head out of their ass and understands that people have the right to screw with their phones, they will allow unlocking options--though I doubt it.
This would be a great little tablet, if Verizon gave us more control over it--Jesus Christ, you're still getting $$ from me on your non-unlimited data. Bunch of ****-tards---I used to work for them back in the day at one of their corporate locations in Folsom, CA. Sadly, I think it's that prison mentality (Folsom Prison) that must have been carried in the air a few miles to the Verizon offices there. That was WDTS (Wireless Data Tech Support)....I was there right when EVDO just came out/expanding (Before Iphones...closest thing would have been a BES-Enabled Blackberry, or a fancy PDA)--oh those were the days...
There are rooting options available if you understand Chinese--but even its for older software versions 3.3.x, etc, and from what I can understand, the flash might actually take (hackers take note: if the flash can take..maybe we can piece together a flash with proper rooted versions)...but since this is a Sim/LTE tablet by doing that it will screw up the radio (Cellular) and recovery partitions. But maybe something round-about could be done that does that, then reflashes modified signed firmware to root it--I dunno.
My google-fu is pretty good and I came across some cached, or snippet that said SRSroot might root 6.0.1 on the ZT581KL, but not sure now legit it is.
Unless more people get this tablet/devs play with it, I don't think we will get root/bootloader/recovery anytime soon. I wish I lived in a country that allowed multiple wifes, because I would do a bounty for root on this devices and give away one of my wives for payment.
I used the tablet mostly for navigation, but I want root/twrp for backup purposes, if I need to wipe the device crossing the border since police now wanting to look at peoples phones/tablets. I love using Waze since I'll be driving down the road with a FAT blunt smoking away, so it's good to know if cops are around.
Zenpad z8 running on Fi
I also have this pad. I bought it from Verizon because it's USB-C and I loathe micro USB and even more so because the helpful sales guy at Verizon let me try my Google Fi data only sim...and sure enough it works awesome after setting h2g2 as the apn. Would love to root it though I hate how I can only have one user account on this for now.
Kind of off-topic, but I can't find any clear answer to my question about the Z8 and Z8s. I'm considering buying one, but I do not want a data-plan. Do these tablets work without a SIM in them, or will I be stuck at a home screen that says "Insert SIM..."?
_HighVoltage_ said:
Kind of off-topic, but I can't find any clear answer to my question about the Z8 and Z8s. I'm considering buying one, but I do not want a data-plan. Do these tablets work without a SIM in them, or will I be stuck at a home screen that says "Insert SIM..."?
Click to expand...
Click to collapse
Of course you can use it without a SIM.
I just ordered this tablet. I'm sad I can't root it, but I mainly use root for adblocking. I will have to use DNS66 or BlockThis instead.
This method doesn't work?
https://neopodapsi.com/how-to-root-asus-zenpad-z8/
replica9000 said:
This method doesn't work?
Nope, just a scam to fill out never ending surveys
Click to expand...
Click to collapse
Zenpad P008 Verizon root - no luck
I just tried One Click Root and that didn't work either. Upon chatting with support they were stymied by the lack of an 'OEM Override' debug mode setting.
Can anybody help, I'm new at this stuff. Plus I'm teaching myself. I've rooted some devices. Did some firmware jobs, kinda' familiar with Odin. But I've tried everything from KingRoot PC to adb tryna' root this thing (P008). Between this thing and that Knox MDM shizzle. Man!, Anybody got anything on these topics......
Anyone try Magisk?? I also want to root this thing. Cannot get a usb gaming controller to recognize either.
Greetings devs, advanced users, enthusiasts.
I purchased this LG Fiesta LTE Model number LG L64VL, a StraightTalk device on Verizon's (Yay) network. I'm convinced that in a former life, my name actually was Murphy S. Lá. because this is my fourth impossible-to-root device in a row. After 5 or so months of study on rooting, APK, ADB, sideloading, TWRP, the ever important custom recovery, the almighty ROM. As with all other attempts, no cwm, TWRP, LineageOS. Not a single one-click-root has worked, either.
Any review of the LG X POWER 2 will read like the box my Fiesta LTE came in, but there is very little information about this model available on any given website, even LG.com. So, the question has the parts : Are they in fact the same model, is there a known ROOT solution, and can a custom recovery be interchanged?
*EDIT*... 19 minutes later...
You see about Murphy's Law? I spent an hour trying not to sound like I'm describing the perpetual nuclear holocaust of the sun with the words, "It go boom." (D. K.©), and the VERY NEXT PAGE I STUMBLE on to, is the FCC IDs for not 1 or 2 devices, but 3!
So, 1/3 of the question answered. The LG Fiesta LTE and the LG X POWER 2 are, according to the FCC, the same device.
He
I'm seeking the answer to this too. My mother bought this phone on sale (~$60 at walmart) and loves it. Problem is, it has lockscreen ads and random popup ads every so often of using the phone. I've done everything within my knowledge base to help remove those, but without root I cannot disable/uninstall certain system/embedded apps. (Unless someone can tell me how).
The LG Fiesta LTE (otherwise known as the lgl64vl) is a very nice device, but we need a root for it. Does anyone know how to test the theory above, that the Fiesta is the same as the X Power, and if so, how to make that root work on this device? Any help would be greatly appreciated!
Well, I too, bought this phone last night as a $99 emergency replacement for my Nexus 6 and I must say I was pleasantly surprised and impressed with it. So of course the next step was to check for a root method which brought me here with you guys. I'll keep looking around and check back with y'all later
Cinephile 74 said:
Greetings devs, advanced users, enthusiasts.
I purchased this LG Fiesta LTE Model number LG L64VL, a StraightTalk device on Verizon's (Yay) network. I'm convinced that in a former life, my name actually was Murphy S. Lá. because this is my fourth impossible-to-root device in a row. After 5 or so months of study on rooting, APK, ADB, sideloading, TWRP, the ever important custom recovery, the almighty ROM. As with all other attempts, no cwm, TWRP, LineageOS. Not a single one-click-root has worked, either.
Any review of the LG X POWER 2 will read like the box my Fiesta LTE came in, but there is very little information about this model available on any given website, even LG.com. So, the question has the parts : Are they in fact the same model, is there a known ROOT solution, and can a custom recovery be interchanged?
*EDIT*... 19 minutes later...
You see about Murphy's Law? I spent an hour trying not to sound like I'm describing the perpetual nuclear holocaust of the sun with the words, "It go boom." (D. K.©), and the VERY NEXT PAGE I STUMBLE on to, is the FCC IDs for not 1 or 2 devices, but 3!
So, 1/3 of the question answered. The LG Fiesta LTE and the LG X POWER 2 are, according to the FCC, the same device.
Click to expand...
Click to collapse
The first step is going to be unlocking the bootloader. The LG website actually had a bootloader unlocking tool very much like HTC. I don't have a PC atm or I'd try it myself. I did go through the account setup and got an LG account.
Perhaps unlocking the bootloader would make one of the other root methods work.
---------- Post added at 01:44 AM ---------- Previous post was at 01:42 AM ----------
protechtedd said:
I'm seeking the answer to this too. My mother bought this phone on sale (~$60 at walmart) and loves it. Problem is, it has lockscreen ads and random popup ads every so often of using the phone. I've done everything within my knowledge base to help remove those, but without root I cannot disable/uninstall certain system/embedded apps. (Unless someone can tell me how).
The LG Fiesta LTE (otherwise known as the lgl64vl) is a very nice device, but we need a root for it. Does anyone know how to test the theory above, that the Fiesta is the same as the X Power, and if so, how to make that root work on this device? Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe if you unlock the bootloader first...? I don't have a PC or I'd try it myself.
Any progress on the LG l164v1 Fiesta 2 LTE ? I have not had any success. But love the phone
Lg Fiesta 2 (l164vl)
Freybergers said:
Any progress on the LG l164v1 Fiesta 2 LTE ? I have not had any success. But love the phone
Click to expand...
Click to collapse
Hello All,
I haven't had any progress with rooting this phone, nor finding anyone else that has in my many hours of searching. Also believe that lg, straight talk, tracfone, one of em, has purposely locked out or simply not included a bootloader with these phone, or mine at least. Checking the build info, I've discovered that ro.boot.recovery=false and bootloader info is unknown. I haven't been able to load into anything other than a factory reset screen with the option to cancel or reset. All other, hard button (can't think of name atm sorry), and adb commands all just reset phone. Does this phone actually not have a bootloader or a recovery? Can they do that? Like is it just that they haven't provided a /recovery partition or just locked it out from users? If I could change to.boot.recovery=false to =true, if I can even do so without adb root access that is, would it make a difference? Maybe inshoukdve put this on a new thread lol. Have many questions but hopefully someone out there is working on this as well and could give some insight as to what is actually going on? I 'll be keeping an eye on this and possibly make a new thread to combat this issue/these issues. Put together some great minds and we can accomplish root on this great device!! (Minus this huge fault it surely has).
I went to the LG Dev site signed up. But couldn't find anything on the unlocking of the bootloader for LG l164vl LG Fiesta 2 LTE. Lots of info on how to, and warning about using the worng one killing the phone. Has anyone been successful unlocking bootloader with the LG website tools? If yes what model did you use?
Hey guys, So i got a t-mobile revvl due to an emergency, it has a mtk6738 chip and im trying to root it... can anyone point me to the right place? ive searched and searched but i cant seem to find anything for this chipset on for the MTK65XX.
thanks in advance!
No luck :/
Daisuke1988 said:
Hey guys, So i got a t-mobile revvl due to an emergency, it has a mtk6738 chip and im trying to root it... can anyone point me to the right place? ive searched and searched but i cant seem to find anything for this chipset on for the MTK65XX.
thanks in advance!
Click to expand...
Click to collapse
Phone came out around 2 months ago, same phone and same problem. Sorry to inform Root/TWRP won't be available for a while on the phone since it's so new no developer has gotten their hands on it to start developing for it. I predict it'll be faster than most new phones because it's exclusive to T-Mobile. It would take much longer if the phone had different variants because of the different carriers, but that's not the case with the revvl so what's left to do is to wait and hope ::fingers-crossed:
Anyone has the stock rom for this device?
it is like this phone doesnt exist. cant find anything. Got this phone in america and it seems impossible to unlock in mexico. do you guys think if a root will be available it will be unlocked for use in mexico? thanks!
I may be able to help with root. I don't have the phone, but if someone is willing to potentially risk their device for the sake of science, let me know.
If this goes the way I think/hope it does (since its a MediaTek), we may be able to get root and recovery in a VERY short time for this. If not, then unfortunately you're out of luck for now. But, if one of you is willing to risk it and try, I'll be more than happy to help you out.
For now though, nobody update their firmware AT ALL. They may release a patch in the future that blocks what I want to do.
UPDATE: I got to play with one at a T-Mobile store. CPU Z says this has a 6755 board, which is commonly available through other phones that have been modified. I'm really getting excited about this... If this goes the way I hope it does, you could be having TWRP and root REALLY soon.
i will be back in germany at on dec.21,if german t-mobile can't unlock it for use in germany I am willing to do anything with it for science..since I will throw this useless piece of technology at the wall anyway
luroxx said:
i will be back in germany at on dec.21,if german t-mobile can't unlock it for use in germany I am willing to do anything with it for science..since I will throw this useless piece of technology at the wall anyway
Click to expand...
Click to collapse
Let me know as soon as you have access to a PC with Windows or Linux, which I'm guessing is when you get back to Germany. For now, make sure you DO NOT TAKE ANY SOFTWARE UPDATES AT ALL. You can update apps from the Play Store still, but keep away from all system updates at all costs.
Send me a PM for how I can reach you, when you're ready to work with me. The procedure I'm thinking of will not unlock your phone in terms of network (like using it on other carriers), but if it works you will definitely have TWRP and root access, and MAYBE even a bootloader unlock (for installing custom ROMs).
But in the meantime, I can't stress this enough, AVOID ALL SYSTEM UPDATES. This goes for anyone who may want to root their phone using this method, if this works.
I just bought one to use on a spare phone line - Cyber Monday sale for $48! I'm happy to experiment when it arrives. Maybe the sale price will entice some other developers...
jasonmerc said:
Let me know as soon as you have access to a PC with Windows or Linux, which I'm guessing is when you get back to Germany. For now, make sure you DO NOT TAKE ANY SOFTWARE UPDATES AT ALL. You can update apps from the Play Store still, but keep away from all system updates at all costs.
Send me a PM for how I can reach you, when you're ready to work with me. The procedure I'm thinking of will not unlock your phone in terms of network (like using it on other carriers), but if it works you will definitely have TWRP and root access, and MAYBE even a bootloader unlock (for installing custom ROMs).
But in the meantime, I can't stress this enough, AVOID ALL SYSTEM UPDATES. This goes for anyone who may want to root their phone using this method, if this works.
Click to expand...
Click to collapse
alkoholic said:
I just bought one to use on a spare phone line - Cyber Monday sale for $48! I'm happy to experiment when it arrives. Maybe the sale price will entice some other developers...
Click to expand...
Click to collapse
$48?????? THEY WERE $179 WHERE I WAS!!!!!
For that price I would've bought one myself... But yes, that would be great if you could work with me when it arrives!
I would be willing to help as much as possible with root access as well. If you need any sort of system dump or something let me know I am very much willing to help!
rsuthers08 said:
I would be willing to help as much as possible with root access as well. If you need any sort of system dump or something let me know I am very much willing to help!
Click to expand...
Click to collapse
PM me where I can contact you (hangouts, telegram, etc.)
[REMOVED BY ME]
Overall, it doesn't look like we have any of the obstructions I was afraid we were going to have so far. We need to work on a few things before we can get the whole thing done, but as of now, this hack looks like it will be 100% possible to do
UPDATE: We're running into some trouble again. Stuff I may not be able to bypass. I'm not sure if this will be 100% possible now...
Picked up two of these for $48 each on the T-Mobile Cyber Monday deal and got them to waive the shipping, set one up for my Mom and it's a pretty nice phone. I still have the other one sealed in the box, debating whether to keep it or sell it. Root and TWRP would be awesome, hopefully it comes soon.
Zephead said:
Picked up two of these for $48 each on the T-Mobile Cyber Monday deal and got them to waive the shipping, set one up for my Mom and it's a pretty nice phone. I still have the other one sealed in the box, debating whether to keep it or sell it. Root and TWRP would be awesome, hopefully it comes soon.
Click to expand...
Click to collapse
A device no one has touched could be beneficial, since that means there's no Google Factory Reset Protection on it (no google account associated with it yet). If you want to use your unused device for some of the tests/methods we're working on, let me know.
Another update on our findings: with the help of @lopestom, I've found out that this device looks to be a 1:1 copy of the Alcatel A30 Fierce, and a distant cousin of the A30 Plus that Amazon once sold as a prime subsidized phone. Despite what SPFT and CPU-Z say, this phone should be running an MT6738 chipset, which uses the same partition layout as the MT6735. I have a completed scatter file for the 6735 from my R1HD days, so if this is the case, knowing where the phone's partitions are should be no problem.
[REMOVED BY ME]
jasonmerc said:
Another update on our findings: with the help of @lopestom, I've found out that this device looks to be a 1:1 copy of the Alcatel A30 Fierce, and a distant cousin of the A30 Plus that Amazon once sold as a prime subsidized phone. Despite what SPFT and CPU-Z say, this phone should be running an MT6738 chipset, which uses the same partition layout as the MT6735. I have a completed scatter file for the 6735 from my R1HD days, so if this is the case, knowing where the phone's partitions are should be no problem.
My biggest fear is, again, that SPFT is being blocked in the same way that it now is on the R1HD. Besides that, we found out that Google's FRP may prevent us from accessing the developer menu to enable ADB on the phone. Now, I could've sworn I got into the developer menu in a store demo Revvl by mashing the Build Number entry like I would on any other phone, but for some reason the person I'm working with is unable to get to this menu (mashing Build Number does nothing for him). If another Revvl user is reading this, can you please try to enable the Developer Menu and ADB for me? I want to see if this issue is just for him or if it affects everyone.
EDIT: The error given from SPFT with the Revvl VS with the R1HD are completely different errors, so this gives me hope that we can still use SPFT with the Revvl.
Click to expand...
Click to collapse
Hey my name is Jakob, i also has a T-Mobile revvl (Alcatel 5049w) and yes my developer options have been enabled without any issues and I'm willing to assist in rooting options if I can help
just tried doing a reboot to bootloader with no luck, it reboots, hangs on the power by angroid then fully boots to stock rom.
video attached
https://drive.google.com/open?id=1Pw61qisWQjC9J_Q9jqHNgRG-n7FmIpcq
[removed by me]
Worked on the Revvl Plus with @oasisfleeting tonight. It's a snapdragon 625 based phone, unlike its mediatek based little brother. This phone actually allows us to go into fastboot mode unlike the normal Revvl though. However, with the exception of fastboot devices (just shows what's connected), no commands actually work. They either all return "..." Or show that no device is connected (when it actually is). Even throwing in the device ID: fastboot -i 0x1ebf oem unlock does nothing.
For the mediatek variant, there is still a very small sliver of hope. For the Plus variant, I'm pretty sure you will never get the bootloader unlocked. Root maybe, but that'll be it.
jasonmerc said:
Worked on the Revvl Plus with @oasisfleeting tonight. It's a snapdragon 625 based phone, unlike its mediatek based little brother. This phone actually allows us to go into fastboot mode unlike the normal Revvl though. However, with the exception of fastboot devices (just shows what's connected), no commands actually work. They either all return "..." Or show that no device is connected (when it actually is). Even throwing in the device ID: fastboot -i 0x1ebf oem unlock does nothing.
For the mediatek variant, there is still a very small sliver of hope. For the Plus variant, I'm pretty sure you will never get the bootloader unlocked. Root maybe, but that'll be it.
Click to expand...
Click to collapse
There are other unlocking commands too. Did you try "fastboot flashing unlock" on the plus
I have also seen bootloader mode renamed before. so try "adb reboot fastboot" to get into fastboot.