SM-G793F doesnt boot after after installing aosp rom - Samsung Galaxy S10 Questions & Answers

I have installed lineage recovery lineage-19.1-20220514-recovery-Linux4-beyond1lte.img and i flashed lineage-19.1-20220514-UNOFFICIAL-Linux4-beyond1lte.zip
i also have updated my firmware to G973FXXUFHVE1 and G973FXXUFHVE1-device_tree-odin_flashable.tar
phone doesnt boot at all after installing i can go to recovery i tried both lineage and twrp both work i even tried to fflash full stock rom but not worked
any ideas to fix that ? thenk you

Related

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

Not booting Android Oreo

Flashed stock rom, flashed different versions of twrp.
But the same stuck on logo after flashing every Oreo rom.
Want to taste but can't, somebody's got any solution?
May be an issue of recovery. Try with twrp 3.1.1-3 from below link.
https://androidfilehost.com/?fid=889764386195917689
Only 8.1 ROMs are not booting. also tried with this recovery and also with mine ported one. But nothing works
i also had the same problem.we need to patch the boot image after flashing the roms provided by daniel hk sir
preform a clean flash{wipe internal storage}
flash supersu 2.82 after flashing the rom
it will work for sure
i got it working on my phone
Can you give me that patched boot image.
How to patch?

I can't flash any Android Oreo ROM

Hello, I have a problem with my Xiaomi Redmi 4X phone, as I said, I can not flash any Custom ROM for Android 8.1 All this happened after I put my phone in service to replace the display on which I've broken it. Now any version of Android 8.1 I try to flash results in a bootloop. I have to mention 3 things
1. In TWRP when flashing I noticed that all Custom ROMs are stuck in "Flashing system files ..." for a few seconds after saying that it ended flash-but did not abssolut anything.
2. Now a few hours I accidentally flashed Pixel Experince, but now I have the same problem.
3. I can not flash any versions of TWRP.Not much but...
THIS IS HAPPENING ONLY ON THE ANDROID OREO ROMs, Nougat ROMs works perfectlly
Try to flash first latest version of twrp or you can flash redwolf recovery then flash firmware v40 then try clean flash for oreo roms
As mentioned by above user...(latest TWRP recovery and firmware is must)
Flash latest TWRP recovery, 3.2.1-0 should be fine but there's update available 3.2.2.-0 so any will do.
Next, flash latest firmware.
Clean flash is must when changing OS.
It's most likely you don't have latest TWRP recovery and firmware.
Do backup first.

Stuck on boot loop after installing official Oxygen OS Pie Community build

I was running a custom ROM (Skydragon) earlier. I simply booted into TWRP, did the basic wipe then flashed the official zip file. Then after booting, its stuck on the boot animation for more than 20 minutes now. Any ideas how to resolve this?
I too faced the same issue. formating the data partition and flashing community beta build booted successfully for me. before you do this, completely back your phone contents to pc
You must flash with TWRP 3.2.3.0 or older!
i had the same issue. formated data had 3.3.0 twrp but still bootloop so i used unbrick tool to put my phone back to stock and then updated to last build though stock recovery and then unlocked bootloader, installed twrp, magisk and done.

Mi5 Unable to boot in OS , boots in twrp despite os installed successful

So i tried installing custom rom , stock rom , Fastboot rom , each time installation was successful through twrp or MiFlash , but whenever i reboot it jumps to twrp , i also tried with stock recovery no success.
Now i dont know what other soln i can try seems all solns tried appeared through google.

Categories

Resources