[Q] i9506 Post-Flashing Screen Deaths - Galaxy S 4 Q&A, Help & Troubleshooting

Hi all, I own an i9506 and I recently flashed a 4.4.2 rom to it (currently using a 4.3 stock from here: http://forum.xda-developers.com/showthread.php?t=2597058). The procedure of this flashing went roughly as follows:
1) Entered into Philz recovery, did the wipe required to flash a new rom (the option which specifically stated this). Cleared all the cache partitions, dalvik cache etc.
2) flashed the new rom, flashed gapps. Of all the KitKat roms available on the i9506 dev board, I've tried Buda's SPL Gaming Rom and solk2's CM11 Rom.
3) Reboot.
Upon startup, I completed the usual logging into Google accounts, cyanogen accounts, time/date settings, before the play store automatically began downloading all of my apps. After all the apps were downloaded smoothly, I turned the screen off. But it never turned back on again, though the two bottom buttons beside the home button light up when the home button was pressed. Having no other choice, I pulled the battery and turned the phone back on. This time, the moment the bootloader animation finished, I got a systemui crash error, which kept reappearing every time I clicked OK to dismiss it, rendering the phone totally useless. I've also tried going straight into a reboot after loading my apps (so no turning off the screen and battery pulling), but it still boots into that systemui crash loop.
Here's what my phone is running on now:
Baseband Version: I9506XXUAMHD
Kernel Version: 3.4.0 [email protected] #1 Sat July 5 16:42:37 CEST 2014
Build Number: JSS15J.I9506XXUBNE1
SE for Android Status: Permissive
In summary;
- after flashing a new rom, everything works fine before rebooting/turning off the screen
- Titanium Backup doesn't come into play here
- Dirty Flashing only makes the new rom hang at the bootloader animation
- no, I can't post on the original thread where I got the ROMs, cuz apparently I'm too noob, and the creators don't answer to PMs.
So my questions are:
1) is this FIXABLE?
2) has this happened to anyone else who's running a similar setup?
3) am I doomed to never enjoy Android 4.4??

gptthehumanboy said:
Hi all, I own an i9506 and I recently flashed a 4.4.2 rom to it (currently using a 4.3 stock from here: http://forum.xda-developers.com/showthread.php?t=2597058). The procedure of this flashing went roughly as follows:
1) Entered into Philz recovery, did the wipe required to flash a new rom (the option which specifically stated this). Cleared all the cache partitions, dalvik cache etc.
2) flashed the new rom, flashed gapps. Of all the KitKat roms available on the i9506 dev board, I've tried Buda's SPL Gaming Rom and solk2's CM11 Rom.
3) Reboot.
Upon startup, I completed the usual logging into Google accounts, cyanogen accounts, time/date settings, before the play store automatically began downloading all of my apps. After all the apps were downloaded smoothly, I turned the screen off. But it never turned back on again, though the two bottom buttons beside the home button light up when the home button was pressed. Having no other choice, I pulled the battery and turned the phone back on. This time, the moment the bootloader animation finished, I got a systemui crash error, which kept reappearing every time I clicked OK to dismiss it, rendering the phone totally useless. I've also tried going straight into a reboot after loading my apps (so no turning off the screen and battery pulling), but it still boots into that systemui crash loop.
Here's what my phone is running on now:
Baseband Version: I9506XXUAMHD
Kernel Version: 3.4.0 [email protected] #1 Sat July 5 16:42:37 CEST 2014
Build Number: JSS15J.I9506XXUBNE1
SE for Android Status: Permissive
In summary;
- after flashing a new rom, everything works fine before rebooting/turning off the screen
- Titanium Backup doesn't come into play here
- Dirty Flashing only makes the new rom hang at the bootloader animation
- no, I can't post on the original thread where I got the ROMs, cuz apparently I'm too noob, and the creators don't answer to PMs.
So my questions are:
1) is this FIXABLE?
2) has this happened to anyone else who's running a similar setup?
3) am I doomed to never enjoy Android 4.4??
Click to expand...
Click to collapse
Hi mate ,
I do not own a I9506 but what i would do is:
1 did you try a factory reset from recovery
2 Factory reset clear dalvick and cache , flash rom full wipe again
3 If everything fail , flash stock rom with Odin and start again......
Only restore data app with TB , do not restore system data only do it if is the same rom , if is a different rom from a different dev it may give you problems

Related

Stock Everything

What I want to do is install a stock non rooted rom, kernel, and recovery. I am not sure how to change recovery to stock either is it like flashing a rom? Please give me some links for these I can't seem to find them, besides the stock kernel I found that.
----------------------------------------------------------------------------------The reason I want the above is bellow, if it matters.-----------------------------------------------------
My phone is about 95% broken.
Before, every rom/kernel combination would randomly restart, it was my phone it self I believe.
I went to a stock rooted rom, but then it restarted, and my lock screen worked, yet my home screen was black all i could do was slide my status bar down.
After that i restarted my self and then it got stock forever on the screen where it says Samsung galaxy s4.
The 5% working part is my recovery, for the most part.
I keep having to do a full wipe, not just system wipe otherwise it says error unable to mount preload or i/o or a few other things, I have to system wipe before every rom attempt.
I tried several popular roms such as sacs and triforce and a few other roms and all the kernels also.
The phone will turn on, work for a little normally, then crash again and go into the infinite loading screen where is simply says galaxy s4.
This phone is only 3 months old, so I want to take it back to sprint being completely stock so they give me a new phone.
I need links to files I need, and if i am forgetting to change anything back to stock please let me know. Thank you.
I replied to you in the newbie thread, but to return to complete stock download the latest firmware from here: http://www.sammobile.com/firmwares/ and install it with odin. Do a factory reset before and after install to make sure you have cleared out what ever is causing your problems. After this process you will be completely stock and unrooted. If you are still having problems after this it is probably hardware related.

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

Nexus 6p not booting (running custom ROM)

A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
JustJohnItalia said:
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
Click to expand...
Click to collapse
The best thing to do is this guide. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page384. Just go full stock without formating the internal. Flash twrp and see if you can get your photos. Next time back your photos up with Google photos if available in your area. Good luck
JustJohnItalia said:
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
Click to expand...
Click to collapse
To update a ROM all you usually need to do is flash the newer version, but you also need to flash the newer vendor.img of the updated ROM is based on a newer Google build. Failure to do this is what caused the "it looks like your vendor image is obsolete" message to appear. I'm guessing you know this though as you went on to flash it later.
Not sure what happened with TWRP but you've done something else wrong at some point. Best idea (as pointed out above) is to flash the factory images. You can try it without formatting userdata in order to retrieve whatever it is that's important on your storage, but once you've retrieved whatever you need (if you even can) you'll need to format it because you really need to start fresh.

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

home button press causing phone to reboot then corrupt

Recovery: twrp 3.1.0.1-klte
Os: lineage-14.1-20170122-UNOFFICIAL-kltedv
Samsung Galaxy S5 SM-G900I
Issue:
Installed twrp over odin with no issues, followed instructions and backed up samsung stock rom.
downloaded open_gapps-arm-7.1-nano-20170822 to go along with lineage-14.1-20170122-UNOFFICIAL-kltedv rom.
Installation went fine with no unexpected errors, pre setup went fine and phone seemed to be in a operational state until the phone would screen timeout then the issues began.
Clicking on the home button to wake screen causes the phone to kill and reboot forcefully with no notice, then tries to load lineage os then goes straight into crash state and constantly reboots then bricking the os.
Tried wiping divik and internal storage, changed gapps to open_gapps-arm-7.1-stock-20170822 and reinstalled the lineage os platform followed same procedure as before and again goes on crash / brick reboot spree when pressing the home button after screen timeout.
gave up and restored stock samsung rom along with everything else (as i backed it all up) running 6.0.1 and no issues since everything working perfectly.
any ideas or is this a known issue? maybe i should look at installing a earlier nightly build of lineage.
dualznz said:
...
any ideas or is this a known issue? maybe i should look at installing a earlier nightly build of lineage.
Click to expand...
Click to collapse
Newest and official nighlies are always here: https://download.lineageos.org/kltedv. Quite an old build you tried... As your device works fine on stock, I'd say the old build is the culprit.
Unified thread for more info: https://forum.xda-developers.com/ga...m-cyanogenmod-14-0-galaxy-s5-android-t3476433.

Categories

Resources