So my family is about to switch to AT&T from Boost Mobile. And I think I am getting a Galaxy S3 from them. And I would love to root and install CM in it. But I have been hearing reports of AT&T's locked bootloader policy and such. Should I worry about it for the S3? Or does it still have an unlocked bootloader? If it doesn't, should. I unlock it first, then root? Or root first? Please reply, and if you do, thanks,
Endo
Endofear said:
So my family is about to switch to AT&T from Boost Mobile. And I think I am getting a Galaxy S3 from them. And I would love to root and install CM in it. But I have been hearing reports of AT&T's locked bootloader policy and such. Should I worry about it for the S3? Or does it still have an unlocked bootloader? If it doesn't, should. I unlock it first, then root? Or root first? Please reply, and if you do, thanks,
Endo
Click to expand...
Click to collapse
if your phone firmware is higher then 4.1.2 then
check if your phone is locked or not Dial *#7465625# into your phone, a screen will pop up telling you what is on.
if Network lock is ON that mean your phone is locked and for now there is no way to unlock your phone for free (you have to pay for unlocking)
if your phone firmware version is 4.1.2 or lower then that then
go this link and find how to unlock your phone for free http://forum.xda-developers.com/showthread.php?t=2529200
Endofear said:
...I would love to root and install CM in it. But I have been hearing reports of AT&T's locked bootloader policy and such. Should I worry about it for the S3? Or does it still have an unlocked bootloader? If it doesn't, should. I unlock it first, then root? Or root first?
Endo
Click to expand...
Click to collapse
The bootloader issues should not be insurmountable. Being a new phone I expect it will come with the 4.3 version of Jelly Bean installed. This will be the first thing to check once you have the phone. If it has 4.3, it will have Knox installed and this will need to be turned off to install a custom ROM. All I have seen regarding removing Knox is either after or at the same time you are rooting. To root, the CF-Auto-Root method works for many. Both the CF-Auto-Root and a second method are here This thread also links to a script which will remove Knox, if needed.
You will need to decide which version of CM you wish to install, probably 10.2 or 11. At this time the 4.3 bootloader will work with both. I would recommend reading about all of this, and having a fair understanding, before doing anything to your phone. I won't hurt to run it on stock for a week or two.
Some things to bear in mind: The phone may come with the 4.1.2 version of Jelly Bean, but I doubt it. If it does you will have to update the bootloader before proceeding, more reading because there is an option involved - the official 4.3 bootloader (MJB) or the leaked 4.3 bootloader (MJ2). There is a bit of a chance the phone could come with Android 4.4, KitKat. It all depends on the timing of when you get your phone, when AT&T rolls out the update, and if the store personnel update the phone giving that 4.4 is available. If it does come with 4.4, DO NOT change anything until those on here that do the good things for our phones understand how it behaves.
Remember all of the warnings about anything you do being your responsibility.
Related
Hello,
I haven't been here in so long. After reading through the forum I am a little confused.
I am on stock 4.1.2, rooted, and using CW recovery.
I see all the discussion about not updating to 4.3, but I'm not sure if what I have read is up to date or not.
Is there still a problem updating to 4.3? KNOX?
How should I update to 4.3? Do it need to undo root and go back to stock recovery? I'm not sure how to do this. I have used custom ROMS in the past but it's been too long.
Also, it seems that rooting 4.3 is no problem. Is this true?
Thanks,
rblancrt
rblancrt said:
Hello,
I haven't been here in so long. After reading through the forum I am a little confused.
I am on stock 4.1.2, rooted, and using CW recovery.
I see all the discussion about not updating to 4.3, but I'm not sure if what I have read is up to date or not.
Is there still a problem updating to 4.3? KNOX?
How should I update to 4.3? Do it need to undo root and go back to stock recovery? I'm not sure how to do this. I have used custom ROMS in the past but it's been too long.
Also, it seems that rooting 4.3 is no problem. Is this true?
Thanks,
rblancrt
Click to expand...
Click to collapse
Sure, you can upgrade to 4.3 if you want to
the reason why people said not to upgrade to 4.3 is because a lot of people DO NOT READ and come asking for help this or that after they upgrade
and the main reason why people mention not to upgrade is because you can unlock for free as long as you can downgrade your phone to 4.1.1, mainly the bootloader since 4.3 bootloader comes with KNOX
since you're still on 4.1.2, you can downgrade and unlock your phone for free while you still can before upgrading it to 4.3
so this is what you should do, check, if your phone is fully unlocked, if not, unlock it then upgrade
or if you're rich and you don't care, just upgrade and then if you wish to unlock later, pay for unlock code =D
and rooting shouldn't be any problem regardless of which version of android you're on.
to upgrade, you can just download the stock img and flash it through recovery or just use odin flash it
or if you're prefer the old fashion way, the long way in fact, is to unroot, upgrade through system update
I would say don't upgrade. The new bootloader has a warranty bit (aka the Knox counter) that, once tripped, can't be reset. Ever. By anyone. The ONLY way I would even consider upgrading is if you need Knox security for work (the majority of us don't). I wouldn't even upgrade if I were selling the device. Let the new owner make that decision for themself. But, I would unlock it. Even if you never need it, it may add a few bucks to the selling price of the phone later on.
mrhaley30705 said:
I would say don't upgrade. The new bootloader has a warranty bit (aka the Knox counter) that, once tripped, can't be reset. Ever. By anyone. The ONLY way I would even consider upgrading is if you need Knox security for work (the majority of us don't). I wouldn't even upgrade if I were selling the device. Let the new owner make that decision for themself. But, I would unlock it. Even if you never need it, it may add a few bucks to the selling price of the phone later on.
Click to expand...
Click to collapse
But what exactly is the effect of this Knox counter. If it's only that I can't reflash a stock ROM and send it back to Samsung that time has long passed.
I guess I'm getting bored with my phone, had it almost two years, and thought updating to the latest firmware might help.
What are the repercussions of going to 4.3 or higher?
Thanks again for the great info.
If you are out of warranty, the only drawback, imo, to updating is you cannot downgrade the firmware or modem. You could still flash older roms and kernels, just not the full firmware and not the modem.
Personally, I wouldn't let knox deter me from updating, or recommending it. This is for each person to decide, but I feel the benefits outweigh any drawbacks. knox is easily removed or disabled, and I find the latest builds to be some of the best in terms of performance and battery. (of course there are always some who disagree with that on every update!) of course there are no guarantees, but most seem to be quite happy with both 4.3 and 4.4.2.
As for downgrading.....I have never found a real need for doing so. Some have though, so thats something you need to decide for yourself.
You can try some of the available roms w/o updating the firmware btw. But if you decide you like them, I do suggest going back and fully updating for stability and performance, but thats something for you to decide if you want to go that route.
There will be some who agree and some who do not, so in the end its up to you make an educated decision whether or not you want to.
Hi!
I'm sorry if this has been asked before but I just can't find a definitive answer to this and I've been trying to search for an answer for nearly a week now.
My boss received a used Samsung Galaxy S3 from a friend of his in the states. It is a locked AT&T phone (SGH-I747) and it is on 4.3.
I managed to root the phone using CF-Auto-Root, which disabled Knox (whatever that is) and also installed CWM and was planning to flash 4.1.1 so I can unlock the phone using the *#NUM# method.
After reading a bit I've seen many people saying that you can't "downgrade" from 4.3 to anything else because it will brick your phone. Hence, I did not try and flash any other rom on the phone.
So I guess I'm just trying to get a definitive answer here because I can't find anything but rumors on this subject. I mean it's weird, I'd expect if you couldn't downgrade from 4.3 than it would be a bit more documented.
Has anybody tackled this problem with success?
Thank you
The normal method for the end user to conduct software updates and upgrades is via OTA or Kies. Using Kies or OTA doesn't require the end user to know about download mode, fastboot, or recovery mode. Samsung probably did not want non-technical users to brick their phones using download mode and Odin. It would be too easy for a non-techie to use the wrong firmware, tick the wrong options in Odin, etc.
I'm sure the fact that you cannot downgrade the bootloader has been well document by Samsung and its service centres. Based on the contents of my first paragraph, there would be no need for Samsung to advertise to the end user that the bootloader cannot be downgraded.
rikonor said:
Hi!
I'm sorry if this has been asked before but I just can't find a definitive answer to this and I've been trying to search for an answer for nearly a week now.
My boss received a used Samsung Galaxy S3 from a friend of his in the states. It is a locked AT&T phone (SGH-I747) and it is on 4.3.
I managed to root the phone using CF-Auto-Root, which disabled Knox (whatever that is) and also installed CWM and was planning to flash 4.1.1 so I can unlock the phone using the *#NUM# method.
After reading a bit I've seen many people saying that you can't "downgrade" from 4.3 to anything else because it will brick your phone. Hence, I did not try and flash any other rom on the phone.
So I guess I'm just trying to get a definitive answer here because I can't find anything but rumors on this subject. I mean it's weird, I'd expect if you couldn't downgrade from 4.3 than it would be a bit more documented.
Has anybody tackled this problem with success?
Thank you
Click to expand...
Click to collapse
Right now there is no free way to unlock your phone if it's on 4.3.(you can downgrade to older stock android, but the 4.3 bootloader remains and messes up your phones IMEI until you go back to stock 4.3)
Anyhow, the reason you can't downgrade the bootloader is because there is no method discovered to do this yet. I ended up using gsmliberty to unlock, and they have a deal that you get a free unlock if you take a video when you unlock and upload it to vimeo/youtube using the format they request.
I did that and they re-funded me very quickly. So IMO this is the best "free" method until we can downgrade from 4.3 bootloader and do the 4.1.1 free unlock.
I was in the same situation, and I had to pay for an unlock code.
If you want to see me unlock it, here is the video: http://vimeo.com/96549806
rikonor said:
Hi!
I'm sorry if this has been asked before but I just can't find a definitive answer to this and I've been trying to search for an answer for nearly a week now.
My boss received a used Samsung Galaxy S3 from a friend of his in the states. It is a locked AT&T phone (SGH-I747) and it is on 4.3.
I managed to root the phone using CF-Auto-Root, which disabled Knox (whatever that is) and also installed CWM and was planning to flash 4.1.1 so I can unlock the phone using the *#NUM# method.
After reading a bit I've seen many people saying that you can't "downgrade" from 4.3 to anything else because it will brick your phone. Hence, I did not try and flash any other rom on the phone.
So I guess I'm just trying to get a definitive answer here because I can't find anything but rumors on this subject. I mean it's weird, I'd expect if you couldn't downgrade from 4.3 than it would be a bit more documented.
Has anybody tackled this problem with success?
Thank you
Click to expand...
Click to collapse
What everyone else has said here is correct. You can't safely downgrade from 4.3 to free unlock - or free unlock by any other means for that matter once you are on 4.3. Your boss' friend would have unlocked prior to shipping the phone down but perhaps this was omitted. Your only options now would be to buy an unlock code online or perhaps the friend can contact AT&T to request the unlock code. If the device was off contract and is eligible for the unlock code, they would oblige the request. Otherwise, the code could cost between $18 - $30 online.
Thank you everybody.
I will use the service posted above.
I think it would be a good idea to make a sticky in this forum explaining that it is not possible at this point to downgrade from 4.3 (or is that just the boot loader).
Thanks again.
rikonor said:
Thank you everybody.
I will use the service posted above.
I think it would be a good idea to make a sticky in this forum explaining that it is not possible at this point to downgrade from 4.3 (or is that just the boot loader).
Thanks again.
Click to expand...
Click to collapse
It is just the bootloader that cannot be downgraded, not the ROM.
I have an SGIII with I747UCUEMJB listed as my baseband version and I wanted to know if this is considered a locked bootloader. I now have a note3 that I (unfortunately) took the OTA. I'm using my old SGIII as a "mess around with". Just curious and thank you in advance for answering.
rxv73 said:
I have an SGIII with I747UCUEMJB listed as my baseband version and I wanted to know if this is considered a locked bootloader. I now have a note3 that I (unfortunately) took the OTA. I'm using my old SGIII as a "mess around with". Just curious and thank you in advance for answering.
Click to expand...
Click to collapse
Why you need that info?
If you wanna root it, use towelroot (really user friendly). From there, you can mess around with it as much as you want.
I keep reading and hearing about not taking the OTA. Which I did on the note 3; limiting me on what I can/can not do with ROMS. Trying to avoid that on the S3 I have. I've rooted with towelroot on the Note3. Trying to be "open" as much as possible with the S3. I don't want to have to take an OTA and have the bootloader locked. If I already am with the baseband I have then this is all a moot point.
rxv73 said:
I keep reading and hearing about not taking the OTA. Which I did on the note 3; limiting me on what I can/can not do with ROMS. Trying to avoid that on the S3 I have. I've rooted with towelroot on the Note3. Trying to be "open" as much as possible with the S3. I don't want to have to take an OTA and have the bootloader locked. If I already am with the baseband I have then this is all a moot point.
Click to expand...
Click to collapse
MJB is 4.3, which has Knox (I'm assuming that's the lock you're talking about, it's more of a security thing though).
Having that doesn't "lock" you from anything really though. You can still root using Towelroot, flash a custom recovery with Flashify or GooManager and flash w/e ROM you feel like using. Note though that you can't downgrade bootloaders from 4.3.
Ok great. Good to know.
Also as far as I can tell all the s3 bootloaders are "open" so they will take custom kernels and such
Awesome. Good to know. Trying to get my arms around all of this and trying to learn as much as possible. Tons of stuff out here and lots information.
Sent from my SM-N900A using XDA Free mobile app
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
I've got a new t807a from AT&T. According to the "about device" settings page, SE is "enforcing." My understanding is that this conclusively indicates that my bootloader is locked. It's currently running Android version 4.4.2, build number kot49h.T807aucu1ank1
I don't need a custom ROM and I don't care about tripping my knox counter (per se). I just want root. I've asked this in several relevant threads this week and gotten contradictory responses. Is there or is there not currently a method to root my tablet?
If not: is there hope? This is a great tablet but I can't live with the bloat for 18 months until I can afford a replacement. I CAN still return it and eat the 70-dollar "restocking" fee.
Thanks in advance.
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
TheArtiszan said:
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
Click to expand...
Click to collapse
So what does that mean for my t807a?
thorvindr said:
So what does that mean for my t807a?
Click to expand...
Click to collapse
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
skeeterpro said:
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
Click to expand...
Click to collapse
Thanks. I have been following that. Just hoping someone knows something I don't I suppose.
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
DUHAsianSKILLZ said:
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
Click to expand...
Click to collapse
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
thorvindr said:
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
Click to expand...
Click to collapse
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
DUHAsianSKILLZ said:
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
Click to expand...
Click to collapse
Well that blows. I guess that's what I get for buying off-the-rack.
Is this info outdated?
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
JMVPSlash said:
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
Click to expand...
Click to collapse
The built-in app manager lets you move apps to SD but I also have not found a solution to install directly to SD (without repartitioning the card). After several months of despair, I'm just now checking back to see if there's been any development on the bootloader front. It appears not. You can get root with Kingroot (also check out supersume, if that's still around, to replace kingroot's su app with supersu) but apparently the bootloader being locked prevents any non-official ROM from booting.