Hello ya'll, I'm new to the forum, I joined because of the wealth of information here.
So I'm not new to Android, had one ever since I was 16. I rooted both my droid phones(droid X with that awesome slider keyboard, and RAZR MAXX) to remove those pesky bloatware apps, but didn't ROM them, as it just wasn't something I wasn't aware of when I did it. So rooting was as far as I got.
But rooting and ROM-ing a tablet seems like it could be a daunting job, I'm new to the tablet world But I already have most of the tools, from previous roots, minus a few that are platform specific that I'm currently downloading to support the new CROMBi-X
I figure I'll go about getting everything I need, so when I get my tablet back from the shop, I'll be able to dive right into the CROMBi ROM.
//
I don't want to brick my tablet so hence the questions I am unclear on.
//
Question 1: Asus doesn't have the standalone unlock tool on their website. How do I go about getting that tool to unlock the tablet? Was it done OTA or downloaded and installed onto the tablet?
I have searched a few places, and browsed the developer forums, but haven't come up with a surefire way yet. I've seen everything from asking ASUS to unlock the tablet, to flashing CWM recovery, and than flashing a rooted version of the stock ROM, 've read several of the forums, but I need a little bit of "English" on the topic, as this is something new to me. I did come across a root.zip link but I'm not entirely sure that is what I am looking for, or if it is version/BLoader specific. If it is, then that pretty much covers that question.
Question 2: Are all the drivers on the ROM? Or do I need to use something like [ADB/FB/APX Driver] Universal Naked Driver 0.7?
Question 3: Mods. Are they downloaded OTA from the play store, or is there a list of compatible mods for the ROM? I realize that most of them are probably cosmetic right? I'm probably asking in the wrong forum, but since this is LINUX based, once rooted, if I put Ubuntu on the tablet, and then run a ROM on top of it? or Do I have to choose between one or the other?
I'm only asking because I run a few programs that aren't able to run on the android platform that I use for recreational purposes.
Anyway, that about covers a few of the base questions I have for now. Time to get ready for work. Thanks for any help in advance!
For 1:
It's on ASUS website
www.service.asus.com/#!downloads/c1wax
Version V1.0
Unlock Device App: Unlock boot loader of TF701T.(Only works with 4.2 JB and later OS)
For 2:
It's been a while since I rooted however I think you only need fastboot to be able to put the custom recovery on the tablet. If you have ADB/FB drivers already installed your pc should see your tablet without an issue. I don't know what APX is.
For 3:
Not sure what you mean by Mods. And last I checked I don't think that you can and Linux to this tablet yet however even if you could you only get one or the other.
Oh and make sure you read through all of the instructions for rooting and roming
Gone_phishing said:
Hello ya'll, I'm new to the forum, I joined because of the wealth of information here.
So I'm not new to Android, had one ever since I was 16. I rooted both my droid phones(droid X with that awesome slider keyboard, and RAZR MAXX) to remove those pesky bloatware apps, but didn't ROM them, as it just wasn't something I wasn't aware of when I did it. So rooting was as far as I got.
But rooting and ROM-ing a tablet seems like it could be a daunting job, I'm new to the tablet world But I already have most of the tools, from previous roots, minus a few that are platform specific that I'm currently downloading to support the new CROMBi-X
I figure I'll go about getting everything I need, so when I get my tablet back from the shop, I'll be able to dive right into the CROMBi ROM.
//
I don't want to brick my tablet so hence the questions I am unclear on.
//
Question 1: Asus doesn't have the standalone unlock tool on their website. How do I go about getting that tool to unlock the tablet? Was it done OTA or downloaded and installed onto the tablet?
Click to expand...
Click to collapse
sleepy2 gave you the link. You find the Unlock Tool under "Utilites" on the TF701 downloads page
I have searched a few places, and browsed the developer forums, but haven't come up with a surefire way yet. I've seen everything from asking ASUS to unlock the tablet, to flashing CWM recovery, and than flashing a rooted version of the stock ROM, 've read several of the forums, but I need a little bit of "English" on the topic, as this is something new to me. I did come across a root.zip link but I'm not entirely sure that is what I am looking for, or if it is version/BLoader specific. If it is, then that pretty much covers that question.
Click to expand...
Click to collapse
.
First you need to determine what firmware you are running now and decide which JB version you want to run.
Check under Settings > About Tablet > Software version. On stock your firmware version and bootloader version are identical.
If you are on JB 4.3 you have either 10.26.1.7 or 10.26.1.18 (if you have the former, update to .18)
If you are on JB 4.4.2 you have 11.4.1.17
On JB 4.3
a) You can root the tablet without unlocking the bootloader with Towelroot v1.
b) You can unlock, flash CWM and then flash sbdag's stock rooted rom, one of several custom roms or just the root.zip
On JB 4.4.2
Right now there is no way to root without unlocking the bootloader and flashing a custom recovery first.
Once unlocked and with CWM installed, you can flash sbdag's rooted stock rom or flash the root.zip.
CROMi-X 7.0 for 4.4.2 is in the works. I do not know if the other custom roms (CM, CROMi-X 6, CROMbi-KK) are compatible with the 11.4.1.17 bootloader yet, but that's just a matter of time.
To install CWM follow the insructions here:
http://forum.xda-developers.com/showthread.php?t=2604462
Question 2: Are all the drivers on the ROM? Or do I need to use something like [ADB/FB/APX Driver] Universal Naked Driver 0.7?
Click to expand...
Click to collapse
Try it. I did not have to install new adb/fastboot drivers and the device drivers installed on my PC automativcally. YMMV
Open Device Manager, then connect the tablet. Let the drivers install and see if it shows up in Device Manager.
Then boot the tablet into fastboot, connect it to PC and see if it shows up as a fastboot device.
Enable USB debugging in Developer Options, then connect the tablet booted into Android and see if it shows up as ADB interface in Device Manager.
If you need drivers you can use the ones you mentioned.
Question 3: Mods. Are they downloaded OTA from the play store, or is there a list of compatible mods for the ROM? I realize that most of them are probably cosmetic right?
Click to expand...
Click to collapse
You'll find mods in the rom thread or at least the links for those that work with that rom.. No OTA updates
I'm probably asking in the wrong forum, but since this is LINUX based, once rooted, if I put Ubuntu on the tablet, and then run a ROM on top of it? or Do I have to choose between one or the other?
I'm only asking because I run a few programs that aren't able to run on the android platform that I use for recreational purposes.
Click to expand...
Click to collapse
There's a thread in the TF700 dev section on dual booting Android and Ubuntu. Not aware that anybody has tried it on the TF701.
Thanks for the link Sleepy! I had searched the website a couple times before, but I must have missed that part of it. Every other time I went somewhere to find it, it came back page unavailable. I'm really disliking this Kuwaiti right now! Well I won't know until I get the tablet back what JB is on it, but I imagine it would be sent back to a factory setting because of the issues I was having, or just get a whole new tablet all together depending on what was causing it not to charge.
I appreciate the clarification on everything guys, without the tablet in my hands I'm pretty much downloading everything I can that might help me out. I already have CWM, and several versions of it to be on the safe side.
I have been doing nothing but non-stop research, but it's daunting to try and go through 115 pages of information and tools, and version changes and what's compatible and how to use them. Watching videos has simplified it a little bit.
The reason I asked about Ubuntu, was I saw it dual booted to an older CROMi 2.X on the 700T
I used to run XP pro/Ubuntu on my laptop. Which was really nice when I needed a lightweight OS to free up processing power. Well before I had to format due to a near catastrophic drive failure and unrepairable data corruption. Anyway, that is a project for another time, one thing at a time!
I'll be around, busy with work 6 days a week!
Thanks again!
berndblb said:
First you need to determine what firmware you are running now and decide which JB version you want to run.
Check under Settings > About Tablet > Software version. On stock your firmware version and bootloader version are identical.
If you are on JB 4.3 you have either 10.26.1.7 or 10.26.1.18 (if you have the former, update to .18)
If you are on JB 4.4.2 you have 11.4.1.17
Click to expand...
Click to collapse
4.4.x is KitKat, not Jelly Bean, isn't it?
pelago said:
4.4.x is KitKat, not Jelly Bean, isn't it?
Click to expand...
Click to collapse
Yes.
List of repairs done
So what I thought was a simple battery not charging issue turned out to be a host of things. I had to have the LCD, Touchpadboard, Docking cable and LCD cable replaced, luckily I was under warranty. I imagine that would have been expensive!
I see it mentioned a few times but what on the phone prevents say 4.4.2 from being installed after the upgrade to 4.4.3?
Because the partion table and bootloader are different and can't be downgraded at all.
Or, you can downgrade... But brick your device after, even later.
Anyone who knows anything about the moto x will tell you just don't. ?
I find that odd. I wonder what the purpose is for doing that.
There is no way to just re-write those sections? Even on a Dev Edition?
knitler said:
I find that odd. I wonder what the purpose is for doing that.
There is no way to just re-write those sections? Even on a Dev Edition?
Click to expand...
Click to collapse
Security!
Look at the whole Windows/AntiVirus industry.
All because Microsoft wanted unsecure compatibility with the old OS.
Saving software dev time making things work.
knitler said:
I find that odd. I wonder what the purpose is for doing that.
There is no way to just re-write those sections? Even on a Dev Edition?
Click to expand...
Click to collapse
No, the Dev edition is no different. All the same "rules" apply.
The Dev edition is the same as any other.... It just keeps is warranty if you unlock it.
aviwdoowks said:
Security!
Look at the whole Windows/AntiVirus industry.
All because Microsoft wanted unsecure compatibility with the old OS.
Saving software dev time making things work.
Click to expand...
Click to collapse
I'm kind of not buying this for a second?
How about linux, which is often pointed to for its security... And you can upgrade, down grade, switch out every component for newer/older/different, switch kernels, upgrade kernels, downgrade kernels... hell change out kernels with out even rebooting.
Really not buying it has anything with security.
KJ said:
Or, you can downgrade... But brick your device after, even later.
Anyone who knows anything about the moto x will tell you just don't. ?
Click to expand...
Click to collapse
I think we understand that, I mean if the OP didn't he wouldn't have the question of "why not?". Its not I think it might be a good idea... We are just trying to understand the situation because it seems unique, and so we were hoping someone who knows a lot about
AGISCI said:
Because the partion table and bootloader are different and can't be downgraded at all.
Click to expand...
Click to collapse
This is the most I have heard so far, and I have heard it once or twice... But can't the recovery image include information on the partition table?
I realize the way it is, but was curious on some more technical information explaining it...
scryan said:
I'm kind of not buying this for a second?
How about linux, which is often pointed to for its security... And you can upgrade, down grade, switch out every component for newer/older/different, switch kernels, upgrade kernels, downgrade kernels... hell change out kernels with out even rebooting.
Really not buying it has anything with security.
I think we understand that, I mean if the OP didn't he wouldn't have the question of "why not?". Its not I think it might be a good idea... We are just trying to understand the situation because it seems unique, and so we were hoping someone who knows a lot about
This is the most I have heard so far, and I have heard it once or twice... But can't the recovery image include information on the partition table?
I realize the way it is, but was curious on some more technical information explaining it...
Click to expand...
Click to collapse
It is security. Specifically the SECURED BOOTLOADER. Don't confuse secured with locked. Yes, you can unlock your bootloader, but it is still secured.
Read up on "TrustZone" and see why it is important, and why the OEMs would not want you to be able to downgrade. You can "buy" or "not buy" whatever you want....
I really don't get the linux reference. We are talking about a bootloader, not linux in general. That's beyond the fact that any smart linux user would almost never have any reason at all to downgrade. Think about the heartbleed vuln that was discovered recently. Why on god's green earth would you want to downgrade openssl back to a version that is vulnerable??
The early (4.2.2 & 4.4) bootloader (motoboot.img) was vulnerable to an exploit that allowed us to disable write protection. The updated bootloader (4.4.2+) is patched. You *CAN NOT* downgrade back to the vulnerable version.
^Does that not have *everything* to do with security??
scryan said:
I'm kind of not buying this for a second?
How about linux, which is often pointed to for its security... And you can upgrade, down grade, switch out every component for newer/older/different, switch kernels, upgrade kernels, downgrade kernels... hell change out kernels with out even rebooting.
Really not buying it has anything with security.
I think we understand that, I mean if the OP didn't he wouldn't have the question of "why not?". Its not I think it might be a good idea... We are just trying to understand the situation because it seems unique, and so we were hoping someone who knows a lot about
This is the most I have heard so far, and I have heard it once or twice... But can't the recovery image include information on the partition table?
I realize the way it is, but was curious on some more technical information explaining it...
Click to expand...
Click to collapse
Because even though the patition file and bootloader are included in the archive, they fail to flash because they have a lower version than what is installed.
AGISCI said:
Because even though the patition file and bootloader are included in the archive, they fail to flash because they have a lower version than what is installed.
Click to expand...
Click to collapse
Can't just fake the version number?
No, it's not possible.
samwathegreat said:
I really don't get the linux reference. We are talking about a bootloader, not linux in general. That's beyond the fact that any smart linux user would almost never have any reason at all to downgrade. Think about the heartbleed vuln that was discovered recently. Why on god's green earth would you want to downgrade openssl back to a version that is vulnerable??
Click to expand...
Click to collapse
The linux reference was in direct reply to the quote above it that was making the argument that the PC anti-virus industry as well as the proliferation of malware and viruses is an example of the insecurity that is a result of a computers administrator having the technical ability to downgrade his OS software.
I mention linux because he was using PC OS's as an example, and Linux allows you not only to downgrade... but rewrite the bootloader. Or use a different bootloader. You bootloader can boot securely with UEFI, or you can just use BIOS. All this insecurity, but virtually no viruses, and very few security issues.
Why would you want to downgrade openssl? I wouldn't. I probably wouldn't flash back to an earlier version of android either... I keep my system pretty damn up to date. The point is more that his assertion that MS and Windows proves that being able to downgrade creates inherent security issues doesn't really hold up when you look at other systems that provide even more freedom.
samwathegreat said:
You can "buy" or "not buy" whatever you want....
Click to expand...
Click to collapse
I know, and that is why I want to understand what it is I would be buying.
AGISCI said:
Because even though the patition file and bootloader are included in the archive, they fail to flash because they have a lower version than what is installed.
Click to expand...
Click to collapse
I guess this is the part that we are not understanding. Perhaps because I don't understand enough and have not looked through decompressed recovery images enough... but basically the issue is that Motorola is bricking the device, rather then letting it be downgraded to an potentially insecure image. I am guessing then this is a soft brick?
Does recovery not have the ability to re-write the partition table though? Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
I guess then that is where the trust zone comes in...
scryan said:
The linux reference was in direct reply to the quote above it that was making the argument that the PC anti-virus industry as well as the proliferation of malware and viruses is an example of the insecurity that is a result of a computers administrator having the technical ability to downgrade his OS software.
I mention linux because he was using PC OS's as an example, and Linux allows you not only to downgrade... but rewrite the bootloader. Or use a different bootloader. You bootloader can boot securely with UEFI, or you can just use BIOS. All this insecurity, but virtually no viruses, and very few security issues.
Why would you want to downgrade openssl? I wouldn't. I probably wouldn't flash back to an earlier version of android either... I keep my system pretty damn up to date. The point is more that his assertion that MS and Windows proves that being able to downgrade creates inherent security issues doesn't really hold up when you look at other systems that provide even more freedom.
I know, and that is why I want to understand what it is I would be buying.
I guess this is the part that we are not understanding. Perhaps because I don't understand enough and have not looked through decompressed recovery images enough... but basically the issue is that Motorola is bricking the device, rather then letting it be downgraded to an potentially insecure image. I am guessing then this is a soft brick?
Does recovery not have the ability to re-write the partition table though? Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
I guess then that is where the trust zone comes in...
Click to expand...
Click to collapse
The custom recoveries don't flash gpt.bin nor motoboot.img so using a custom recovery it's impossible to correctly flash a Moto X. You MUST use stock recovery with a Moto X. The problem isn't that it causes a brick by flashing an old version. The problem is that a brick happens the next time you do an OTA update. When the OTA update occurs there is a mismatched partion table and bootloader, so it ends up causing a brick.
The developer edition and the standard moto x are 100% identical. They only difference is that you don't void the warranty when you unlock the bootloader on the dev edition, however with the non dev edition your warranty is voided. So the same problem with the partition table and the bootloader ALSO apply to the developer edition as well.
AGISCI said:
The custom recoveries don't flash gpt.bin nor motoboot.img so using a custom recovery it's impossible to correctly flash a Moto X. You MUST use stock recovery with a Moto X. The problem isn't that it causes a brick by flashing an old version. The problem is that a brick happens the next time you do an OTA update. When the OTA update occurs there is a mismatched partion table and bootloader, so it ends up causing a brick.
The developer edition and the standard moto x are 100% identical. They only difference is that you don't void the warranty when you unlock the bootloader on the dev edition, however with the non dev edition your warranty is voided. So the same problem with the partition table and the bootloader ALSO apply to the developer edition as well.
Click to expand...
Click to collapse
Well said :good:
Still the answer is security.
So upgrade as Moto intended & do not downgrade!
---------- Post added at 07:37 PM ---------- Previous post was at 07:30 PM ----------
scryan said:
Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
Click to expand...
Click to collapse
Our recovery devs never restore such partitions or boot loader elements.
scryan said:
The linux reference was in direct reply to the quote above it that was making the argument that the PC anti-virus industry as well as the proliferation of malware and viruses is an example of the insecurity that is a result of a computers administrator having the technical ability to downgrade his OS software.
I mention linux because he was using PC OS's as an example, and Linux allows you not only to downgrade... but rewrite the bootloader. Or use a different bootloader. You bootloader can boot securely with UEFI, or you can just use BIOS. All this insecurity, but virtually no viruses, and very few security issues.
Why would you want to downgrade openssl? I wouldn't. I probably wouldn't flash back to an earlier version of android either... I keep my system pretty damn up to date. The point is more that his assertion that MS and Windows proves that being able to downgrade creates inherent security issues doesn't really hold up when you look at other systems that provide even more freedom.
I know, and that is why I want to understand what it is I would be buying.
I guess this is the part that we are not understanding. Perhaps because I don't understand enough and have not looked through decompressed recovery images enough... but basically the issue is that Motorola is bricking the device, rather then letting it be downgraded to an potentially insecure image. I am guessing then this is a soft brick?
Does recovery not have the ability to re-write the partition table though? Is there no partition table information in this recovery image? I get that the stock recovery would not allow it, but wouldn't a developer edition user be able to flash a custom recovery that wouldn't have issues flashing the partition table. Don't TWRP or CWM, ect do this?
I guess then that is where the trust zone comes in...
Click to expand...
Click to collapse
Smh I normally don't chime into these threads but I had to, you can't downgrade the bootloader because of security/compatibility plan and simple. It's the same concept as why you can't downgrade most PC's bios, if there is a flaw found in the system as a whole, then they don't want you to downgrade to that version. A lot of the times when people brick their device trying to downgrade is because it will flash, but because an efuse was blown when it was upgraded the downgraded version will not boot. Yes the recovery can technically rewrite those partitions but again because the efuse was blown it will not boot. Also yes being able to downgrade on any system Windows, Linux, Unix, IOS, Xbox, PS, etc are causes to security issues. If you can downgrade a system to a vulnerable version, it is then by definition less secure, no matter how you try to spin it. Take the futex vulnerability which affected most linux kernels from the past 5 years, so why would any desktop linux user ever want to downgrade to a vulnerable kernel? They wouldn't but if the end user isn't knowledgeable of the vulnerability they wouldn't know that downgrading makes them vulnerable. So since phones are used by so many people who are not knowledgeable of vulnerabilities, why would you want to give them the opportunity to downgrade themselves to a vulnerable OS?
Appreciate the info given... I don't want to downgrade, I am not trying to downgrade, I understand why its a bad idea, ect...
My view point was more questioning the insistence that it being technically possible to downgrade creates a security flaw on a machine that is kept up to date by a responsible individual. Unless we are trying to speak more abstractly about that fact that given someone the opportunity to make a mistake makes it more likely for one to occur, I don't think that security threat exists until you actually use that ability to downgrade to something with a flaw.
I guess then it comes down to personal viewpoint of do I want my phone to brick it self to protect me from myself and like sam said, you choose to go elsewhere... But then that is somewhat what I am trying to figure out. Even though its not something I would probably ever have to deal with, I don't like the idea... But "bricking" can be such a vague term with manufacturer specific recovery tools and "different levels of bricking".
Just trying to understand how what and when actually happens. I probably need to read some more of the recovery threads, and I have been looking through old threads here while considering VZ dev moto X and waiting for the x + 1 announcement, but I figured I would jump on the thread while it was here.
I understand keeping it simple because its generally a bad idea all around, and its just best not to confuse things... but its been hard to find deeper discussion or information then the general warnings. A bit of a better picture from this thread though.
aviwdoowks said:
Still the answer is security.
So upgrade as Moto intended & do not downgrade!
---------- Post added at 07:37 PM ---------- Previous post was at 07:30 PM ----------
Our recovery devs never restore such partitions or boot loader elements.
Click to expand...
Click to collapse
By "Our recovery devs" do you mean the ones doing the moto specific stuff? Do you know if this Is typical of the custom recoveries for other devices?
@scryan
I know far less then other posters, but yes android recoveries are all very similar in that regard.
scryan said:
Appreciate the info given... I don't want to downgrade, I am not trying to downgrade, I understand why its a bad idea, ect...
My view point was more questioning the insistence that it being technically possible to downgrade creates a security flaw on a machine that is kept up to date by a responsible individual. Unless we are trying to speak more abstractly about that fact that given someone the opportunity to make a mistake makes it more likely for one to occur, I don't think that security threat exists until you actually use that ability to downgrade to something with a flaw.
I guess then it comes down to personal viewpoint of do I want my phone to brick it self to protect me from myself and like sam said, you choose to go elsewhere... But then that is somewhat what I am trying to figure out. Even though its not something I would probably ever have to deal with, I don't like the idea... But "bricking" can be such a vague term with manufacturer specific recovery tools and "different levels of bricking".
Just trying to understand how what and when actually happens. I probably need to read some more of the recovery threads, and I have been looking through old threads here while considering VZ dev moto X and waiting for the x + 1 announcement, but I figured I would jump on the thread while it was here.
I understand keeping it simple because its generally a bad idea all around, and its just best not to confuse things... but its been hard to find deeper discussion or information then the general warnings. A bit of a better picture from this thread though.
Click to expand...
Click to collapse
The thing is you keep looking at it from a PC point of view, where you basically have full control over the software and hardware. Phones have much tighter restrictions on them from carriers, fcc, etc they're not personal computers. So the reason they make it where you can't downgrade the bootloader is because that's what controls the restriction on downgrading any other partition on the device.
So with the Moto X's 4.4.4 update they probably blew an efuse, so users with a locked device can't downgrade. This is done because with locked devices they can only flash signed kernels, so by blowing the efuse they can't downgrade to the vulnerable 4.4.2 and below kernel even though it is signed correctly. This is because lets say a malicious app was able to get on a device that had the ability to downgrade say back to 4.2.2. That app could flash the older vulnerable signed kernel to the recovery partition, to disable write protection gain more control over the phone etc, without the users knowledge. Now that is a stretch and probably will never happen but that doesn't mean the threat isn't there, and hackers are very creative at deploying malicious attacks. So by updating the bootloader and blowing an efuse the older vulnerable kernels can't be flashed. Now this is all negated if you're unlocked of course, but if you don't want to ever worry about this issue don't update your bootloader. This is not recommended but I've mentioned it several times on this forum I haven't updated my X's bootloader since I bought it, it's still running the factory 4.2.2 bootloader, running 4.4.4 with no problem.
The other thing you're missing is we're technically not supposed to have the ability to restore our phones, except for the developer edition of course. The fastboot restore files are leaked not released to the public, they are designed for use when phones are returned to be refurbished. So they don't want the phones that are being refurbished to be flashed back to an older version, they want it to be refurbished and the latest software version flashed to it.
iKrYpToNiTe said:
The other thing you're missing is we're technically not supposed to have the ability to restore our phones, except for the developer edition of course. The fastboot restore files are leaked not released to the public, they are designed for use when phones are returned to be refurbished. So they don't want the phones that are being refurbished to be flashed back to an older version, they want it to be refurbished and the latest software version flashed to it.
Click to expand...
Click to collapse
A bit selfish, and perhaps lazy of me but I am only really here talking about the developer version, I just haven't bothered to write the full "verizon developer edition " every time (most of this is research for next phone, which will be developer handset)... To me, obviously a locked phone is going to have weird restrictions and hacked together paths to getting things done, your not supposed to have admin rights...(yeah, maybe I do look at it too much as a computer. Mostly because I am annoyed the differences seem intentionally imposed). But when I pay outright for a device so that I can own it and have full administrative control... anyways, thats a different more philosophical discussion. The point is I have been talking about an unlocked device using third party software where possible.
Either way, appreciate the reply. I have a better understanding of the issue... Though coming from an S4 it still seems weird that MDK*/developer phones don't seem to have the same issues/warnings. It would seem however that the difference may be that MDK/dev owners only use kernels/roms prepared for their devices and do not update the bootloader. I suppose if more people in the Moto X community were worried about maintaining the ability to downgrade an unlocked device it would be technically possible to upgrade in a way that could be easily reversed, similar to the S4.
(*MDK was the first VZ S4 firmware, and the only one that has a released exploit to allow for a full custom recover. Later locked firmwares must rely on safestrap)
Hey, i recently bought a Fire 7, so this questions is posted here, but it could be asked for any device with similarily strong protection mechanisms.
I ask if someone could explain what the difficulties are in simply flashing a performant Linux Distribution on the Fire 7 and using it as a Computer/display together with an external keyboard. The hardware should be supported by the Linux kernel right?
I'm not talking about rooting, which is essentially taking over the current OS, and in no question a difficult task, but about simply erasing everything and flashing a totally different OS. If i loose passwords to my home PC it'd be almost impossible to gain root or even access again, but i can most easlily install a new OS, so what does prevent me from doing the same to Fire 7?
borartr said:
Hey, i recently bought a Fire 7, so this questions is posted here, but it could be asked for any device with similarily strong protection mechanisms.
I ask if someone could explain what the difficulties are in simply flashing a performant Linux Distribution on the Fire 7 and using it as a Computer/display together with an external keyboard. The hardware should be supported by the Linux kernel right?
I'm not talking about rooting, which is essentially taking over the current OS, and in no question a difficult task, but about simply erasing everything and flashing a totally different OS. If i loose passwords to my home PC it'd be almost impossible to gain root or even access again, but i can most easlily install a new OS, so what does prevent me from doing the same to Fire 7?
Click to expand...
Click to collapse
Bootloader controls access to all partitions. It is "locked" so no modifications are possible outside the restrictions it imposes. Device also protects the BL from modification/replacement. Attempt to do so will score an unrecoverable brick.
Is it possible to unlock?
At this moment, no.
You will know as it'll be reported here very early. There are some third party companies that do it. Some are cheaper than others.
For the moment, there is nothing..
Sucks I know
I asked this before on another similar thread and didn't get a response. Is it possible to dump the bootloader from either an unlocked or locked phone to analyse it for potential vulnerabilities either in how it handles the unlock code, or more generally that would allow a user to soft-mod unlock the phone? I know for the 5th, 7th, and 9th gen Fire 7 tablets exploits were found in the LK part of the bootloader which eventually allowed for a customised version of TWRP to be flashed onto the devices, and later LineageOS. If we could dump the current Huawei bootloader surely we could try to find if there are any similar exploits?
I am found metod but it needs mrt dongle((
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
The Restless Soul said:
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
Click to expand...
Click to collapse
I am need it for root and lineage os