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!
Every time I try to activate wifi the following error appears in logcat:
Code:
I/WifiManager( 1421): setWifiEnabled : true
I/WifiService( 879): setWifiEnabled: true pid=1421, uid=10141
E/WifiHW ( 879): ##################### set firmware type 0 #####################
E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 879): ==========[WIFI] Station firmware load ===========
D/SSRMv2:Monitor( 879): SIOP:: AP = 400 (read only)
E/WifiHW ( 879): return of insmod : ret = -1, No such device
E/WifiStateMachine( 879): Failed to load driver
D/WfdService( 879): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 1421): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 1421): Nothing, mRoamingIconId = 0
I/elm ( 2716): MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
E/WifiStateMachine( 879): sendErrorBroadcast code:10
E/WifiController( 879): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
I/elm ( 2716): MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
D/elm ( 2716): ELMEngine.getInstance().
I/DownloadNowBroadcastReceiver( 3770): onReceive
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.TMNetworkReceiver() Enter 1 main
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - exit
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() UnHandled
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Exit
D/MTPRx ( 4799): DRIVER_TIME_OUT 60s lapsed
and I tried all sorts of wifi fixers available in the forum without success. After some research I found the following post:
http://forum.xda-developers.com/showthread.php?t=1652702
what makes me think it's a problem with the driver.
The solution was found by this user:
I fixed this issue by copying libhardware_legacy.so from my OEM ROM to the ported ROM. Rebooted and WiFi worked just fine
Click to expand...
Click to collapse
I would like to know how to apply this solution to the GT-I9505. I must confess I do not think there is a solution to my problem, so any suggestion will be very welcome.
I am using Stock 4.3
Thanks in advance
Must have something similar I've gone 3 days without WiFi
I'll give this a go and get back to you. :good:
Edit: What a random series of events!
I looked at the line in your Logcat 'E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory' and when I looked I did have this file so deleted it and tried Wifi, nothing.
So I tried to replace that 'libhardware_legacy.so' file, but without thinking about it I'd taken it from a stock TW rom when I'm on a AOKP based rom. Doh!
Of course, it didn't boot and then I was left thinking "Oh ****"
I then tried flashing an old Android 4.2 rom I had on my SDCard but I did it lazily by only formatting the system and clearing Cache and Dalvik.
When I restarted it showed the boot image and then did nothing, so I went back into recovery and restored the system partition from a backup I created the other day (But whilst it was broken) of the same ROM I was on at the beginning of this post.
When it booted again it had a weird corrupted image, from my experience that's normally Kernel related, I also had a copy of KT Kernel on my SDCard, so flashed that, then wiped Cache and Dalvik
Low and behold when it finally booted, I went into settings and there was Wifi switched on and had found all my local Wifis. I got it to connect and ran some speed tests. Also restarted the phone and switched it on and off to make sure it wasn't just a fluke or hoax and now it seems I'm all sorted!
.... But for how long....
Pulse654321 said:
Must have something similar I've gone 3 days without WiFi
I'll give this a go and get back to you. :good:
Edit: What a random series of events!
I looked at the line in your Logcat 'E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory' and when I looked I did have this file so deleted it and tried Wifi, nothing.
So I tried to replace that 'libhardware_legacy.so' file, but without thinking about it I'd taken it from a stock TW rom when I'm on a AOKP based rom. Doh!
Of course, it didn't boot and then I was left thinking "Oh ****"
I then tried flashing an old Android 4.2 rom I had on my SDCard but I did it lazily by only formatting the system and clearing Cache and Dalvik.
When I restarted it showed the boot image and then did nothing, so I went back into recovery and restored the system partition from a backup I created the other day (But whilst it was broken) of the same ROM I was on at the beginning of this post.
When it booted again it had a weird corrupted image, from my experience that's normally Kernel related, I also had a copy of KT Kernel on my SDCard, so flashed that, then wiped Cache and Dalvik
Low and behold when it finally booted, I went into settings and there was Wifi switched on and had found all my local Wifis. I got it to connect and ran some speed tests. Also restarted the phone and switched it on and off to make sure it wasn't just a fluke or hoax and now it seems I'm all sorted!
.... But for how long....
Click to expand...
Click to collapse
You are lucky!
Can you explain the process of extract 'libhardware_legacy.so from a stock ROM and flash it on lhe device?
About lhe kernel, i Tried them all with no success.
Thank tou!
arleybarros said:
You are lucky!
Can you explain the process of extract 'libhardware_legacy.so from a stock ROM and flash it on lhe device?
About lhe kernel, i Tried them all with no success.
Thank tou!
Click to expand...
Click to collapse
Well I actually took it from a ROM that was in zip format, that you can flash in CWM so was quite easy. I've included it for you to try. It may not work the same as mine so make sure you have a backup to revert to!
And the KT kernel I used was KT-SGS4-JB4.3-AOSP-INTL-11.14.2013, but you'll need the TW version if you're on stock ROM? That version can be downloaded Here.
Pulse654321 said:
Well I actually took it from a ROM that was in zip format, that you can flash in CWM so was quite easy. I've included it for you to try. It may not work the same as mine so make sure you have a backup to revert to!
And the KT kernel I used was KT-SGS4-JB4.3-AOSP-INTL-11.14.2013, but you'll need the TW version if you're on stock ROM? That version can be downloaded Here.
Click to expand...
Click to collapse
I really appreciate the help, but this also did not work. I'm starting to think I have a hardware problem. is possible to diagnose it via ADB?
I'm thinking that I must have a problem with the permissions of folders and partitions, because the file "/ data / .cid.info" should be created automatically (if I'm not mistaken) and here, no matter what I do, this file is not available.
Could someone show me how to check the correct permissions for the folders and partitions?
Yeah that's really odd. The file is recreated for me when I was deleting it before and restarting. I'm not sure which file browser I'm using atm. 2 secs and I'll get some pictures up and the permissions for folders.
This is the file manager I'm using, should work ok. Hopefully it works with root features.
I've included pictures of permissions for folders, hopefully they help.
Whoops mis interpreted the pictures
Cat you give an example of what should be in the .cid.info?
**TLDR** - If your shield keeps rebooting after the 2.1.0 update, unplug your ethernet cable and/or disable your wifi as a temporary fix.
I recently got a 16GB model. After the latest firmware update (to 2.1.0) I started to get constant rebooting. My first thought was to use fastboot to get back to 2.0.0 - I believe you can do this without wiping your user data, as the official images are signed with the nvidia key and I believe their bootloader would allow you to downgrade - can anyone confirm this? See https: // developer .nvidia. com/ gameworksdownload (sorry, can't link with <10 posts...) for nvidia 2.0.0 image.
However I wanted to see what was happening first. Running
Code:
$ adb logcat
...lots of output
...the system just rebooted, so let's watch the logs!
D/AndroidRuntime( 4318): Shutting down VM
E/AndroidRuntime( 4318): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 4318): java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0
E/AndroidRuntime( 4318): at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:255)
E/AndroidRuntime( 4318): at java.util.ArrayList.get(ArrayList.java:308)
E/AndroidRuntime( 4318): at com.android.server.pm.PackageManagerService$PMLocationListener.getCountryFromLocation(PackageManagerService.java:14375)
E/AndroidRuntime( 4318): at com.android.server.pm.PackageManagerService$PMLocationListener.onLocationChanged(PackageManagerService.java:14282)
E/AndroidRuntime( 4318): at android.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:281)
E/AndroidRuntime( 4318): at android.location.LocationManager$ListenerTransport.access$000(LocationManager.java:210)
E/AndroidRuntime( 4318): at android.location.LocationManager$ListenerTransport$1.handleMessage(LocationManager.java:226)
E/AndroidRuntime( 4318): at android.os.Handler.dispatchMessage(Handler.java:104)
E/AndroidRuntime( 4318): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 4318): at com.android.server.SystemServer.run(SystemServer.java:276)
E/AndroidRuntime( 4318): at com.android.server.SystemServer.main(SystemServer.java:177)
E/AndroidRuntime( 4318): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 4318): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 4318): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
E/AndroidRuntime( 4318): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
I/Process ( 4318): Sending signal. PID: 4318 SIG: 9
E/installd( 226): eof
E/installd( 226): failed to read size
I/installd( 226): closing connection
For those of you that don't speak stacktrace or android internals, what happened here is that something (presumably, my network state tracker noticed either an IP change or something else from my ethernet) sent a message to the internal LocationManager saying "something happened, update your location estimate". In the process of doing this LocationManager crashes, and then the entire android framework crashes in response to this critical component (system_server) crash. Then the init binary helpfully restarts everything, and in a few minutes it crashes again.
Unplugging the ethernet cable has resulted in a stable system. I haven't experienced the crash while on WiFi, but I wouldn't rule it out yet.
While I have not looked in extreme detail, my suspicion is that something about the firmware update broke google mobile services - I see an error trying to mount the data for GMS in the logs, and noticed the stacktrace above seems to be failing when the LocationManager uses the PackageManager which uses installd which then fails with some kind of file read.
Code:
E/Vold ( 206): Failed to find mounted volume for /storage/sdcard1/Android/data/com.google.android.gms/files/
W/Vold ( 206): Returning OperationFailed - no handler for errno 0
W/ContextImpl( 6163): Failed to ensure directory: /storage/sdcard1/Android/data/com.google.android.gms/files
Turning off location services seems to stop this too
I'm 100% that no ethernet stops the rebooting (got a few hours of testing and no crashes). Tried turning off location services after I saw the logs of the error, and I've had about 30 min with no crashes, so that's obviously a much more preferred way to address this issue until nvidia fixes the bug
well interesting to know about this issue.
slammertime said:
I'm 100% that no ethernet stops the rebooting (got a few hours of testing and no crashes). Tried turning off location services after I saw the logs of the error, and I've had about 30 min with no crashes, so that's obviously a much more preferred way to address this issue until nvidia fixes the bug
Click to expand...
Click to collapse
Has having locations services turned off solved the random restarts for you inevitably?
Yes, it seems so
Sorry for resurrecting an old thread, but I'm still having this issue.
Tried disabling location, changing languages, every other suggestion here and elsewhere online.. still getting reboots ~3-5 mins after the system starts, and random lockups. Only started happening post 2.1. The device is basically unusable at this point.
I'm just about to factory wipe/reinstall. Is there any other solution?
Same
grivad said:
Sorry for resurrecting an old thread, but I'm still having this issue.
Tried disabling location, changing languages, every other suggestion here and elsewhere online.. still getting reboots ~3-5 mins after the system starts, and random lockups. Only started happening post 2.1. The device is basically unusable at this point.
I'm just about to factory wipe/reinstall. Is there any other solution?
Click to expand...
Click to collapse
I am having the same issue. Talked to support, and they told me to unpair, and reset my devices that were attached to it, and unplug the hdmi and power, and still no dice.
peppy6582 said:
I am having the same issue. Talked to support, and they told me to unpair, and reset my devices that were attached to it, and unplug the hdmi and power, and still no dice.
Click to expand...
Click to collapse
I got sick of it, wiped the device, and did a fresh install of 2.1 (IIRC, whatever factory image was available a few weeks back) and applied the OTA once prompted. Zero issues since. It took some time installing and configuring everything again, but having a completely stable device made it worth it. It was unusable before, as it'd reboot every few minutes no matter what it was doing.
It looks like they have the 3.0 image up now, if you're thinking of reinstalling as well.
https://developer.nvidia.com/shield-open-source
grivad said:
I got sick of it, wiped the device, and did a fresh install of 2.1 (IIRC, whatever factory image was available a few weeks back) and applied the OTA once prompted. Zero issues since. It took some time installing and configuring everything again, but having a completely stable device made it worth it. It was unusable before, as it'd reboot every few minutes no matter what it was doing.
It looks like they have the 3.0 image up now, if you're thinking of reinstalling as well.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
Yeah, I actually did that, with a fastboot -w after the system.img part, just to make sure.
hey guys, do you still have the problem with the random reboot?
I have the same problem with the 500gb version but I didn't root this device or whatever, it isn't even my intention to root it.
Any idea what it is?? Nvidia want to send me a new one (or refurbished item) but I have like the idea that it will not be solved if I get a new one.
I read to much people with the same problems, even on 2 links I read from someone who got a new one and the problem was still there :s
I'm a little scared to send it back , because I fear it will not be solved.
Any idea guys???
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.