Related
Can someone walk me through how to Unlock the bootloader, root, and install TWRP? I'm so confused. I tried to do the newbie way, even though I'm not a newbie, and I lost my B29 Stock Recovery and can't find the download for it.
Sent from my ZTE A2017U using Tapatalk
I haven't done it yet but I've done a lot of reading and this seems to me the best guide.
Head over to this link which is the TWRP thread. https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
Once you're in there go to bootloader unlock section. Download all the necessary files and on the bottom of the guide there will be instructions link which will take you here https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
Follow that and that should do it.
When i get a weekend off ill be using this method to get the Lineage OS 14.1 on my device.
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
amphi66 said:
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
Click to expand...
Click to collapse
greatzt said:
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
Click to expand...
Click to collapse
This was back last Nov, but I followed the guide, using the recommended files (was on B29, but used the B27 OK, then reflashed B29 at the end).
The warning involved backing up and then restoring the EFS partiton with tenfar's tool. DON'T! If you stick with system, data, and boot partitions you should be fine.
Good luck. You may want to check with @nolimit78. He has done this much more recently.
Yes, I agree with you @amphi66 that there is a lot of different places to get information about how to root/flash recovery for A2017U B29. Here's what I've done with two different A7's and both have worked each time.
1. Boot the phone to EDL Mode (Both Vol+Power on boot it'll quick flash the red notification light and then act like it's off.. it's not)
2. Use tenfar's tool to flash the recovery. (I renamed the updated TWRP img and named it "recovery". This used tenfar's tool to flash the updated TWRP on your device.
3. Once in TWRP, run the command (reboot disemmcwp and relaunch TWRP) and flash the package to use modifiable bootloader from B20.
4. Once that flashes now you can send the command in Fastboot "fastboot oem unlock" which will unlock the bootloader that doesn't trip anything notifying ZTE
5. At this point you can flash a B29 rom and have a grand ol' time. However, I would recommend using the LineageOS Rom that's available. Trumps everything else out there IMHO.
6. To do that You'll need to flash the Nougat Bootstacks for that rom to boot prior to flashing the Rom itself. I would recommend flashing the nougat bootstacks, reboot to TWRP, flash LineageOS, reboot.
Like I said, I've done with this with two different devices (Thanks ZTE) and both worked out just fine. I did this method with a device with b27 and b29, both ended up updated and flashed with CM/LineageOS with ZERO issues. This post here should also be pinned as the one true guide (THE KING OF THE NORTH) for unlocking/rooting a stock Axon 7. I spent probably about 4-5 hours working, trying to figure out how to get my device unlocked/rooted. However.. at the very end I wrote out instructions trying to help those who would come after me.. I searched the threads to make sure there wasn't already a thread out there.. and then.. it turns out there was.
Someone have the 5 files to unlock the bootloader 2017u on drive
Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..
OK Please note (4-25-17) this message is a work in progress, as I slowly restore my system.
This is a listing and hopefully helpful listing of what I did (right and wrong)
in upgrading my Systemless-rooted (suuser) phone from 6.01 to 7.00 (nougat)
# 1. it did not work, and I went back to 6.01 successfully using the twrp recovery
I have previously used Bender's guid (here) to get the system-less root on 6.01.
essentailly, here's the best plan. Use the Minimal ADB and Fastboot package (MADB &F) (here)
(Explanation: the MADB&FB package will allow you do do LOTS of stuff related to updating your phone, with very little grief.)
it also includes the ability to automatically "push" a package over your usb connection if the ZIP file doesnt load right. **THIS will come in handy later!
Once MADB&F is installed, make note of your directory, and then make sure you start your dos window (for pc users) as an administrator!
BTW, if I HADN'T made the "TWRP backup" of my system, I'd be Sh*t out of luck right now...", because I screwed up the 7.0 upgrade.
the technical problem was that I had no data, no modem, no way of getting data/voice in/out.
SIMPLY using the TWRP restore fixed me!!!
(so far, we have MADB&FB, downloaded and bender's (chainfire) rootless guide.
Next you want to download the current firmware image for your phone. This will be a lifesaver, I promise!
3) Download a TWRP image (this will MAGICALLY load on your pc when you tell it you need help! Look HERE
(Athene is the Motorola Codename for the motoG4+)
3) copy the athene TWRP image into your madb&FB directory to make it easy to load
4) next, (you still haven't touched your phone yet, you realize: (skipping some basics here, you can search here on XDA to find more info)
a) plug your phone into your pc
b) make sure you are a developer
c) make sure your phone shows you are connected to your pc for file transfers, NOT for charging
5) in your MADB&FB directory, (aka a dos/(admin) window) type the following:
all commands at this point will take place in whatever directory you installed Minimal ADB & Fast boot (MADB&FB)
Connect your phone to your PC and open MADB&FB, check the connection with:
adb devices
return should include your "serial-no" and "device".
6) next, on pc, tell the system to reboot your phone to the bootloader!
Reboot into bootloader with:
adb reboot-bootloader
and check again with:
fastboot devices
7) Next you are going to download TWRP to your phone (not permanently, just for a bit!)
fastboot. flash recovery twrp-3.0.2-0-athene.img
Now you have TWRP (Team Windows RECOVERY PROJECT) loaded.
SO.. THIS is where you create a backup of your current stuff using the backup options.
NEXT:
take the suUser2.78 (stateless rooting), and once your backup is done, install it from TWRP
Then (I was) back to 6.01 rooted.
NEXT: 7.0 and then rooting... (will update tomorrow)
did a successful upgrade to 7.0,
then unsuccessfully tried to sideload supersu2.78, which bricked loader
then downgraded again to 6.01 (and rooted again, ok)
will continue tomorrow.
need working phone for now..
cheers to all, and to all, a happy spelunking!
You can't root factory Nougat as is, it is well encrypted.
You need to replace first the kernel with the ElementalX one, or you will end up with bootloops.
Only after that you can do SuperSU, but only with the latest beta.
A few pointers from your story:
1)As you've found out the hard way, you won't be able to update to Nougat if you have root and/or TWRP, because the update requires a stock system - stock recovery, system and no modifications (bootloader status doesn't matter). In other words, you'll need to unroot and restore your stock recovery - might be easier to reflash the stock system, probably the quickest way to flash a stock ROM (and update to Nougat) is to use the fastboot ROM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this will remove root and TWRP, as well as potentially wipe your data, so back up accordingly. This should flash the NPJ25.93-14 build on your device, which appears to be the latest global build.
1a)Also, if you flash Nougat this way, your bootloader and GPT partitions will be updated, so if you wish to downgrade to Marshmallow at any point, when flashing do not flash these partitions from the Marshmallow ROM. Fastboot should stop you, but a brick may occur if these get flashed.
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
2) As SoNic67 has already mentioned, the stock kernel security will cause your device to bootloop should you choose to try to root following the Marshmallow method. If you wish to use SuperSU, follow this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You may wish to use a more up to date TWRP than the official 3.0.2 (I recommend shrep's TWRP 3.0.3 n4 here:https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337) Whatever you do, ensure you flash first the ElementalX kernel before you flash the SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), or apply the systemless fix with earlier SuperSU versions as directed in the aforementioned rooting with SuperSU guide. Else you'll be having bootloops or your device will not boot whatsoever. Here's my steps in successfully rooting Nougat: https://forum.xda-developers.com/showpost.php?p=71817346&postcount=225. Good luck either way.
echo92 said:
A few pointers from your story:
[...]
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
[...]
Click to expand...
Click to collapse
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shreps' unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shrep's unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Nice one, hopefully that'll help more XT 1644 users I'm still not sure if TWRP can backup/flash the baseband by itself, but I don't have a XT 1644 to test. I imagine your backup will need a clean flash (wipe data/cache/Dalvik) to work?
The OTA process does update the partition table, but as far as I know, that should not prevent you from flashing back to Marshmallow/Nougat as you wish, so long as you did not try to downgrade the GPT/bootloader.
There was an effort to create TWRP flashables of the stock ROMs a little while ago (you can see the thread here: https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147) which if I understood it created flashable radios and ROMs from the firmware files we have. We can't touch the GPT/bootloader since, as I recall, you need a signed stock firmware to do so (and besides, downgrading GPT might be asking for a brick). I recall some users mention they were able to run Nougat TWRP flashes on the MM bootloader/GPT without issue.
There were issues with simply flashing the Nougat 93-14 radio baseband files for some US users, losing LTE in the process and appears the only resolution was to flash the stock ROM - I don't know what the cause was (perhaps no/incorrect CDMA support in the radio files?). Your TWRP flash is from a US based phone so may have better luck in that department, and will likely behave on your device since that OTA has updated all the firmware on your device that TWRP isn't able to touch. I still am not sure if we can use this TWRP backup to update on a MM device without issue, but only one way to find out...
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
2CanSan said:
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
Click to expand...
Click to collapse
It's really simple actually: if you install B15 your data will be wiped, after that just skip everything and update to B29 (is B29 the latest? I have a G, dunno) and then use it. What you describe is not the actual performance that it should have, it's your specific case obviously.
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
tabletalker7 said:
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
Click to expand...
Click to collapse
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
2CanSan said:
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
Click to expand...
Click to collapse
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
tabletalker7 said:
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
Click to expand...
Click to collapse
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Choose an username... said:
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
Click to expand...
Click to collapse
OK on the A2017U units you need the official marshmallow B29 package to roll back, and that only works with stock recovery on a clean B15 N install. The Rollback package I told you to use earlier will roll you back to B29 marshmallow NO MATTER WHAT YOU ARE USING (I have used this a lot, and OBVIOUSLY there are differences between the the A2017U version in North America and the A2017G version in Europe). If you want stock and rooted, I personally recommend B29 marshmallow over B15 Nougat, but either way go for it (I think the marshmallow had a much better radio than any of the Nougat packages). If you are interested in TWRP and root, I found B29 marshmallow much easier for both, and the marshmallow version of android also gives you Xposed, but back to your first post, you mentioned wanting marshmallow, and this is the best way to get it.
Step by Step method
1. Roll back to B15. Use the update.zip method. It will factory reset your device so backup everything you can't lose
2. Use MiFlash to unlock and install TWRP - check that thread on XDA for instructions.
3. (If desired) In TWRP, install the B29 marshmallow rollback. Do not reboot into system afterwards.
4. (If step 3 is done) In TWRP, flash TWRP. The marshmallow rollback will overwrite recovery with stock recovery
If you do this you will have exactly what you wanted in your original post. I can personally tell you this works, as I have tried every custom rom on here and always wind up back at B29 marshmallow when all is said and done. It has never failed me, and it will never fail you either.
Hi,
I have a Nexus 6P that has Android 7.1.2 (N2G47W) installed. I've just unlocked the bootloader, installed TWRP then installed Magisk 16.0 for root.
I'd like to next downgrade from Nougat to Marshmallow. Are there any steps to do so? Can I just boot to TWRP, and immediately install the factory image from https://developers.google.com/android/images#angler?
Or are there any additional steps I need to take?
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Exodusche said:
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Click to expand...
Click to collapse
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
goister said:
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
Click to expand...
Click to collapse
That's exactly what I'm saying unless you want to flash a marshmallow ROM. Then you can use TWRP but would still need 6.0 gapps and a computer to fastboot flash MM bootloader of that months build. MM vendor could be flashed by either fastboot or TWRP. Your best to download a MM build from Google site. Then unzip that folder and inside unzip again. You will get all the bootloader, vendor (radio optional) you will need for that months MM build. Then follow the guide from hiesenberg for returning to stock . Best to put all the images files and fastboot in the folder that is suggested in the guide . That way you can copy and paste the commands as written on the guide. There might be a flash all bat file you can use in the stock folder but not sure if MM had that I never used. If you have any more questions feel free to ask.
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
goister said:
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
Click to expand...
Click to collapse
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Exodusche said:
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Click to expand...
Click to collapse
Thanks. I've no issues wiping the phone as this is pretty much a fresh phone. There's nothing to even back up. The only thing I've done so far beyond rooting, was to import a certificate into /system. I suppose a factory reset would delete this certificate and bring it back to stock (but rooted)? Or should I wipe with TWRP instead?
Looking at the zip file of the stock ROM, here's what I see
bootloader-angler-angler-03.54.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mtc20l
radio-angler-angler-03.61.img
After wiping with TWRP, would I be able to run flash-all?
Edit: I've just TWRP wiped everything, and rebooted. However, the device is stuck at the initial "Google" screen with the lock icon at the button. How long is it supposed to take to boot up after a full TWRP wipe?
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.