Hi everyone
I have an LG Optimus Vu device and due to LG's tremendous support for this phone, the operating system is still ICS and the kernel version is 2.6.39 (even the I/O scheduler for this phone is set to noop, and there aren't any alternatives :| ). It could be all good and well if there aren't hundreds of crashes appearing every day about different applications, which is driving me crazy. I've searched and searched and it seems that there are no custom ROMs for this phone, nor is there any custom recovery application. I could barely find an application to root this phone.
To get to the point; I'm considering to make a custom ROM for this phone, but I am a noob in these kind of stuff.
I have the kernel source and the original ROM zip file. Since the original OS version is 4.0.4, is it possible to bring the required proprietary drivers from the original and use it in a newer Android version like 4.4.x?
Can I use Google's recent Tegra 3 kernel (3.10) and port those LG specific drivers from the older kernel?
Am I even starting this process in the correct way?
Any help is appreciated.
set-0 said:
Hi everyone
I have an LG Optimus Vu device and due to LG's tremendous support for this phone, the operating system is still ICS and the kernel version is 2.6.39 (even the I/O scheduler for this phone is set to noop, and there aren't any alternatives :| ). It could be all good and well if there aren't hundreds of crashes appearing every day about different applications, which is driving me crazy. I've searched and searched and it seems that there are no custom ROMs for this phone, nor is there any custom recovery application. I could barely find an application to root this phone.
To get to the point; I'm considering to make a custom ROM for this phone, but I am a noob in these kind of stuff.
I have the kernel source and the original ROM zip file. Since the original OS version is 4.0.4, is it possible to bring the required proprietary drivers from the original and use it in a newer Android version like 4.4.x?
Can I use Google's recent Tegra 3 kernel (3.10) and port those LG specific drivers from the older kernel?
Am I even starting this process in the correct way?
Any help is appreciated.
Click to expand...
Click to collapse
Hate to be the bearer of bad news, but you're pretty much stuck. LG has locked the bootloader on it and has said they have no plans on unlocking it. Since the phone is around a year and a half old or older, I'd imagine they aren't going to change their minds all of a sudden for the relatively small amount of people still using the phone.
http://forum.xda-developers.com/showthread.php?t=2055272 - discussion about your phone here
FYI
What is a bootloader?
The bootloader is the first thing that starts up when a phone is turned on. At its most basic level, a bootloader is the low-level software on your phone that keeps you from breaking it. It is used to check and verify the software running on your phone before it loads. Think of it like a security guard scanning all the code to make sure everything is in order. If you were to try to load software onto the phone that was not properly signed by the device vendor, the bootloader would detect that and refuse to install it on the device.
When we speak about locked bootloaders, the context is often used to give meaning to the term “locked.” Almost all phones ship from the factory with locked bootloaders, but some are encrypted as well. It is this encryption that most reports are referring to when using the term “locked.” If a bootloader is encrypted, users can’t unlock it to load custom software of any sort. The device will be restricted to running software ROMs provided by the manufacturer.
Now, there are ways to unlock or circumvent bootloaders in special situations, but with ones that have no dev support like yours, it's pretty much a lost cause and most likely way beyond your capabilities to figure out without spending 100s of hours of learning about Android stuff. This is not a knock on you or anything of the sort, but it is what it is. It is a very difficult thing to figure out encrypted bootloaders even for the most experienced android developers and hackers and depending on how they are encrypted, there just might not be a way (ask the older Moto phones, especially from VZW).
es0tericcha0s said:
Hate to be the bearer of bad news, but you're pretty much stuck. LG has locked the bootloader on it and has said they have no plans on unlocking it. Since the phone is around a year and a half old or older, I'd imagine they aren't going to change their minds all of a sudden for the relatively small amount of people still using the phone.
...
Now, there are ways to unlock or circumvent bootloaders in special situations, but with ones that have no dev support like yours, it's pretty much a lost cause and most likely way beyond your capabilities to figure out without spending 100s of hours of learning about Android stuff. This is not a knock on you or anything of the sort, but it is what it is. It is a very difficult thing to figure out encrypted bootloaders even for the most experienced android developers and hackers and depending on how they are encrypted, there just might not be a way (ask the older Moto phones, especially from VZW).
Click to expand...
Click to collapse
Two thumbs up for the detailed reply.
Shame really. The phone was released in November 2012 but there wasn't a single OS update...
I guess I would have to give up on that, but I'm interested in system level developments for both Android and desktop systems. Any idea where to start?
set-0 said:
Two thumbs up for the detailed reply.
Shame really. The phone was released in November 2012 but there wasn't a single OS update...
I guess I would have to give up on that, but I'm interested in system level developments for both Android and desktop systems. Any idea where to start?
Click to expand...
Click to collapse
Yea, it does suck. That's one of the downfalls to making 8 million different phones. You have no incentive ($$$), no interest, and no manpower to be able to update them all in a reasonable fashion. But it's not like LG is alone. All of the manufacturers have had decent phones just...disappear in regards to updates or anything of the sort.
As far as getting started, there is a ton of info right here on XDA:
http://xda-university.com/
Modify hashes?
Hi!
Sorry for digging out a dead thread, but for the p895 probably all threads are more or less dead...
I wonder if it is really necessary to decrypt the bootloader. Since it must be able to boot different versions of the stock roms, it would probably only calculate a hash value of some files and compare that to a value stored elsewhere.
By comparing different versions of stock roms it might be possible to get some information about what files are hashed. If it is a standard hash algorithm and the comparison value the bootloader uses is stored in plain text (hope....!) there might be an atack vector in
comparing several known plain texts.
I also noticed, that the p895 has a "software integrity check" in the hidden menu that shows has values for some (a lot) of files. these hash values are likely already calculated when entering that menu option (i am pretty certain because they show immediately), so they might belong to the files checked at boot time and also hint to the hash algorith used.
The idea is to calculate a hash value for the custom rom and put it in the appropriate place so the bootloader thinks of the rom as an update.
These are just vage ideas, but i have no intention whatsoever to buy a new phone anytime soon and I guess I could as well spend "some" time tinkering and learning the tech details...
thank you!
Related
>>>> 22Jan2012: linboothkvc v1.0 source released in my linboothkvc thread. It works successfully on Omap3 and Omap4 based devices including NookTab. And with minimal changes/love can work with any rooted arm based linux device <<<<
>>>> 17Jan2012: Kernel module SUCCEEDS on NookTab to reboot into NIRVANA - NO NEED to BREAK the default SECURE BOOT CHAIN and NOTE THAT EVEN THIS CAN WORK ON ANY ROOTED DEVICE and not just NT, with minimal love so ENJOY <<<<
>>>> 16Jan2012: My kernel module based path (linboothkvc) to running custom kernels and roms is almost done, except for a __small part__ to get it running on NT now - IF ONLY PEOPLE HAD WAITED ...., we could have reaped the potential benefit in future, Why not !!!! why not ....WHY NOT !?!?. NOTE that it can allow one to run custom kernel/roms WITH OUT MODIFYING ANY CRITICAL PARTITIONS provided one sets it up properly/appropriately. Source for beta version available in my linboothkvc thread, for the interested developers/experimenters for now ... <<<<
>>>> I may not respond to the posts on this thread currently, because I am trying to get a alternate option called linboothkvc using kernel modules up and running (which will occupy my free time), which AVOIDS the NEED for this flaw in the first place for most of the people out there (i.e Custom ROMS with different kernels). However over the weekends, I will go thro all the posts on this thread <<<<
>>>> 14Jan2012: Initial pre-alpha version of kernel module path based source code uploaded to my linboothkvc thread for those still interested to experiment
http://forum.xda-developers.com/showthread.php?t=1427610
<<<<
Hi All,
If you have been following my posts over the last few days
NOTE: To people frustrated with UART requirement - I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then do note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all. AND THAT By holding off now, we can _potentially_(Risk is always there) reap the benifit with next years NEXT GEN Nook Tab+ or what ever they call it.
a) I have implemented 2ndihkvc, which follows the same fundamental concept as 2nd-init, but achieves it in a simpler way (Needed because some of the calls used in original 2nd-init doesn't work on NookTab, or have unnecessary dependencies (in this given context, otherwise they are good in them selves) which can be avoided with my simpler method)
b) I have provided the NOP Bypass method of running a modified Ramdisk and also 90% a modified kernel, provided UART access is there.
c) There is still the power of linux KERNEL MODULES to EXPLOIT. (Haven't had time on that yet).
If you ask me, this should cover all category of people. Be it people who want to run custom Roms, or people who want to experiment with Kernel and or other low level stuff for the fun of it.
There is a 4th method which will allow one to achieve (b) above with out requiring UART access or even uSD (potentially . If one reads between the lines from all my posts till date, the answer is hidden in there. Only that I haven't spelt it out directly or in the face. The reason is because It is a fundament flaw (rather there are potentially two at two different levels - one relatively simple and one relatively bit more involved - One I know for sure, another I have to dig bit more) in the way things are done currently in the secure boot chain on this device as well as potentially other devices with same or similar SOC (and or different SOC but with similar boot chain s/w components.
SHOULD WE BE WASTING i.e providing a solution which uses it, when there is already 2ndihkvc and NOP Bypass over UART and also the Linux KERNLE MODULE ROUTE to cater to most peoples needs.
Because if we do, then even the Device manufacturers and their partners will come to know about it and can easily fix it in their Newer/NextGen devices. While if we withhold it for now, we may be able to get access to it on their Next generation Devices with hopefully Arm A15 core or .... (NOTE: Depending on the boot sequence ROOT access may or may not be required for this).
The reason I am asking now is because, few people are asking my help on certain things and the reality is I know that the concept for which they want my inputs/guidance, can be applied at a more fundamental level here (or even at the same level), but that I have not ventured into it because of my delimma above.
NOTE: People who wanted my inputs/guidance wrt uSD, you all know who you are, I know the flaw to achieve what you want to achieve, but it is more powerful than what you all are currently thinking of doing/ ristricting yourselves to (You all have one input/... in there wrt devices . Unless let me think thro further and see if something can be done differently, with out exposing the flaw I have in mind to help you achieve what you want, otherwise i.e if there is nothing else I can come up with, and in turn if you people experiment further and are able to come up with the solution on your own, I would suggest that hold off on it for few days, think thro all the implications keeping what I have mentioned in this thread, and then take a call one way or the other.
Please provide your thoughts on this after thinking thro the options already available on NookTab (root access, kernel modules, UART UBoot access and inturn 2ndihkvc and NOP Bypass or equivalents)
Based on all the feedbacks as well as bit more thinking from my side, I will take a call on this.
Forum moderators I know this is the development portion of the forum, but I wanted feedback from Developers also that is the reason why I have posted here. But beyond that I leave it to you, whether you want this to continue here or move it out.
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
cfoesch said:
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
Click to expand...
Click to collapse
Hi
I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all.
By holding off now, we can potentially reap the benifit with next years Nook Tab+ or what ever they call it.
Im not a Developer but I've got a few questions. NOP requires to open up your device, so I think probably 95% won't open their device for ICS and I think since the device had a dual core CPU we should get ICS roms. Now my actual question how does your 2init work or how do you install it on our device? But great work so far keep on.
Sent from my SGH-T989
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
PM me about the flaw, I'll see if we should have it outed yet or not (sorry guys, but if it's a decent exploitable flaw and we have other methods, I'm pretty sure I'm with hkvc on it.)
xdahgary said:
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
Click to expand...
Click to collapse
Not worried for 2 reasons,
a) It doesn't bother if my name comes or not. I am exploring just for the fun of exploring.
AND MORE IMPORTANTLY,
b) Actually I have already revealed the flaw in my NOP Bypass thread, indirectly, if only, one reads carefully all my lines as well as between them. Only that I have just replaced one or two of the steps with a different steps thats all for now.
If someone else find the same flaw, he will realise the same, if he reads my posts once again with his new knowledge.
What an awesome idea, we can have a root for the Nook Tablet+ or whatever else in a years time!
...
So, um... what do I do now with my Nook Tablet? It's a piece of garbage now, I guess, so, I'll just return it since it's still within the Holiday return period? I suppose I'll just have to wait for the Nook Tablet+ to have a custom ROM running on my Nook... ("But you can UART hack it!" ... *sigh* I've already explain that that is not sufficient. The UART hack is a stop gap, and should only be stopped at if that is the absolute only option available.)
And I mean no disrespect to xIndirect, but why should he be the lone gatekeeper of what exploits and hacks are out there for the Nook Tablet? I would rather see this exploit before making a decision as well, but I don't think it fair that someone should have privileged access to the exploit. Either release it to everyone or DON'T SAY ANYTHING IN THE FIRST PLACE.
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Indirect said:
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Click to expand...
Click to collapse
If you buy a plot of land and the seller has accidentally left seeds there and isn't coming back for them, do you grow a garden on your current plot of land, or do you decide not to plant them and hope that the next time you buy a plot of land they might forget some seeds again?
I would rather tend the garden I own than hope for a better plot of land with seeds I may never have.
Cheers!
-M
XDA member since 2007
Sorry if my post is offtopic, I just want to help with development.
My SE Xperia x10 came worh a locked bootloader and devs figured out how to make a bootable recovery (xrecovery) based on CWM, may be with an adaptation for the NT we can get the world of custom roms, even with locked bootloader this crappy phone got cuatom kernels by bypassing the bootloader, hope this give little ligth to you guys the real Developers.
If this post is garbage mods please delate it.
Sent from my BNTV250 using xda premium
Hello, I beleive if there is a software way to get ICS + maybe overclocking it should be tried first as this IS what most people are waiting for. That's the big dream they got. If someone knows how to implement that, then please by all means do so ..
P.S. you said so much where to look for the flaw in your posts that if I was a programmer from B&N I'd know where to look like everybody else. Assuming they are not complete morons they can already figure it out too. Can they plug the hole or not? Is it oversight or permanent design flaw ? We'll see. Best way to keep a secret is to " keep it secret " , ie not talk about it at all. Especially if soft mod ICS, hw acceleration and overclocking already available.
Sent from my LG-P500 using Much Love
First of all hkvc +1 for your efforts.
I voted yes, the NT developers can read between the lines in your posts as well.
Whats life without risks once in a while
Hi All,
I understand very well that even BN devs will be looking and potentially can figure out and fix it. That is the risk, but at one level I don't mind taking the risk and see if it works out to my/our advantage (i.e the bug being still open in a new device (From BN or any other Vendor)) or disadvantage(the bug is either way fixed).
Also the flaw can affect ANY DEVICE (Not just NOOK TAB) using similar secure boot chain not just NookTab, that is also one reason why I am bit wary of releasing the info or a implementation which uses it just like that.
I will share my finding with few people on the forum/outside in few days time so that even If I loose interest in this, there will be few people with the required knowledge (i.e if they haven't already figured out on their own by then (and released something or not ...)).
Also I haven't taken a final call on this yet. I am in a delima, so getting all your opinions also before I decide.
Time permitting I will also attack/explore the KERNEL MODULE PATH in a few days time, so that people don't have to depend on this flaw in the first place, but use the wonderful world of Linux Kernel Modules to achieve what they want.
LexS007 said:
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Click to expand...
Click to collapse
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
absolutely YES, we r all xdaers, right hehehe. Thanks all devs especially hkvc for the efforts
hkvc said:
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
Click to expand...
Click to collapse
It's very good. Thanks!!!
First off, not a dev but read religiously.
2nd, release it if the people who would take advantage of it agree. The rest of us say "great,woohoo!" But I must admit, I can't take advantage of it. But I certainly don't want to make a hardware uart to boot custom roms.
That being said, if its more complicated to install with a different method, that's fine. As long as it doesn't include a soldering iron.
But if it were easier to make a custom rom, or open up more capabilities of the kernal or whathaveyou, well that would attract more developers to make roms, etc. and so on and so forth.
Btw. Yes, exploit may exist if outedin a later tablet, but you found this one.... I have faith the next flaw will be found in the next one too.
A bird in the hand is worth two in the bush.
Posted from my B&N Nook Tablet... rooted of course!
jotekman said:
A bird in the hand is worth two in the bush.
Click to expand...
Click to collapse
I would say this summarizes everything I want to say on the topic.
Since I asked a lot of question on this forum I would like to share the answers with everybody and maybe help them.
NOTE: Please don't post any replys as I want to keep the post clean and room for updates, send me a PM if you have and idea or any fails that I made in this post, if this post helped you don't post hit just the thanks button. Cheers.
Current list of questions with answers(will be updated):
Why would I want to root my phone?
Is rooting worth the trouble?
Is rooting illegal?
Will I have any customer support?
Is it dangerous?
Isn't rooting a complex and difficult process?
Will I still receive operating system updates from my carrier?
Application updates?
What if I want to un-root my phone?
Do I run the risk of bricking my phone?
Could my phone overheat and explode?
Why would I want to root my phone?
Everything in a Linux system is a file, or is treated as a file. Since Android runs on top of Linux, it acts the same way. Most of the files you will need to access or change are available to you without having elevated permissions. "Most" being the key term here. When you want to do things that affect or change the core software of your device -- like updating the version of Android on your phone, or adding a nice piece of software from another device -- you'll have to do it as root. Dream and Magic users have been running Eclair on their phones for a good while now, and it’s because they have rooted their device. Rooting also gives you access to some handy software that you couldn’t use otherwise. Things like a complete system backup or ad blocking software require you to root your device. Don’t root your phone just for the sake of rooting your phone, but if you come across something you feel you could use or would like to have, then consider it. You'll find that the open source community is usually pretty helpful and encouraging new people to do new things is common. And when you get to the point where you can lend a hand to the new folks, pay it forward.
Is rooting worth the trouble?
The answer is a resounding yes. The phone is faster than it has ever been, the battery lasts longer, and have all kinds of new features, including free wireless tethering and notification-bar widgets. Rooting your phone is generally a fairly quick process, though the complexity depends on your specific situation. Once you're rooted your handset, you can begin installing apps (many directly from Android Market) that will take advantage of your handset's new capabilities. Installing custom ROMs (replacement operating systems) built by hackers is a longer, more involved process , and generally involves your wiping all the data from your phone, but even that is worthwhile.
Is rooting illegal?
Nope. You bought the phone, it's your equipment, you own it, and you can do what you want with it. No one is going to come and get you, and your service provider will not cancel your contract. In fact, the U.S. federal government recognized the legality of rooting a phone in July 2010.
What you will do, however, is void the warranty on your device. If you don't want to live without a warranty, rooting isn't for you. Personally, I finally decided to take the plunge when I realized that the potential benefits outweighed the potential consequences. My phone was becoming slow and buggy, with lots of force-closes, and I was just about eligible for an upgrade anyway.
Will I have any customer support?
Rooting can be daunting because there is no toll-free number you can call for help, and no governing body to which you can turn for definitive answers. But the collective process of rooting phones and creating custom ROMs has engendered cool and supportive communities. The user-generated forums out there contain a staggering amount of information; the CyanogenMod forum has offered answers to almost all of my questions, as has the XDA Developers forum, but you can find many more. No matter your question, the forums most likely already have threads that can answer it. If you really can't find anything, you can always start a new thread to ask your question. If you think you've really mucked things up and you need immediate help, many IRC chat channels specialize in support for rooters. (Download an IRC client on your computer and head to irc.freenode.net, where the channels #android and #android-root are particularly helpful.)
Is it dangerous?
It can be, It might, and Yes. By not allowing access to the superuser account, the manufacturer and your carrier have basically protected you from doing things that change the system and make it unusable. All it takes is one wrong keystroke to turn your shiny new Android phone into a plastic and metal brick with no connection. Most times this is recoverable, but not always. You have to decide how capable you feel you are, and how well written the instructions you’ve found seem to be. Nobody will blame you if you decide against the risk, especially your cell carrier. All major carriers and manufacturers plainly state that altering or using unapproved software voids your warranty, and rooting falls into that category. While that seems a bit harsh, they need to be able to support the products they sell. For that to happen, they need to know exactly what’s running and what it’s doing.
Apps that run as root need a little further consideration. You need to have a level of trust in the person who wrote the app first and foremost. Does the developer have other software available? Do the user comments (for Market apps) have anything that raises a red flag? Do the requested permissions seem a little odd? These are all questions you need to think about before you allow something to run as root. For a further level of security, think about installing an application that warns you anytime something tries to run as root. SuperUser Whitelist is a great little app that does exactly that. If you decide to go on and root, ask users with the same device as you for a link to a version of SuperUser Whitelist that works with your firmware. Once installed, anytime something wants to run as root, the app intercepts and asks if you would like to allow it. You’re given the choice to accept, decline, or grant the app in question full privileges each time it runs.
One last thing to touch on here. Many custom ROMs include some sort of SSH server. This can be a wonderful tool, or it can get you in hot water. This is what caused the whole “Rick-Roll” episode with the latest iPhone jailbreak. The server sits and waits for an outside connection, and if that connection provides the right password full control of the device is turned over. In the case of the iPhone, users never bothered to change the default SSH password for root. A clever (or devious) group of users simply scanned for servers listening on the correct port, then attempted to sign in as root with the default password. Lesson learned, but this is easy to prevent. Ask other users of the ROM or firmware you’re thinking of flashing if there is a server listening, and if so how to disable it or change the default password.
Isn't rooting a complex and difficult process?
Yes and no. It really depends on what model of phone you have. On many phones (such as the Nexus One, Motorola Defy, or EVO 4G) the process is incredibly easy: You can download an app such as Simple Root, Universal 1-Click, or Z4root that will safely root your phone with a single click. Those apps are no longer available from the Android Market, but you can find them online with a simple search and install them onto an SD Card.
It is important to note that different approaches will work for different phones. For example, Z4root will work on many Android phones, but it won't work on most HTC models. Some rooting apps will work on an early build of Android 2.2 (Froyo), but will not work on later builds (though more and more apps are being released for that now). Rooting is phone/OS specific, so make sure to check that the root tool you're considering is compatible with your phone. For other models, rooting may take much more work. You might be required to connect the phone to your computer and enter some lines of code in a terminal utility.
Fortunately, more and more root apps do not require you to hook up your computer and get in that deep. Do some research as to what is required for your setup, read some step-by-step guides, and be honest with yourself about how comfortable you would be trying to follow the directions. If it feels like you'd be in over your head, it's probably best to avoid rooting.
Note that generally rooting is even tougher to do if you use a Mac, as most of the software for doing this sort of thing is written for Windows or Linux.
Will I still receive operating system updates from my carrier?
Maybe. More than likely if you’ve just rooted your phone so you could have access to the full file system and haven’t drastically changed things, the phone will still pass your carrier's checks and upgrade. If you’ve delved deeper and really customized your device, count on not being able to upgrade. Carrier updates were designed to work with the original software, so they need to be sure that’s what the phone is running. Again, this is for your own good. T-Mobile or Verizon can’t offer technical support for things they haven’t trained their technicians on, and if you flash a carrier approved update over custom software it’s probably not going to work.
The good news is that failing the checks the carrier does during an update won’t cause any damage to your phone. The update will just quit and you’ll be back where you started. Then you can decide if you would like to un-root and upgrade or take another path. The worst case scenario is that the phone passes the carriers checks, updates, and then things get broken. That’s pretty unlikely, but possible. If that would happen, you won’t be alone. Everyone in your situation will scramble to their favorite Android user forum and hopefully a work around can be found.
Note - a carrier update may also break the ability to root the device and a new method will need to be found. Any discussion of upgrading and root needs this mentioned as well. Most folks who root and decide to install a custom ROM wait for the ROM developer to provide an update that includes any bug fixes or new capabilities of the carrier update.
Application updates?
Yes. While it’s not being used, the program that allows permissions to be upgraded just sits and does nothing. Normal applications won’t even be aware it’s there, and applications that use it expect it to be there. Application updates, whether they are from the Market or other third parties will still install as normal.
What if I want to un-root my phone?
It depends on the model of your phone. Some are ridiculously easy to revert, some not so much. This is the most important question you can ask before you dive in and root your phone. Usually the website you found the method to root your phone will also have a discussion about un-rooting and going back to stock firmware. Take the time to find and read this information so you’re aware of just how difficult it’s going to be to go back. Pay close attention and create backups when recommended while you’re rooting your phone, as these may be needed to go back. I’ve not heard of any device that can’t be restored to factory firmware provided the original was backed up properly as recommended during the rooting process. The most important thing to always remember is to ask for help. If you do find yourself stuck without a backup or a working phone and need to roll back, ask for advice. Our forums are full of fine folks from all walks of life, and the majority are more than happy to help. There’s a good chance you’re not the first person in that situation and a solution has already been worked up!
Do I run the risk of bricking my phone?
This is one of the Internet's favorite bogeymen. "Bricking" is the idea that if you try to tinker with root access, you'll mess something up so it becomes completely unusable, and you'll essentially turn your phone into a paperweight. While that's certainly not outside the realm of possibility, the good news is that Android phones are generally very hard to brick. Yes, even the Droid X, which was purported to be the "unrootable" phone, has been safely rooted for quite some time (Z4root reportedly works with the Droid X).
If you do get caught in a boot loop, you may have to connect your phone to your computer and rewrite some code, but if you are patient and willing to do some more reading, you will almost always be able to find a way to at least restore your phone to its original state (read more on where that help comes from in the next section).
A common mistake that actually will lead to a bricked phone is running out of battery power in the middle of trying to install a custom ROM. The operating system only half installs, and that really is tough to fix. So always make sure that your battery is full before you install a new OS or ROM.
Also, just because a phone is rootable does not mean you can install any custom ROM you want. Differerent ROMs will work for different phones. Even the extremely popular CyanogenMod works for many phones, but certainly not all, so do plenty of research to make sure your phone is supported before trying to install a custom ROM.
Could my phone overheat and explode?
One of the major incentives to root your phone is the ability to overclock your processor to gain more speed (or underclock it to extend battery life). My phone has gotten considerably faster because of overclocking. When you overclock your processor, though, it will get hotter. If you try to push your phone too far and you don't set any fail-safes (a maximum allowable temperature in the overclocking utility), then you could burn out your processor. However, it is very easy to set safety thresholds to ensure that you don't do that.
SetCPU, the most popular app for overclocking or underclocking, allows you to set up various profiles.
Reading the rooting forums will give you plenty of advice on how far you can push your specific device and maintain stability. It pays to do some experimentation: Different phones behave differently, even if they're the same model.
Sources: androidcentral.com, pcworld.com
Useful threads:
[TUTORIAL] Unlocking, rooting, custom roms installing, going back to stock
[INDEX] HTC Desire X (protou) - Everything Desire X is here!
Reserved.
Hello,
I've seen some threads on rollbacks but want to be sure I'm doing it right since I'm on an old version.
I have a Apollo 8.9. I can't even remember all the steps I took to get Google apps, but I know I'm on 3.2.5 and have the HDXposed module installed to block updates etc. I'm on Safestrap v 3.75. All I want to do is get back to factory stock latest version so I can sell this. I don't care about getting root again or custom ROMs.
Any help is appreciated. Thanks!
Tim
Imo, it would be easier to sell as is. Many people want the flexibility that your device has. The ability to have a wonderful screen and be able to put one of many roms on it.
lekofraggle said:
Imo, it would be easier to sell as is. Many people want the flexibility that your device has. The ability to have a wonderful screen and be able to put one of many roms on it.
Click to expand...
Click to collapse
Agreed. Clearly state the firmware version and indicate the bootloader can be unlocked. Knowledgeable buyers will recognize what this means and may be willing to pay for this capability. Where to sell it and a fair asking price are unknowns (at least to me).
Ironically, market value may be reduced somewhat by a flurry of recent tool/rom releases that work on rooted HDX devices regardless of firmware level as it opens the door for many users who were previously shut out - unless they had a device like yours.
Attempting to restore you device to 'factory defaults' introduces risks that could yield a brick. Best not mess with it unless you are willing to assume those risks.
Title more or less says it all, I've been tasked by my company to do some research into the topic of large-scale Android deployments that involve flashing a custom, stripped-down image. I found a few threads and posts online discussing topics similar to this one, but they all ultimately end up being more concerned about the device setup after initial boot situation, and not so much about just flashing a custom image to 1000s of tablets. I'm fairly experienced with the typical Android flashing process, but I just can't seem to think of a way to scale it up that big without just flashing the tablets one by one, which would likely take years of time I don't have. We are being provided unlocked tablets by the manufacturer, so typical flashing tools should work just fine.
I've already entertained the idea of running several computers at once in order to get flashing done in parallel, since my company has a number of machines that I could use for this purpose, but that's still not entirely ideal.
My company is also not opposed to investing in proper hardware that could achieve this, if such a thing exists, but I can't seem to find evidence that such a thing exists. Feel free to correct me on this, if I'm wrong, however.
It suddenly occurs to me that OTA might be a good solution to this situation, though I have no knowledge of how that exactly works currently, but would it make sense that I could build the custom image we need, then do whatever is necessary to make the image update OTA, and then push it out to the devices? I realize this would still mean having to do initial Android setup on all the tablets, but that would still be faster than going at it one at a time.
I've also thought about trying to write a batch script, and then connecting a mass number of tablets to a large USB hub, then using the script to grab device IDs one by one, and then feed that into fastboot. I guess the issue there might be power, that would have to be one beefy USB hub.
So, any ideas/thoughts/suggestions as to how I might go about accomplishing this? Not looking for exact details or processes, just rough ideas of what could actually work to achieve this goal.
Hi everyone,
I can't find a satisfactory answer on my favorite search engines, so I thought I'd come here and ask. Sorry if this question has already been put on the table, carved, sliced and gobbled, I couldn't find trace of it in the forum's search engine either.
My phone's a Leagoo T5c that will forever be stuck on Android 7.0, it seems, because the OEM has already lost interest, and because its SoC makes it difficult, if not downright impossible, to find a suitable custom ROM.
The latest ROM I could find and install on this phone goes back to August of 2018 (no-no, no typos), and its Security Update is even one month older (July 2018).
My question is in the title: Is it possible to install Security Updates without reinstalling/updating/upgrading the firmware itself, like you would in, say, Windows or any other OS, I presume?
UglyStuff said:
Hi everyone,
I can't find a satisfactory answer on my favorite search engines, so I thought I'd come here and ask. Sorry if this question has already been put on the table, carved, sliced and gobbled, I couldn't find trace of it in the forum's search engine either.
My phone's a Leagoo T5c that will forever be stuck on Android 7.0, it seems, because the OEM has already lost interest, and because its SoC makes it difficult, if not downright impossible, to find a suitable custom ROM.
The latest ROM I could find and install on this phone goes back to August of 2018 (no-no, no typos), and its Security Update is even one month older (July 2018).
My question is in the title: Is it possible to install Security Updates without reinstalling/updating/upgrading the firmware itself, like you would in, say, Windows or any other OS, I presume?
Click to expand...
Click to collapse
With android 10 were introduced Google play security updates that lets you received security updates (not all of them unfortunately, some requires to upgrade) without updating the full OS. You can't do it because you're stuck with the wrong Android version
Hopefully you won't have any issues with hacking but consider buying a new phone when you'll get a chance
Security updates get rolled out as OTA by OEM/Carrier if they consider it's necessary. You can't force it. Theoretically, all Android smartphones should get around two years of security updates. However, the reality is often very different.
The Leagoo T5c is a small-budget phone what was sold for 99 USD - so more or less a disposable item. You cannot expect OEM/Carrier to have any interest in providing updates for such a phone.
Thank you both for your explanations. I understand that Android works differently when it comes to updating itself, mostly because Google isn't the only party to have a voice in the chapter; still, it's unnerving to see that the end-user is more or less captive anyway.
It kinda defeats the very purpose of an open-source OS, to have to wait for an OEM to release (or not) an update, when you could install the patches yourself.
As for buying another phone, well, as soon as I've got the dough, I will, believe me. Not because I'm dissatisfied with this one, but because I don't like the idea of totting around with a phone that hasn't seen a security update in over two years.
I'm also seriously considering moving to Ubuntu Touch, though there again, my phone's exotic platform could be problematic. Custom ROMs seems to be as complicated an avenue as others, too.
All in all, Android isn't what they sold me: It's not secure, it's not "free", it's just another way to make you shell out bucks for new hardware every couple years.
Android is just iOS without the eye-candy, you ask me...
UglyStuff said:
Thank you both for your explanations. I understand that Android works differently when it comes to updating itself, mostly because Google isn't the only party to have a voice in the chapter; still, it's unnerving to see that the end-user is more or less captive anyway.
It kinda defeats the very purpose of an open-source OS, to have to wait for an OEM to release (or not) an update, when you could install the patches yourself.
As for buying another phone, well, as soon as I've got the dough, I will, believe me. Not because I'm dissatisfied with this one, but because I don't like the idea of totting around with a phone that hasn't seen a security update in over two years.
I'm also seriously considering moving to Ubuntu Touch, though there again, my phone's exotic platform could be problematic. Custom ROMs seems to be as complicated an avenue as others, too.
All in all, Android isn't what they sold me: It's not secure, it's not "free", it's just another way to make you shell out bucks for new hardware every couple years.
Android is just iOS without the eye-candy, you ask me...
Click to expand...
Click to collapse
Android isn't iOS precisely because you can break free from your OEM by flashing a custom ROM. You can develop one for almost any device as long as the OEM releases the kernel source code. And most OEM do (expect for some very unknown phones).
Custom ROMs like GrapheneOS are made to free you from google Services and are truly privacy oriented. And all of that is possible because Android is open source.
Trust me, the Android community has always worked actively to counter aging of their devices (including me).
Just buy a phone with a solid community behind and you'll be able to keep it up to date a looong time
Raiz said:
Android isn't iOS precisely because you can break free from your OEM by flashing a custom ROM. You can develop one for almost any device as long as the OEM releases the kernel source code. And most OEM do (expect for some very unknown phones).
Custom ROMs like GrapheneOS are made to free you from google Services and are truly privacy oriented. And all of that is possible because Android is open source.
Trust me, the Android community has always worked actively to counter aging of their devices (including me).
Just buy a phone with a solid community behind and you'll be able to keep it up to date a looong time
Click to expand...
Click to collapse
I agree with you in principle, but if I must take an example: I have this Early 2006 MacBook Pro with a Core Duo CPU that precludes me from even installing Mac OS X 10.7 "Lion" on it, because the CPU is 32-bit-only, and Lion requires a 64-bit CPU.
The machine itself works very well, albeit a bit slowly, but then it's got only 2 GB of RAM and a 120-GB SSD. When I got fed-up with OS X applications not updating/upgrading and Firefox addons not installing because my copy of Firefox was too old, I partitioned the SSD, installed rEFInd as boot manager, and installed Zorin 15.2 (now 15.3) Lite 32-bit.
I now spend more time on the Linux side of this Mac than on the OS X side, and updating/upgrading it is a breeze, either via the dedicated application or in Terminal. I know there'll be an end-of-the-line there too, someday, but at least I'll keep using this Mac until it truly dies on me, not when Apple tells me it's dead.
This, for me, is the very essence of open-source: Not just the fact that it's free, but that you can revive an old machine and keep it running long after Apple et al have decided that it had gone the way of the dinosaurs.
The same doesn't apply to Android, alas. Here, you must have a compatible SoC/chipset/what-have-you, a Treble-compatible device, you must have this, you must have that...
In the end, only a fraction of Android users really get to enjoy everything their device has to offer for as long as they choose; the others just pop into the nearest phone store, be it brick-and-mortar or cyber, and must produce their credit card.
My question was as much a challenge to myself as anything else. I would really like to learn how Android works, but the tutorials and articles I've found here and there are all a bit cryptic.
That's why I'm regularly prowling this forum, I guess.
"Hunting high and low", as the song goes... :laugh:
yep, good question but google & manufactures are in it for the moola not the users 2 yr old phone.
hiitsrudd said:
yep, good question but google & manufactures are in it for the moola not the users 2 yr old phone.
Click to expand...
Click to collapse
Don't I know it! It's true that even budget phones have decent specs nowadays, still, why dump a perfectly functioning phone simply because you can't update/upgrade the software?
I understand Google's rationale, of course: They invest tons of money year after year after year to keep the whole boat afloat, and they need a steady income. OK. Still, to not be able to keep your phone ***safe*** is a no-go for me.
I'm seriously beginning to think about installing Ubuntu Touch on the device. I think I'm going to try that next weekend.
I'll probably come back here with my eyes red, asking for help in unbricking my phone, though.
Stay tuned! :good:
A followup, if you are mindful of your own security it's conceivable to get more usage of that android. I don't use a banking app, but if need be use a good browser( thats updated of course) And update all often used apps via playstore. I'm still running Oreo on my phone. FYI you iOS ppl need to do critical updates asap