Rolling Screen S5 SM-G900F - Galaxy S 5 Q&A, Help & Troubleshooting

Hi,
I tried flashing LineageOS on my S5 and after installing Gapps with some minor difficulties it started working properly.
Then 20minutes later it started doing the rolling screen effect exactly like in this video: 123.youtube.com/watch?v=LSsOGpF_a8I
Can't link the video, new user policy.
But then i tried flashing the ROM stock again lest it was Lineage's fault and now i can't even access the phone.
I can go to Download and Recovery Mode although it's a little difficult navigating.
The phone was italian branded TIM.
Anybody has any idea on how to solve this?
Thanks

its your fault for not making a full wipe of your phone before stock rom
you should have installed twrp and then wipe >>>> advanced wipe and check everything but not external sd lol
then swipe to wipe
then go to download mode and flash stock

Related

N9005 camera problem

Hi guys, does anyone have problems with taking pictures with samsung camera? When I take pictures sometimes phone immediatelly shut down and I cannot turn him on until I take battery out and then turn it on.
I am using official rom. 5.0 lollipop.
Does someone had similar situation? Any solution on this?
Tnx
Try to reflash your rom and clean cache and dalvik.
Its official 5.0 rom. Installed who knows when Phone is not rooted.
Try what the above person said.
Install custom recovery TWRP. Boot into it. Go to Advanced wipe section, wipe everything. (Be informed that this will completely wipe the phone, you will have nothing after this on your phone). Upgrade the boot loader to Lollipop if you already haven't. Then flash an official Lollipop ROM.
No, I have never had that issue, not once.

[G900F] [VRToxin-v2.0-20151205-klte-RELEASE] System UI Stopped Working error loop

Hi all, this is my first post so be nice!
First off, I'm a complete newbie when it comes to flashing custom roms. I've had my G900F for almost a year now and I always hated one thing about it: TouchWiz (or DungWiz as I like to call it). So, last week, I decided to take the plunge and flashed albinoman's CM13 on it. For the most part, it has served me well but I wanted to try out VRToxin as well and so, I flashed it today. However, I wasn't able to get past the Welcome screen because of constant 'SystemUI has stopped' error loop. To better explain my problem I'll list exactly what I did:
Note: Before flashing VRToxin, I had CM13 Dec 10 build.
1. Downloaded VRToxin-v2.0-20151205-klte-RELEASE and Stock GApps from opengapps.org
2. Copied the files to phone's internal storage.
3. Shut down the phone and booted it into TWRP.
4. Did a full nandroid backup.
5. Did a full wipe: Delvik cache, System, Data and Cache.
6. Flashed the VRToxin rom and then flashed the open gapps (stock)
7. Rebooted the phone and got to the Welcome screen. However, I cannot get past this as 'SystemUI has stopped' error keeps popping up.
I've since restored CM13 from TWRP backup.
If anyone can help out with this problem or provide info about why this is happening, I'd greatly appreciate it!
NadirMichael said:
Hi all, this is my first post so be nice!
First off, I'm a complete newbie when it comes to flashing custom roms. I've had my G900F for almost a year now and I always hated one thing about it: TouchWiz (or DungWiz as I like to call it). So, last week, I decided to take the plunge and flashed albinoman's CM13 on it. For the most part, it has served me well but I wanted to try out VRToxin as well and so, I flashed it today. However, I wasn't able to get past the Welcome screen because of constant 'SystemUI has stopped' error loop. To better explain my problem I'll list exactly what I did:
Note: Before flashing VRToxin, I had CM13 Dec 10 build.
1. Downloaded VRToxin-v2.0-20151205-klte-RELEASE and Stock GApps from opengapps.org
2. Copied the files to phone's internal storage.
3. Shut down the phone and booted it into TWRP.
4. Did a full nandroid backup.
5. Did a full wipe: Delvik cache, System, Data and Cache.
6. Flashed the VRToxin rom and then flashed the open gapps (stock)
7. Rebooted the phone and got to the Welcome screen. However, I cannot get past this as 'SystemUI has stopped' error keeps popping up.
I've since restored CM13 from TWRP backup.
If anyone can help out with this problem or provide info about why this is happening, I'd greatly appreciate it!
Click to expand...
Click to collapse
The problem is GAPPS. I noticed this too. Just do a full wipe (i know, again ) and install the GAPPS from VRToxin (filename = vrtoxin-gapps-mm-20151101). Link = http://downloadandroidrom.com/file/GalaxyS5/900froms/VRToxin. I don't have a actual fix but he its a workaround :cyclops:
Thanks Dante, I'll give it another go
NadirMichael said:
Thanks Dante, I'll give it another go
Click to expand...
Click to collapse
And? did it worked?
I'm gonna be honest with you im currently searching for the stock Lollipop (rooted) for S5 (SM-G900F) because this ROM isn't working for me.
- Bluetooth isn't working. (it does not turn ON, you can slide but its still OFF)
- 2x clock-app in the menu
- Music player does not work even the google play music app. ( i use VLC media player)
- No fingerprint security lock.
But its a pain in the [email protected]#$%^&*()_+ to find it here on XDA. If you know where to find it please let me know.

Messed up software (maybe)

Hello, so I got an s4 GT-I9505 that had a cracked screen so I fixed it.
Phone booted as it should and worked fine for few minutes, then things started to crash (statusbar, touch wiz home), it starts to lag and behave very weird so I decided to do factory reset - same stuff happened.
So I flashed CM12 everything works fine besides the fact I dont have sound.
So I flashed back to stock using odin and pit file, it boots to stock sometimes it has sound and sometimes it doesn't, also it crashes like it used to after few minutes and reboots to bootloop.
I flashed CM12 again so I can use the phone somehow, but whenever I go into the AudioFx app it crashes so do other apps that need sound either crash or lag.
What is the issue? I'd love to stick to stock rom but I cant use it as it keeps crashing.
How do I fix this problem it's important for me to have this phone working.
Did you do full wipe before flashing?and is the screen original or chinese?
Try a custom stock rom.
johnaras said:
Did you do full wipe before flashing?and is the screen original or chinese?
Click to expand...
Click to collapse
I don't really know, got it on ebay for 50 pounds. And I did a full wipe using the stock recovery.
Possible loose connection somewhere?
Flash twrp and then wipe all..make wipe data/factory reset,wipe cache,wipe system,wipe dalvik cache and wipe data.all these from advanced wipe.then turn off phone and put it in dowload mode.then flash stock rom using odin.this is the cleanest way to flash rom.maybe in system is something from cm and messes up with stock.as for the sound it may be from the screen.some chinese screens make phones lag,even not boot up.
I forgot to add that I get sound at the boot animation but after that no sound at all
I have installed costum rom F14 on the 4.4.2 android version. It makes the modified boot noise and the sound works for for a few minutes, only sometimes but.
Anybody?

[SM-T530] Screen "frozen" after flashing stock 5.0 Lolipop

So I've been having this strange issue for a year now, where I want to upgrade my SM-T530 (Tab4 10.1 wifi) to the stock Lolipop (5.0.whatever) ROM in order to get the damn kernel updated so I can access all these wonderful custom ROMs (Stuck on CM 12 atm...).
But whenever I flash a stock ROM for my model, it seems to freeze the screen after the boatloader. As in, everything seems to be working, sound and touchscreen, it just doesn't update/refresh the screen. Basically, the same behaviour as described in this post.
So here's the steps I took, in the hope that anyone can point me in the right direction:
Boot tablet in recovery (TWRP 3.0.1, in this case) and wipe Dalvik, /data, /cache, /system, basically everything)
Reboot tablet into bootloader/download mode
Using Odin 3.11.1, flash T530XXU1BOL2_T530PHN1BOE1_HOME.tar.md5 (Found here, which should be the correct ROM for my model (Bought in the Netherlands, but I have no idea where you folks are pulling this T530XX stuff from, it's nowhere to be found on the back))
Reboot tablet
After the 4th step, the tablet will be unresponsive for ~10 minutes (I think it's doing the whole "upgrading apps" thing that follows a new installation). After that, when I hit a certain area of the screen, I can hear the regular Android touchresponse, raising the volume also give the normal beeps and pushing the power button plays the "turning off screen" sound, but the screen stays active, showing the Samsung Galaxy Tab4 boot logo.
Soooo... Anyone care to take a guess what I'm doing wrong?
Personally, I think it might have to do with flashing the incorrect stock ROM, but for the life of me, I can't find out which T530-code I have. I've been flashing different ROMs, but no luck so far...
As for troubleshooting I've already tried:
The above procedure, afterwards flashed TWRP via Odin and flashed a custom ROM via TWRP. Same effect.
Variations of the above procedure, where I keep wiping the tablet after each step
Different custom ROMs
Ugh, nevermind.
Turns out I have an UK tablet (BTU-T530XXU1BOG2). After flashing a dozen or so ROMs, this one did the trick.
Oh well, problem solved :good:

[solved] Phone is acting weird ... random reboots shortly after boot

Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you
If nothing helps reflashing the whole firmware is always an option
minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.
rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case
Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.

Categories

Resources