Database Users

[Q] need some help with boot.img

hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
thanks for everything

On the official Oppo forum's there's a guide on how to install the latest Omnirom. Under known issues it says:
5)After installing the TWRP recovery the Screen Touch firmware update goes on for more than 5-7 minutes, do a hard reboot and you would be fine,
Click to expand...
Click to collapse
I haven't tried it myself since I didn't get the problem when flashing Omni and Asylum, but it seems to be worth a shot.
In case you are looking for the topic, search for "How to Install OmniRom 4.4".

S5 booting only to TWRP

since yesterday i wasnt able to use my galaxy S5 GM900F , when i try to turn it on it only boots to TWRP and it seems like he is trying to install something then he freeze for a couple seconds and reboots again to the same loop again and again .
any idea about whats happening and how to fix this , and is there any chance to save my data ?
Thank you all !
Edit: TWRP is trying to install a zip and fails at it reboots and automatically repeats the process

what version of TWRP is it?

youdoofus said:
what version of TWRP is it?
Click to expand...
Click to collapse
i dont remember but i believe its the last one downloaded it a couple days ago

if its 3.0.2-2, that might be your problem. Its buggy. Flash 3.0.2 and then reflash your ROM

youdoofus said:
if its 3.0.2-2, that might be your problem. Its buggy. Flash 3.0.2 and then reflash your ROM
Click to expand...
Click to collapse
any idea where can i find official unbranded OS for my SMG900F ? thank you

The same thing happens when you try to install a kernel that is not properly supported for your ROM. Try flashing a different kernel for your device and baseband.
TWRP recovery > Install > kernel.zip > wipe delvik/cache > reboot

TWRP aroma install freeze

I downloaded the aroma installer in the open gapps app, then hit install, the device rebooted into recovery but TWRP froze immediately after starting the install. After freezing for a few seconds it restarts TWRP and tries again, I can't boot into the is because it constantly tries to boot into recovery , what should I do to stop it from booting into recovery?

Try Twrp 2.8.0.0 I think the problem will be solved

get the latest download, 3.1.0.0 as of 03Mar17... believe that they fixed that issue...

I have TWRP 3.1. the only thing I can access to flash anything is download mode

darkforce81 said:
I have TWRP 3.1. the only thing I can access to flash anything is download mode
Click to expand...
Click to collapse
reflash TWRP. also, redownload the aroma package, its likely a corrupted d/l

Re-flashing TWRP 3.1 didn't work, I had to revert to 2.8.7 to get aroma working but thank you

darkforce81 said:
Re-flashing TWRP 3.1 didn't work, I had to revert to 2.8.7 to get aroma working but thank you
Click to expand...
Click to collapse
right on, that was going to be my next suggestion, however i dont think i would have said to go back that far in the revisions

darkforce81 said:
Re-flashing TWRP 3.1 didn't work, I had to revert to 2.8.7 to get aroma working but thank you
Click to expand...
Click to collapse
How do I revert To 2.8.7 version

Ahmad Alvi said:
How do I revert To 2.8.7 version
Click to expand...
Click to collapse
Just install TWRP 2.8.7 over your existing twrp installation

only use twrp 3.0.2

[Q] GApps not visible (installed)?

Hi guys
It may sound stupid, but... It's so strange, I've never noticed it since I began having fun with custom ROMs.
The problem occurs on every AOSP ROM. I flash the ROM, then flash GApps and then I flash magisk.
Everything in latest TWRP.
TWRP says that installations was succesful, but after boot there's no configuration menu, no Google Apps, no Magisk.
I tried many OpenGapps versions: nano, pico and one more (i don't remember its name) and it happens on every version. I tried with Magisk 16.2 and 16.3 - the same situation.
What's going on?
Everything works fine, EFS (IMEI) works correctly

Bruce666 said:
Hi guys
It may sound stupid, but... It's so strange, I've never noticed it since I began having fun with custom ROMs.
The problem occurs on every AOSP ROM. I flash the ROM, then flash GApps and then I flash magisk.
Everything in latest TWRP.
TWRP says that installations was succesful, but after boot there's no configuration menu, no Google Apps, no Magisk.
I tried many OpenGapps versions: nano, pico and one more (i don't remember its name) and it happens on every version. I tried with Magisk 16.2 and 16.3 - the same situation.
What's going on?
Everything works fine, EFS (IMEI) works correctly
Click to expand...
Click to collapse
Trick is to flash rom and after flash twrp recovery installer.
Then reboot recovery and flash gapps and magisk. Then reboot phone and gapps should work.

daveve said:
Trick is to flash rom and after flash twrp recovery installer.
Then reboot recovery and flash gapps and magisk. Then reboot phone and gapps should work.
Click to expand...
Click to collapse
worked! Thanks a lot!

Bruce666 said:
worked! Thanks a lot!
Click to expand...
Click to collapse
Your welcome

daveve said:
Trick is to flash rom and after flash twrp recovery installer.
Then reboot recovery and flash gapps and magisk. Then reboot phone and gapps should work.
Click to expand...
Click to collapse
Thanks, this helped a lot:
This was my step by step to install lineage 17.1
reboot to fastboot
fastboot boot <twrp.img>
wipe > (data, system, davlink)
reboot > slotA: go back
install lineage.zip
reboot > slotB: go back
install lineage.zip
install twrp-installer.zip
reboot to recovery
install gapps.zip and magisk.zip
reboot to system.

'The System has been Destroyed' when installing TWRP zip in hotboot TWRP

UPDATE - Did not manage to find a way to get TWRP installed permanently but did manage to install Lineage OS 16 (which was my end goal) via hotboot of their recovery IMG, so happy with that at least! Appreciate any help given!
Not sure what I am doing wrong. have never come across this before!
I just completely reset my phone to stock via MiFlash
I then boot into TWRP recovery from Fastboot
I then install the TWRP installer in TWRP
I then reboot to recovery but get 'The System has been Destroyed'
I can still boot into the stock ROM
I can still boot into Fastboot
I just can't seem to get TWRP to install, I can only access it in hotboot
Any help would be amazing!

It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system

Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Oh well damn, I will give that a shot thank you!

Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message

MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Never install twrp on stock pie. You'll get the same message. Hotboot it only.

MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
From what I have tried it seems that it is a bug with stock pie, custom roms with pie and stock oreo don't have this problem.
Anyway, you can basically get the same functionality by hotbooting but it's less convenient.

I have TWRP installed and resurrection remix. Maybe their TWRP works for you, just check the instructions and give it a try.

I think you should install TWRP in both slot A and B for it to work.

MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Weird, it used to work for me when I was on stock pie.
I'm on a custom rom right now so I cannot test if it still works.
Sorry

I also have the same problem but now I'm on a custom rom and the TWRP without magisk works, but I would like to try an sGSI, on a custom rom does the procedure work?

Try another twrp

I'm here also had the same problem on mi A2 lite
But Rom run smooth and stable for a long time that I even forgot I have no twrp. Instead I backed up with titanium bk just in case. So ,Hotbooted with adb.... less convinient but u get to where u wanna flash though