Database Develop

Switching between 6.0.1 and 7.0.1 (backup in TWRP 3.0.2.0)

Is it OK to switch between Android 6 and Android 7 in TWRP 3.0.2.0 backups?
I would like to use both Androids on my phone until Xposed will be ready for Nougat, but I'm afraid of file structure, partitions and so on.
Both Androids are rooted and no encryption.
Restore backup of Android M won't mess with Nougat will it?

belek1979 said:
Is it OK to switch between Android 6 and Android 7 in TWRP 3.0.2.0 backups?
I would like to use both Androids on my phone until Xposed will be ready for Nougat, but I'm afraid of file structure, partitions and so on.
Both Androids are rooted and no encryption.
Restore backup of Android M won't mess with Nougat will it?
Click to expand...
Click to collapse
No problem provided u have N bootloader to use N ROMs. N bootloader is backward compatible. Nutty Nexus thread has link to latest N bootloader and radio combined in one zip to be flashed in TWRP 3.0.2.0 before flashing N roms

HueyT said:
No problem provided u have N bootloader to use N ROMs. N bootloader is backward compatible. Nutty Nexus thread has link to latest N bootloader and radio combined in one zip to be flashed in TWRP 3.0.2.0 before flashing N roms
Click to expand...
Click to collapse
Thank you for your answer.
I'm going to update from ADB (factory image):
1 fastboot flash bootloader
2 fastboot flash radio
3 fastboot restart-bootloader
4 fastboot flash boot
5 fastboot flash system
6 entering twrp recovery from bootloader
7 flash SuperSU (root and no encryption)
TWRP doesn't backup BL or radio?

Why not use MultiROM so you can actually switch between them and not wipe/restore all your partitions each time you want to switch back and forth? I think it should work between MM and N so long as the kernels in each ROM are kexec patched.

belek1979 said:
Thank you for your answer.
I'm going to update from ADB (factory image):
1 fastboot flash bootloader
2 fastboot flash radio
3 fastboot restart-bootloader
4 fastboot flash boot
5 fastboot flash system
6 entering twrp recovery from bootloader
7 flash SuperSU (root and no encryption)
TWRP doesn't backup BL or radio?
Click to expand...
Click to collapse
TWRP only backs up \system, \data, \boot, \recovery, \EFS (\cache also but who cares)
You could flash like that but you could also just flash debloated N rom from tupac4u or DanvH straight from TWRP (after flashing N bootloader and radio zip).
Multi-rom can be tricky for Noobs
EDIT: Here are the useful links: N radio and bootloader in 1 flashable zip in TWRP by RatchetPanda: https://www.androidfilehost.com/?fid=312978532265362066
Here is tupac4u latest debloated N rom:
https://mega.nz/#!e9JDyRRY!mJl2CJeWTmlhELPbHdHdzT1GHE15awdlqd3Q4sIED70
(needs MEGA app to download or use "desktop" emulator on mobile browser to download)

Rooted on android 5.1, accidently allowed OTA to try to Install, Now powers off

Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.

serifle said:
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
Click to expand...
Click to collapse
Try flashing this 6.0.1 stock-based ROM:
Computerfreek274_MM_1.0.6 Marshmallow 6.0.1
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's debloated, tweaked version of 6.0.1 Verizon stock firmware.
Yes, you may lose root temporarily. Just re-flash this version of SuperSu, found in this post. On stock 6.0.1 or stock-based 6.0.1 ROM ONLY that version of SuperSu (BETA-SuperSU-v2.62-3-20151211162651) will work for initial root. After you re-root, THEN you can update to newest version of SuperSu.
Also, not sure why you don't want to update to newer TWRP. You don't have to... but I always do. You just flash newer TWRP within TWRP. You install it like any other file in TWRP. Choose install, then "image", then "recovery".
What version TWRP are you using. Our official TWRP maintainer @bhb27 has released TWO newer versions just in 2017 alone.
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
Note:
This is a pre released of 3.0.3 when all the changes are finalized I make and released a new one or when important bugs fix are released
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Any problem found report and use a old version.
Click to expand...
Click to collapse

Just wipe the cache in TWRP.

[C6903] - cant run new NOUGAT custom roms - bootanimation 2-3 sec and phone turns off

At the beginning, please forgive me the quality of my English.
Me and other friends using c6903 have posted on the forum about trouble with running Nougat ROMs:
- [ROM][7.1.X][27/07/17][STOCK-CAMERA][3.4 KERNEL][TESTING] LineageOS 14.1 - UNOFFICIAL
- [ROM] [7.1.2] [OMS] [OFFICIAL] [Honami] Resurrection Remix Nougat v5.8.3 [01/08/2017]
- [ROM] [7.1.2] [Substratum/OMS] [UNOFFICIAL] [Honami] Android Ice Cold Project 12.1
For example LinageOS 14.1.
I flashed build from 11/07 without any problems.
Everythings worked fine, but when i try to flash newest build I encountered a big problem.
Bootanimation continues 2-3 sec. and phone turn off [check plz video].
Then only the launch button was active.
Everything I do exactly the same as in 11/07 build.
Why rom can't run?
The situation applies to all the above versions.
Resurrection Remix Nougat from 28/06 booted fine too.
Newer versions not...
One of friends - MIcHiJK - suggested that this could be a problem with changing the screen for "fake".
Me and him changed screens probably for counterfeiting.
Maybe someone else did it and have this problem?
....but why build from 11/07 (LinageOS), 26/08 (RR) and 20/06 (ACIP) booted without any problems?? In my case change screen was earlier.
What have I done so far to solve the problem.
- used TWRP 3.0.0 and 3.0.2
- Always full wiped (a few times format internal storage using twrp too)
- flashed roms when using Cyanogenmod 12.1
- flashed roms when using stock .236
- restored software using EMMa and Flashtool, then root (kingroot), flashed twrp by fastboot, full wipe, flash rom - without result
- used others kernels referenced by creators roms (flashed after installation rom).
Nothing worked.
I know I'm not alone. Many guys have problem like me.
Is anyone able to give a solution?
May God bless guy which will solve our problems!
"https://youtu.be/sOBquHNlbzQ"

Hello to all ppl which had this problem.
Since I replace my broken original xperia z1 Display, I wasn´t able to boot any of the new Nougat rom releases.
I solved this problem with a new Kernel.
Super Lamic Posted this Kernel to test the Battery Life but with this Kernel the problem was solved and I was able to run the new Releases on my fake Display.
Kernel Link: https://mega.nz/#!RN1nFYRT!546WMDdM2ToJEeZlleKTjS-TdR54rkYiOGKUDDWQ-t0
Install new LineageOS build on your xperia z1 with TWRP 3.1 (with 3.0 it wasnt able to install the boot.img).
Before you reboot select images, boot and flash the boot.img.
Then the new build should run without problems.
On other roms like Resurrection Remix it endet in invinite boot so I was just able to run normal Lineage.
I hope it helped someone. Im still interested what the devs changed that causes this problem. And I hope there will be improvments in future that this problem wont happen anymore.

same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.

For those wo will flash AICP maybe this solution will work in RR too.
In normal Lineage it worked when i flashed cm12.1 Nouagt Kernel after flashing LOS 14.1.
But for RR or AICP it ended in infinite boot. Here is how I managed to get it work.
1. Download AICP (Latest Version [2017/08/01]) then download AICP (Version 2017/06/20).
2. Delete 'boot.img' from the Latest Version zip and put the 'boot.img' from the older relase into the Latest
3. Boot into TWRP 3.1 or 3.0, Wipe all and flash your Latest AICP zip with the older boot.img.
4. Boot phone. The z1 will show you just the Sony Logo. I waited some Minutes and powered off with power + volume up.
5. Connect phone in fastboot mode on PC and flashed cm12.1 Nougat Kernel.
6. Type 'Fastboot Reboot', the phone Turns on with the newer Boot screen where xperia stands on the bottom. You will finally see AICP Boot Animation and after some time rom boots.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
Aaskereija said:
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
Click to expand...
Click to collapse
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.

MIcHiJK said:
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
Click to expand...
Click to collapse
really funny. sound good, doesn't work

Aaskereija said:
really funny. sound good, doesn't work
Click to expand...
Click to collapse
How did you installed the rom?
From which rom you came and which recovery did you used and how did you installed the recover?

different ways, but mostly with my standard custom-rom Tesla which is on Android 5.1.1. TWRP is on 3.1 which i install via cmd (fastboot flash recovery) cause build in recovery of tesla is broken.
Or i go over latest stock with dualrecovery, flash boot.img of the custom-rom (wich work) and then flash rom. but still recovery is gone after that.

@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated

Guys, you don't have to create threads for this. I'll have an aftermarket display too, so I'll be forced to fix it anyway. And I have an idea what can be wrong...

MIcHiJK said:
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Click to expand...
Click to collapse
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download

Aaskereija said:
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Click to expand...
Click to collapse
Android Sdk put twrp.img in platform tools folder then open CMD in this foder, fastboot flash recovery TWRP.img.
I asked about twrp cuz in advanced kernel is TWRP 3.1 inbuild but I can't find just the twrp 3.1 IMG without kernel. Strange.

Fingerprint not detecting in custom os since installed official 8.1

Fingerprint not detecting since I have installed custom ROM after I have installed official Oreo
On official Oreo fingerprint shows up in settings but in custom Oreo all works fine and best but fingerprint doesn't show up in any settings I have tried 4 8.1 custom roms like sex pixelexpirience 64 bit versions all works flawlessly tested Google camera it works the best but not detecting fingerprint even after searching fingerprint it only shows up gestures's fingerprint in gestures's system menu PLZZ give me link of official Oreo build OPSS28.65-36-3 with Indian band so I could try to flash via fastboot and then recheck if custom roms fingerprint gets detected or not..

Update ur bootloader to Oreo one and then try flashing the rom

Surya Guduru said:
Update ur bootloader to Oreo one and then try flashing the rom
Click to expand...
Click to collapse
I don't have fastboot official oreo link can anyone give me plzz

hondraopranav said:
I don't have fastboot official oreo link can anyone give me plzz
Click to expand...
Click to collapse
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin

change the base of your fp to nougat base again

Hey check this out

Surya Guduru said:
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin
Click to expand...
Click to collapse
The OP didn't say they had the official 8.1 ROM, they said they had installed official Oreo. AFAIK There is no official 8.1 ROM for Sanders. Some people have taken the OTA for their device and repackaged it into an UNofficial flashable package, but that's not the same thing, and reportedly may be causing problems on EU & US variants, so I wouldn't recommend it.
I have the same problem with my FP reader.
I don't have an official 8.1 ROM (because there isn't one, lol), but I installed stock nougat 7.1.1 (retus, in my case) and then got the OTA upgrade to 8.1, after that fp+VoLTE are 100% working.
Then, as soon as I change to a custom 8.1 (or 9) ROM, VoLTE still works, but the fp is no longer recognized by the system.
If I flash back to stock nougat, FP comes back (and LTE breaks, but can be fixed by installing the 8.1 OTA upgrade again, or by getting to a root terminal and fixing permissions on /persist, I've personally verified both methods to restore functionality (assuming your /persist is unmolested - if it is, you're SoL).
Going from fully working official nougat or official Oreo, to any Oreo (or Pie) custom ROM still seems to break the FP reader again. I'm getting really tired of wiping my device...
Not A Solution #1
As suggested here: With FP + VoLTE working under official 8.1 OTA update, I installed TWRP & backed up /EFS, then installed my custom 8.1 ROM (Validus final) and restored the backed up /EFS, but instead of bringing my FP back, it just caused bootloop and I had to roll back to stock and start over. I skipped rolling back to Nougat before flashing custom, is that important? Why would it matter?
Not A Solution #2
After installing the custom 8.1 ROM I tried flashing the Nougat FP base. It had no effect.
Maybe A Solution? UPDATE: YES. A SOLUTION.
As suggested in this post:
1 - download the latest nougat stock rom (link removed - the correct one will vary depending on your device, up to you to obtain the correct firmware);
2 - unzip the above file and cd into the resulting directory;
3 - reboot your phone in fastboot mode;
4 - from terminal (linux or windows, in linux I had to do it as root user, using sudo), type:
fastboot flash bootloader bootloader.img <enter>
fastboot flash modem NON-HLOS.bin <enter>
fastboot reboot <enter>
By doing above steps, your phone should get fingerprint options back.
I did this, it worked, with one additional step - I had a pattern set before. After the fingerprint reader was 'reinstated' the pattern no longer worked. Rebooting into Recovery and flashing lockfix.zip removed the security so that I could set it up again properly. Find lockfix.zip in this post.

can't flash TWRP 3.3.1 - 3.0.2 works just fine

I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.

RNZL3R said:
I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
Click to expand...
Click to collapse
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)

liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
Screwed badly with the systems to the point where I softbricked the phone, and had to revert to stock. Will try going straight to 3.3.1 instead now.
Edit: I used adb to go to fastboot (adb reboot bootloader), from there I tried all the different twrp images I have, including latest Android 10 one using the fastboot boot image.img (replace image by name of image, I name them A8, A9, A10 to match android version).
All of them booted, which means I can flash them without issues. I don't know which version I want to install though for now, and I don't want to be stuck again on a version that I won't be able to upgrade later on... so will probably go straight to A10 and Lineage 17 even if it's quite buggy.

liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
did you found a solution? i have the same issue...