yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Having trouble getting the logs. I boot into recovery, connect via USB, then on my PC, enter "adb locat".

I got "/sbin/sh: exec: line 1: logcat: not found"

After a quick search, found that I should go into the "Mounts and Storage" menu in recovery, and mount /system. Did that, now I got some output:

--------- beginning of system
I/Vold ( 203): Vold 2.1 (the revenge) firing up
D/Vold ( 203): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 203): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 203): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 203): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 65, PARTN 1
D/Vold ( 203): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
--------- beginning of main
I/ARMAssembler( 201): generated scanline__00000077:03545402_00000A02_00000000 [ 31 ipp] (53 ins) at [0xb3acc1f0:0xb3acc2c4] in 72552 ns
I/ARMAssembler( 201): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at [0xb3acc2d0:0xb3acc3a0] in 45208 ns
I/ARMAssembler( 201): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at [0xb3acc3b0:0xb3acc484] in 38177 ns
I/ARMAssembler( 201): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at [0xb3acc490:0xb3acc540] in 36562 ns
I/Vold ( 203): /dev/block/vold/179:65 being considered for volume sdcard1
D/Vold ( 203): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 203): Trying to get filesystem type for /dev/block/vold/179:65
I/fsck_msdos( 203): ** /dev/block/vold/179:65
D/Vold ( 203): Found vfat filesystem on /dev/block/vold/179:65
I/fsck_msdos( 203): ** Phase 1 - Read and Compare FATs
I/fsck_msdos( 203): Attempting to allocate 3747 KB for FAT
I/fsck_msdos( 203): Attempting to allocate 3747 KB for FAT
I/fsck_msdos( 203): ** Phase 2 - Check Cluster Chains
I/fsck_msdos( 203): ** Phase 3 - Checking Directories
I/fsck_msdos( 203): ** Phase 4 - Checking for Lost Files
I/fsck_msdos( 203): 176 files, 3026368 free (749934 clusters)
I/Vold ( 203): Filesystem check completed OK
W/Vold ( 203): blkid failed to identify /dev/block/vold/179:65
D/Vold ( 203): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)

I restart the device through the "reboot" menu option in recovery, and the logcat session exits. I retype "adb logcat", and then I get

"- waiting for device -"

Seems promising, like once the OS on the device starts loading I might start getting log messages, but nothing happens, and it just sits there. Device starts up, then restarts like it's been doing.

Anything obvious I'm doing wrong regarding getting a realtime output of the log? Anything of interest in the log output that did get while it was in recovery? That "blkid failed to identify /dev/block/vold/179:65" could be something, couldn't it?
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
While in recovery, USB connected, after mounting /system so logcat works, started logcat. Then mounted /data. Then mounted /storage/sdcard1. This was the logcat output:

--------- beginning of system
I/Vold ( 204): Vold 2.1 (the revenge) firing up
D/Vold ( 204): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 204): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 204): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 204): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 65, PARTN 1
D/Vold ( 204): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
--------- beginning of main
I/ARMAssembler( 202): generated scanline__00000077:03545402_00000A02_00000000 [ 31 ipp] (53 ins) at [0xb3aa01f0:0xb3aa02c4] in 70573 ns
I/ARMAssembler( 202): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at [0xb3aa02d0:0xb3aa03a0] in 46563 ns
I/ARMAssembler( 202): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at [0xb3aa03b0:0xb3aa0484] in 37604 ns
I/ARMAssembler( 202): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at [0xb3aa0490:0xb3aa0540] in 36042 ns
I/Vold ( 204): /dev/block/vold/179:65 being considered for volume sdcard1
D/Vold ( 204): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 204): Trying to get filesystem type for /dev/block/vold/179:65
D/Vold ( 204): Found vfat filesystem on /dev/block/vold/179:65
I/fsck_msdos( 204): ** /dev/block/vold/179:65
I/fsck_msdos( 204): ** Phase 1 - Read and Compare FATs
I/fsck_msdos( 204): Attempting to allocate 3747 KB for FAT
I/fsck_msdos( 204): Attempting to allocate 3747 KB for FAT
I/fsck_msdos( 204): ** Phase 2 - Check Cluster Chains
I/fsck_msdos( 204): ** Phase 3 - Checking Directories
I/fsck_msdos( 204): ** Phase 4 - Checking for Lost Files
I/fsck_msdos( 204): 176 files, 3026368 free (749934 clusters)
I/Vold ( 204): Filesystem check completed OK
D/Vold ( 204): blkid identified as /dev/block/vold/179:65: UUID="9016-4EF8" TYPE="vfat"
D/Vold ( 204): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)

The /dev/block/vold/179:65 were written after mounting /storage/sdcard1. So I wonder if that "blkid failed to identify /dev/block/vold/179:65" message indicates some issue with my internal storage. Could it somehow be unavailable once the OS starts up?
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
No, don't flash anything custom, not even the same ROM

That ROMs links were removed from XDA because of this problem, where did you get it from?

Go into settings, hit the magnifying glass at the top, and search for "Reactivation Lock" - it's possible you might find it that way, and if you do, disable it immediately

Once it's turned off, you can factory reset, or flash another ROM

I have a vague memory of someone else finding it that way
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Wow, so reactivation lock is enabled by default for this ROM, but is it possible to set it to disabled at some point during the install process, and if so, is there a way I can see if I set it to disabled?

I got the ROM almost a year ago, so it doesn't look like this issue was known at that point, at least in the ROM's thread.

I'm running 2.1. Is it possible the reactivation lock wasn't an issue with that version (latest is 2.2, although looks like there are unofficial versions 2.3 and 2.4)?

Would I be able to re-install the ROM from zip file in recovery, then at first boot follow this procedure? -- http://myandroid.nl/reactivation-lock-solution-for-galaxy-s5/

Or actually, upon looking at that, can I just go into settings-->security and uncheck "Reactivation Lock"? It sometimes gives me up to 30 secs before restarting, so I could probably manage that.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
If the setting is there, disable it and you're golden

The problem was with the latest version (2.2 I think), the only setting was during 1st boot

Possibly able to find using the search function in settings too according to a member here but not 100% on that
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
I was finally able to get some potentially useful logs.

Not sure if it was all necessary, but I enabled developer options by doing the "tap build number 7 times" thing, then enabled USB debugging, which I thought I've always had on for every phone/ROM I've had, but must not have ever done it for this one. Then I had to either plug in the USB cord after the phone started booting up, or select the USB connection options notification (not sure which of those actions did it), and I was suddenly able to maintain an adb shell while the phone continuously booted up and restarted.

At first, trying to use logcat, I'd get a "Unable to open log device 'main'" error message. So I had to comment out the "rm /dev/log/main" line from /system/etc/init.d/logcat. Which I was only able to do which the phone in recovery mode. However, in recovery mode, I didn't have vi in my path, but eventually found it under /system/xbin (just putting that here in case it helps anyone in the future).

So finally logcat was working while the boot loop was in progress, and I got the attached logs. The first one was taken starting from right after the phone restarted. It went until it got to the lock screen, then for some reason my adb session would get dropped, even though I could immediately reconnect. The second file is from right after that happened to just after the restart happened again.

Any obvious messages that explain why it's restarting?

"FATAL EXCEPTION IN SYSTEM PROCESS: WifiStateMachine" doesn't look good.

"FATAL EXCEPTION: UlrDispSvcFastTask" also... I see here that enabling "keep awake" permission for Play services fixed that, so I'll try to figure out how to do that.

There are a lot of "Unknown permission" messages.

Lot of "RuntimeException: android.os.DeadObjectException" and "RuntimeException: Package manager has died" errors. Maybe some/all of these are caused by the system shutting down and aren't actually problematic.

Also looks like some warnings/errors could be related to lack of any network connectivity (no SIM installed and I have wifi off).

Thanks for any help deciphering this stuff.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
I'm not into the coding side of Android, so it would be the blind leading the blind if we went down that route

--Try safe mode--

Turn on safe mode

Turn the device off.

Press and hold the Power key.

When 'Samsung Galaxy S5' appears on the screen, release the Power key.

Immediately after releasing the Power key, press and hold the Volume down key.

Continue to hold the Volume down key until the device finishes restarting.
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Thanks for the suggestion, but that was actually the very first thing I tried. I was totally confident it *must* be an issue with one of the two apps I installed since last rebooting, so all I'd have to do is start in safemode, remove those apps, and it'd be fixed, right? Man I wish it had been that easy.

Is it even possible to set reactivation lock to disabled at some point during the ROM install process, or is it just forcefully enabled? Seems like a lot of people must not be having this issue, so they must have been able to disable it at some point, unless it's just that all those people haven't had to reset, reinstall, or install a new ROM. Really wish I could see if it's enabled or disabled for me, as I can't see myself enabling it if given the choice. If that question came up during the install, I'm pretty sure I'd have looked up what "reactivation lock" was and chosen to disable it.
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Didn't have any luck finding a way to enable "keep awake" permission for Play services. At least, under settings-->Application Manager-->Google Play Services, I see a bunch of descriptions for permissions, but no way to enable/disable them. And I haven't even been able to find one that looks like it'd be the "keep awake" permission.
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Looking at t-mobile's page on reactivation lock, they have directions for enabling/disabling it: https://support.t-mobile.com/docs/DOC-21136

Logging into http://findmymobile.samsung.com/, my account shows that no devices are associated with it. Would that indicate that I haven't had reactivation lock enabled before, or is this completely irrelevant?
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Boot into download mode and check if it tells you Reactivation Lock is enabled (Volume Down & Home & Power)

Problem is, if you flash that ROM again, to initiate setup, you'll get locked out most likely

There is a solution, which works for 'most' people, but lately it's been less and less effective, and it means risking locking yourself out to try it

Flashing a stock KitKat ROM, and logging into your Samsung / Google accounts on first boot, allows disabling of reactivation lock

Problem would only start, if ODIN fails to flash that KitKat ROM

Like I say, this usually works, but with newer revisions of the S5, it's been failing for a few people lately

You say you have had this ROM installed for a year, and I got my S5 around a year ago, and I can flash with ODIN fine, so you will likely be OK to go for it

Other alternative would be to remove the apps manually from recovery or ADB via PC USB
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Okay, I went into download mode and it's not giving me any sort of info that blatantly tells me whether or not RL is enabled/disabled. This is what I get:

ODIN MODE
PRODUCT NAME: SM-G900T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START

Then there's the message on the middle of the screen with the green android logo saying "Downloading... Do not turn off target".

I got it almost two years ago, pretty much right when the S5 came out, so it's probably the first version.

How would I go about doing that? In recovery I can't find any option that looks related to app removal, and I can't even really browse+delete files from there (there is an "aroma file manager" item, which fails because it says it's not installed). From ADB I could delete files, but I'm not sure what all I'd need to delete in order to fully remove an app. Plus, I've already uninstalled the apps that should, *in theory*, be the only possible offenders, just through regular means (app drawer, drag app icon to "uninstall") during the small window of time I get after each boot.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
I was expecting a screen showing this

For removing the apps, you'd need to navigate to /data/app and delete any packages you think could be the offenders

That should be enough to kill them from starting up with Android

but it could also be a system app, /system/app

Other location could be /data/data

If the phone is 2 years old, I'd say you have a very good chance of just flashing a KitKat ROM and then boot into recovery > factory reset > log in with your Samsung & Google accounts and disable reactivation lock (If it is enabled, which I assume it will be)
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
Looking at the thread, and in particular this guy's post, it sounds like the reactivation lock issue might have been introduced in 2.2. Since I'm on 2.1, maybe I can still re-install 2.1 without RL-related problems. Seems like people with the RL enabled can't even boot into recovery. I've been living in recovery.

Even if I can't, and I get locked out after re-installing the ROM, I can still go back and flash a KK ROM with Odin, disable the RL setting, which is what I'd have to do anyway, right? Is there any disadvantage to trying to install the ROM directly to see if I have RL disabled?
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Give it a shot, phone is not usable as it is
[Galaxy S 5 Q&A, Help & Troubleshooting] Brent212:
I went ahead and installed the original version I was on, 2.1, but tried selecting the non-full wipe option in an attempt to keep my apps/settings. Basically did nothing. Phone still restarted after booting. Then I did a full wipe+install, got through the startup prompts, including the "do you want to enable reactivation lock?", which I unselected (and am now positive I unselected the first time as well). Google/Android gives an option to restore apps/settings from some backup done through your google account, so I selected a few that I knew I'd need right away and/or have extensive setup.

Unfortunately, I think that last step was a bad one, because I still got the auto restarts. So I did the whole thing again, and instead selected the option that's along the lines of "set this up as a new device". Everything worked fine after that. Phone boots up, and amazingly, stays on.

I even went ahead and upgraded to 2.2, since I figured, if I'm going to start from ground zero, I might as well use a newer version of the ROM, mainly because I'm hoping I can use the KToonsez kernal, which I remember seemed to cause my phone to be unstable/buggy when I first installed 2.1 almost a year ago.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Nice one, so it sounds like it was indeed an app causing the reboots, if restoring apps caused it again, and not restoring them fixed it
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] musiclover7:
Ok, I went in today to reload MOAR ROM on my phone. I had initially thought to check if maybe there was a higher compatible firmware version than BOC4, so I posted to the thread, but then I figured everything was working fine on my phone so why bother.

I loaded NI2 and booted up into safestrap recovery.

Once in safestrap, I tapped wipe, but strangely, it was like the touch screen registered 2 rapid taps, and before I know it the phone is formatting. Me, I try to do a data wipe after this, silly me, and it doesn't work. It no longer seems to detect distinct partitions, probably cuz the entire internal drive just got formatted.

Anyways, I proceed to install MOAR, and then the BOC4 firmware. Now the phone starts to boot, gets to Samsung screen, hangs there for a few seconds, then reboots. It's caught in a boot loop. I am guessing that safestrap might have been removed, and I am looking advice as to how I might go about reloading it, if that is indeed my problem.

Or really, any pertinent advice on how I might make my phone function again would be greatly appreciated!
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] musiclover7:
Worth noting, I am able to boot into Recovery, which I am pretty certain means that my phone is not bricked. Just not sure what to do from here. Thanks!
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] musiclover7:
hmm.. I just tried factory reset in recovery, and now it maybe appears to be booting for first time. I have that spinning tornado boot animation that came with MOAR. Should maybe come up in 10-15 min, fingers crossed...
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] CVertigo1:
Did it work? If you formatted, assuming you are not on the latest bootloader, you'll need to flash the NCG restore tar and start the root process from the beginning.

Also, I'd suggest upgrading to [MENTION=1949695]jrkruse[/MENTION] latest safestrap, as it removes the format button.
[Zenfone 2 Laser General] Mandrakerj:
Someone has already Deodexar the Stock Rom Zenfone Laser?

Would very much welcome a Tutorial,

help at all ..
[Zenfone 2 Laser General] rajlko:
use superr kitchen, linux based.

http://xdaforums.com/chef-central/android/kitchen-superrs-kitchen-t3202296

for windows based

http://xdaforums.com/showthread.php?t=2639400

every thread has very good tutorial, hope it will help you. :good:
[Zenfone 2 Laser General] Mandrakerj:
Well I can not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
[Zenfone 2 Laser General] Mandrakerj:
not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
[Zenfone 2 Laser General] Mandrakerj:
Someone has already Deodexar the Stock ROM and install the device?

Can anyone help ??
[Zenfone 2 Laser General] Rizzed:
I will deodex the stock ROM later when I get back. I currently have kitchen running on my Mac.
[Zenfone 2 Laser General] Mandrakerj:
I also needed to Zenfone selfie ZD551KL
[Zenfone 2 Laser General] Rizzed:
Alright. I will try to get it done by today..
[Zenfone 2 Laser General] Rizzed:
*Link deleted*

FOR ZD551KL VARIANTS ONLY. Any attempt to flash this ROM on other ZenFone 2 series' variants would result in getting stuck at the manufacturer's logo. In that case, you would need to flash the stock ROM back to get it back to a working condition.

I do not have the ZD551KL variant of the ZenFone 2 Selfie with me now, thus, I can't test it out. Please do report back the results after flashing, and inform me immediately if "errors" or "signals" appear upon installation. Thanks!

EDIT: If this works out fine, I will be doing the same for the other variants of the ZenFone 2 series and then place them all into another thread!
[Zenfone 2 Laser General] beenkenobee:
this is for the ze551kl?

install from root with twrp?

rooted?

thanks
[Zenfone 2 Laser General] Rizzed:
Nope, only for ZD551KL devices. I just found out that there's essentially no point in removing the verification checks, as even if it installs on the other variants, it would fail to boot as the kernel files are different. That is, unless you are willing to flash the boot.img yourself, which requires downloading the original ROM, extracting, and using the fastboot commands "fastboot flash boot boot.img".

Following up on your other questions, no. No root is required to install this ROM, only a custom recovery, such as TWRP or CWM. The ROM is also NOT pre-rooted (well, I need to learn HOW first.)

I could compile a deodex-ed ROM for you later. Though I would suggest you to wait out a while for the people with the ZD551KL variants to test it out first and see if the Android Kitchen's modifications really worked.

As for now, I will leave the download file as it is (no verification checks). I will update it tomorrow, together with the compiling for the deodex-ed ROM for ZE551KL variants (as well as others, if time permits).
[Zenfone 2 Laser General] Mandrakerj:
Rizzo, what application you are using to Deodexar the Rom? Here I only use Windows 7 x64
[Zenfone 2 Laser General] Mandrakerj:
Rizzo, I still do not understand anything.

This Stock ROM that you made available for download, it would be for selfie ZD551KL? What would be the version of this Stock Rom? She has not estarai Deodexada, correct? What do I do here with her in my ZD551KL? Install from sdcard or would the TWRP? I would like to learn how to Unzip the System Image Stock Rom ZD551KL. I do not know how to do this. How can I help you?
[Zenfone 2 Laser General] Rizzed:
Sorry for the confusion guys.... I will be testing it out on my ZE550KL first and see if the tool works properly. If it does, I will help to de-odex the ZD551KL variants (and possibly others too) and post it on an entirely new thread.
[Zenfone 2 Laser General] Mandrakerj:
Hi there friend thank you for your help. I will wait for the results with your Laser ZE550KL. I'm hoping that everything goes well. So I will wait for the procedure for Variant selfie ZD551KL because this is what I need right now.
[Zenfone 2 Laser General] Rizzed:
Alright! Everything appears to be working... I have not tried flashing yet, but, it should be able to boot up fine.
[Zenfone 2 Laser General] Mandrakerj:
I've deodexar the Stock rom selfie ZD551KL. I just can not install because of the error in updater-script.
[Zenfone 2 Laser General] Rizzed:
In that case, could you upload the updater-script so that I could have a look at it?
[Zenfone 2 Laser General] Mandrakerj:
So my friend..

In fact I do not even have the original file to the selfie ZD551KL.

What I was tested in a template JoelDroidLollipopBatchDeodexer the page.

This man did not work ...

I found no script created for Deodexar Rom in selfie ZD551KL.

Here for you ..http://www.mediafire.com/download/84m7v0qubav1m32/InstallerTemplate.zip
[Zenfone 2 Laser General] Mandrakerj:
So my friend Rizzed..

In fact I do not even have the original file to the selfie ZD551KL.

What I was tested in a template JoelDroidLollipopBatchDeodexer the page.

This man did not work ...

I found no script created for Deodexar Rom in selfie ZD551KL.

Here for you ..http://www.mediafire.com/download/84...erTemplate.zip
[Zenfone 2 Laser General] Mandrakerj:
Rizzed

Any progress?

I got the Deodex ?
[Zenfone 2 Laser General] danmar90:
Is this working for ZD551kl? Hehe thankyou!
[LG G Flex 2] pelelademadera:
Hi.

Can someone find full housing for the phone?

I need the frame and battery cover... Its not destroyed, It works great, but I want a renew...

Im from argentina, I found it in India, but dont ships here.

Maybe someone can recive my money, buy it, and reship it to me...

Thanks so much
[LG G Flex 2] k3lcior:
Check Ebay & Aliexpress