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 !
Related
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,
I rooted my Z2 tablet a few days ago and have found that I don't really need the advantages it brings (from what I can tell). SO - I want to get it back to the way it was when I first opened the box.
I have seen threads about different devices and how to restore them to factory or stock (??), but they seem to call for specific files or flash software. So that brings me once again to this forum to figure out whether anyone can direct me to some instructions on how to do this. I figure it shouldn't be too hard. Just being careful.
Thanks very much for the advice once again.
I think if you flash the rootable kernel again, you could use an unrooting tool to undo the root. I'm also aware that there are files that you can flash to re-lock the bootloader (I once did this with an Xperia mini pro, although I'm not sure if such file exists for this tablet) but the DRM keys are lost forever a.f.a.i.k. But at least if you manage to re-lock the bootloader you will be able to install F/W upgrades through official ways again.
degraaff said:
I think if you flash the rootable kernel again, you could use an unrooting tool to undo the root. I'm also aware that there are files that you can flash to re-lock the bootloader (I once did this with an Xperia mini pro, although I'm not sure if such file exists for this tablet) but the DRM keys are lost forever a.f.a.i.k. But at least if you manage to re-lock the bootloader you will be able to install F/W upgrades through official ways again. Anyhow, you won't be able to restore to (more or less) factory status without at least flashing a couple of files.
Click to expand...
Click to collapse
THank you for the response. Unfortunately i'm not even sure how I would go about flashing 'the rootable kernel'.... Feeling a bit foolish for getting into this actually.
From what i'm reading, it seems like I need to get the stock software and start again. So i'm looking for the 'FTF' for my tablet, which is a SGP511. Not having any luck though.
Which was the process that you followed to root it?
degraaff said:
Which was the process that you followed to root it?
Click to expand...
Click to collapse
It was on another site - can't remember which. It got the clockwork mod installed. I think? Or was that just a recovery thing? No idea.
I'm actually now just doing a factory reset to see what happens, and it said 'root access possibly lost' in the process, which I thought was a good sign. Guess i'll keep tinkering with enough caution to eventually get the warranty back in tact.
Hopefully the loss of DRM doesn't effect the warranty.
In that case I guess you will have to download a firmware ftf file of an official unmodded firmware (preferably one of your region but I think especially if you have the wifi-only version it doesn't matter much as long as it contains the interface and input languages that you need), and install (or "flash") that using Flashtool. After that the root will certainly be gone and if you could then find a file to relock your bootloader I think your warrenty will be fine. I honestly don't think that Sony service and repair personel will check for DRM keys every time before repairing a device.
UPDATE
Factory reset appears to have gotten things back to normal. My plan is now just to unroot using an unroot tool (app i guess?) and then to lock the bootloader some how as well.
fearofbirds said:
Factory reset appears to have gotten things back to normal. My plan is now just to unroot using an unroot tool (app i guess?) and then to lock the bootloader some how as well.
Click to expand...
Click to collapse
So it's certain that the tablet is still rooted at this moment? Some superuser apps have an option to do a full unroot, such as SuperSU, you could try that
That's great. I think that's sorted it out. SuperSU had the full unroot option and it looks like it's all sorted.
Thanks for the help.
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?
I have my T-Mobile LG V-10 rooted with Sir-Altus rom currently.
Without starting a fight or anything, I am trying to find out how I could go about restoring my phone to stock to be able to accept the Marshmellow update successfully without bricking my phone.
I understand that there is a difficulty in rooting Marshmellow and I am OK with that.
Can anyone link to a step-by-step on how to restore my phone to fully stock so I can accept the Marshmellow update and apply it?
Thank you,
Whiteice
WhiteiceDMSTech said:
I have my T-Mobile LG V-10 rooted with Sir-Altus rom currently.
Without starting a fight or anything, I am trying to find out how I could go about restoring my phone to stock to be able to accept the Marshmellow update successfully without bricking my phone.
I understand that there is a difficulty in rooting Marshmellow and I am OK with that.
Can anyone link to a step-by-step on how to restore my phone to fully stock so I can accept the Marshmellow update and apply it?
Thank you,
Whiteice
Click to expand...
Click to collapse
Should be pretty straight-forward. Also as an FYI, you now CAN root you LG V10 starting from 6.0 (Marshmallow) stock. So there's really not much risk involved. I think the upgrade from 5.1.1 to 6.0 relocks your bootloader so...i don't think you have to do much. If you have an upgrade option in your settings on the phone you can take it or you can go to the LG website and download the software and follow the steps. http://www.lg.com/us/support/mobile-software-updates
Can I accept the update on the phone rooted and with TWRP installed?
"I wouldn't do it by just downloading the update and installing it through the ui", you'll probably get stuck in a boot loop on the lg logo boot screen! Try researching kdz or tot flashing! Youll then only have to click a few times on your PC and after that the file should just upgrade the phone through your USB hub
You can uodate using Eliminater74's Rom.
Flash Part 1 - Dont Reboot
Flash Part 2 - Dont Reboot
Flash Super SU
*in Eliminater74s Rom OP it says to use Fastboot again to OEM unlock. Just read it thoroughly*
Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.