Database Develop

P9 Unable to get into TWRP due to flashing a different ROM

So I installed a version of the P9 OS EVAL09 from here - https://forum.xda-developers.com/p9/development/bluewei-test-crossflash-to-l09-c432-t3608270 the B387 version.
Prior to this, I was running unofficial CM 13 with TWRP installed, and it worked mostly fine.
The B387 .zip had a .update log which I was supposed to install via SDcard upgrade or something like that, however instead I removed a few lines from the update binary and installed via TWRP (in hindsight, probably what caused this problem).
Since then, I have launched into the new ROM with the purpose of updating, then moving to the unofficial Lineage OS.
However, I have encountered the biggest problem which is that, when I tried to reaccess TWRP it would automatically redirect to Huawei eRecovery, which does not allow me to reset/upgrade (as it says package info isn't correct).
I then tried to redo the process of flashing TWRP via ADB fastboot, and then it says that writing recovery has failed.
I can't download the stock ROM from huawei hicloud from the thread here - https://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 - as it always says the website is unavailable.
So far, the current OS installed is unusable, and I do not have any custom recovery software. If I can get TWRP to work again, then I should be ok as I made backups before.
edit 2018-01-18: The fix is to make the dload folder in the sd card and hard flash the ROM, which will get me back to a working stable version.

[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.

Help with root

Every time i try and flash Super su or magisk it fails, TWRP is unable to mount anything and when i try to reboot TWRP says no os installed. I then have to flash stock recovery to get the phone to boot normally, I have rooted phones in the past but i just dont get why this is happening. Can anyone shead any light on this please
Phone and FRP unlocked
P8 lite 2017 8.0.0.383(C432)
Android (stock) and EMUI version 8
TWRP 3.2.1.0

I don't think the normal root method works anymore on genuine EMUI 8. I believe that we need to flash Askuccio's TWRP (hard to find without knowing it exists already), and then a custom treble rom (of which there are many), and then flash magisk over it. Not too difficult, but personally I've been having troubles with actually booting into custom ROMs.

I can't flash the Ashuccio TWRP - keep getting FAILED (remote: partition length get error)...any help?

You have to type to flash: fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img

Thank you - I missed the ramdisk command
---------- Post added at 12:02 PM ---------- Previous post was at 11:20 AM ----------
Dru79 - now that I have TWRP - and many thanks for that, would you guide me quickly through the next steps for a custom ROM (I have read all sorts of posts that say you have to flash stock then a ROM then do all sorts - things have REALLY changed since I did this last!). I am on And 8 and emui 8 and want (ideally) as close to asop as poss with the ability for adoptive storage a must. Just unsure exactly how to progress, ie is it super SU (which most now seem to say no) or magisk etc....I really would appreciate a simple guide.
Thanks

3T - Stock ROM, TWRP, Magisk & OTA updates

Hi,
I have a somewhat general question about different OTA update application methods for OOS when Magisk and potentially TWRP is involved.
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Going forward, I'd like to be in a state where I have a Magisk-rooted phone, able to use TWRP, and receive OTA updates. Generally I've seen these two methods being recommended:
1) With TWRP:
a) download full image from OP site;
b) boot to TWRP, flash said image, followed by re-flashing TWRP as flashing full image restores stock recovery;
c) wipe dalvik & cache
d) reboot to TWRP & flash Magisk
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Now, my questions:
1. Which of the two methods above should be preferred?
2. Could either of the two methods used for OTA updates without losing data nor apps/settings?
3. Is there anything inherently different between flashing full image as in method 1) vs. going for the regular incremental OTA update as in method 2)?
4. for option 2), should b.1 OR b.2 be used? Magisk tutorials page seems to be recommending the latter.

I like to keep things simple, so if I'm going to install TWRP, then that's what I use for updates.
There's no benefit in swapping recoveries, especially since you end up with the same result.
By the way, it's been a long time since TWRP stopped patching kernels to prevent it being replace by the stock recovery. So, your step 1 is simpler:
a) download full image
b) flash it in TWRP
c) flash Magisk
And that's it. There's no need to wipe Dalvik or cache. I've not wiped either of these for years (and I've updated countless ROMs) and I've never had an issue requiring me to wipe them.
Sent from my OnePlus 3T using XDA Labs

Thanks for the reply.
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Any specifics re. Android P releases, or old flashing methods should work the same?

laur89 said:
Hi,
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Click to expand...
Click to collapse
There is nothing stopping you from installing an Oreo version OOS (such as the latest stable 5.0.8). Who knows when stable P is coming. Maybe soon, maybe not that soon?
Just download the full zip, flash in TWRP, and flash Magisk right away (do not reboot before flashing Magisk). Same process BillGoss suggested in a previous reply.
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
laur89 said:
Hi,
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Click to expand...
Click to collapse
I wouldn't mess with any of this. The phone is modded, and it seems that the above process is just trying to "trick" the system into thinking it has never been modded, so you can do an incremental update. For no actually benefit, and just making a much more complicated process.
Full zip makes for a cleaner install than incremental, anyway. You can keep your user data in either case, so again, you aren't gaining anything with incremental (versus full zip) OTA.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
laur89 said:
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Click to expand...
Click to collapse
Well, are you encrypted, or not?
I've always had the phone encrypted, so can only say for certain about that condition. If it is encrypted, it will stay that way. There are a few TWRP builds that don't play well with encryption. But for the most part, just flash the update as stated previously, and you don't need to worry about encryption.
If decrypted, I believe flashing by TWRP will keep it that way. If you flash an update by stock recovery, I think it will force back to being encrypted. But again, I can't say for certain, as I've always been encrypted.
laur89 said:
Any specifics re. Android P releases, or old flashing methods should work the same?
Click to expand...
Click to collapse
The community beta P release is having issue with devices which are bootloader unlocked and encrypted. If the device is just one of those (or neither) and not both, then it seems to work fine in most cases.
For the stable P release, I'm guessing it will work the same as the "old flashing methods" which has been described above. But we won't know for certain, until a stable P build is released.

How to flash ASOP based ROMs?

Hi
A few months ago I was able to flash on angelica lineage-17.1-20210326-UNOFFICIAL-angelica.zip and this worked well. Yesterday I tried to flash the s same image again and after several attempts I get a black backlit screen when lineage is meant to start. I reflash stock _V12.0.10.0.QCRMIXM then a recovery - PBRP 3.0.1. From there I was having issue
What is the flashing process for an unlocked device that has something like TWRP/Pitch Back/Orange Fox installed?
I guess once you unlock and can flash the recover you use the recover to flash the zip, then reboot and flash magisk.zip and everything should work? Or is there some step missing.

I had this problem too with the google pixel 7 pro. Can't help ya there on that one. I even tried re installing older firmware and it still didn't work. Maybe the bootloader is permanetly downgradable but the firmware of the stock is. Just a guess. Lineage os 20 is an unofficial build at the moment that receives hardly any updates.