Database Users

[Q] Seems like I've got corruption of some kind...

ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx

I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[Q] Is my G2 dead?

Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?

I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?

GApps not working

First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.

Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.

I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.

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

YU YUREKA AO5510 random bootloop

Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.

AndroGuy18 said:
Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
Click to expand...
Click to collapse
Flash crdroid nougat