Hi,
I have an LG Optimus One P500 and would like to root it. However, I spent all my cash on it and I wouldn't want to brick it or VOID THE WARRANTY. I need a method of rooting my Optimus that will not void my warranty, preferably a one click root app or something.
Please help me.
Thanks.
If your phone came with android 2.2.1 or 2.2.2 onboard, then rooting first involves downgrading the firmware to 2.2. This process has the most chances of bricking your device. There is no concrete way of ensuring that bricking does not happen, though if you follow the instructions correctly, you will in all probability have no problems as lots of people have sucessfully completed the instructions.
You can chose to root your phone using a one click app like 'z4root'. Since there is an option to unroot your phone,you wont void your warranty.
You can even restore the phone to factory state even after installing a Custom recovery or Custom ROM by installing Original Firmware provided by LG using the same procedure used to downgrade yourr firmeware. This will remove all the traces of your fiddling with the phone and thus will preserve warranty.
I suggest that you read this -
[HOWTO] Rooting, Installing - Android SDK, Custom Recovery, Custom ROM's
Related
I saw that the XDA team had rooted the new software, so I went ahead and did an upgrade via my PC instead of over the air. Now that I've started researching the root methods it looks like all of them void your warranty, so if your phone dies (and lets be honest phones do die often on their own accord), you will be stuck buying a brand new phone.
I like the new software, but there are tools I use that need root such as titanium backup, and settings profiles (for gps scripting). Will there ever be a root going forward that won't break your warranty?
vmlinuxz said:
I saw that the XDA team had rooted the new software, so I went ahead and did an upgrade via my PC instead of over the air. Now that I've started researching the root methods it looks like all of them void your warranty, so if your phone dies (and lets be honest phones do die often on their own accord), you will be stuck buying a brand new phone.
I like the new software, but there are tools I use that need root such as titanium backup, and settings profiles (for gps scripting). Will there ever be a root going forward that won't break your warranty?
Click to expand...
Click to collapse
no, the act of rooting voids your warranty not the method. How hard motorola actually tries to determine if your phone is rooted is another matter though especially if something is making your phone disfunctional.
Warranty is not a tangible item that is "broken." It is a legal agreement. By rooting your phone, you are exposing the delicate inner workings to possible breaking. However, since the manufacturer doesn't see what happens to the phone and it stops working, you can generally at least partially restore it, hiding the fact it was rooted. Is your warranty still void? Technically yes. However, the manufacturer doesnt know. Further, Although it is possible to break your phone, you will never have any trouble as long as you follow these guidelines:
- Avoid rooting phones with the OTA 2.3.4
- DO NOT FLASH SBF TO OTA 2.3.4 ATRIX. IT WILL BREAK FOR GOOD
- Read all instructions
- Make sure all mods are for YOUR specific version of the OS
- Backup with CWM before every mod.
- Lastly, insure that the phone battery is fully charged before doing any flashing. This will avoid the possibility that your phone will get bricked and then run out if battery b4 u can fix it (bricked phones do not charge).
- Aside from that, as long as u do not have OTA gingerbread 2.3.4 on your phone, don't freak out if u brick your phone. I have done it 9 times in the past month and everytime managed to restore it with RSD Lite.
Finally: IF YOU DON'T HAVE GINGERBREAD 2.3.4 OTA DO NOT UPGRADE VIA THE OTA UPDATE. USE THE FRUIT CAKE METHOD OR YOU MAY BRICK YOUR PHONE NEXT TIME THAT YOU ROOT/UNLOCK IT.
Sent from my Atrix using XDA App
Excellent replies. That makes sense, I just didn't realize it was a legal issue more than technical.
Another quick question. If I used the Motorola PC upgrade to 2.3.4 is it still considered an OTA update since I downloaded the stock from Motorola and upgraded it via PC?
Sun3vi1 said:
- Avoid rooting phones with the OTA 2.3.4
Finally: IF YOU DON'T HAVE GINGERBREAD 2.3.4 OTA DO NOT UPGRADE VIA THE OTA UPDATE. USE THE FRUIT CAKE METHOD OR YOU MAY BRICK YOUR PHONE NEXT TIME THAT YOU ROOT/UNLOCK IT.
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
Huh? you can root just fine with the OTA 2.3.4 using the preinstall method. Works perfectly. If you OTA'd to 2.3.4 you don't ever want to attempt to flash back down to a previous version. You can still root and unlock the phone even with OTA 2.3.4.
The only thing that using the OTA breaks is being able to SBF to previous builds. But you can still use pudding to unlock and use other roms including froyo ones with pudding built in.
I highly doubt it is illegal to root. Where did you hear this?
Google doesn't charge to license Android, and it's their license, AFAIK individual companies cannot do what they want with this license. It remains open source software that anyone can develop for. It's based on Linux/Unix.
Does anyone here even know what rooting does? It is the act of re-enabling the Superuser. A right EVERY Linux distribution should have. Phone or not.
nexxusty said:
I highly doubt it is illegal to root. Where did you hear this?
Google doesn't charge to license Android, and it's their license, AFAIK individual companies cannot do what they want with this license. It remains open source software that anyone can develop for. It's based on Linux/Unix.
Does anyone here even know what rooting does? It is the act of re-enabling the Superuser. A right EVERY Linux distribution should have. Phone or not.
Click to expand...
Click to collapse
Sun3vi1 said "the warranty is a legal agreement". It says that if your phone breaks within a certain period of time they'll replace it, *provided* you haven't modified it in any way. Rooting may or may not be legal in your jurisdiction, but either way it voids the warranty by modifying the phone.
If you only root in a method that allows you to unroot easily enough, there's no problem. Since rooting is not a particularly invasive set of changes, unrooting should not be difficult.
Following is not really a tutorial or manual to be followed without questioning. You need to know what you are doing with your phone by yourself and not follow what others say.
What is safe?
Before all, know what you are doing!!! Processes that may be safe in certain conditions may brick your phone in other circumstances. Don't just flash to get root or some custom FW like you install your market apps. Flashing can go wrong even if everything "should be safe" either because of hardware or software failures/oddities/other factors. So before you do anything with your phone study what you're about to do and what will it give as a result, has anyone had problems with similar process, if there are not safer methods, etc.
Currently one safe way to get root access is by unlocking bootloader and using recoveryNeo.img provided by Bin4ry to install RootXperia.zip. Bootloader can be safely locked after this and only this tweak.
Another safe way to get root is to unlock bootloader and flash custom kernel.
What is not safe?
Since Sony Ericsson Arc 2.3.2 update to 2.3.3 we can observe that phones do get bricked by OTA update.
OTA is very unreliable method of flashing. Via cable you can be assured that connection will not fail as easily. Also files can become corrupted via any network connection. Consider that before you decide in favor of OTA.
OTA is not meant by SE for you to keep your root access. So your using it for this purpose is an unofficial and unsupported tweak. SE may include features and settings in FW that conflict with root access.
Secondly SE seems to have made lot of changes between 2.3.2, 2.3.3 and 2.3.4. If you have unlocked your bootloader and want to root your phone there is absolutely no reason to flash 2.3.2 and then to 2.3.4. These firmwares are so different that mere OTA, which does not perform full erasing and flashing of your Nand memory, is logically not safe practice.
If you have 2.3.3 and rooted then wait till OTA becomes available in your country and then update to 2.3.4. Even this is bad suggestion, given that SE officially does not support root in any of their firmwares, so beware. If your local FW does not have OTA available then you should not get another FW that allows you. Remember, providing these updates needs to be supported by SE. If they don't provide your local FW OTA update then they don't support it in your area and are not liable to damages you may cause to your phone by misusing their services.
Consider what you need more, a working phone or root access or tweaked kernel? You can always wait and maybe later you'll have tested, working and safe methods for rooting and all else.
Good things come over time, with patience, not by rushing.
You make some really good points there.
Sent from my MT15i using XDA App
hi guys, i would like to ask some questions.
as we know, rooting phone void our warranty.
what i'm curious is, if i root my phone, then in case some problems occured, and i need to go back to samsung, can unroot my phone prevent samsung from checking that i had rooted the phone before?
thanks.
Well, I've got a different phone (Sony Ericsson) but I seem to remember that via Chainfire Method you can both get root and install ClockWorkMod Recovery 5, without involving the counter, whereas it shouldn't be si via Odin.
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
there are a lots of guide but everyone say a different method. OK I AM A NOOB OF MODDING.
but is quite difficult to understand guides that are different in this way:
1) some indicates to just use an apk autorooting the device
2) some do require to change thekernel + manually install the superuser apk
3)not permanent root....
4) others......
so, please be patient......:angel: i only want to find a "normal" root method.......and IF POSSIBLE a root that could allow me to easily UNroot the device to be able to update my firmware OTA in the moment samsung will update our great device to kitkat
If you are a noob at modding don't even bother with rooting. Its dangerous and BTW I think your firmware has KNOX which the GMega doesn't have a workaround.
Sent from my GT-I9200 using Tapatalk
realista87 said:
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
Click to expand...
Click to collapse
If you are brave enough you can try it using this tutorial
http://forum.xda-developers.com/showthread.php?t=2574953
But read it thoroughly and if you do not understand one thing though - do not attempt to try.
Read forums and learn till you can understand what you are doing lest you have quite expensive paperweight... I am not responsible for what you do with your phone!
my previous phone was rooter, the optimus 3d and the ascend mate.
i don't need toor for extreme modding but just to install a custom recovery for a nandroid backup and for use SOME APP THAT REQUIRE root to work properly.
i never installed a recovery but i read everywhere that it is a lot usefull in case of some errors, to restore the previous backup made 1:1 (nandroid)
Every modding attempt must start from root and (optionally) custom recovery. In fact - rooting itself is modding and quite heavy from system point of view. If you want to change ONE THING in system, you have to root your phone. Doing this you are tripping 'warranty flag' and from now on your warranty is void.
If you have firmware with KNOX and new bootloader - tripping this flag is irreversible. But as long as you do not attempt to flash older firmware (before KNOX) it does not affect the operation of the system. Trying to flash older firmware makes your phone softbrick because of tripping security mechanism in new bootloader.
If you already rooted your phone it is resonable to flash custom recovery and by this have wide possiblity making backups of your whole system (nandroid backup) or flashing custom ROMs