Database Users

[Q] How to flash a bootstack?

Hey guys, definitely new to this, haven't flashed a rom since I had a HTC Droid Incredible about five years ago. My brother just helped me root my phone and install TWRP, except when we go to look at flashing a new rom it states that you need TWRP 2.8.6.3. We are currently running 2.8.5.1 I found the 39A bootstack which supposedly includes TWRP 2.8.6.3, but I'm lost when it comes to how to flash this bootstack with the updated TWRP. Can anybody provide instructions, or a link to a previous thread? I did try using the search bar, but when you search "how to flash bootstack" the results are overwhelming because almost every post has the word "how," "flash," or "bootstack."
Really appreciate the help!

amcleod1995 said:
Hey guys, definitely new to this, haven't flashed a rom since I had a HTC Droid Incredible about five years ago. My brother just helped me root my phone and install TWRP, except when we go to look at flashing a new rom it states that you need TWRP 2.8.6.3. We are currently running 2.8.5.1 I found the 39A bootstack which supposedly includes TWRP 2.8.6.3, but I'm lost when it comes to how to flash this bootstack with the updated TWRP. Can anybody provide instructions, or a link to a previous thread? I did try using the search bar, but when you search "how to flash bootstack" the results are overwhelming because almost every post has the word "how," "flash," or "bootstack."
Really appreciate the help!
Click to expand...
Click to collapse
Interested in this as well. I've just started with the LG G2 and am at the same point. How do we go about flashing a boot stack? Does, as @amcleod1995 stated, the boot stack include the newer version of TWRP? Can someone provide a step by step tutorial or a video maybe? Thanks in advance! Here are the steps below we took to root and add recovery.
We both have our phones rooted following:
1. Root - http://forum.xda-developers.com/andr...vices-t3049772
2. Recovery ( TWRP) - http://forum.xda-developers.com/veri...-twrp-t3053134

Deathscyth3 said:
Interested in this as well. I've just started with the LG G2 and am at the same point. How do we go about flashing a boot stack? Does, as @amcleod1995 stated, the boot stack include the newer version of TWRP? Can someone provide a step by step tutorial or a video maybe? Thanks in advance! Here are the steps below we took to root and add recovery.
We both have our phones rooted following:
1. Root - http://forum.xda-developers.com/andr...vices-t3049772
2. Recovery ( TWRP) - http://forum.xda-developers.com/veri...-twrp-t3053134
Click to expand...
Click to collapse
amcleod1995 said:
Hey guys, definitely new to this, haven't flashed a rom since I had a HTC Droid Incredible about five years ago. My brother just helped me root my phone and install TWRP, except when we go to look at flashing a new rom it states that you need TWRP 2.8.6.3. We are currently running 2.8.5.1 I found the 39A bootstack which supposedly includes TWRP 2.8.6.3, but I'm lost when it comes to how to flash this bootstack with the updated TWRP. Can anybody provide instructions, or a link to a previous thread? I did try using the search bar, but when you search "how to flash bootstack" the results are overwhelming because almost every post has the word "how," "flash," or "bootstack."
Really appreciate the help!
Click to expand...
Click to collapse
Very simple, update twrp manually from blastagator's website, reboot to recovery , flash bootstack zip, reboot to recovery and the flash anything that requires it (ie: CAF roms) . Now you're on the latest bootstack (bootloader, modem and everything else that comes with it).

I'm in twrp right now (wiped the system)
Choristav said:
Very simple, update twrp manually from blastagator's website, reboot to recovery , flash bootstack zip, reboot to recovery and the flash anything that requires it (ie: CAF roms) . Now you're on the latest bootstack (bootloader, modem and everything else that comes with it).
Click to expand...
Click to collapse
can I install blastgator bumped recovery from within current TWRP recovery (I've 2.6.3.3) ? and the install blasgator bumped bootstack - I want cm 12.1 so the 3rd link from here http://blastagator.ddns.net/bootloader.php

roberto32 said:
can I install blastgator bumped recovery from within current TWRP recovery (I've 2.6.3.3) ? and the install blasgator bumped bootstack - I want cm 12.1 so the 3rd link from here http://blastagator.ddns.net/bootloader.php
Click to expand...
Click to collapse
Sure can.

[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS

Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you

matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt

Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.

Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?

jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.

Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?

jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.

I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?

jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.

I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.

Duplicate post.Deleted

ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader

matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!

ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful

Is this enough to install CM14 or do i have to install the whole room and them flash CM14?

Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP

I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm

slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate

1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)

walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Z1C: First Custom-ROM

Hello,
my Sony Xperia Z1 Compact has the standard Android 5.1 version of Sony. Now I want to upgrade to a new Android version.
I need it for everyday-use and it should be relatively stable. The camera is not that important, but it should work. I use especially the browser, so the mobile datas should also work. Otherwise it should be only be stable and the battery should not discharge too fast. Is there any good build for me?
That one looks very interesting: AICP 7.1 ROM amami (I can't link the URL, because I am a new user )
Is it okay for a Custom-ROM beginner? I think I will find some instructions and tutorials how to install it. I just have to know if it is a good choice.
If there are any English mistakes, please correct me. I have to improve my English.
Thank you!

Skylac06 said:
Hello,
my Sony Xperia Z1 Compact has the standard Android 5.1 version of Sony. Now I want to upgrade to a new Android version.
I need it for everyday-use and it should be relatively stable. The camera is not that important, but it should work. I use especially the browser, so the mobile datas should also work. Otherwise it should be only be stable and the battery should not discharge too fast. Is there any good build for me?
That one looks very interesting: AICP 7.1 ROM amami (I can't link the URL, because I am a new user )
Is it okay for a Custom-ROM beginner? I think I will find some instructions and tutorials how to install it. I just have to know if it is a good choice.
If there are any English mistakes, please correct me. I have to improve my English.
Thank you!
Click to expand...
Click to collapse
Anything over LP 5.1 has an unusable camera, with one possible exception: DU Marshmallow rom with custom kernel. Read op of this thread - https://forum.xda-developers.com/sony-xperia-z1-compact/general/z1c-marshmallow-roms-t3372565 Note the addenda at the bottom.

levone1 said:
Anything over LP 5.1 has an unusable camera, with one possible exception: DU Marshmallow rom with custom kernel. Read op of this thread - https://forum.xda-developers.com/sony-xperia-z1-compact/general/z1c-marshmallow-roms-t3372565 Note the addenda at the bottom.
Click to expand...
Click to collapse
Thank you for your fast answer.
Is the camera completely unusable or just "not good"? I do not need the best quality, but it should at least work and you should be able to identify what the picture shows.
However, thank you for the link. I think I will try it. Android 6 is, I hope so, an improvement. Maybe I will then upgrade to Nougat.
There are no other options like Ubuntu Touch or Sailfish, right?

Skylac06 said:
Thank you for your fast answer.
Is the camera completely unusable or just "not good"? I do not need the best quality, but it should at least work and you should be able to identify what the picture shows.
However, thank you for the link. I think I will try it. Android 6 is, I hope so, an improvement. Maybe I will then upgrade to Nougat.
There are no other options like Ubuntu Touch or Sailfish, right?
Click to expand...
Click to collapse
Put a piece of tape over your camera lens, and turn off the lights, and shake the phone back and forth while taking a picture... That's what most of the photos will look like.
No Sailfish, and @munjeni has built Ubuntu touch for Z1c, but I couldn't get the Internet to work, (except for Ubuntu store, which downloads apps fine). - https://mega.nz/#!YEpCHLoS!tRxZpJHUSKL_cZz9wisGZvWl7igYAlYJRjwbcT_s868 Besides that, fxp has built Firefox OS, but probably hard to find at this point, and there are a few MIUI builds out there that are very good. Check here - https://forum.xda-developers.com/showpost.php?p=71329395&postcount=5 and here - https://forum.xda-developers.com/so...lopment/23-2015-miui-v6-5-5-22-d5503-t3116494

Hello again,
I decided to try out some Custom-ROMs.
Now I find many different ways how to root my phone and unlock the bootloader. Which way do you here recommend?
And how difficult is going back to the stock ROM and lock the bootloader againg, if nothing works?
Thank you!

Skylac06 said:
Hello again,
I decided to try out some Custom-ROMs.
Now I find many different ways how to root my phone and unlock the bootloader. Which way do you here recommend?
And how difficult is going back to the stock ROM and lock the bootloader againg, if nothing works?
Thank you!
Click to expand...
Click to collapse
Backup TA - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Root and recovery :
Download custom kernel to pc, and extract boot img to ADB directory - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 and download twrp img to ADB directory - https://www.androidfilehost.com/?fid=457095661767147235 then use fastboot commands to flash boot and recovery. Now you have recovery, and you can either flash SuperSU zip, or flash custom rom.
Restore TA - https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893 or use Flashtool relock bl option - http://www.flashtool.net/

levone1 said:
Backup TA - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Root and recovery :
Download custom kernel to pc, and extract boot img to ADB directory - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 and download twrp img to ADB directory - https://www.androidfilehost.com/?fid=457095661767147235 then use fastboot commands to flash boot and recovery. Now you have recovery, and you can either flash SuperSU zip, or flash custom rom.
Restore TA - https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893 or use Flashtool relock bl option - http://www.flashtool.net/
Click to expand...
Click to collapse
One little question: if I unlock my bootloader, my complete internal storage is wiped, right?
But if my bootloader is locked, I can not use the nandroid-backup-function of TWRP, because I can not use the custom kernel to root my phone. (Am I right? )
Currently I only have done your first step - backup the TA.
And of course, thank you again. :fingers-crossed:

Skylac06 said:
One little question: if I unlock my bootloader, my complete internal storage is wiped, right?
But if my bootloader is locked, I can not use the nandroid-backup-function of TWRP, because I can not use the custom kernel to root my phone. (Am I right? )
Currently I only have done your first step - backup the TA.
And of course, thank you again. :fingers-crossed:
Click to expand...
Click to collapse
You can root with locked bl, but your options are: 1) use Kingroot, (and it's generally preferred to not keep Kingroot, so after rooting you can replace Kingroot with SuperSU or wipe everything and flash a new rom with SuperSU), or 2) downgrade to KK and use doomlord rootkit, then flash LP prf.

levone1 said:
You can root with locked bl, but your options are: 1) use Kingroot, (and it's generally preferred to not keep Kingroot, so after rooting you can replace Kingroot with SuperSU or wipe everything and flash a new rom with SuperSU), or 2) downgrade to KK and use doomlord rootkit, then flash LP prf.
Click to expand...
Click to collapse
Okay.
I would like to avoid using Kingroot and downgrade to 4.4 is not even better.
But I found the Sony-Flashtool "Emma" for Windows. It seems to be able to restore completely the Stock-5.1-ROM. So I think I don't need a whole nandroid-backup. Am I right?
So I will unlock my bootloader, flash the custom kernel using TWRP-Tool and have a rooted phone. Then I am able to flash any custom-ROM I want to try out.
Did I misunderstand anything?

Skylac06 said:
Okay.
I would like to avoid using Kingroot and downgrade to 4.4 is not even better.
But I found the Sony-Flashtool "Emma" for Windows. It seems to be able to restore completely the Stock-5.1-ROM. So I think I don't need a whole nandroid-backup. Am I right?
So I will unlock my bootloader, flash the custom kernel using TWRP-Tool and have a rooted phone. Then I am able to flash any custom-ROM I want to try out.
Did I misunderstand anything?
Click to expand...
Click to collapse
True, Emma will restore you to stock. The backup would be if you want to restore the particular state of your phone right now.
Unlock bl, then flash the boot and recovery imgs, and you will be able to get into recovery. You'll want to have whatever rom you want to flash already downloaded on sdcard.

It works.
Now I have the AICP 12.1 7.1.2 Nightly Version.
Only the camera is not good, but better than expected. The aroma-GApps-package does not work, the GUI is hidden under the GUI of TWRP, but you can select your choice. However, after clicking install nothing was installed. After I downloaded and installed the super-GApps-package everything works fine.
If I find some issues, where can I report them? In the officiall AICP-12.1 N 7.1 amami Thread?
And at least a great thank you to levone1. :fingers-crossed:

Skylac06 said:
It works.
Now I have the AICP 12.1 7.1.2 Nightly Version.
Only the camera is not good, but better than expected. The aroma-GApps-package does not work, the GUI is hidden under the GUI of TWRP, but you can select your choice. However, after clicking install nothing was installed. After I downloaded and installed the super-GApps-package everything works fine.
If I find some issues, where can I report them? In the officiall AICP-12.1 N 7.1 amami Thread?
And at least a great thank you to levone1. :fingers-crossed:
Click to expand...
Click to collapse
https://forum.xda-developers.com/so...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288

levone1 said:
https://forum.xda-developers.com/so...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288
Click to expand...
Click to collapse
That is the thread I meant, but I can not post any URLs.

Best Custom ROM for Z1C
Not to open a new thread, which Custom ROM would you guys recommend to install on my Z1C?
I'm having some issues atm. It keeps restarting; I did a factory reset, it worked well for a while, now the issue is back. However, it does seem to work fine when hooked up to my PC (with the PC Companion active). Before I start shopping for a new phone, I'd like to root it first.
For this purpose, I'd like to know whick custom ROM is the most stable that you would recommend I install. Also, I'd be very helpful if you could direct to a good guide about the entire process.
Thank you in advance, I appreciate it!

levone1 said:
Backup TA - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Root and recovery :
Download custom kernel to pc, and extract boot img to ADB directory - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 and download twrp img to ADB directory - https://www.androidfilehost.com/?fid=457095661767147235 then use fastboot commands to flash boot and recovery. Now you have recovery, and you can either flash SuperSU zip, or flash custom rom.
Restore TA - https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893 or use Flashtool relock bl option - http://www.flashtool.net/
Click to expand...
Click to collapse
OP's intention is different than mine but this approach looks suit me well. I would like to keep my stock (14.6.A.1.236), so can I flash kernel.sin from Stock Rom via Flashtool after restoring TA and keep root status and recovery or should I use the custom kernel henceforth?

prustr said:
OP's intention is different than mine but this approach looks suit me well. I would like to keep my stock (14.6.A.1.236), so can I flash kernel.sin from Stock Rom via Flashtool after restoring TA and keep root status and recovery or should I use the custom kernel henceforth?
Click to expand...
Click to collapse
I don't think I've ever done it that way, but I don't see why not. As long as you don't wipe your recovery, you should still be good... (if you'd rather use stock kernel for whatever reason).

levone1 said:
I don't think I've ever done it that way, but I don't see why not. As long as you don't wipe your recovery, you should still be good... (if you'd rather use stock kernel for whatever reason).
Click to expand...
Click to collapse
Thanks for the answer. Actually the whole story is, the phone belongs to my wife and she is neither techsavvy nor has patience with electronics, especially when any problem come up. I would like to remove bloatwares and have backup yet keep the phone as Stock as possible. I'm trying to keep my ROM related modifications at minimum. That's been said, I would welcome any correction on this manner as I feel you found returning the stock kernel is pointless.

prustr said:
Thanks for the answer. Actually the whole story is, the phone belongs to my wife and she is neither techsavvy nor has patience with electronics, especially when any problem come up. I would like to remove bloatwares and have backup yet keep the phone as Stock as possible. I'm trying to keep my ROM related modifications at minimum. That's been said, I would welcome any correction on this manner as I feel you found returning the stock kernel is pointless.
Click to expand...
Click to collapse
I wouldn't say pointless, but for the most part, any custom kernel is an improvement. Most of the customizations wouldn't mean anything to someone like that, but I doubt there's any harm or risk in keeping it.

stuck in unlock phone screen

succesfully unlock the bootloader,flashed the twrp but when i flashed the supersu then it get stuck in the unlock warning screen..and after fewsecond it relaaunched the twrp recovery...guyz anyone plss help..i get worried about my phone..thanks in advance

ahadabdul said:
succesfully unlock the bootloader,flashed the twrp but when i flashed the supersu then it get stuck in the unlock warning screen..and after fewsecond it relaaunched the twrp recovery...guyz anyone plss help..i get worried about my phone..thanks in advance
Click to expand...
Click to collapse
You need to flash ElementalX kernel prior to flash SuperSu or magisk if you want to root stock nougat or marshmallow rom.
Instructions are here if you need details: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918

strongst said:
You need to flash ElementalX kernel prior to flash SuperSu or magisk if you want to root stock nougat or marshmallow rom.
Instructions are here if you need details: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
i am in soak test when i unlock bootloader and rooted it..when i wiped data it shows os not installed....what does it mean?

ahadabdul said:
i am in soak test when i unlock bootloader and rotted it..when i wiped data it shows os not installed....what does it means?
Click to expand...
Click to collapse
Even in soak test it you need to install exkernel as mentioned.
Maybe you wiped the system partition too?! Then you can here's no os at all... Can you remember what partitions you exactly wiped?
I would recommend to clean flash the last available stock nougat rom in terms of security https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't want to install the soak test again and you're willing to upgrade

strongst said:
Even in soak test it you need to install exkernel as mentioned.
Maybe you wiped the system partition too?! Then you can here's no os at all... Can you remember what partitions you exactly wiped?
I would recommend to clean flash the last available stock nougat rom in terms of security https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't want to install the soak test again and you're willing to upgrade
Click to expand...
Click to collapse
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?

ahadabdul said:
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
Click to expand...
Click to collapse
Welcome here and have a great time on this great device :laugh:
You don't want to root? Why you have flashed supersu mentioned in your first post? I'm a little bit confused now
please take some time to hold on and think about what you want and what's your intention with your device. I don't know what you want and can't recommend anything unless I know what you want.
You should tell
After that we will see what suits you best:good:

ahadabdul said:
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
Click to expand...
Click to collapse
As strongst has mentioned, please clarify what you're trying to accomplish with your device - what you want may elicit a different set of suggestions from us.
However, if you're trying to flash a custom ROM, you do not require root at all for our device. You simply require TWRP on your device, then you flash the custom ROM through TWRP. Be aware that many of the latest custom ROM builds are 64 bit in nature and as such require a 64 bit TWRP flashed. The instructions in the relevant custom ROM thread should have the link.
Also, you may wish to clarify what state your device is in at the moment: as far as I can see, it's still in the stock ROM, with TWRP, no system loaded and failing to boot from flashing SuperSU onto the stock ROM kernel, is that correct?

strongst said:
Welcome here and have a great time on this great device :laugh:
You don't want to root? Why you have flashed supersu mentioned in your first post? I'm a little bit confused now
please take some time to hold on and think about what you want and what's your intention with your device. I don't know what you want and can't recommend anything unless I know what you want.
You should tell
After that we will see what suits you best:good:
Click to expand...
Click to collapse
what i actually want is to need a new custom rom to atleast run my device ...which is my primaary device ..please tell me should i flash a rr rom ...i flash twrp 3.2.0.0....please tell me?...first i want a rooted phone with new custom rom but now i have to run this phone which is dead now..anyhow...please tell me the way i can..

echo92 said:
As strongst has mentioned, please clarify what you're trying to accomplish with your device - what you want may elicit a different set of suggestions from us.
However, if you're trying to flash a custom ROM, you do not require root at all for our device. You simply require TWRP on your device, then you flash the custom ROM through TWRP. Be aware that many of the latest custom ROM builds are 64 bit in nature and as such require a 64 bit TWRP flashed. The instructions in the relevant custom ROM thread should have the link.
Also, you may wish to clarify what state your device is in at the moment: as far as I can see, it's still in the stock ROM, with TWRP, no system loaded and failing to boot from flashing SuperSU onto the stock ROM kernel, is that correct?
Click to expand...
Click to collapse
i was in the soak test version.i unlocked bootloader,flash recovery and flash supersu..but phone does not on..it stuck in the unlock screen..and ..and i think i accidentally did thw wipe data ...what should i do

ahadabdul said:
what i actually want is to need a new custom rom to atleast run my device ...which is my primaary device ..please tell me should i flash a rr rom ...i flash twrp 3.2.0.0....please tell me?...first i want a rooted phone with new custom rom but now i have to run this phone which is dead now..anyhow...please tell me the way i can..
Click to expand...
Click to collapse
1)Again, you do not need root to install custom ROMs, only TWRP is required.
1a)Which TWRP have you flashed, is this the 32 bit or 64 bit version? If this is the official TWRP 3.2, I think that may be the 32 bit version. In which case, you'll want Resurrection Remix 5.8.5 https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
As you cannot boot properly, the easiest way to flash would be to boot your device to TWRP recovery, then connect your device to your computer. Your device's internal storage should be visible then, you may wish to back up your files at this point. Copy the RR custom ROM zip and the GApps package of your choice to your device and flash in TWRP as per the instructions. As usual with flashing custom ROMs, you will have to wipe /system, /data, cache and Dalvik in TWRP before flashing. Up to you if you choose to wipe internal storage as well (but usually a good idea switching between stock and custom ROMs).
Once you've booted into RR, you should have root as it already comes with magisk.
If you want to flash the RR 6.0 custom ROM, you must have the 64 bit TWRP recovery flashed before you attempt to flash the 6.0 custom ROM or any Oreo custom ROMs at the time of writing.
2)Alternatively, as strongst has suggested, if you simply want your device to be working again, you'll have to flash the latest stock ROM again, since you've likely tripped the anti-rooting measures in the stock kernel.
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
ahadabdul said:
i was in the soak test version.i unlocked bootloader,flash recovery and flash supersu..but phone does not on..it stuck in the unlock screen..and ..and i think i accidentally did thw wipe data ...what should i do
Click to expand...
Click to collapse
Which soak test, NPJ25.75-2? If so, that's a really old soak test, and as such I would recommend you flash the latest stock ROM available for your device, else you may run into issues with the newest custom ROMs, particularly if you have a G4 Plus. Can you mention what device and what region you're in, so we can guide you to the correct stock ROM to flash?
Yeah, that phone not turning on is because of SuperSU flashed onto the stock Nougat kernel, which you cannot do for our device - you need a custom kernel. The main ways to get around it are as I described above - flash a custom ROM or re-flash the correct stock ROM for your device.