7.1 bricked by an official security update - Nokia 7.1 Questions & Answers

Hi! A friend got his 7.1 bricked, by the update v3.54h (July security update)
If he recover his phone, can he skip the update? Or he's never gonna recieve another update (android 10 for example) till he install that one?

ushoda said:
Hi! A friend got his 7.1 bricked, by the update v3.54h (July security update)
If he recover his phone, can he skip the update? Or he's never gonna recieve another update (android 10 for example) till he install that one?
Click to expand...
Click to collapse
i Had this same issue,once. Only option now is to send the phone to service centre, they’ll restore the phone. After that you can install the update like usual.

i have the same Issue since the latest Update, is there a way to get the .key File for unlock the bootloader anyway without install the apk from nokia?

pumpk1n86 said:
i have the same Issue since the latest Update, is there a way to get the .key File for unlock the bootloader anyway without install the apk from nokia?
Click to expand...
Click to collapse
Nope. no official unlock method from nokia. you must go through techmesto or through hikari calyx via a paid service. PSA: If your phone is prone to getting stuck in download mode after an OTA update, it will probably be the best 8$ you spend to restore your phone yourself without having to send in to customer support.

Related

Can't Update LG L70 After Root?

I successfully rooted my LG L70 with towelroot, but I have a problem now. I can't update the software on my phone from ms32310b to ms32310c. It downloads, reboots and appears to install and says system is up to date, but it's still at ms32310b and a couple days later says I need to download the update again. Will it not update because my phone is rooted now with towelroot? Does anyone know how I can maybe force the update so I can stop getting these update notifications? Thank you!
I seem to have this same problem but my phone is the ls740
lil-g-gamegenuis said:
I seem to have this same problem but my phone is the ls740
Click to expand...
Click to collapse
I guess we have to use lg flash tool to manually flash the KDZ update file, but I'm not sure if updating will unroot the device since the new version in my case doesn't support root.
well on my phone i have CWM so i could probably find a zip to flash
bogarty said:
I successfully rooted my LG L70 with towelroot, but I have a problem now. I can't update the software on my phone from ms32310b to ms32310c. It downloads, reboots and appears to install and says system is up to date, but it's still at ms32310b and a couple days later says I need to download the update again. Will it not update because my phone is rooted now with towelroot? Does anyone know how I can maybe force the update so I can stop getting these update notifications? Thank you!
Click to expand...
Click to collapse
if you root your phone mostly you do not get ota updates and if you get one and install it you lose root
Crom4rtie said:
if you root your phone mostly you do not get ota updates and if you get one and install it you lose root
Click to expand...
Click to collapse
This is absolutely correct. I rooted my LGMS323 with Towelroot (which worked beautifully I might add) but weeks later made the terrible oversight of approving an OTA update without thinking which nuked the root. I've been stuck ever since. Once you update to MS32310c there is NO EASY WAY of rooting your device (as of yet). The only way to reroot is to start over and downgrade from (c) back to (b) or (a) by flashing the KDZ as you mentioned. Because I'm without a machine at the moment and unable to do this I'm TRULY stuck. Don't be me! Stick with what you've got!
jaydeedub said:
This is absolutely correct. I rooted my LGMS323 with Towelroot (which worked beautifully I might add) but weeks later made the terrible oversight of approving an OTA update without thinking which nuked the root. I've been stuck ever since. Once you update to MS32310c there is NO EASY WAY of rooting your device (as of yet). The only way to reroot is to start over and downgrade from (c) back to (b) or (a) by flashing the KDZ as you mentioned. Because I'm without a machine at the moment and unable to do this I'm TRULY stuck. Don't be me! Stick with what you've got!
Click to expand...
Click to collapse
Thank you! I probably will. Unless of course they come out with a stable Lollipop rom, then I might be tempted to install Clockworkmod and check it out.

[Q] 5.1.1 OTA for the LTE?

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.

march update

has anyone lost root updating to current this month? i know my v10 became an ad filled, stock navbar, paper weight after it's last forced update.
I'm curious about this as well.
I finally got around to rooting my Stylo 3 Plus for the first time over the weekend, after closely following the developments in this forum for the past 6 months. It took a lot of trial and error and reflashing of TWRP before I got the timing down right, but I finally got it rooted (using Magisk 15.2).
And of course, luck would have it that within a few hours of my rooting success, a new system update notification (which I had never heard of until now!), pops up and asks me to restart to install it. I am using Titanium Backup to force stop the particular Google service involved, which makes the notification go away and I can reboot without it upgrading. But it always come back within 24 hours or so.
Has anyone installed this update yet (MP45010f) and successfully re-rooted? I'm currently using Magisk 15.2 with systemless hosts, Ad-Away, and Xposed with Greenify & MinMinGuard enabled. I would welcome any advice on how to proceed after the update to restore root and continue using Ad-Away, Xposed, etc. Or even how to disable the update notification for good so I can stay on MP45010e a while longer.
eliaslear said:
has anyone lost root updating to current this month?
Click to expand...
Click to collapse
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
yeah thats what i did was revert back to stock so u can update then i update it then re rooted my phone
if you update using the LG Bridge computer program, it will update a rooted phone. but you will need to reroot afterward.
joetbd said:
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
Click to expand...
Click to collapse
Thanks for testing this out. If you don't mind me asking, which method do you use to root? And do you also use Xposed?
To anyone else who might know, does everything Magisk- or Xposed-related get removed by the security updates (frameworks, modules, configs, etc)? Just trying to get an idea how many of my modules I should expect to reinstall and configure from scratch if I decide to update from 10e to 10f.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
Yeah, I thought this was kind of weird too. I've never used LG Bridge to update. The notification just appeared on my phone shortly after rooting.
Is Xposed only for Magisk or can it be used on the rom, if so can I get a link to how to do so
LG Bridge
DM.IDOL said:
root?
Click to expand...
Click to collapse
Im using Magisk 16.1 (no Xposed) and TWRP 3.2.1
I have not run into any issues.
It appears to simply be a security patch update.
I doubt it should cause any new headaches.
The original method still works to reroot and reinstall TWRP.
Using the LG Bridge program is about as easy as an update can be. You install it on your computer, plug your phone into the computer, and click "update" on the computer program. Its all automatic.

Bricking with an OTA ?

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 !

T-Mobile 10.0.40 update released

Surprised I haven't seen any posts. 10.0.40 landed on my phone on Oct 28th. Only change is the October security update.
Hello
After rooting my Mclaren, I can't do any more system updates. Does anyone know how I can do it?
Best Regards
FilFire said:
Hello
After rooting my Mclaren, I can't do any more system updates. Does anyone know how I can do it?
Best Regards
Click to expand...
Click to collapse
You need to restore the boot image back to stock. In Magisk Manager, select uninstall and select restore images. Then reboot and try again. Howerver, depending on what method you used to root, it may not be able to restore the factory boot image. In which case you'll need to find it online.
Seems very skippable lol. Certainly not worth the effort of unrooting and rerooting.
Mine was rooted and had .35 on it. This popped up on mine too and I was able to do OTA upgrade. Not full and lose my data. Happy here
The only change was October security update
Do you have to run the OTA fixer every time there's a new OTA?
RypeDub said:
Do you have to run the OTA fixer every time there's a new OTA?
Click to expand...
Click to collapse
nope. just once after bootloader unlock
adit07 said:
nope. just once after bootloader unlock
Click to expand...
Click to collapse
Ok, so I have the update waiting to be installed, and I've ran the fixer in the past after a bootloader unlock:
What is the process to update now? Lol do I need to do anything with Magisk?
I think my phone failed to install it, or I just never tried yet cause I'm stupid and still trying to learn all this properly.

Categories

Resources