Database Users

sailfish npg05e (7.1.2 beta)

Wiped phone and Clean installed new, sailfish npg05e (7.1.2 beta) update, TWRP RC1 and Newest SuperSU Aroma installer, all is working very well!!

Hi,
I just got my phone the other day from Verizon.
FIrst thing I did was unlock the boot loader and root, was working fine.
Then I saw 7.1.2 BETA was out. I did a fresh install of nmf26u 7.1.1 and updated to 7.1.2.
BUt when I tried the boot-to-root method my phone was soft bricked and had to start all over again.
How did you get root on 7.1.2?
Any help would be appreciated.

nickf1227 said:
Hi,
I just got my phone the other day from Verizon.
FIrst thing I did was unlock the boot loader and root, was working fine.
Then I saw 7.1.2 BETA was out. I did a fresh install of nmf26u 7.1.1 and updated to 7.1.2.
BUt when I tried the boot-to-root method my phone was soft bricked and had to start all over again.
How did you get root on 7.1.2?
Any help would be appreciated.
Click to expand...
Click to collapse
I thought the verizon one if you updated using the official images relocked the bootloader?

Still says it's unlocked when I start it up

nickf1227 said:
Hi,
I just got my phone the other day from Verizon.
FIrst thing I did was unlock the boot loader and root, was working fine.
Then I saw 7.1.2 BETA was out. I did a fresh install of nmf26u 7.1.1 and updated to 7.1.2.
BUt when I tried the boot-to-root method my phone was soft bricked and had to start all over again.
How did you get root on 7.1.2?
Any help would be appreciated.
Click to expand...
Click to collapse
I am have the Google store Pixel. This was my install process
Download factory image
Extract folder
Run flash-all.bat
Setup phone with passcode
Fastboot boot TWRP.img (RC)
Flash TWRP.zip
Reboot to phone
Reboot back to recovery
ADB push latest super user .Zip
Then I had root
Hope that helps

ne0ns4l4m4nder said:
I am have the Google store Pixel. This was my install process
Download factory image
Extract folder
Run flash-all.bat
Setup phone with passcode
Fastboot boot TWRP.img (RC)
Flash TWRP.zip
Reboot to phone
Reboot back to recovery
ADB push latest super user .Zip
Then I had root
Hope that helps
Click to expand...
Click to collapse
So..
I'm lost here. I have TWRP installed.
I downloaded this: https://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
Booted into TWRP.
Installed the zip and rebooted.
Turned my phone on and no root?

nickf1227 said:
So..
I'm lost here. I have TWRP installed.
I downloaded this: https://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
Booted into TWRP.
Installed the zip and rebooted.
Turned my phone on and no root?
Click to expand...
Click to collapse
Did you make sure you were booted into the right slot?

Never mind
Got it working thanks guys

Wrong SU. You need 2.79 SR3

Did anyone try franco or elementalx kernel on this?

I have elemental X installed and so far there is no comparable Kernel released, and I expect this to be the case till 7.1.2 is released

Has anyone went from NPG05E to the new NOF26V - I just did and the home button would not work and developer options were gone. DO I need to go from NMF26U to the new NOF26V?

bturkel said:
Has anyone went from NPG05E to the new NOF26V - I just did and the home button would not work and developer options were gone. DO I need to go from NMF26U to the new NOF26V?
Click to expand...
Click to collapse
Usually when you step down, a clean flash would be recommended.

Yes I flashed with Clean WIpe - what a pain

FYI - Substratum works in legacy mode on this (as expected for a stock rom) however... When using swift black theme, you have to select an os version. Typically on the Pixel you must choose the 7.1_Pixel in order to not have a bootloop, and you still end up with stock system ui. BUT with the NPG05E build, I selected 7.1_OMS within this theme and rebooted. Google has done something wonderful here and allowed (from what i can see) full theme support. System UI is fully themed including notifications. Only thing not themed is the ambient display notifications. Everything else from what i can see is equal to a custom rom with full OMS support.
Lets hope Google continues this trend with future previews and finally the official release!

Anyone else have a broken wifi assistant with this update?
Or maybe it's just the settings. If you go to wifi settings and hit the settings icon on the top right, your settings will force close.

npg05e is the first beta right?

quick quesiton? is this still on the January security update or has it updated the beta 7.1.2 to February security patch?

January
Gesendet von meinem Pixel mit Tapatalk

KevnRobles said:
Anyone else have a broken wifi assistant with this update?
Or maybe it's just the settings. If you go to wifi settings and hit the settings icon on the top right, your settings will force close.
Click to expand...
Click to collapse
Yes this happens to me also. Beta bugs...
---------- Post added at 12:00 AM ---------- Previous post was at 12:00 AM ----------
Sh0X31 said:
npg05e is the first beta right?
Click to expand...
Click to collapse
Yes it is.

Anyone who installed TWRP and rooted on Marshmallow able to update to Nougat?

If so, how? Thanks!

magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.

worked for me perfectly

pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.

Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.

pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.

Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.

What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you

Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?

Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).

mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.

mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.

+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?

mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.

+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.

mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?

mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.

+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,

mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

Welp, I searched, didn't find a relevant answer. XT1625 help wanted.

Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.

Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)

Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.

What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck

superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.

superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.

Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.

impossible to update the April security on nokia 6 ta-1033 UB & rooted

Hello, I have an issue with my nokia 6 ta-1033.
Currently, it's under android Pie, March security update, bootloaded unlocked and rooted with magisk (v19.1) and twrp-3.2.3-0-PLE in custom recovery.
I wanted to do the last update in April.
So I, restarted in download mode
Then, fastboot flash boot boot.img (rom stock android 9.0)
Fastboot reboot
I uninstalled magisk (maybe I shouldn't have)
I started the ota update
The phone restarts but the update is not done, and I arrive in the twrp recovery.
I restart and the phone boot normally but the update has not been done.
The strange thing is that twrp wasn't overwritten by the flash boot.img (rom stock android 9.0)
Do you have any idea where the problem might come from?
Thank you.

boot.img is different with recovery.img,
boot is kernel not recovery

I have proplem with fastboot, that doesn't work latest update. So I go twrp and flash old 8.1 boot image. Now I get fastboot back and then I use nost to get my nokia 6 back on working. After that I just do all the ota updates and I still get have working fastboot. Then just flash twrp and magisk and so on.. If you can, use Migrator to backup you app and data to SD so you can get all your data and files back when finish.
---------- Post added at 10:21 AM ---------- Previous post was at 10:18 AM ----------
arl0ng said:
Hello, I have an issue with my nokia 6 ta-1033.
Currently, it's under android Pie, March security update, bootloaded unlocked and rooted with magisk (v19.1) and twrp-3.2.3-0-PLE in custom recovery.
I wanted to do the last update in April.
So I, restarted in download mode
Then, fastboot flash boot boot.img (rom stock android 9.0)
Fastboot reboot
I uninstalled magisk (maybe I shouldn't have)
I started the ota update
The phone restarts but the update is not done, and I arrive in the twrp recovery.
I restart and the phone boot normally but the update has not been done.
The strange thing is that twrp wasn't overwritten by the flash boot.img (rom stock android 9.0)
Do you have any idea where the problem might come from?
Thank you.
Click to expand...
Click to collapse
Nokia does not wanna let you use fastboot. They blocked that. You need to fool them using old boot image

DoggyStar said:
I have proplem with fastboot, that doesn't work latest update. So I go twrp and flash old 8.1 boot image. Now I get fastboot back and then I use nost to get my nokia 6 back on working. After that I just do all the ota updates and I still get have working fastboot. Then just flash twrp and magisk and so on.. If you can, use Migrator to backup you app and data to SD so you can get all your data and files back when finish.
---------- Post added at 10:21 AM ---------- Previous post was at 10:18 AM ----------
Nokia does not wanna let you use fastboot. They blocked that. You need to fool them using old boot image
Click to expand...
Click to collapse
Oh yes, I had just thought of flashing the .nb0 via Nost as a last resort but I didn't want to have to reinstall everything. I didn't know migrator, thanks

arl0ng said:
Oh yes, I had just thought of flashing the .nb0 via Nost as a last resort but I didn't want to have to reinstall everything. I didn't know migrator, thanks
Click to expand...
Click to collapse
Migrator is the best :good:

frnsl3 said:
boot.img is different with recovery.img,
boot is kernel not recovery
Click to expand...
Click to collapse
So how we can install our April update if we are rooted with magisk? Any idea about it?

I had the same peoblem.
This was worked on nokia 6 ta-1021
1.unstall magisk. (Restore stock boot image)
2.go to download mode
3.flash december stock recovery
4.then reboot into system
5.install update from settings-->system-->update system
6.after software update finished flash twrp as usual. (if u want)
****It will take about 30mins to update*****

cbkottege said:
I had the same peoblem.
This was worked on nokia 6 ta-1021
1.unstall magisk. (Restore stock boot image)
2.go to download mode
3.flash december stock recovery
4.then reboot into system
5.install update from settings-->system-->update system
6.after software update finished flash twrp as usual. (if u want)
****It will take about 30mins to update*****
Click to expand...
Click to collapse
Stock recovery fromDecember 2017 security patch? And will it able to boot Normally after flashing December security patch recovery ? According to me after flashing December 2017 stock recovery it won't boot ..
Can you please elaborate the whole procedure how you did it exactly .
It would be great for me .

Emmykay223 said:
So how we can install our April update if we are rooted with magisk? Any idea about it?
Click to expand...
Click to collapse
I just do it. I have latest update and magisk installed.
You need to flash that old boot image backing 2018. Then you need to use nost.
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
Emmykay223 said:
Stock recovery fromDecember 2017 security patch? And will it able to boot Normally after flashing December security patch recovery ? According to me after flashing December 2017 stock recovery it won't boot ..
Can you please elaborate the whole procedure how you did it exactly .
It would be great for me .
Click to expand...
Click to collapse
No it won't. But you get working fastboot, and then you can use nost to get back everything.
---------- Post added at 05:01 PM ---------- Previous post was at 04:53 PM ----------
This is how I get it work.
First go twrp and then flash that old boot image backing 2018. Then you get working fastboot.
now read my another instructions how you can do it.
https://forum.xda-developers.com/nokia-6/how-to/how-to-unbrick-nokia-6-ta-1021-1033-t3927332
I do it like this and there is no proplem at all

Emmykay223 said:
Stock recovery fromDecember 2017 security patch? And will it able to boot Normally after flashing December security patch recovery ? According to me after flashing December 2017 stock recovery it won't boot ..
Can you please elaborate the whole procedure how you did it exactly .
It would be great for me .
Click to expand...
Click to collapse
this is maybe you flash december 2017 update, then flash stock nougat and you booting in system.
so you can use OTA update again, but all data will be formatted

frnsl3 said:
this is maybe you flash december 2017 update, then flash stock nougat and you booting in system.
so you can use OTA update again, but all data will be formatted
Click to expand...
Click to collapse
Yes all data go, but use titanium Backup before that.
I explain procedure my messages here. It's works :good:

cbkottege said:
I had the same peoblem.
This was worked on nokia 6 ta-1021
1.unstall magisk. (Restore stock boot image)
2.go to download mode
3.flash december stock recovery
4.then reboot into system
5.install update from settings-->system-->update system
6.after software update finished flash twrp as usual. (if u want)
****It will take about 30mins to update*****
Click to expand...
Click to collapse
I think I'll look into it tonight.... I found the June 2018 ota (there is a recovery file in it) I will test the flash later...

arl0ng said:
I think I'll look into it tonight.... I found the June 2018 ota (there is a recovery file in it) I will test the flash later...
Click to expand...
Click to collapse
You can get it, I get it too :good:

arl0ng said:
I think I'll look into it tonight.... I found the June 2018 ota (there is a recovery file in it) I will test the flash later...
Click to expand...
Click to collapse
It didn't work for me, I have flash the full firmware nb0 with nost

arl0ng said:
It didn't work for me, I have flash the full firmware nb0 with nost
Click to expand...
Click to collapse
Okey, I flash with nost too.
But you get it work? Working twrp and latest magisk??

Here

DoggyStar said:
Okey, I flash with nost too.
But you get it work? Working twrp and latest magisk??
Click to expand...
Click to collapse
Yep it work twrp and magisk
But method 1 for install twrp doesn't work for me.
Method 2 (patched boot ) work
Envoyé de mon TA-1033 en utilisant Tapatalk

arl0ng said:
Yep it work twrp and magisk
But method 1 for install twrp doesn't work for me.
Method 2 (patched boot ) work
Envoyé de mon TA-1033 en utilisant Tapatalk
Click to expand...
Click to collapse
Okey, but you get it :victory: it's a main thing

DoggyStar said:
Okey, but you get it :victory: it's a main thing
Click to expand...
Click to collapse
Yep[emoji16]
Envoyé de mon TA-1033 en utilisant Tapatalk

I installed nokia extensions on magisk. There is a Nokia updater function, has anyone ever tried it?
View attachment 4757810
Envoyé de mon TA-1033 en utilisant Tapatalk