Related
Scandinavian Desire Z, Cyanogenmod 6.1 RC-3 for Vision.
When selecting "Network Operators" under Settings --> Wireless and Networks --> Mobile Networks, I expect to see a list of the different providers, but nothing comes up. When selecting "Search networks" an error message comes up saying: "Error while searching for networks".
This is important to me because I have a provider which has terrible coverage, and I want to lock the phone to use another provider. (Which is kind of part of their subscription).
So I try to add an APN manually, without really knowing if this might work or not, but it just disappears from the list (of APNs) after I've saved it.
Does anyone else experience the same issues or can tell me how Im ******* up?
I would post this up in the thread on CyanogenMod in the G2 forum, you should get a response there (the developers look in on that one).
Yeah, great minds think alike, etc. I did just that and got a reply saying I might be using the wrong radio, and maybe I didnt catche the OTA radio update. I've not seen any OTA, but my radio seems to be up to date:
12.28b.60.140eU_26.03.02.26_M <---- mine
12.28b.60.140e_26.03.02.18 <--- latest from this thread (which looks outdated)
Also, there i posted the logcat:
Code:
D/RILJ ( 1592): [0141]> QUERY_AVAILABLE_NETWORKS
W/RILSWITCH( 1410): RIL REQUEST: QUERY_AVAILABLE_NETWORKS --> Vendor RIL
D/HTC_RIL ( 1410): ril_func_get_avail_networks():called
D/HTC_RIL ( 1410): (t=1291119508)>> AT+COPS=?\r
D/HTC_RIL ( 1410): (t=1291119514)<< +COPS: (2,"Network Norway N","NetworkN","24205",0),(1,"N Telenor","TELENOR","24201",0),(1,"N NetCom","NetCom","24202",0),,(0,1,2,3,4),(0,1,2)\r\n0\r
D/RILSWITCH( 1410): RILD <-- RIL (token 0xdef0)
D/RILSWITCH( 1410): atdToken : 0xdef0, bECMRedirected 0
W/RILJ ( 1592): [0141]< QUERY_AVAILABLE_NETWORKS exception, possible invalid RIL response
W/RILJ ( 1592): java.lang.RuntimeException: RIL_REQUEST_QUERY_AVAILABLE_NETWORKS: invalid response. Got 10 strings, expected multible of 4
W/RILJ ( 1592): at com.android.internal.telephony.RIL.responseNetworkInfos(RIL.java:2895)
W/RILJ ( 1592): at com.android.internal.telephony.RIL.processSolicited(RIL.java:2141)
W/RILJ ( 1592): at com.android.internal.telephony.RIL.processResponse(RIL.java:2045)
W/RILJ ( 1592): at com.android.internal.telephony.RIL.access$300(RIL.java:207)
W/RILJ ( 1592): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:537)
W/RILJ ( 1592): at java.lang.Thread.run(Thread.java:1096)
So, i keep both threads up and will update when/if I find a solution.
My other thread for reference: http://forum.cyanogenmod.com/topic/10939-select-network-operator-does-not-work/
There hasn't been an OTA update as yet for the Desire Z, as far as I know. Folks there might be assuming you've got a G2 (which has had an OTA update).
Seems there is an issue with libril.so according to this bug report
http://code.google.com/p/cyanogenmod/issues/detail?id=2729
Does anyone have access to the libril.so they speak of here?
Ok, so yesterday the bug report got updated and the files are available. Im just gonna leave a quick howto here:
Download libril.zip (Mediafire) and extract the two files libril.so and librilswitch.so to anywhere on your sdcard.
Remount /system to read/write. (can be done both in ADB Shell, terminal and several root file managers)
Rename /system/lib/libril.so to /system/lib/libril.so.bak
Copy the downloaded libril.so and librilswitch.so to your /system/lib/
Reboot and switch from your crappy network operator.
Yay
Is this fixed in 7.0?
Hey guys!
Hoping someone might be able to help. My camera stopped working about a year ago and I haven't been able to get it to work. Every time I try to use it my phone reboots. I've tried running every ROM available here, every radio, every SPL. At this point I figure it's probably hardware but I want to rule out every other possibility before I give up on it. Any suggestions ?
TY in advance.
PS. 32a Rogers - current radio is 6.35.16.19 - playing with gingerbread atm
I have the same issue with a Vodafone htc magic 32b. It started after the OTA of Vodafone to go to Android 2.2.1. I hoped it would work in Cyanogenmod 6.1 but it still gives reboots.
This is the log cat when I start the camera:
Code:
I/ActivityManager( 155): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera }
I/ActivityManager( 155): Start proc com.android.camera for activity com.android.camera/.Camera: pid=771 uid=10011 gids={1006, 1015}
I/WindowManager( 155): Setting rotation to 1, animFlags=1
I/ActivityManager( 155): Config changed: { scale=1.0 imsi=206/1 loc=nl_BE touch=3 keys=1/1/2 nav=3/1 orien=2 layout=18 uiMode=17 seq=8}
I/GPSButton( 155): Update State
I/ActivityManager( 155): Start proc com.ramesp.amissed for service com.ramesp.amissed/.LockWatchDog: pid=779 uid=10093 gids={1015}
E/mm-camera( 123): mt9t013_process_start: ioctl(MSM_CAM_IOCTL_ENABLE_OUTPUT_IND) error Invalid argument
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
D/RAMES ( 779): Registering--------------
D/Camera ( 771): app passed NULL surface
D/CameraSettings( 771): [antibanding-values=off,50hz,60hz,auto, antibanding=auto, effect-values=none,mono,negative,solarize,sepia,posterize,whiteboard,blackboa
rd,aqua, effect=none, exposure-compensation-step=0.5, exposure-compensation=0, focal-length=3.72, focus-mode-values=auto,infinity, focus-mode=auto, horizontal-v
iew-angle=51.6, jpeg-quality=90, jpeg-thumbnail-height=384, jpeg-thumbnail-quality=90, jpeg-thumbnail-size-values=512x384,0x0, jpeg-thumbnail-width=512, max-exp
osure-compensation=4, max-zoom=12, min-exposure-compensation=-4, picture-format-values=jpeg, picture-format=jpeg, picture-size-values=2048x1536,1600x1200,1024x7
68,512x384, picture-size=2048x1536, preview-format-values=yuv420sp, preview-format=yuv420sp, preview-frame-rate-values=15, preview-frame-rate=15, preview-size-v
alues=800x480,720x480,640x480,576x432,480x320,384x288,352x288,320x240,240x160,176x144, preview-size=384x288, vertical-view-angle=39.7, whitebalance-values=auto,
incandescent,fluorescent,daylight,cloudy-daylight, whitebalance=auto, zoom-ratios=100,102,107,109,114,117,123,128,131,138,141,148,155, zoom-supported=true, zoom=0]
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
V/camera ( 771): startPreview
It also reboots if I start any application that uses the camera e.g. goggles, barcode scanner,...
Would really like to have this fixed. Any suggestions?
my fix
try to reflash your rom if all else fail do a restore or flash of your stater rom and send it back to your carrier don't forget to unroot after that flash change your boot image back if not changed double check your fastboot
I've had this same issue. It looks from your logcat that the camera hardware works, it's just not loading properly.
The problem is that the camera's preferences file needs to be rewritten by the system. the solution is to adb shell into your phone, then go into /data/data/com.android.camera (or your Rom's specific directory; different Roms will likely have different directory names, but it shouldn't vary too much) and look for camera_hardware_preferences.xml (or your Rom's specific hardware preferences XML file for the camera) and move this to camera_hardware_preferences.xml_, then reboot.
Doing this will make your phone have to rewrite it's profile for camera hardware. Once done, it should work.
Findulmundo. I tried this and now my camera no longer crashes but is stuck on a black screen when starting the camera app. The camera_preferences.xml file is not being generated either. Any ideas?
Guys im having a similar issue, my camera will start normally but when i try to take a picture it will get stuck and wont shoot the pic. I can exit the app normally, no force close but im unable to take any pics any ideas?
Currently on cm5, already tried different sd cards, fastboot wipe and then reflashed the ROM, tried different roms also its still a no go though
Sent from my HTC Glacier using XDA Premium App
I'm not sure, but you should try to flash a new kernel - you'll find it in the dev section...
Btw. I'm using Ginger Yoshi RC 6.1 - to use it I needed to flash a new radio hboot and kernel - you can find the instructions in the ROM's thread step-by-step!
Hi guys, I've got a little problem here. I played with my Nook Simple Touch Glowlight and even rooted it. But I couldn't install apps for some reason, so I decided to restore and root it again with other tool (Glownooter) so I could have Google's App Market. Here comes my first fault. I installed [NST]Touch-Formatter v2 .zip - I didn't notice it is only for the normal NSG - using CWM. Everything worked fine, I registered my Nook and then, using CWM, installed glownooter. But instead of showing me Android homescreen, it rebooted itself. And it got stuck booting (five dots loading) until the battery died. So I charged it and then I tried it again (NST Touch Formatter, Glownooter...). And "surprisingly", I ended up with the same result. I tried that about four or five times and then I gave up for two days. Today, I wanted to read something, so I used only the Touch Formatter, registered it, uploaded the book on it... And held the "n" button to turn the glowlight on. But nothing happened. So I went to settings and there wasn't anything about glowlight. Well then, I had a backup, so I restored from backup. When it booted, it kept me showing the screen "your system is damged" (or something like that) "you must perform a system restart". Tried that 2 times. Didn't help. I did factory reset (holding the two bottom buttons during boot up). After that, I had trouble with connecting to my wifi, so I skipped the registration proccess.
Now, I can use it, but without Glowlight and that was the main reason why I bought Nook and not Kindle. I guess, the Touch Formatter somehow installed the normal NSG software, so the device thinks, it's the old model. And that may also be the reason why Glownooter didn't work. Then again, my opinion has 90% to be wrong - given to what I did with my nook, and that this is my first Android device.
I did the backup with Windows, everything else using Terminal in OS X (if that info helps).
Thanks for any idea that comes up onto your mind.
P.S.: Sorry for mistakes in my text, I'm not a native speaker and I've been learning English for 3 years (plus it's 1 a.m. ).
,
The good thing about that screen that says "You must reboot your Nook" is that it means that your Nook is almost working.
At least in some cases it's caused by not being able to mount partitions.
Here's an example:
Code:
I//system/bin/fsck_msdos( 744): ** /dev/block//vold/179:6
I//system/bin/fsck_msdos( 744): Invalid cluster size: 0
I/logwrapper( 744): /system/bin/fsck_msdos terminated by exit(8)
D/vold ( 744): Filesystem check failed (unknown exit code 8)
E/vold ( 744): vfat filesystem check failed on 179:6 (I/O error)
D/SurfaceFlinger( 811): Frame buffer posted; elapsed time = 34 msecs
D/MountListener( 811): handleEvent volume_checking:/media
D/MountListener( 811): handleEvent volume_damaged:/media
I/ActivityManager( 811): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.interna
l.app.RebootRequiredActivity (has extras) }
I/RebootRequiredActivity( 811): getReason(): received reason [REASON_MEDIA_UNMOUNTABLE [/media]]
The easy solution is to check whether all the partitions mount.
You can do that with noogie and a Linux system or Clockwork Recovery.
If you still can't figure it out, get ADB over USB working on your Nook and get a logcat.
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
mjh74 said:
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
Click to expand...
Click to collapse
So what is everything found on this site with regards to fix it?
/persist folder is also empty on my phone.
mjh74 said:
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
Click to expand...
Click to collapse
Dial *#1234# and paste here what appears.
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505BTUGNG2
So far I've tried the following:
Flashing the wifi-fix
Re-partitioning before flashing a stock rom
Rooting, Phillz recovery, clear dalvik, factory reset and format for new rom option before flashing various different 4.4.2 UK stock roms.
Editing build.prop and changing "ro.securestorage.support=true" to false.
Removing the back, removing and replacing the antenna wire.
Flashing a CM11 nightly.
Deleting wpa_supplicant.conf
Dmesg shows some interesting stuff.
"<4>[ 1277.591125] ## wifi_remove
<4>[ 1277.591125] wifi_set_power = 0
<4>[ 1277.591156] ####btlock released, cookie: WiFi
<6>[ 1277.591156] ------------------------------------------------
<6>[ 1277.591156] ------------------------------------------------
<6>[ 1277.591156] brcm_wlan_power Enter: power off
<6>[ 1277.591186] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<7>[ 1277.592590] usb 1-1: usb wakeup-resume
<7>[ 1277.592651] usb 1-1: finish resume
<7>[ 1277.599456] hub 1-0:1.0: resume on port 1, status 0
<7>[ 1277.599487] hub 1-0:1.0: port 1, status 0503, change 0004, 480 Mb/s
<6>[ 1277.727569] [email protected] 42
<6>[ 1277.732635] set_freq_limit: 0x1 -1, min 384000, max 1350000
<4>[ 1277.822662] wifi_set_carddetect = 0
<4>[ 1277.822692] brcm_wifi_status:298 status 0
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
<4>[ 1277.823638]
<4>[ 1277.823638] failed to power up wifi chip, max retry reached, exits **"
As I'm typing this, the phone has a stock rom and isn't rooted. I've just rooted again with CF-ROOT and Odin, rebooted the phone and wifi enabled instantly, something I've not seen before! It was the first boot and SuperSU wanted to update and reboot. After the reboot, wifi will no longer come on again.
I See you have the same error as I'm having:
Code:
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
Can you check dmesg for mmc1 CRC errors and post output here?
ajax505 said:
I See you have the same error as I'm having:
Code:
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
Can you check dmesg for mmc1 CRC errors and post output here?
Click to expand...
Click to collapse
Here you go.
mjh74 said:
Here you go.
Click to expand...
Click to collapse
So after pretty much giving up and weeks of flashing and faffing around. I managed to get wifi enabled. I've no idea how but I went from stock rom XXUGNG2, rooted with CF-AUTO-ROOT, Phillz recovery installed and a Cyanogen nightly and no wifi. Flashed XXUGNG2 back to the phone and wifi sprung into life! I then flashed XXUGNG8 and wifi still worked! I then performed a factory reset from Backup & Reset and wifi hasn't worked again since!?!?
So I'm not so convinced now that it's a hardware issue as I first thought.....
Lucky you I tried every possible solution. The interesting thing is that if I flash stock I can see Wifi mac, toggle button is "alive" but wifi won't turn on. If I flash cyanogen, wifi mac is not available and the wifi button is gray saying "turning wifi on" like forever.
ajax505 said:
Lucky you I tried every possible solution. The interesting thing is that if I flash stock I can see Wifi mac, toggle button is "alive" but wifi won't turn on. If I flash cyanogen, wifi mac is not available and the wifi button is gray saying "turning wifi on" like forever.
Click to expand...
Click to collapse
Like you, I'm back at exactly the same place. Cyanogen won't even let me turn wifi on now, the button is grayed out and says "turning wifi on". Stock roms show a pale green wifi signal icon until it turns gray again and fails. Arghhh how did I get it working briefly?!
mjh74 said:
So after pretty much giving up and weeks of flashing and faffing around. I managed to get wifi enabled. I've no idea how but I went from stock rom XXUGNG2, rooted with CF-AUTO-ROOT, Phillz recovery installed and a Cyanogen nightly and no wifi. Flashed XXUGNG2 back to the phone and wifi sprung into life! I then flashed XXUGNG8 and wifi still worked! I then performed a factory reset from Backup & Reset and wifi hasn't worked again since!?!?
So I'm not so convinced now that it's a hardware issue as I first thought.....
Click to expand...
Click to collapse
mjh74 said:
Like you, I'm back at exactly the same place. Cyanogen won't even let me turn wifi on now, the button is grayed out and says "turning wifi on". Stock roms show a pale green wifi signal icon until it turns gray again and fails. Arghhh how did I get it working briefly?!
Click to expand...
Click to collapse
When people learn that means "nightly" with CM?
I recently restarted my phone after the battery died, and now every time it gets to the lock screen, I can unlock it, and it'll function seemingly fine for up to 30 seconds (usually more like 5-10), but then it automatically restarts.
The only apps I've installed since last restarting, maybe a week ago, are FolderSync and Tasker. It's possible I haven't restarted since installing AnyConnect and OpenConnect, although I'm pretty sure I did restart at least once after those, and haven't touched them since. OpenConnect did have some permissions fix item in the settings menu that would supposedly attempt to get it to work on devices where it wouldn't (it didn't work on mine), so that has me suspicious, especially since it seems sometimes these boot loops are related to permissions errors.
I'm running Philz recovery, which I can get into fine. I read about a permissions fix in some recoveries, but Philz (at least mine) doesn't seem to have it.
When the battery died, I was connected to a bluetooth speaker, playing music with Spotify. Not sure if something could have gotten corrupted having it die while the bluetooth connection was active.
It's a T-Mobile S5 and the ROM I'm running XtreSoLite 2.1 Lollipop XXU1BOC7.
Any suggestions for things to check to get it to stop restarting? If I have to wipe it, are there any ways to sort of partially wipe it? Are there a series of things I can try that would go from least extreme (not losing anything) to most extreme (fully re-flashing)? I have been able to open an adb shell and pull everything from internal storage that I don't want to lose.
Thanks in advance for any help.
Boot into recovery and clear the CACHES
Boot back up, see if that fixes it, if it died while busy, it might just be a corrupted cache
Don't factory reset while you are running that ROM, it is a deadly bricking ROM because it doesn't allow you to disable Reactivation Lock, if you missed the setting during first boot, it's now permanently enabled and will lock you out of your phone if you try to flash something else, or reset
I tried "wipe cache partition" and "wipe dalvik cache" with no luck. After dalvik, it even did the "optimizing x out of y android apps" thing at startup, getting my hopes up that at least *something* was happening so it'd possibly get fixed.
So no factory reset... is there any way to then to get the ROM back to its original, freshly-installed, state? I guess the way to do it would be to install the ROM again with the zip file in recovery.
Are there any system logs that show what's happening at startup? There's gotta be a way to figure out what step it's getting to that causes it to restart... there's definitely a consistent set of things that happen before it does it. Lock screen comes up, the "no sim installed" notification comes up. There's an "unable to update automatically" message pop up (not in the notification panel), which I think is from the clock being unable to update from the internet from having no network connection. Usually happens right after that. Wish I could get a task manager installed that could view which processes/services are running.
Use an adb log/shell, just get adb working and then you can have it so adb sits there waiting for the device and starts spewing logs as soon as it can until it looses the device.
Sent from my SAMSUNG-SM-G900A using Tapatalk
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:
Code:
--------- 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?
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:
Code:
--------- 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?
Brent212 said:
I tried "wipe cache partition" and "wipe dalvik cache" with no luck. After dalvik, it even did the "optimizing x out of y android apps" thing at startup, getting my hopes up that at least *something* was happening so it'd possibly get fixed.
So no factory reset... is there any way to then to get the ROM back to its original, freshly-installed, state? I guess the way to do it would be to install the ROM again with the zip file in recovery.
Are there any system logs that show what's happening at startup? There's gotta be a way to figure out what step it's getting to that causes it to restart... there's definitely a consistent set of things that happen before it does it. Lock screen comes up, the "no sim installed" notification comes up. There's an "unable to update automatically" message pop up (not in the notification panel), which I think is from the clock being unable to update from the internet from having no network connection. Usually happens right after that. Wish I could get a task manager installed that could view which processes/services are running.
Click to expand...
Click to collapse
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
*Detection* said:
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
Click to expand...
Click to collapse
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.
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
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.
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.
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.
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.
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?
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
*Detection* said:
Boot into download mode and check if it tells you Reactivation Lock is enabled (Volume Down & Home & Power)
Click to expand...
Click to collapse
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:
Code:
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".
*Detection* said:
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
Click to expand...
Click to collapse
I got it almost two years ago, pretty much right when the S5 came out, so it's probably the first version.
*Detection* said:
Other alternative would be to remove the apps manually from recovery or ADB via PC USB
Click to expand...
Click to collapse
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.
I was expecting a screen showing this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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)
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?
Give it a shot, phone is not usable as it is
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.