Green screen after flashing custom ROM - Samsung Galaxy J5 Questions & Answers

Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.

aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.

#Henkate said:
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
Click to expand...
Click to collapse
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?

aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
I have the same problem …

aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
SiiXFX said:
I have the same problem …
Click to expand...
Click to collapse
You must be on Lollipop to flash RR 6.0.1, just like CM13.

#Henkate said:
You must be on Lollipop to flash RR 6.0.1, just like CM13.
Click to expand...
Click to collapse
Thanks friend I will try.

Same Green Screen
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?

Vityy said:
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Click to expand...
Click to collapse
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.

aytida4 said:
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
Click to expand...
Click to collapse
I flashed the 5.1.1 rom but still i get the green screen/lines at the boot. I always get bootloops when i flash any zip. Plz help

aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ... ???

I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5

Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
Which Custom Rom did you flash?

Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.

AndroiDTechi said:
Which Custom Rom did you flash?
Click to expand...
Click to collapse
not custom rom but kernel idk what the problem is so now i decided to have android backup in order to back again to my current system
---------- Post added at 06:46 AM ---------- Previous post was at 06:31 AM ----------
#Henkate said:
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
Click to expand...
Click to collapse
:good: i back to its current system now what i want is stock rom with customize and rooted system

aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Flash 5.1.1 cynogenmod rom then install RR remix

Demicro said:
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ...
Click to expand...
Click to collapse
For those, who -as I did - don't really understand this (see the quote)...
I had the same issue when I wanted to install a custom Marshmallow ROM (6.0.1) over my stock Lollipop (5.1.1). The solution was to download and flash a new Bootloader and Modem with Odin. See tis:
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801

I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
https://forum.xda-developers.com/galaxy-j5/development/rom-resurrectionremix-v5-8-1-t3566035

iH8Ecchi said:
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
Click to expand...
Click to collapse
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.

wrongwriter3 said:
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
Click to expand...
Click to collapse
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.

iH8Ecchi said:
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
Click to expand...
Click to collapse
Yes.
Because it work only with 5.1.1 bootloader.

Related

HELP regarding Upgrade to MM STOCK ROM OR CM 13.0 !!!

Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.

Flashing Rom Problems

I am trying to change my rom on my Galaxy J5 2015. I have installed TWRP using odin and when I tried flashing Resurrection Remix and Slim 6 I am having the same problems. When I flash the Roms an reboot I get 2 green lines across the display an then it would fade out green and do nthing. Has anyone else have this problem or is it just my phone?
This problem comes when you try install roms like rr6 and slim6 to mm bootloader. They need you to be on ll bootloader. So you would need first to downgrade your phone to stock 5.1.1 and then flash twrp and then flash roms you tried to flash before.
Please read the forum for the rom before flashing.
Almost all the time they say which bootloader you need.
To flash RR and slim 6 you need lollipop bootloaders
claytoncamilleri100 said:
I am trying to change my rom on my Galaxy J5 2015. I have installed TWRP using odin and when I tried flashing Resurrection Remix and Slim 6 I am having the same problems. When I flash the Roms an reboot I get 2 green lines across the display an then it would fade out green and do nthing. Has anyone else have this problem or is it just my phone?
Click to expand...
Click to collapse
You need to downgrade to 5.1.1 through Odin before you can use those roms
Sent from my Galaxy Tab A 10.1 using XDA Labs

[HELP] Is my stock rom hardwired so that no other ROM can be installed??

Is it possible or is it with the recovery image im using
Asus Zenfone 2 laser ze550kl z00l is my phone model
I have tried many stockroms to install but only one get installed perfectly namely back2stock-1.17.40.1234.zip. Because of this i can't even install any other custom roms like i tried to install lineage rom but itstuck on bootloop
Any kind of replies and queries about my problem asked will be much help full
moddinandroid said:
Is it possible or is it with the recovery image im using
Asus Zenfone 2 laser ze550kl z00l is my phone model
I have tried many stockroms to install but only one get installed perfectly namely back2stock-1.17.40.1234.zip. Because of this i can't even install any other custom roms like i tried to install lineage rom but itstuck on bootloop
Any kind of replies and queries about my problem asked will be much help full
Click to expand...
Click to collapse
Install mm framware then install custom ROM...it will sure booted up
mg712702 said:
Install mm framware then install custom ROM...it will sure booted up
Click to expand...
Click to collapse
What im trying to tell is that my problem is not only installation in custom roms but i also cant install any other roms eiether from official site or some other site which means i cant install any roms accept the one the stock rom i mentioned above. And also i already tried to install MM firmware but it gives out error code 7 in twrp. I tried as i was said to install the previous version of lollipop before the update of MM came out but still i cant install them.
moddinandroid said:
What im trying to tell is that my problem is not only installation in custom roms but i also cant install any other roms eiether from official site or some other site which means i cant install any roms accept the one the stock rom i mentioned above. And also i already tried to install MM firmware but it gives out error code 7 in twrp. I tried as i was said to install the previous version of lollipop before the update of MM came out but still i cant install them.
Click to expand...
Click to collapse
Which Android u r using now
Lolipop or MM
is your bootloader locked on unlocked?
just go back to stock versions for now
if u r on lollipop, download the 'next version' from asus
if u r on marshmallow, download the next version from asus
use fastboot (bootloader) mode to flash if required
when all is stable and done,
download & flash twrp
flash lineage 13, then lineage 14
yograjfire18 said:
Which Android u r using now
Lolipop or MM
Click to expand...
Click to collapse
Iam using lollipop right now
pokipokipxorn said:
is your bootloader locked on unlocked?
just go back to stock versions for now
if u r on lollipop, download the 'next version' from asus
if u r on marshmallow, download the next version from asus
use fastboot (bootloader) mode to flash if required
when all is stable and done,
download & flash twrp
flash lineage 13, then lineage 14
Click to expand...
Click to collapse
Yes my bootoader is unlocked cuz i tried rooting my phone when MM update came out
I cant roll back to the original/factory rom cuz i can't install any rom including official asus ones
2. Ill be trying to using fastboot will post results soon
moddinandroid said:
Iam using lollipop right now
Click to expand...
Click to collapse
that's the reason u can install any custom rom, bcs they r all MM or N
so U hav to first upgrade to mm using stock rom
then u can flash any rom
moddinandroid said:
Iam using lollipop right now
Click to expand...
Click to collapse
https://basketbuild.com/filedl/devs?dev=LuK1337&dl=LuK1337/ZF2L-FW/Z00L-WW-21.40.1220.1615.zip
Download and flash then u r ready to go
Now u can install any rom, like RR MM, CM 13 many others too
Hit thanks if i helped
Yeah that right..or you can make backtostock.zip by your self,just download stock mm rom and copy the following requirement file to backtostock.zip and flash that on twrp..
Thnsk guys for all your replies
My problem i was not using latest twrp recovery
Again thank you so much for ur help

After replacing my display touch are not responsive.

My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Prince parth said:
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Click to expand...
Click to collapse
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash moun kernel in different ROMs to check whether it works or not?
ImSSin said:
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash mourn kernel in different ROMs to check whether it works or not?
Click to expand...
Click to collapse
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine??
Prince parth said:
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine
Click to expand...
Click to collapse
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
ImSSin said:
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
Click to expand...
Click to collapse
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Prince parth said:
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Click to expand...
Click to collapse
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Don't need to flash stock ROM I'm on Resurrection Remix treble ROM and for flashing I followed steps stated in forum.. it's work for me no bootloops.
First fastboot flash userdata userdata.img and then boot into Twrp and flash ROM zip that's all.
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Userdata.img is not necessary, just install the rom and format data(must) then reboot
Thnx for the help guys but after spending hours flashing different ROMs, TWRPs and kernels, I finally found the solution for the touch screen bug.
eXtreme kernel is the only kernel that was able to fix the screen completely. Its working in all of the custom ROMs (tried on LOS15.1 & 16, RR, LR Oreo and pie, etc.)
The stock versions of francokernel, void kernel are able to fix the touch screen but it breaks WiFi so they are not a complete fix.
And btw stock versions of Franco,extreme,void kernels work on the stock ROM.
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
yasars said:
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
Click to expand...
Click to collapse
have you tried flashing the extreme kernel?
extreme kernel v11 not working only V8 working for me.
What about you guys??
only with kernal 4.9 based custom roms, i have touch issues as described in here. and yeah i had screen replacement too.
now i can't flash any new pie roms as they all are based on 4.9 kernals and i can't find the old pie roms based on 3.18(link dead)..right now on los15.1
:crying::crying::crying::crying::crying::crying::crying:
Same problem here
ImSSin said:
have you tried flashing the extreme kernel?
Click to expand...
Click to collapse
ImSSin
Were you able to solve this problem? Can you put the link to download the kernel?

Has anyone managed to get any custom ROM to work on a SM-A405FN/DS ?

Hello !
Has anyone actually managed to get any custom ROM to work on a Samsung Galaxy A40 SM-A405FN/DS ?
Mine is currently running the current latest stock ROM (SM-A405FN_2_20211030045838_jg43vcqbiw_fac) downloaded with Frija and I managed to install TWRP from here : https://forum.xda-developers.com/t/recovery-a40-teamwinrecoveryproject-3-6-x-unofficial.4364575/
However, ANY custom ROM that I try to install :
https://forum.xda-developers.com/t/a11-r-arm64-a40-lineageos-18-1-unofficial-by-kevios12.4335409/
https://sourceforge.net/projects/eurekaroms/files/Samsung/A40/R/lineage/
GSI
maybe others that I forgot
will either bootloop or end up with a black screen.
Looking at the following threads, I'm starting to wonder if the SM-A405FN/DS is custom-ROM-compatible at all ?
https://forum.xda-developers.com/t/help-my-a405fn-wont-boot-any-custom-rom.4337041/
https://forum.xda-developers.com/t/samsung-a40-black-screen.4354421/
https://forum.xda-developers.com/t/galaxy-a40-infinite-loop-impossible-to-turn-on.4337343/
Im running CrDroid 7.13 without any issues with root and gapps. Many custom roms bootloop because of your newer firmware with Bit/SW REV.
Security Patch Lvl. being 4 and those custom rom were built on the older firmware with probably patch level 3. I had installed DotOS fan edition fully working like a year ago, then I tried some new custom roms, which somehow broke my system so the system couldnt start up even after reflashing original boot image, so I reflashed to the newest firmware which was working, then I tried flashing older one and it wouldnt boot, it just shows black screen with error bit/sw 3 boot 4. So you have to flah roms, whose are built on the newer bit level to boot up, the best is CrDroid and now the newest ALT-F4 version 0.0.3 from this forum: https://forum.xda-developers.com/t/rom-oneui-3-1-a40-alt-f4-v0-0-1-updated-2021-12-18.4373813/
I tried it myself and it is the best for this phone, it is fully debloated and pre-rooted stock rom. I also tried CrDroid 8x, everything works for me, but it fells slow and the ram is almost maxed out. I also recommend upgrading to this TWRP: https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
The unofficial twrps had some bugs for me. I hope this helps and happy flashing!
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
breversa said:
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
Click to expand...
Click to collapse
Good luck!
Well, luck has not been enough: after updating TWRP to the official version, I tried yesterday to install ALT-F4 0.0.3 but got the exact same result: black screen, need to reflash the stock ROM to make it boot (even to recovery !!) again.
Would you have any other idea ?
EDIT:
I actually tried crDroid in the past, to no avail either.

Categories

Resources