Phew. Thanks to some very good help, I have unbricked my Mate 10 Pro. I bricked it last week after it froze up from a Magisk update and I kept messing with it too much.
So now it is back to life and running BLA-L09 8.0.0.148(C432). Previously it was 8.0.0.137(C34). C432 is not branded or bloated and looks a heck of a lot prettier booting up.
I have just rooted, put on TWRP, and rooted with Magisk. So it is basically how I want it. It is over a year since I last did any of this kind of stuff as it has simply been running the way I like it.
It has been prodding me to update to 8.0.0.150. I don't mind redoing TWRP etc again, but I have this memory that if you go too high with the build number, you can no longer TWRP or root, due to a security update.
Am I remembering right? How high can the version number go before it screws up?
Related
Has anyone received thus OTA yet? Google posted the images for 5.1.1 online 29 days ago, but I haven't received it yet.
Germany lte version using 5.1.1 since ca. 2 weeks or so
Translated with my own brain to English
I still have not received the Android 5.0.2 update to upgrade
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
stock not rooted lte nex 9 -- received the ota to 5.1.1 over two weeks ago i think - los angeles
swcampbell said:
I still have not received the Android 5.0.2 update to upgrade to Android 5.1.1
I have a Nexus 9 LTE that I purchased from Google. I have emailed many times. Disappointing.
Click to expand...
Click to collapse
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
DonDerham said:
Where did you email? I called them and got double-talk. So, I'll email them. It probably takes X number of calls/emails from disappointed customers before they bother to look into it.
I never got 5.02. When I initially booted the device last December, it automatically OTA'd 5.01. I was hoping I'd get an OTA that would take from to 5.1.1 from 5.01.
Click to expand...
Click to collapse
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Guys, this is XDA. It's pretty easy to update yourself with the factory image. No need for the ota. Just flash the bootloader, system and boot images. No lose of data either.
Click to expand...
Click to collapse
No loss of data assume the bootloader is already unlocked. In my case, it's still locked. Obviously, I can back up everything and flash, but part of the reason for buying a Nexus device includes prompt OTAs.
The device downloaded and installed 5.0.2 without a hitch. On reboot, it downloaded the 5.1.1 OTA, but errored on installation. I cleared the cache, rebooted and it repeated the process with the same error result. Nexus tech support, when they hear OTA, pretty much say "we know nothing."
So, I'll backup the device as best I can, do a factory reset and try the OTA again.
Now, I can unlock the device and ADB the images manually. Why not do so? You'd have to be married to understand. This is my wife's tablet. If I unlock the bootloader or root it or do anything other than "normal" Google stuff and anything ever goes amiss, my lovely wife will complain that my tinkering has caused her Candy Crush and Facebook to malfunction.
Before I begin, I would like to make it very clear that this is all very new to me. I have been researching this for quite a bit and read/followed quite a few guides. Most seem to not fit the OH7 version though.
The phone;
Model: SCH-I545PP
Version: 5.0.1
Build: LRX22C.I545PPVRUAOH7
Rooted with kingroot 4.5.0 and cleaned with Super SuMe Pro.
I have had to root this phone 7 times after 6 soft bricks, been at this for days. So I have rooted for the 7th time and stopped to hopefully acquire some help here. I know this phone has a locked bootloader so I have tried to work around that by deodexing to acquire Xposed. After pulling the system with the app, priv-app and framework folders, I used Lordroid's deodexer tool. Followed his guide as well as I can and received no errors in the process.
After putting the flashable zip onto my phone, I attempted to flash using flashfire from the app store. I can link the guides I used if needed. But all attempts landed me at the verizon splash screen. Waited 30 minutes on one attempt then just shut it down and went back to stock. So that is as far as I have gotten.
At this point, I am unsure if there is something I am missing or is this just a lost cause? I am thankful for any help there is to offer.
I got a notice today saying that my nook needs to be updated. Apparently they are forcing TLS 1.2 and a firmware update is needed to do so. Being the update file is 278mb this is the whole ROM not just the TLS update (v1.4.4 now).
Anyone installed this and will the old rooting tools still work? I am 98% certain they won't as B&N has always tried to block such access. Is anyone still around willing to update the tools? Or even have devices to do so?
I personally still like my NT, and it does all I need from a tablet at the moment (once I rooted it and installed a different launcher that is). I *think* I disabled OTA back when I rooted, but I am not 100% certain on that. Is there a easy way to check?
I have thought about doing other ROM's but never got around to it since this still meets my needs (reading, and a couple of simple games, and email/newsfeeds).
Updated, rooted using old tools for 1.4.3, flashed nougat, works fine.
Oh COOL. I guess they didn't bother changing anything more than the TLS. Glad to see. Now I just need to dig up my old microSD and get this done lol.
Probably will do a nandroid backup beforehand just to be safe. I have a lot of customizations I don't want to lose lol.
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 !
Coming from a rooted Oneplus 3t.
Should I unlock the bootloader in case I'd want to root it down the road?
The biggest reason stopping me from rooting is the hassle to flash OTA updates.
If I unlock the bootloader now, rooting in the future won't require a factory reset. Is that right?
Main reason to root for me would be Adaway/minminguard, etc. Are there other uses of rooting which outweigh the hassle of OTA updates?
I just recently purchased a Moto G Power, and I was a little hesitant at first as it seems there isn't a lot of activity for development on the forum yet. However during my investigation, there is a fair amount of people who have recently obtained the device as it's newer, and the information that was provided is extremely helpful. I decided to take the plunge because I was determined to get the hotspot functionality working that is blocked through my carrier (Sprint), and once I completed all of the steps, I realized how easy it was. Many have reported no issues unrooting, updating, and rerooting their devices, and Magisk makes it extremely easy.
i was one of the first to get the device, and it took some time to get used to android 10 rooting process and updating ...
if i see the "update" notification, i think ... ah here we go again, i have to plan that, but
it actually only takes about 20 minutes to do the entire unroot --> update --> reroot thing
so it's a "minor inconvenience"
so why not root straight away?
BTW , your statement is correct, you don't need to wipe for root, but it does get whiped at bootloader unlock,. so do that straight away and save the hassle of losing your config/ apps/data
edit:
did the latest update today ( ...124-2 ) with the July security patch
total time ( including 15 minutes waiting for the update to install) was 30 minutes
You can flash full ROM instead.
Grab full ROM from LMSA and get boot from there and regain root.
OTA is not a big deal