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
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.
So I have a completely original Neo, still on the on the original Gingerbread (2.3.3) it had and I don't quite know how to proceed.
The only thing I do know is that if at all possible I don't want to unlock the bootloader.
Ideally I want to back everything up before I do anything but from my understanding Titanium Backup needs root to back everything up so that creates a bit of a catch 22. Similarly installing CWM so that I can access recovery is risky and could break everything so I'd want a backup first but for that I need either root or recovery so another catch 22. So what would be the safest option?
Also I want to update to ICS, I figure it's about time I get my phone current, but I don't know in what order I should do that in either...
Should I gingerbreak my Gingerbread and then update to ICS?
Should I just update to ICS and then root?
Should I upgrade using generic firmware to a version supporting the zergRush root, then root and then continue updating to current ICS?
I'm fairly confident I can get everything right first time on any method (and I know what all the methods are/am to not to lazy to research the methods myself) but I just can't figure out the safest course of action here...other than staying on Gingerbread for the duration of my phone contract.
Any help you can give me is appreciated.
Start by reading the stickies in the development section, do some reading and you'll know
look at the stickies in neo v section too
Ok so you're saying I should follow the "noob's guide" exactly and try a zergRush Root first? (Skip unlocking the bootloader since it'm not interested in cutoms roms with custom kernels) and then install CWM and make a nandroid backup?
Ok....but that still doesn't tell me whether I should update first or root first?
Also I can't seem to tell from it's thread whether the zergRush root works on the latest ICS (I don't see mention of .431 in the thread with .62 apparently being the last version that worked so that would be a no then?)?
Also my case is different because I could actually even still root with Gingerbreak if that was best/safest unlike most people trying to root (I never downgraded either so I wouldn't be exposed to the 0% issue).
ZergRush method doesn't work on fw's after .42.
There is another method, which you can find in sticky thread in general section.
First update, then root, as root is gone after flas/update.
p.s. whatever you do, just don't flash android 2.3.2 on your phone after you flash 2.3.4, but there is no really point in going to that old fw, same as there is no point in still being on 2.3.3.
Root is only gone if I don't update OTA
SCHUMI_4EVER said:
Root is only gone if I don't update OTA
Click to expand...
Click to collapse
Really? Thanks for telling me that..
I know that, I also know that you can't update from 2.3.3 to 4.0.4(which you said it's your initial goal, in your first post) via OTA. Or you can?
As far as I know I can but I admit I haven't checked yet. I don't see why once it's available for my region through the PC Suite it shouldn't also be available OTA.
Try and let us know.
It's not same if you're updating from x.x.x to x.x.y and from x.x.x to y.y.y, in first case OTA is possible, in second case I kinda doubt
I also didn't try, but if I remember correctly that's how it is.
Yeah but surely it should then just be 3 steps? So from x.x.x to x.x.y to y.y.y...that would would make sense to me anyways
Still reading up on a bit of other stuff then I'll check
http://forum.xda-developers.com/showthread.php?t=1973017
hope it helps..
Hey guys, I've currently got some wifi issues that I believe are firmware related, I've currently got 17.1.1.A.0.402 but would like to revert back to 17.1.A.2.36 ideally without having to factory reset my phone, I'm also not sure it would go back to 17.1.A.2.36 even if I reset it, I didn't note what firmware it had before I upgraded the firmware so it might take it back to an even earlier version ideally I just want to step back one firmware update but I'm not sure if this is possible? I noticed there's an option on PC companion to reinstall all the updates again although I don't know if you can choose which updates to install or whether it'd just install all the updates so far including 17.1.1.A.0.402 which would be no good. It also said I would lose all my phone data which is not ideal. I was considering rooting my phone and getting an older firmware installed then but tbh I don't really have a lot of knowledge on the subject and I'm not sure if that's even possible. If anyone could help help me out that would be great, even if it's to conform that factory resetting is the only option as ideally I don't want to lose all my data
If you're simply looking to root the device at the .402 firmware, then have a look at this thread. I personally did the same steps on my international D6503, and now have root access, my own TA backup file, PhilZ + TWRP recovery modes, and a locked bootloader. Originally my intent was to downgrade firmwares and us a root exploit that way, however, the 'EasyRoot' method has saved a lot of trouble and my firmware version has not needed to change at all.
That said, if you're still adamant about rolling back firmwares, I'd suggest that you have a look here. Norti has posted a fairly comprehensive set of instructions, as well as a list of firmwares for different versions of the Z2. Although I haven't rolled it back, I have heard that using flashtool to jump to different official firmware versions will not wipe data if you choose to not select WIPE USERDATA, since they're performed in a way that is similar to OTA updates (might need confirmation on this one). Some of the posters in that thread have claimed that as long as your device matches the firmware, loading up a different region's firmware shouldn't have any detrimental affects (i.e. an international phone using Taiwanese/German versions), but that's another piece of information I can't confirm since I haven't tried it.
TL;DR you don't have to change firmware to root, but you can if you really want to. Neither method should touch your SD card, and flashtool should be able to choose what should or should not be wiped.
1740
First of all thanks for the informative response! I tried resetting my phone anyway and it already had 402 installed at stock so unfortunately I can't do it that way, I think I'll try rooting my phone now as I've wanted to do it for a while and I might as well now seeing as I basically have a fresh phone with nothing installed on it. I think I'll follow this guide since I already have an unlocked bootloader: http://forum.xda-developers.com/showpost.php?p=53220418&postcount=2 However I was wondering when I can flash the older firmware, would it be during of after I've rooted my phone?
Hi!
I have the SGP311 with the 4.2.2 Version of Android. Back then I rooted it using the tool VRoot (i think that was the name).
As all I wanted was root for TiBackup I left it at that. Stock ROM, some modifications through root access, but I saw no need to go further.
I would now like to update. OTA does not work, either because I am root or because the bootloader unlock (which I think happened during the root process).
There are so many guides out there, some contradictory or rather relying on going from certain versions to the newest.
What is my best bet?
Unroot and Relock, OTA update, then re-root? Is there a Guide to that?
Or how do I get a recovery on there easily? Guide?
Then assuming I have recovery on, what do I flash. Sony has grown on me, so I am happy with a stock rom or something very close to it, if I can root it for my mods.
What is the least dangerous way to get this tablet up to date?
Thanks for your help!
Walter_White said:
Hi! I have the SGP311 with the 4.2.2 Version of Android. Back then I rooted it using the tool VRoot (i think that was the name). As all I wanted was root for TiBackup I left it at that. Stock ROM, some modifications through root access, but I saw no need to go further. I would now like to update. OTA does not work, either because I am root or because the bootloader unlock (which I think happened during the root process). There are so many guides out there, some contradictory or rather relying on going from certain versions to the newest. What is my best bet? Unroot and Relock, OTA update, then re-root? Is there a Guide to that? Or how do I get a recovery on there easily? Guide? Then assuming I have recovery on, what do I flash. Sony has grown on me, so I am happy with a stock rom or something very close to it, if I can root it for my mods. What is the least dangerous way to get this tablet up to date? Thanks for your help!
Click to expand...
Click to collapse
Vroot would not have unlocked the tablet's boot loader, so are you sure it is unlocked? And have you tried using Sony PC Companion to update the firmware? I was going to recommend trying to use Sony Mobile Update Service, which I preferred over PC Companion, but it appears Sony stopped supporting it.
Hi !
I just got a brand new Mate 10 Pro, and managed to get a bootloader unlock code since I haven't updated the phone yet. I plan on unlocking it and then updating it to the latest version of Android.
I spent quite some time trying to figure out in which cases the device could brick, but since it seems that it can brick pretty easily I haven't found a complete answer.
Eventually, I would like to know if there a risk of bricking the device when updating with the official OTA after unlocking the bootloader ? I know that every bit of tinkering could potentially brick a device, but I have not found a similar case to this one. This is not totally related, but I also plan on rooting the device with Magisk once I successfully update it so feel free to tell me if there is something I should be aware of.
Thanks a lot XDA !
Unlocking
Pouni said:
Hi !
I just got a brand new Mate 10 Pro, and managed to get a bootloader unlock code since I haven't updated the phone yet. I plan on unlocking it and then updating it to the latest version of Android.
I spent quite some time trying to figure out in which cases the device could brick, but since it seems that it can brick pretty easily I haven't found a complete answer.
Eventually, I would like to know if there a risk of bricking the device when updating with the official OTA after unlocking the bootloader ? I know that every bit of tinkering could potentially brick a device, but I have not found a similar case to this one. This is not totally related, but I also plan on rooting the device with Magisk once I successfully update it so feel free to tell me if there is something I should be aware of.
Thanks a lot XDA !
Click to expand...
Click to collapse
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
revjamescarver said:
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
Click to expand...
Click to collapse
There are multiple sources for valid unlock codes, though all are paid. (OP probably used DC as he said he didn't update phone yet)
Rooting does not disable OTA. You will still receive them. Only problem is installing them... It should go fine if you flash back stock ramdisk and recovery_ramdisk, this will remove both Magisk and TWRP.
However, if you have modified any other partition it may not install anyway, in that case you can try going to menu in System Update and select Download latest full package. This would install FullOTA rather than regular OTA.
Or you can use HuRUpdater to install firmware using TWRP.
One way to hard-brick right now is to downgrade from a firmware using new bootloader to one using old bootloader. This will give you a black screen.
ante0 said:
There are multiple sources for valid unlock codes, though all are paid. (OP probably used DC as he said he didn't update phone yet)
Rooting does not disable OTA. You will still receive them. Only problem is installing them... It should go fine if you flash back stock ramdisk and recovery_ramdisk, this will remove both Magisk and TWRP.
However, if you have modified any other partition it may not install anyway, in that case you can try going to menu in System Update and select Download latest full package. This would install FullOTA rather than regular OTA.
Or you can use HuRUpdater to install firmware using TWRP.
One way to hard-brick right now is to downgrade from a firmware using new bootloader to one using old bootloader. This will give you a black screen.
Click to expand...
Click to collapse
The plan is to update to a stable and recent version using OTA (from BLA-L29 8.0.0.120(C432) to BLA-L29 8.0.0.157(C432)-FULL) and then root this version. Once I have root on this latest version, I plan on using it as long as the phone works, so updating to newer versions in the future and risking to brick the device shouldn't be a problem. I just want a functional root with a decent version of stock EMUI. Would updating from stock locked 120 to 157 and then unlocking + rooting be safe ? Thanks for the valuable info !
revjamescarver said:
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
Click to expand...
Click to collapse
I used DC Unlocker since my device was still on an old version, as Ante0 said ! I think that if I ever want to update, I'll remove root (getting back to stock) and then update with OTA. Thanks for the warning, I haven't rooted nor unlocked a device since 2 years and things have changed with the new methods (Magisk etc...).
Pouni said:
The plan is to update to a stable and recent version using OTA (from BLA-L29 8.0.0.120(C432) to BLA-L29 8.0.0.157(C432)-FULL) and then root this version. Once I have root on this latest version, I plan on using it as long as the phone works, so updating to newer versions in the future and risking to brick the device shouldn't be a problem. I just want a functional root with a decent version of stock EMUI. Would updating from stock locked 120 to 157 and then unlocking + rooting be safe ? Thanks for the valuable info !
Click to expand...
Click to collapse
Yes, that should be fine. You could just unlock bootloader right away and then update, if you wanted to.
Just be cautious, do not downgrade past B146 on C432 (if you ever plan to downgrade), that was the first build with the new bootloader so going to B145 or lower will result in a brick.
ante0 said:
Yes, that should be fine. You could just unlock bootloader right away and then update, if you wanted to.
Just be cautious, do not downgrade past B146 on C432 (if you ever plan to downgrade), that was the first build with the new bootloader so going to B145 or lower will result in a brick.
Click to expand...
Click to collapse
Thanks again for the valuable information. Now I'm debating whether I should unlock now or after the update I don't plan on downgrading, except if I have problems after updating and HAVE to downgrade. Last question if I may: I plan on using Magisk (latest version, I guess) to root once I update to BLA-L29 8.0.0.157(C432)-FULL. But I've seen that Magisk/TWRP doesn't necessarily work on the latest versions for some people when using the "basic" way of installing it, I tried to search for an up-to-date guide to rooting but didn't find anything, is the "old" way still good ?
Edit: When I said "basic/old" way of installing Magisk, I meant that it seems impossible to get it to work by installing TWRP and flashing Magisk through TWRP, but that it seems to work by finding a patched "ramdisk.img" with Magisk. Is the latest option a reliable way to get root on BLA-L29 157(C432), considering that I would not have TWRP to restore a backup if using this method ?
Edit 2: Tried the usual way (flashing Magisk zip through TWRP) and it seems to work ! Thank you !