I bought a Literati for only $65 shipped and was thinking maybe android could be ported to this device.
CPU:S3C6410 [email protected]
Audio: None
Camera: None
Touch screen: None
Screen: Color 7" unknown X Unknown
Memory
SD: up to 16gig
User: 256mb(black) expandable to 1gb once telnet is enabled.
System: 64mb(i think)
USB
Mini USB: Mode=device
internal USB: Mode=Host(currently connected to a wireless dongle)
Network
Wifi: rt2860sta
3G: None
Ethernet: None
NAND 512MiB 3,3V 8-bit
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00340000 : "Kernel"
0x00340000-0x00d40000 : "resource"
0x00d40000-0x11140000 : "File System 1"
0x11140000-0x20000000 : "User space"
The Bootloader is:
U-Boot 1.1.6-g794ab523-dirty (Aug 23 2010 - 00:52:53) for SMDK6410
The Environment has:
bootargs=console=ttySAC0,115200 loglevel=0 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs
bootcmd=nand read c0008000 40000 300000;bootm c0008000
bootdelay=0
baudrate=115200
ethaddr=[MAC of Literati]
ipaddr=192.168.1.28
serverip=192.168.1.27
gatewayip=192.168.1.2
netmask=255.255.255.0
The Kernel is:
Linux (none) 2.6.24.2 #180 Mon Aug 23 00:49:07 CST 2010 armv6l GNU/Linux
The resource:
It begins with FILE_SECTION04 and then a file directory which shows logo.bin, update.bin, and zImage_rfs.
Here is the development website with more information http://literatidevs.com
Just got one of these today, actually. I looked up and down that board, but didn't find any info on enabling telnet. You have a link handy?
Hi (Posting here as I am not yet permitted to in dev section)
I need to get access to the /dev/voc* devices which come from the vocpcm.c code from olher HTC kernel releases.
It looks like it was meant to work with qdsp5 DSP and I am not sure whether I should assume it works
So, I added it to the kernel and once running, I can see the devices
ls -al /dev/voc*
crw-rw-rw- 1 root root 10, 49 Jul 28 21:18 /dev/voc_rx_playback
crw-rw-rw- 1 root root 10, 50 Jul 28 21:18 /dev/voc_rx_record
crw-rw-rw- 1 root root 10, 47 Jul 28 21:18 /dev/voc_tx_playback
crw-rw-rw- 1 root root 10, 48 Jul 28 21:18 /dev/voc_tx_record
But it looks like they really aren't mapping to the DSP as I get no audio from and when i try and tail the file, I get
[email protected]:/dev # tail voc_rx_playback
tail voc_rx_playback
tail: can't open 'voc_rx_playback': No such device
tail: no files
Which is a different result than on my working HTC Tattoo.
Any ideas here as to whether I might need to do something more to get it working with qdsp6 or whether I need a different handset etc
As far as I know, these devices are completely different (and different concept) from the voice uplink and voice downlink that comes with the 2 way recording patch. Is that right ?
cheers
Mark
I'm having issues with my Gnex. I has posted a query regarding the same
[Q] Galaxy Nexus radio/modem failure, baseband ... - XDA Developers
The baseband stopped working on a virgin phone (except OTA updates). So I tried flashing factory images just to try my luck. What I noticed was "Unknow Baseband" IMEI null etc
I managed to get some log files after rooting I found following logs.
***********************************
[email protected]:/factory # cat nv.log
cat nv.log
Sat Jan 1 00:00:34 2000: nv_data.bin does not exist.
Sat Jan 1 00:00:35 2000: default NV restored.
Sat Jan 1 00:00:36 2000: default NV restored.
Sat Jan 1 00:12:06 2000: MD5 is turned off on 0
Fri Feb 17 00:01:15 2012: NV data back-up begin.
Fri Feb 17 00:01:16 2012: secondary NV built.
Fri Feb 17 00:01:16 2012: NV data back-uped.
Fri Feb 17 00:01:16 2012: MD5 is turned on.
Fri Feb 17 23:04:56 2012: MD5 is turned off on 0
Fri Feb 17 23:05:33 2012: NV data back-up begin.
Fri Feb 17 23:05:33 2012: secondary NV built.
Fri Feb 17 23:05:33 2012: NV data back-uped.
Fri Feb 17 23:05:33 2012: MD5 is turned on.
Sat Feb 18 08:43:12 2012: MD5 is turned off on 0
Sat Feb 18 08:44:23 2012: NV data back-up begin.
Sat Feb 18 08:44:23 2012: secondary NV built.
Sat Feb 18 08:44:24 2012: NV data back-uped.
Sat Feb 18 08:44:24 2012: MD5 is turned on.
Sat Feb 18 08:46:42 2012: MD5 is turned off on 2
Sat Feb 18 08:52:38 2012: MD5 is turned off on 0
Sat Feb 18 08:53:32 2012: NV data back-up begin.
Sat Feb 18 08:53:33 2012: secondary NV built.
Sat Feb 18 08:53:33 2012: NV data back-uped.
Sat Feb 18 08:53:33 2012: MD5 is turned on.
Sat Feb 18 08:55:20 2012: MD5 is turned off on 0
Sat Feb 18 08:55:24 2012: NV data back-up begin.
Sat Feb 18 08:55:24 2012: secondary NV built.
Sat Feb 18 08:55:24 2012: NV data back-uped.
Sat Jan 1 00:00:06 2011: NV data back-up begin.
Sat Jan 1 00:00:06 2011: secondary NV built.
Sat Jan 1 00:00:06 2011: NV data back-uped.
Sat Jan 1 00:00:06 2011: MD5 is turned on.
Sat Jan 1 00:01:02 2011: /data/radio/nv_data.bin does not exist.
[email protected]:/factory #
***********************************************************
[email protected]:/data/radio/log # cat nv.log
cat nv.log
Sun Nov 11 11:30:48 2012: /data/radio/nv_data.bin does not exist.
Sun Nov 11 11:30:48 2012: /data/radio/nv_data.bin does not exist.
Sun Nov 11 12:49:31 2012: MD5 fail. orignal md5 '84373eddf2a1617f795b1c1af650f8a
784373eddf2a1617f795b1c1af650f8a7' computed md5 '3eddf2a1617f795b1c1af650f8a7' (
rild)
Sun Nov 11 12:49:31 2012: NV restored.(GED)
[email protected]:/data/radio/log # cd ..
cd ..
[email protected]:/data/radio # cat nv_data.bin.md5
cat nv_data.bin.md5
[email protected]:/data/radio # cat /factory/.nv_dat
a.bin.md5
cat /factory/.nv_data.bin.md5
sh: cat: /factory/.nv_data.bin.md5: No such file or directory
1|[email protected]:/data/radio # cd /factory
cd /factory
******************************************************************
Any clue ?
I found in different forums that there are atleast a few who are having the same issues without doing any manual upgrade.
Thanks
Sanu
It took me a while to understand how the imei system woks but i think i have the gist of it now. i don't know if this works for other models but it must considering i took information from a multitude of sources to work out a solution here's what I did
Before starting this tricky set of commands please make sure your phone has the following settings:
ROOTED
HAS BUSYBOX INSTALLED
HAS EITHER ROOTEXPLORER OR ADB
YOUR PC HAS A PROPER UNIX TEXT EDITOR (NOTEPAD++ OR JEDIT)
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery):good:
If you have any problems please list them below and i will do my best to solve them
Thank you for posting. Awesome!
Sent from my SGH-I897 using Tapatalk 2
Saved. My. Ass.
Thanks!
Hi,
I have this problem with my GT-N7100 where I've rooted it, flashed a ROM and somewhere along the way (I think it was when it rooted), I have lost my IMEI to this generic one. I have been following the steps but I'm a little stuck.
I have found nv_data.bin and nv.log in the /efs folder... but the nv.log doesn't have anything about a corrupted MD5?
This is my nv.log file:
Sun Jan 1 00:02:12 2012: nv data does not exist
Sun Jan 1 00:02:12 2012: md5 compute error
Sun Jan 1 00:02:12 2012: md5 compute error
Sun Jan 1 00:02:13 2012: default NV restored
Sun Jan 1 00:02:21 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:21 2012: 2nd NV built
Sun Jan 1 00:02:21 2012: NV data back-uped
Sun Jan 1 00:11:44 2012: check off
Tue Mar 26 17:23:05 2013: MD5 status = (OFF)
Sun Jan 1 00:00:02 2012: check off
Sun Jan 1 00:00:02 2012: MD5 status = (OFF)
Sun Jan 1 00:00:07 2012: MD5 status = (OFF)
Sun Jan 1 00:00:08 2012: MD5 status = (OFF)
Sun Jan 1 00:00:13 2012: MD5 status = (OFF)
Sun Jan 1 00:00:13 2012: MD5 status = (OFF)
Sun Jan 1 09:36:24 2012: check off
Sun Jan 1 09:36:24 2012: MD5 status = (OFF)
Sun Jan 1 09:36:29 2012: MD5 status = (OFF)
Sun Jan 1 09:36:29 2012: MD5 status = (OFF)
Sun Jan 1 09:36:34 2012: MD5 status = (OFF)
Sun Jan 1 09:36:34 2012: MD5 status = (OFF)
Wed Mar 27 14:21:54 2013: MD5 status = (OFF)
Wed Mar 27 14:21:54 2013: MD5 status = (OFF)
Wed Mar 27 14:21:55 2013: MD5 status = (OFF)
Wed Mar 27 14:21:55 2013: MD5 status = (OFF)
Wed Mar 27 14:21:59 2013: MD5 status = (OFF)
Wed Mar 27 14:21:59 2013: MD5 status = (OFF)
Wed Mar 27 14:22:18 2013: MD5 status = (OFF)
Wed Mar 27 14:22:18 2013: MD5 status = (OFF)
Wed Mar 27 14:23:47 2013: MD5 status = (OFF)
Wed Mar 27 14:23:47 2013: MD5 status = (OFF)
Wed Mar 27 14:23:57 2013: MD5 status = (OFF)
Wed Mar 27 14:23:57 2013: MD5 status = (OFF)
Wed Mar 27 14:23:58 2013: MD5 status = (OFF)
Wed Mar 27 14:23:59 2013: MD5 status = (OFF)
Wed Mar 27 14:23:59 2013: MD5 status = (OFF)
Wed Mar 27 14:24:00 2013: 2nd NV built
Wed Mar 27 14:24:00 2013: NV data back-uped
Wed Mar 27 14:24:00 2013: check on
Wed Mar 27 14:29:40 2013: check off
Wed Mar 27 14:30:05 2013: 2nd NV built
Wed Mar 27 14:30:05 2013: NV data back-uped
Wed Mar 27 14:30:05 2013: check on
Wed Mar 27 14:30:58 2013: fail - no checksum info
Wed Mar 27 14:30:58 2013: NV restored
Wed Mar 27 14:34:48 2013: OFFSET_FOR_PRESET1 writing input
Wed Mar 27 14:34:48 2013: 2nd NV built
Wed Mar 27 14:34:48 2013: NV data back-uped
Wed Mar 27 14:34:54 2013: OFFSET_FOR_PRESET2 writing input
Wed Mar 27 14:34:54 2013: 2nd NV built
Wed Mar 27 14:34:54 2013: NV data back-uped
Wed Mar 27 14:34:57 2013: OFFSET_FOR_PRESET2 writing input
Wed Mar 27 14:34:57 2013: 2nd NV built
Wed Mar 27 14:34:57 2013: NV data back-uped
Tue Jun 18 14:31:16 2013: input from cp
Tue Jun 18 14:31:16 2013: 2nd NV built
Tue Jun 18 14:31:16 2013: NV data back-uped
Tue Jun 18 19:18:19 2013: OFFSET_FOR_PRESET2 writing input
Tue Jun 18 19:18:19 2013: 2nd NV built
Tue Jun 18 19:18:19 2013: NV data back-uped
Click to expand...
Click to collapse
Any ideas?
Thanks.
readinc cuneiform
I have the same problem, my nv.log is this:
Fri Jun 21 16:54:32 2013: md5 compute error
Fri Jun 21 16:54:32 2013: md5 compute error
Fri Jun 21 16:54:32 2013: default NV restored
Fri Jun 21 16:54:59 2013: OFFSET_FOR_PRESET2 writing input
Fri Jun 21 16:54:59 2013: 2nd NV built
Fri Jun 21 16:54:59 2013: NV data back-uped
Fri Jun 21 17:07:09 2013: input from cp
Fri Jun 21 17:07:09 2013: 2nd NV built
Fri Jun 21 17:07:09 2013: NV data back-uped
Been trying to fix this damn problem for ages. I have two logs, one looks exactly like the post above, the other looks like the one OP posted but just says expected ms5 "" and then the current one. Anywhere else to find the expected one?
Thanks
If your nv.log ends with backup NV restored.(GED) that is good it mean even though the m5d didn't mach the expected md5 hash it still restored the proper IMEI. If however your nv.log end in default NV restored that is a sure indication that the default IMEI i.e 004999901064000 is in use.
With my Nexus S even though my EFS partition is corrupt I was able to restore the proper IMEI from the /data/radio partition. I suspect every Samsung model stores its NV data (i.e the IMEI and Blue Tooth Data) in different places. I have noticed if I try to flash a custom rom like CM10 over a stock rom 4.1.2 JZ054K that is when I loose my NV data.
004999010640000 IMEI on my Samsung N7100
Hi
I downgraded my phone to a previous stock samsung rom via odin, due to battery back up issue and I got this generic IMEI. I had previously used the same rom to downgrade and it all went well(unfortunately it got updated back then :silly: , so I had to downgrade again ). This time it gave me a generic IMEI 004999010640000 and I'm in a fix . My phone has been never ever rooted. I googled and somewhere, it was a mentioned that efs folder should be deleted and then a reboot would do the trick. Don't know how right that was, but I couldn't delete/move/rename the efs folder. Secondly, it shows 0 bytes and is empty.
Pls help me. Thanks in advance!
Dave
i wish this thread had been out back in the summer of 2011... i had such a hard time trying to fix this on my own and ended up just pulling a old switcharoo on bestbuy
imei
ethan_hines said:
If your nv.log ends with backup NV restored.(GED) that is good it mean even though the m5d didn't mach the expected md5 hash it still restored the proper IMEI. If however your nv.log end in default NV restored that is a sure indication that the default IMEI i.e 004999901064000 is in use.
With my Nexus S even though my EFS partition is corrupt I was able to restore the proper IMEI from the /data/radio partition. I suspect every Samsung model stores its NV data (i.e the IMEI and Blue Tooth Data) in different places. I have noticed if I try to flash a custom rom like CM10 over a stock rom 4.1.2 JZ054K that is when I loose my NV data.
Click to expand...
Click to collapse
hi my nv.log ends with backup nv restored but still 00499......should i still do this method:fingers-crossed:
zadia24 said:
hi my nv.log ends with backup nv restored but still 00499......should i still do this method:fingers-crossed:
Click to expand...
Click to collapse
Unfortunately I don't have a correct nv.log and everything is corrupted and I'm in generic IMEI. How can I fix it without efs? Is it possible to use someone else files?
I have a nand backup but after I restored it nothing changed. It seems that efs are not backed up in nand backup. Please help me. I spent more than 12 hours to fix this problem.
Bom dia amigo, não consegui encontrar nenhum arquivos com vários números e letras, exemplo xxxxxxxxxxxx. E meu log está assim:
Sun Jan 1 00:00:30 2012: no nv data
Sun Jan 1 00:00:31 2012: default Nv restored.
Sun Jan 1 00:00:31 2012: Nv created
Sun Jan 1 00:00:42 2012: item 2 written
Sun Jan 1 00:00:42 2012: Nv core done
Sun Jan 1 00:00:42 2012: Nv data backup
Sun Jan 1 00:06:29 2012: checksum off
Wed Apr 17 11:12:47 2013: current checksum status is off
Sun Jan 1 00:00:02 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:01:35 2012: current checksum status is off
Sun Jan 1 00:01:42 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 02:54:29 2012: current checksum status is off
Sun Jan 1 02:54:36 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Thu Apr 18 22:00:10 2013: current checksum status is off
Thu Apr 18 22:00:17 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:57 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:59 2013: Nv core done
Thu Apr 18 14:01:59 2013: Nv data backup
Thu Apr 18 14:01:59 2013: checksum on
Thu Apr 18 14:49:10 2013: checksum off
Thu Apr 18 14:50:06 2013: Nv core done
Thu Apr 18 14:50:07 2013: Nv data backup
Thu Apr 18 14:50:07 2013: checksum on
Thu Apr 18 14:50:09 2013: checksum off
Thu Apr 18 14:50:32 2013: Nv core done
Thu Apr 18 14:50:33 2013: Nv data backup
Thu Apr 18 14:50:33 2013: checksum on
Thu Apr 18 21:20:53 2013: item 1 written
Thu Apr 18 21:20:53 2013: Nv core done
Thu Apr 18 21:20:53 2013: Nv data backup
Thu Apr 18 21:21:02 2013: Nv core done
Thu Apr 18 21:21:02 2013: Nv data backup
Tue Jan 1 08:02:35 2013: item 2 written
Tue Jan 1 08:02:35 2013: Nv core done
Tue Jan 1 08:02:36 2013: Nv data backup
Tue Jan 1 08:02:38 2013: item 2 written
Tue Jan 1 08:02:38 2013: Nv core done
Tue Jan 1 08:02:39 2013: Nv data backup
Tue Jul 30 23:22:40 2013: Nv core done
Tue Jul 30 23:22:40 2013: Nv data backup
Fri Aug 23 13:59:45 2013: item 2 written
Fri Aug 23 13:59:45 2013: Nv core done
Fri Aug 23 13:59:45 2013: Nv data backup
Can you help me please?!
---------- Post added at 08:45 PM ---------- Previous post was at 08:39 PM ----------
Good day friends, I could not find in my Galaxy S4 any files with multiple numbers and letters, eg xxxxxxxxxxxx, just found nv_data.bin, nv_data.bin.md5 and nv.log. And so is my log:
Sun Jan 1 00:00:30 2012: no nv data
Sun Jan 1 00:00:31 2012: default Nv restored.
Sun Jan 1 00:00:31 2012: Nv created
Sun Jan 1 00:00:42 2012: item 2 written
Sun Jan 1 00:00:42 2012: Nv core done
Sun Jan 1 00:00:42 2012: Nv data backup
Sun Jan 1 00:06:29 2012: checksum off
Wed Apr 17 11:12:47 2013: current checksum status is off
Sun Jan 1 00:00:02 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:01:35 2012: current checksum status is off
Sun Jan 1 00:01:42 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 02:54:29 2012: current checksum status is off
Sun Jan 1 02:54:36 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Thu Apr 18 22:00:10 2013: current checksum status is off
Thu Apr 18 22:00:17 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:57 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:59 2013: Nv core done
Thu Apr 18 14:01:59 2013: Nv data backup
Thu Apr 18 14:01:59 2013: checksum on
Thu Apr 18 14:49:10 2013: checksum off
Thu Apr 18 14:50:06 2013: Nv core done
Thu Apr 18 14:50:07 2013: Nv data backup
Thu Apr 18 14:50:07 2013: checksum on
Thu Apr 18 14:50:09 2013: checksum off
Thu Apr 18 14:50:32 2013: Nv core done
Thu Apr 18 14:50:33 2013: Nv data backup
Thu Apr 18 14:50:33 2013: checksum on
Thu Apr 18 21:20:53 2013: item 1 written
Thu Apr 18 21:20:53 2013: Nv core done
Thu Apr 18 21:20:53 2013: Nv data backup
Thu Apr 18 21:21:02 2013: Nv core done
Thu Apr 18 21:21:02 2013: Nv data backup
Tue Jan 1 08:02:35 2013: item 2 written
Tue Jan 1 08:02:35 2013: Nv core done
Tue Jan 1 08:02:36 2013: Nv data backup
Tue Jan 1 08:02:38 2013: item 2 written
Tue Jan 1 08:02:38 2013: Nv core done
Tue Jan 1 08:02:39 2013: Nv data backup
Tue Jul 30 23:22:40 2013: Nv core done
Tue Jul 30 23:22:40 2013: Nv data backup
Fri Aug 23 13:59:45 2013: item 2 written
Fri Aug 23 13:59:45 2013: Nv core done
Fri Aug 23 13:59:45 2013: Nv data backup
Can you help me please?!
Same here
My log says nothing
Fri Aug 23 19:29:02 2013: default NV restored
Fri Aug 23 19:29:40 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 23 19:29:40 2013: 2nd NV built
Fri Aug 23 19:29:40 2013: NV data back-uped
Hi,
I have the same problem, my log doesn't contain the MD5 failure messages:
Code:
Sun Jan 1 00:02:16 2012: nv data does not exist
Sun Jan 1 00:02:16 2012: default NV restored
Sun Jan 1 00:02:24 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:25 2012: 2nd NV built
Sun Jan 1 00:02:25 2012: NV data back-uped
Sun Jan 1 00:08:02 2012: check off
Sun Jan 1 00:00:08 2012: check off
Sun Jan 1 00:00:02 2012: check off
Sun Jan 1 09:27:28 2012: check off
Tue Dec 4 03:45:25 2012: 2nd NV built
Tue Dec 4 03:45:25 2012: NV data back-uped
Tue Dec 4 03:45:25 2012: check on
Tue Dec 4 03:46:13 2012: check off
Tue Dec 4 03:47:36 2012: 2nd NV built
Tue Dec 4 03:47:36 2012: NV data back-uped
Tue Dec 4 03:47:36 2012: check on
Tue Dec 4 03:47:44 2012: check off
Tue Dec 4 03:47:59 2012: 2nd NV built
Tue Dec 4 03:47:59 2012: NV data back-uped
Tue Dec 4 03:47:59 2012: check on
Tue Dec 4 03:48:20 2012: fail - no checksum info
Tue Dec 4 03:48:20 2012: NV restored
Tue Dec 4 03:49:02 2012: OFFSET_FOR_PRESET1 writing input
Tue Dec 4 03:49:02 2012: 2nd NV built
Tue Dec 4 03:49:02 2012: NV data back-uped
Tue Dec 4 03:49:07 2012: OFFSET_FOR_PRESET2 writing input
Tue Dec 4 03:49:07 2012: 2nd NV built
Tue Dec 4 03:49:07 2012: NV data back-uped
Tue Dec 4 03:49:09 2012: OFFSET_FOR_PRESET2 writing input
Tue Dec 4 03:49:09 2012: 2nd NV built
Tue Dec 4 03:49:10 2012: NV data back-uped
Fri Jun 21 10:40:51 2013: input from cp
Fri Jun 21 10:40:51 2013: 2nd NV built
Fri Jun 21 10:40:51 2013: NV data back-uped
Fri Aug 30 03:11:27 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 30 03:11:28 2013: 2nd NV built
Fri Aug 30 03:11:28 2013: NV data back-uped
I checked /data/radio but there is no folder with that name. Any idea where I can find this file on SG Note2 ?
Any further advice?
ethan_hines said:
It took me a while to understand how the imei system woks but i think i have the gist of it now. i don't know if this works for other models but it must considering i took information from a multitude of sources to work out a solution here's what I did
Before starting this tricky set of commands please make sure your phone has the following settings:
ROOTED
HAS BUSYBOX INSTALLED
HAS EITHER ROOTEXPLORER OR ADB
YOUR PC HAS A PROPER UNIX TEXT EDITOR (NOTEPAD++ OR JEDIT)
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery):good:
If you have any problems please list them below and i will do my best to solve them
Click to expand...
Click to collapse
Hey i have the same problem in my I9500. But i dont see the log saying MD5 fail. I am confident from you post that this is why one country's modem is working and my country's is not working. Can you tell me how to find out the MD5 my Country's modem is expecting?
What's the best/preferred method to create a backup for this issue? I tried flashing CM 10.x on my Galaxy S3 (GT-I9300) a few days ago and I had this problem. By some miracle, and after about 30 flash attempts, I got my proper IMEI back. Just in case this happens again, I want to create a suitable backup file(s) to have the option to use this "fix".
when I get my phone back from service is show that imei ...is a problem?
anyone ?
What is the significance of having the generic IMEI?
I'm hoping to hide the identity of a phone by using this. I don't want to use any DATA on A** network, but I don't want to get smashed with a Data plan just because. I just need 2G and 3G voice to work.
I wasn't able to even make phone calls when it had that generic imei.
Hi!
I have trouble with rooting my MEDION LIFETAB S10333. This tablet runs Android 4.4.2, so I tried to run psneuter exploit but Android shell returned error: "FATAL: Kernel is too old Aborted".
After this I tried to install Magisk via adb and program returned error: "Failure [INSTALL_FAILED_OLDER_SDK]". Then I tried to root this device via towelroot and kingoroot to no effect.
Do you know other ways to root this tablet?
Kernel version: 3.0.36+
Regards!
AFAIK Magisk only is supported on devices running Android 6.0 ( released 2015 ) - API-level 23 - and higher.
You can try to temporarily root your tablet's Android by means of ADB if you have a su binary what is matching Android 4.4 at your hand.
FYI:
Android 4.4 ( released 2013 ) is API-level 19, today ( 2022 ) Android 12 ( released 2021 ) is API-level 31.
xXx yYy said:
AFAIK Magisk only is supported on devices running Android 6.0 ( released 2015 ) - API-level 23 - and higher.
You can try to temporarily root your tablet's Android by means of ADB if you have a su binary what is matching Android 4.4 at your hand.
FYI:
Android 4.4 ( released 2013 ) is API-level 19, today ( 2022 ) Android 12 ( released 2021 ) is API-level 31.
Click to expand...
Click to collapse
I cloned this github repo: https://github.com/jpacg/su-binary, then I tried to compile it but I got this error:
make[1]: Entering directory '/home/tomek/.bin/su-binary'
Android NDK: WARNING: Building static executable but APP_PLATFORM android-21 is not the latest API level android-31. Build may not succeed.
make[1]: Leaving directory '/home/tomek/.bin/su-binary'
make[1]: Entering directory '/home/tomek/.bin/su-binary'
[armeabi-v7a] Executable : su
ld: error: duplicate symbol: setxattr
>>> defined at common.c:113 (jni/su/common.c:113)
>>> ./obj/local/armeabi-v7a/objs/su/su/common.osetxattr)
>>> defined at syscalls-arm.S:1639 (out/soong/.intermediates/bionic/libc/syscalls-arm.S/gen/syscalls-arm.S:1639)
>>> syscalls-arm.o.text+0xE28) in archive /home/tomek/.bin/android_ndk/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/../sysroot/usr/lib/arm-linux-androideabi/21/libc.a
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [/home/tomek/.bin/android_ndk/android-ndk-r23b/build/core/build-binary.mk:728: obj/local/armeabi-v7a/su] Error 1
make[1]: Leaving directory '/home/tomek/.bin/su-binary'
make: *** [Makefile:5: build] Error 2