Database Users

[Help] Rom doesn't flash correctly. Really strange behavior...

Ok this is a really strange Problem. I have two notes. On both I flashed the s5 port from Fahadali. Both had v6 on them and everything was awesome. He left development though so I continued the Project trying to make a "v7" Version, while doing that after I flashed the modified v6 many times but suddenly it softbricked. All I did Change though were some apks.
I've done this many times before with other roms without any Problems at all.
Then I reflashed stock NF4 through Odin and the newest twrp. Flashed v6 (the original non modded version) and it softbricked again...
I tried again, same result. I tried to Flash other recoveries, other bootloaders, other fw's through Odin and a lot more but: nothing.
Everytime I Flash v6 it breaks. I tried to Flash v5 and then suddenly: It worked! I tried to Flash other roms like Omega, and they work aswell. Only the v6 Version doesn't.
So if that's the case and the phone itself is clean (wiped 100 times Flashed stock even with a pit file) the Rom must be corrupted right? So I checked the md5 and well it was correct. I redownloaded and still: same md5. I checked the md5 on the note aswell. I tried using a sd Card instead and still: the same result.
In the meantime my other note worked perfectly, even with my modded Rom. So I continued to work on the v7 using that one. And then after like 14 flashes: the same Problem on that one aswell.
In detail:
I use twrp. And get into the Aroma installer of the Rom. It installs without any Errors whatsoever. Then I reboot.
And now the important part: the kernel has not been flashed cause it's not showing up in red (the rom's using a custom kernel).
This doesn't happen when I use the v5 Rom(still), and never happened before even with the v6. So I even tried flashing the kernel afterwards trough Odin and it gets successfully flashed. But the Rom still doesn't boot...
This means though that because of the kernel not being flashed (even though in Aroma it Shows that it does) even the rest might not get flashed. It only wiped the System Partition and that's it. But then the question remains why did it work before?? And why does it work for all the other People that have flashed it? And why did it work on mine until I flashed it more than 14 times?? And why does v5 and all the other roms still work fine?
I really don't get why this happens. Some v6 files have to still be on the device somehow, or idk. It's impossible cause I wiped but who knows. I've never seen anything like it, neither has the original dev of the Rom.
I Need to get v6 working, else I can't continue to build this Rom. Which is a big Problem for all who wants the s5 Rom.
I hope someone knows what to do. Thank you for your time.

Stuck at "Checking connection" screen. Tried all the options. No luck. Pls help.!

Stuck at "Checking connection" screen. Tried all the options. No luck. Pls help.!
Hello,
I have tried to flash Android Open Source Project 5.1, BlissPop, crDroid. I have been using Android Open source project 5.1. I tried to flash BlissPop and it started this issue. I have no idea for my next steps. My phone is down since last two days so thought to come here for help.
Steps I tried.
1) Removed Data, cache, Internal storage, system and Dalvik cache. Flashed new ROM and GApps.
2) Tried to re-connect wifi at "Checking connection" stage and rebooting device again and again.
Any help would be appreciated.
Thanks in advance.

DhavalVyas said:
Hello,
I have tried to flash Android Open Source Project 5.1, BlissPop, crDroid. I have been using Android Open source project 5.1. I tried to flash BlissPop and it started this issue. I have no idea for my next steps. My phone is down since last two days so thought to come here for help.
Steps I tried.
1) Removed Data, cache, Internal storage, system and Dalvik cache. Flashed new ROM and GApps.
2) Tried to re-connect wifi at "Checking connection" stage and rebooting device again and again.
Any help would be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Serious ? You only tried these 2 steps and looking at a dead phone for 2 days,lol.
Why you dont take the time to try restore your stock image or find another custom rom based on marshmallow.
Seems like the roms your trying are outdated.

Sickaxis79 said:
Serious ? You only tried these 2 steps and looking at a dead phone for 2 days,lol.
Why you dont take the time to try restore your stock image or find another custom rom based on marshmallow.
Seems like the roms your trying are outdated.
Click to expand...
Click to collapse
Thanks for the response. The thing is I got busy with another event so didn't work much. But I will re-install stock OS first and see if it works or not. After that, i will try other custom ROMs.

3 Problems after flashing Superman custom ROM, PLEASE HELP!

Hello everyone,
I tried flashing Superman ROM 3 days and at first i was faced with a problem regarding package installer
the problem was no APK file could be installed either from downloading an APK, Play store or from Samsung apps
so i decided to go back to the STOCK rom after trying a couple of troubleshooting things
i cant install ANY stock rom if i put in a Bootloader it just fails and the phone has to be restarted for a new Download mode start
and now when i install STOCK roms SIM card is not working the phone just wont read them ( either in slot 1 or slot 2 ) and last but not least Samsung account is inaccessible and when i try to login it shows Samsung account has stopped.
any help with ANY of these issues is highly appreciated
EDIT: i forgot to mention what ive tried doing
- downloading separate BL and installing them separately
- installing another custom rom ( same results as Superman ROM )
- changing Modem
- changing CSC
- changing the physical Sim card
- installing marshmallow stock Rom
- clearing cache and app data to all the apps with the mentioned problems
its been 3 days and I've tried everything i can think to solve those problems to no avail

I've had issues before with flashing Superman 2.9 with TWRP 3.2.1.x -- just downgrade to TWRP 3.1.1.0 and try again. Chances are you'll be fine with Superman then.

Sim card not detected
I installed superman rom on my s7 edge, the installation was successful but the sim card was not getting detected, so I decided to install rr os, which I had been using for the past few weeks, and still the problem is not solved, can anyone please help me with this ?

Do a stock software through odin and it should be alright..

Redmi Error with TWRP (A rare one )

Hi everybody,
As i installed TWRP through the fastboot mode and tried to remove the Data/Delvik Cache, The error said
Error Opening : /data/data/com.instagram.android/cache/images/13118ca1.clean (I/O error)
I have tried deleting through the file manager but it still gives the same error, I cant flash a new rom as well as my Original stock rom is already screwed. Anybody has Idea regarding that ?

Try different version of TWRP
anyway I'm using latest one and it works calmly without any issue

HashanR said:
Try different version of TWRP
anyway I'm using latest one and it works calmly without any issue
Click to expand...
Click to collapse
I have tried TWRP every version and the error still remains the same. Its something related to the I/O of the phone, Which i couldnt figure out.

Screen problem

Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.

Up :good:

When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.

Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.

Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.

Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !