Related
So this I9000 was given to me to try and repair for a friend. Basically phone had never been hacked, modded or anything. Was stock, not even rooted. One day the phone turned off and when turned on, it shows the GT screen, the Samsung screen, then the screen goes black and the lower buttons illuminate. That's it.
So i have tried to install multiple ROM's, repartitioning, odin, CWM all of it.
The last thing i have found is a thread where someone gave instructions on how to list your device memory from shell using parted. I have done just that but i do not see my internal memory there. If i put my 512MB sd card in it, it becomes visible, the external that is. But thats it.
In CWM i cannot mount data or emmc. Nor can i format them.
Here is the output from parted. Any ideas?
~ # cd /sbin
cd /sbin
/sbin # ls -al /dev/block
ls -al /dev/block
drwxr-xr-x 3 root root 700 Mar 29 21:55 .
drwxr-xr-x 11 root root 2880 Mar 29 21:55 ..
brw------- 1 root root 7, 0 Mar 29 21:55 loop0
brw------- 1 root root 7, 1 Mar 29 21:55 loop1
brw------- 1 root root 7, 2 Mar 29 21:55 loop2
brw------- 1 root root 7, 3 Mar 29 21:55 loop3
brw------- 1 root root 7, 4 Mar 29 21:55 loop4
brw------- 1 root root 7, 5 Mar 29 21:55 loop5
brw------- 1 root root 7, 6 Mar 29 21:55 loop6
brw------- 1 root root 7, 7 Mar 29 21:55 loop7
brw------- 1 root root 31, 0 Mar 29 21:55 mtdblock0
brw------- 1 root root 31, 1 Mar 29 21:55 mtdblock1
brw------- 1 root root 31, 2 Mar 29 21:55 mtdblock2
brw------- 1 root root 31, 3 Mar 29 21:55 mtdblock3
brw------- 1 root root 31, 4 Mar 29 21:55 mtdblock4
brw-rw---- 1 radio radio 31, 5 Mar 29 21:55 mtdblock5
brw------- 1 root root 31, 6 Mar 29 21:55 mtdblock6
brw------- 1 root root 31, 7 Mar 29 21:55 mtdblock7
drwxr-xr-x 3 root root 60 Mar 29 21:55 platform
brw------- 1 root root 1, 0 Mar 29 21:55 ram0
brw------- 1 root root 1, 1 Mar 29 21:55 ram1
brw------- 1 root root 1, 10 Mar 29 21:55 ram10
brw------- 1 root root 1, 11 Mar 29 21:55 ram11
brw------- 1 root root 1, 12 Mar 29 21:55 ram12
brw------- 1 root root 1, 13 Mar 29 21:55 ram13
brw------- 1 root root 1, 14 Mar 29 21:55 ram14
brw------- 1 root root 1, 15 Mar 29 21:55 ram15
brw------- 1 root root 1, 2 Mar 29 21:55 ram2
brw------- 1 root root 1, 3 Mar 29 21:55 ram3
brw------- 1 root root 1, 4 Mar 29 21:55 ram4
brw------- 1 root root 1, 5 Mar 29 21:55 ram5
brw------- 1 root root 1, 6 Mar 29 21:55 ram6
brw------- 1 root root 1, 7 Mar 29 21:55 ram7
brw------- 1 root root 1, 8 Mar 29 21:55 ram8
brw------- 1 root root 1, 9 Mar 29 21:55 ram9
Also, i tried using a CM7 rom last, so i am currently looping the Cm7 skateboard guy. I have the logcat of that available if you think it may help, but it just list a whole bunch of java failures and alike and then does it all over again.
I'm sure my GT-I9000 Galaxy S came with a 2 year Warranty. Would be well worth checking whether that phone was 1yr or 2yrs, as all 2yr warranties should still be valid, as they are all less than two years old still.
Hope you get it sorted.
---------- Post added at 12:04 PM ---------- Previous post was at 12:00 PM ----------
Just realised you are in Canada, does that mean this is a I9000M?... as I know they had major memory issues. There is a thread about it here somewhere. Not sure what the outcome was, but it was a known defect. Maybe you could convince Samsung to fix it for free (even if it is out of Warranty)?
Ya i have been getting snippits of info on the i9000m internal sd problem but can find any hard info on it.
Basically there was a huge batch of them with onboard memory that would fail when you upgraded to GB....or eventually on their own.
I had one, a friend of mine had one...
If it was still on warranty they would replace it outright for you but I'm guessing if you got it in Canada (Bell?) It's way past warranty.
You could try flashing an Claire or froyo ROM and see if you have any luck there. Chances are though that it's as good as dead.
Sent from my GT-I9000 using Tapatalk 2 Beta-4
Yes, its a Bell I9000M.
I dont see a date of manufacture on it though. I guess i will have to call Samsung to verify warranty then?
Date of manufacture should be on the battery. I got mine on release day and it still works great after being flashed dozens of times.
As far as I remember it was a later batch that had a corrupt boot loader. I was weary of flashing due to all the dying I9000M's and followed the discussions closely. The second GB update was supposed to have fixed it.
Sent from my GT - I9000M running Team Hacksung's ICS port.
Hello mates,
I have a common but also weird case with note n7000.
after wiping data without abyss kernel, i stuck at boot screen then tried to flash GB with odin, it also stuck at last quarter, tried to flash ICS with odin but same as GB.
now i am able to flash kernels with ODIN and i am able to boot in recovery.
i go in to recovery, flash abyss 4.2 kernel and reboot in recovery then make all the wipes and even flash a custom rom but when i reboot the device, nothing happens. again stuck in boot screen and no further process.
i am really desperate about it now. as i bought it from ebay, i dont have the receipt of it. only the box, accs. and some papers(warranty and guide).
can anyone suggest me anything in this case? is there anything i can do or its done for good?
and in the case of superbrick, can anyone from germany tell me whether i can claim warrany without receipt(quittung, kassenbon, kaufbeleg) ?
any reply, any attempt of help will be highly appreciated.
thanks in advance
SOLUTION: i followed the link posted by Aluyi
http://forum.xda-developers.com/showthread.php?t=1667886
downloaded the rar file with many modified .pit files and flashed Rooted_Stock_Odex_N7000XXLC1(ICS XXLPY works also) with the downloaded .pit file (N7000_16GB_Q1_20110914-patched-standard) and IT DID WORK!
if u check the given link u will understand what was causing that problem.
after this process i did save the device from being bricked but sacrified 3 gb of internal sd. so it shows only 8.3 gb now.
try pc odin to flash.
mrbat said:
Hello mates,
I have a common but also weird case with note n7000.
after wiping data without abyss kernel, i stuck at boot screen then tried to flash GB with odin, it also stuck at last quarter, tried to flash ICS with odin but same as GB.
now i am able to flash kernels with ODIN and i am able to boot in recovery.
i go in to recovery, flash abyss 4.2 kernel and reboot in recovery then make all the wipes and even flash a custom rom but when i reboot the device, nothing happens. again stuck in boot screen and no further process.
i am really desperate about it now. as i bought it from ebay, i dont have the receipt of it. only the box, accs. and some papers(warranty and guide).
can anyone suggest me anything in this case? is there anything i can do or its done for good?
and in the case of superbrick, can anyone from germany tell me whether i can claim warrany without receipt(quittung, kassenbon, kaufbeleg) ?
any reply, any attempt of help will be highly appreciated.
thanks in advance
Click to expand...
Click to collapse
Try This Method;
1. Take Off The Phone And Wait A Minute Or Two,
2. Remove The Battery And Wait 5 Minutes,
3. Boot In Recovery And Do All 3 Wipes.
Alles Wird Gut, Happened To Me Yesterday, Please Do Holla Back If It Did Work Fine For You.
try pc odin to flash.
Click to expand...
Click to collapse
yea tried maybe 30 times. but as i mentioned above, it sticks at the last quarter of the installation.
Aluyi said:
Try This Method;
1. Take Off The Phone And Wait A Minute Or Two,
2. Remove The Battery And Wait 5 Minutes,
3. Boot In Recovery And Do All 3 Wipes.
Alles Wird Gut, Happened To Me Yesterday, Please Do Holla Back If It Did Work Fine For You.
Click to expand...
Click to collapse
i tried it. waited more than 5 minutes then booted in recovery, did wipes and still the same thing.
wiping cache and dalvik cache works normal but wiping data takes too long (around 4 mins)
Just wondering did u wiped system in recovery ?
sahilarora2003 said:
Just wondering did u wiped system in recovery ?
Click to expand...
Click to collapse
yes mate, i wiped everything in the "mounts and storage"
even sdcard and mmc. but still no success
mrbat said:
i tried it. waited more than 5 minutes then booted in recovery, did wipes and still the same thing.
wiping cache and dalvik cache works normal but wiping data takes too long (around 4 mins)
Click to expand...
Click to collapse
Maybe You Should Try This Method When No Other Method Helps You Out. http://forum.xda-developers.com/showthread.php?t=1667886&highlight=boot+loop.
What You Got To Lose Anyway? As It Stands Right Now You F..ked, So Give It A Try I´ll Do It.
Aluyi said:
Maybe You Should Try This Method When No Other Method Helps You Out. http://forum.xda-developers.com/showthread.php?t=1667886&highlight=boot+loop.
What You Got To Lose Anyway? As It Stands Right Now You F..ked, So Give It A Try I´ll Do It.
Click to expand...
Click to collapse
yea i got nothing to lose now, i surely will give a shot.
but here is the log file i got from CWM if anyone can get anything from it :
Code:
Starting recovery on Sat Jan 1 20:03:29 2000
framebuffer: fd 4 (800 x 1280)
ClockworkMod Recovery v5.8.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /efs ext4 /dev/block/mmcblk0p1 (null) 0
3 /cache ext4 /dev/block/mmcblk0p7 (null) 0
4 /system ext4 /dev/block/mmcblk0p9 (null) 0
5 /data ext4 /dev/block/mmcblk0p10 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /emmc vfat /dev/block/mmcblk0p11 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=8
ro.emmc=0
dpm.allowpolicy=1
init.svc.recovery=running
init.svc.adbd=stopping
ro.build.product=smdkc210
ro.product.device=smdkc210
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 17
ev: 1 102 0
fd: 17
ev: 0 0 0
fd: 17
ev: 1 115 0
fd: 17
ev: 0 0 0
Starting recovery on Sat Jan 1 20:03:33 2000
framebuffer: fd 4 (800 x 1280)
ClockworkMod Recovery v5.8.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /efs ext4 /dev/block/mmcblk0p1 (null) 0
3 /cache ext4 /dev/block/mmcblk0p7 (null) 0
4 /system ext4 /dev/block/mmcblk0p9 (null) 0
5 /data ext4 /dev/block/mmcblk0p10 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /emmc vfat /dev/block/mmcblk0p11 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=8
ro.emmc=0
dpm.allowpolicy=1
init.svc.recovery=running
init.svc.adbd=stopping
ro.build.product=smdkc210
ro.product.device=smdkc210
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 16
ev: 3 53 198
fd: 16
ev: 3 54 532
fd: 16
ev: 3 48 44
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 198 532
down
fd: 16
ev: 0 0 0
fd: 16
ev: 3 53 198
fd: 16
ev: 3 54 532
fd: 16
ev: 3 48 0
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 198 532
event: 198 532
up
fd: 16
ev: 0 0 0
failed to open /sys/class/android_usb/android0/state: No such file or directory
fd: 16
ev: 3 53 201
fd: 16
ev: 3 54 590
fd: 16
ev: 3 48 45
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 201 590
down
fd: 16
ev: 0 0 0
fd: 16
ev: 3 53 201
fd: 16
ev: 3 54 590
fd: 16
ev: 3 48 0
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 201 590
event: 201 590
up
fd: 16
ev: 0 0 0
failed to open /sys/class/android_usb/android0/state: No such file or directory
Fixing permissions...
sh: fix_permissions: not found
Done!
fd: 16
ev: 3 53 258
fd: 16
ev: 3 54 314
fd: 16
ev: 3 48 53
fd: 16
ev: 3 50 5
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 0
fd: 16
ev: 3 60 7
fd: 16
ev: 0 2 0
event: 258 314
down
fd: 16
ev: 0 0 0
fd: 16
ev: 3 53 258
fd: 16
ev: 3 54 314
fd: 16
ev: 3 48 0
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 0
fd: 16
ev: 3 60 7
fd: 16
ev: 0 2 0
event: 258 314
event: 258 314
up
fd: 16
ev: 0 0 0
failed to open /sys/class/android_usb/android0/state: No such file or directory
Click to expand...
Click to collapse
mrbat said:
yea i got nothing to lose now, i surely will give a shot.
but here is the log file i got from CWM if anyone can get anything from it :
Click to expand...
Click to collapse
Take Your Time And Just Follow The Directions, Download The Files And Copy/Paste The Codes. Again Alles Wird Gut. Believe Me It Happened To Me Many Times Before.
I'm porting Ubuntu Touch on an y991 (Elephone Vowney Lite).
I managed to boot the system and run its apps. Now I need to debug RIL, wireles, camera etc., but I cannot get any logcat output.
I tried both /system/bin/logcat both /android/system/bin/logcat from an adb root shell. It just returns to prompt. No error, no log. Logs exist:
Code:
ls -l /dev/log*
srw-rw-rw- 1 root root 0 Jan 1 01:00 /dev/log
crw-rw-rw- 1 root root 10, 59 Jan 1 01:00 /dev/log_events
crw-rw-rw- 1 root root 10, 60 Jan 1 01:00 /dev/log_main
crw-rw-rw- 1 root root 10, 58 Jan 1 01:00 /dev/log_radio
crw-rw-rw- 1 root root 10, 57 Jan 1 01:00 /dev/log_system
I was about to suggest that you ask the ubport's guys ..... but mayyybe you know them already https://forums.ubports.com/user/4javier
My son's Moto X with unofficial Lineage OS 13 has been working just fine until today, when it suddenly stopped finding any network operators. The SIM card is still recognized, I may enter the pin, but then it says "No service", and when I go to network operators choice, I find that not a single operator is displayed.
I tested the SIM in another phone, it seems to be fine. I also inserted different sim, which I know to work into this phone, but that did not help.
This is what I get from adb logcat, but I can't make sense of it:
XXXXXXXXXXX simSlotIndex=0 displayName=Willkommen carrierName=No service nameSource=0 iconTint=-16746133 dataRoaming=0 [email protected] mcc 26
2 mnc 7 mUserNwMode=9}]
01-07 18:11:59.254 1572 1572 D NetworkSettings: onSubscriptionsChanged: Slot matched SimSlotIndex: 0
01-07 18:11:59.257 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1572 3902 D OpenGLRenderer: endAllStagingAnimators on 0x99f02e00 (RippleDrawable) with handle 0x9d070520
01-07 18:11:59.361 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.361 1833 1833 D KP2AAF : event: 32, package = com.android.phone
01-07 18:11:59.361 1833 1833 D KP2AAF : event package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : root package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : URL=androidapp://com.android.phone
01-07 18:11:59.368 1833 1833 D KP2AAF : Cancel notif
01-07 18:11:59.438 1881 6159 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.458 1881 1903 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.575 1572 1572 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
01-07 18:11:59.579 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.634 1572 1572 I art : Explicit concurrent mark sweep GC freed 29733(3MB) AllocSpace objects, 7(156KB) LOS objects, 40% free, 10MB/17MB, paused 610u
s total 41.233ms
01-07 18:11:59.656 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.676 1572 1572 I art : Explicit concurrent mark sweep GC freed 13973(846KB) AllocSpace objects, 2(80KB) LOS objects, 39% free, 9MB/15MB, paused 640u
s total 19.563ms
01-07 18:11:59.676 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.691 1881 1901 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.695 1572 1572 I art : Explicit concurrent mark sweep GC freed 3(96B) AllocSpace objects, 0(0B) LOS objects, 40% free, 9MB/15MB, paused 579us total
19.136ms
01-07 18:12:00.121 21030 21030 W ps : type=1400 audit(0.0:1428831): avc: denied { getattr } for path="/proc/1" dev="proc" ino=3578 scontext=u:r:untrusted_app:s0:c5
12,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
01-07 18:12:00.145 1833 1833 D KP2AAF : OnAccEvent
01-07 18:12:00.145 1833 1833 D KP2AAF : event: 2048, package = com.android.systemui
01-07 18:12:00.145 1833 1833 D KP2AAF : return.
Could it be that suddenly the hardware has become faulty? Does anybody have suggestions how to test for the cause?
Thanks very much in advance!!!
Did a factory reset, which did not solve it. Still no network operators found.
Trying to understand the problem. logcat reveals that when it scans for networks, something goes wrong:
IsDataRoamingFromRegistration=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false IsDataRoamingFromRegistration=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1
Can someone enlighten me, what CSS stands for?
Now I spotted more errors:
01-10 15:54:50.960 2132 2132 D DCT : [0]stopNetStatPoll
01-10 15:54:50.964 2132 2132 D DCT : [0]overall state is IDLE
01-10 15:59:14.763 2132 2795 D RILJ : [4000]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB0]
01-10 15:59:14.770 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_req_log: req QMI NAS, msg id: 67, e len:0
01-10 15:59:14.804 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_resp_log: rsp - QMI NAS, msg id: 67, e len:7
01-10 15:59:14.804 2132 2243 D RilRequest: [4000]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
01-10 15:59:14.804 2132 2132 D GsmSST : [GsmSST] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-10 15:59:14.804 2132 2795 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
01-10 15:59:14.805 2132 2795 D GsmSST : [GsmSST] getCellLocation(): X empty mCellLoc and CellInfo mCellLoc=[-1,-1,-1]
01-10 15:59:14.817 1929 3007 D TelephonyManager: getCellLocation returning null because CellLocation is empty
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): return last, back to back calls
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
This "Generic failure" sounds spooky to me. As if something about the hardware is broken.
yahya69 said:
Did a factory reset, which did not solve it. Still no network operators found.
Click to expand...
Click to collapse
Have you tried restoring to the stock firmware? If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
VitaTaf said:
Have you tried restoring to the stock firmware?
Click to expand...
Click to collapse
Yes, but that also did not help, so I returned to LineageOS again.
If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am not clear what that does. Seemingly, it erases two partitions. Is their content rebuilt after? Are those two partitions shipped with the custom rom? I did several google searches and each time I found it accompanied by the instruction to flash something else in the next step. So before nuking a partition I certainly would want to know., but so far I have not found an explanation of the partition layout.
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
Click to expand...
Click to collapse
I know. There it says it has no cellular network. As the logs I posted indicate, something goes badly wrong while searching for cells.
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
yahya69 said:
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
Click to expand...
Click to collapse
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related. Which method did you use to restore to the stock firmware?
VitaTaf said:
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related.
Click to expand...
Click to collapse
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
VitaTaf said:
Which method did you use to restore to the stock firmware?
Click to expand...
Click to collapse
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
yahya69 said:
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
Click to expand...
Click to collapse
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
VitaTaf said:
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
Click to expand...
Click to collapse
I reflashed them but as a result, the sim card is no longer recognized, rebooted several times.
Update: Reflashed lineageOS and now I got my sim card back, although still not connecting to the network. Reflashed the stock firmware with twrp (not sure how this would be done via fastboot), I got my phone to re-connect to the network for a few seconds, which made me jump up and down in excitement, but then the connection dropped again, before I could even make a phonecall
Update 2 Tried a different sim card, but again, when I try to register automatically, this is what I see:
}
D/PHONE (15915): [ServiceState] setDataRegState=1
D/PHONE (15915): [ServiceState] setDataRadioTechnology=0
D/GsmSST (15915): [GsmSST] 0handlPollStateResultMessage: GsmSST setDataRegState=1 regState=0 dataRadioTechnology=0
D/PHONE (15915): [ServiceState] setVoiceRegState=1
E/PHONE (15915): [ServiceState] setState deprecated use setVoiceRegState()
D/GsmSST (15915): [GsmSST] 0handleSIB5LackIssue: no cell location change and config is 'on'
D/GsmSST (15915): [GsmSST] 0Poll ServiceState done: oldSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1 realOldType=Unknown realNewType=Unknown mNewReasonDataDenied=-1
D/PHONE (15915): [ServiceState] setNullState=1
Needless to say it fails.
Hi,
I am running stock N960FXXS3CSG1 AP firmware on a freshly factory reset Exynos-based Note 9 device and I observed that when either face or iris is enabled as screen lock type, SystemUI is continuously generating warning logs as long as the screen is on. This can be seen by connecting the phone to a PC and running 'adb logcat' after enabling USB debugging. The warning logs are generated even if the phone is unlocked using the fingerprint sensor, without even showing the lock screen. Restarting the phone does not help.
The lines that are continuously written to the log by the SystemUI process are:
Code:
07-20 11:24:58.157 5439 5439 W View : requestLayout() improperly called by com.android.keyguard.biometric.KeyguardBiometricSmallIconView{c777788 V.E...... ......ID 0,84-1440,217 #7f0a0273 app:id/keyguard_iris_text_preview} during layout: running second layout pass
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayout is already in process
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayoutDuringLayout is already in process
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayoutDuringLayout is already in process
07-20 11:24:58.159 5439 5439 W View : requestLayout() improperly called by com.android.systemui.statusbar.phone.NotificationPanelView{5a9da25 V.E...... ........ 0,0-1440,2960 #7f0a0387 app:id/notification_panel} during second layout pass: posting in next frame
07-20 11:24:58.159 5439 5439 W View : requestLayout() improperly called by com.android.keyguard.biometric.KeyguardBiometricSmallIconView{c777788 V.E...... ........ 0,84-1440,217 #7f0a0273 app:id/keyguard_iris_text_preview} during second layout pass: posting in next frame
This behavior causes high CPU usage and battery drain when either iris or face unlock is enabled.
Here is a snapshot of top running after the phone was unlocked, with face unlock enabled:
Code:
800%cpu 80%user 7%nice 104%sys 608%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
5439 u0_a8 20 0 4.9G 380M 300M S 74.3 6.7 8:16.99 com.android.systemui
4388 system 12 -8 3.0G 45M 37M S 31.6 0.7 5:07.57 surfaceflinger
4261 logd 30 10 21M 4.7M 2.7M S 18.3 0.0 4:04.49 logd
4366 system 20 0 166M 5.0M 4.3M S 16.0 0.0 2:03.32 [email protected]
2259 root RT 0 0 0 0 S 11.0 0.0 2:49.27 [decon0]
20277 root 20 0 0 0 0 S 7.0 0.0 0:06.64 [kworker/0:0]
20228 root 0 -20 0 0 0 S 6.6 0.0 0:02.47 [kworker/u17:1]
15695 root 0 -20 0 0 0 S 6.0 0.0 0:19.06 [kworker/u17:4]
4931 system 18 -2 5.4G 429M 318M S 5.6 7.6 32:10.51 system_server
21346 shell 20 0 12M 5.1M 3.9M R 3.6 0.0 0:00.35 top
This is how it looks when face and iris unlock are disabled (phone was restarted so different pids):
Code:
800%cpu 10%user 2%nice 9%sys 778%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
4927 system 18 -2 5.2G 502M 400M S 11.0 8.9 5:07.68 system_server
17742 shell 20 0 12M 5.0M 3.8M R 3.3 0.0 0:00.33 top
17650 root 20 0 0 0 0 S 1.6 0.0 0:01.89 [kworker/0:2]
4569 wifi 20 0 19M 5.8M 5.5M S 1.6 0.1 0:08.97 wificond
6128 u0_a15 20 0 3.7G 138M 120M S 1.0 2.4 0:12.86 android.process.acore
6414 system 20 0 3.7G 132M 118M S 0.6 2.3 0:26.58 com.sec.android.sdhms
4532 system 20 0 11M 3.3M 3.2M S 0.6 0.0 0:10.69 argosd
7 root 20 0 0 0 0 S 0.6 0.0 0:09.04 [rcu_preempt]
5406 u0_a8 20 0 4.5G 358M 286M S 0.3 6.3 0:42.20 com.android.systemui
Here is the logcat output for pid/tid 5439 (com.android.systemui), starting from when the power button was pressed, with face unlock enabled:
https://pastebin.com/zX77zHW8
The messages at the end keep repeating until the screen is turned off.
Here is the logcat output with face unlock disabled:
https://pastebin.com/1An2X6TJ
Can anyone else run 'adb shell top' with face or iris unlock enabled and confirm whether this is a firmware issue or it's just something on my end?
Thanks!
Did you manage to figure it out? I'm getting the same exact issue.
artoria5 said:
Did you manage to figure it out? I'm getting the same exact issue.
Click to expand...
Click to collapse
Unfortunately, no. I was hoping to get more input on this. Samsung Community hasn't been much help either.