.. I flashed chain fire 3d now I have no signal what soever... I uninstalled... still nothing
Iv recovered an old nandroid ... Still nothing !
Also tried flashing k3 radio ... And nothing again
Help!
Sent from my Nexus S using Tapatalk 2 Beta-5
-Try another sim card
-Toggle Airplane Mode On and Off
-Manually choose your wireless provider in the settings
-Enter " *#*#4636#*#* " (*#*#info#*#*) and press Phone Information and play around with the settings there. Hit the menu button for more options. Unsure if this could provide any success. Note: DON'T press the update or refresh buttons next to SMSC, it'll be an effort sorting that out again (it takes the PDU SMSC number).
Some things to try out.
Tried them all... Nothing
Also tried wiping rom and reinstalling a different one..
still broken...
this isnt good ....
Sent from my Nexus S using Tapatalk 2 Beta-5
{
"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"
}
Sent from my Nexus S using Tapatalk 2 Beta-5
Ok so some how my imei number messed up.... Great.. It doesn't backup in clock work does it?
Sent from my Nexus S using Tapatalk 2 Beta-5
am i screwed?
It doesn't back up in clockwork. Its recommended to back it up manually but android seems to back it up itself. I'm no expert so it might be better to take someone elses advice before you do mine
I can't take responsibility for what happens if you try this, but you should be fine with a backup anyway.
Make a backup of the /efs folder and place it somewhere safe. I've heard you can try deleting the contents of the folder and rebooting. If you're lucky it will restore your original imei.
If not, likely nothing will happen and you move onto other options before begging Samsung.
Didn't work ...
Sent from my Nexus S using Tapatalk 2 Beta-5
Have a look at this thread also.
1- it doesnt let me remain the elfs folder... says operation failed.. and yes i have rw permissions
2- i dont have any .bak files in there..
strange
Indeed strange. What you may be able to try is to delete what is in there now and copy over your .bak files from the backup you made and removing the .bak at the end - if the backup you made has any .bak files in there.
Also, is your wifi mac address correct (found behind battery i believe)?
i have no .bak files im afraid...... lol it looks like its completly dead... i didnt make any backups of efs folder except for the one after it messed up...
i dont get why mine hasnt made any backups itself like others have
couldnt find the wifi mac . but the wifi is working if that helps
Original address found behind battery. EFS has it in the /efs/imei/.nvmac.info file. It is displayed in the status settings too. Don't think there is anywhere to compare bluetooth address so no point with that.
Btw, do you have an nv.log file? Post that up, might reveal something, though i doubt we can fix it.
i have no ... elf/imei file...........
:-(
also this is the . nv.log
9' (rild)
Mon Apr 2 18:25:56 2012: truncate 10250 -> 5130 bytes
Mon Apr 2 18:25:58 2012: backup NV restored.
Tue Apr 3 22:01:07 2012: MD5 fail. orignal md5 'c7c309bde3cccb7666b801c0c4e8fca2' computed md5 '91f9c3635dc57f57a14d796446554268' (rild)
Tue Apr 3 22:01:09 2012: backup NV restored.
Tue Apr 3 22:18:21 2012: MD5 fail. orignal md5 'aa7c086cb7c98a7a4ddb411597eebe89' computed md5 '11c47abd9671baa5964b445ade3fb974' (rild)
Tue Apr 3 22:18:23 2012: backup NV restored.
Tue Apr 3 23:03:50 2012: MD5 fail. orignal md5 'aa7c086cb7c98a7a4ddb411597eebe89' computed md5 '11c47abd9671baa5964b445ade3fb974' (rild)
Tue Apr 3 23:03:52 2012: backup NV restored.
Wed Apr 4 18:00:19 2012: MD5 fail. orignal md5 'e0779b7c50bcadec9914b2b410f04263' computed md5 '293932a0ebbaf6889ab81d9051964ab3' (rild)
Wed Apr 4 18:00:20 2012: backup NV restored.
Wed Apr 4 18:18:51 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 '47abcb88e4dbf55d1d10b84f382f9bde' (rild)
Wed Apr 4 18:18:52 2012: backup NV restored.
Thu Apr 5 10:43:07 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 '47abcb88e4dbf55d1d10b84f382f9bde' (rild)
Thu Apr 5 10:43:09 2012: backup NV restored.
Fri Apr 6 11:03:46 2012: MD5 fail. orignal md5 'fafc81076bb2b81829be89a8b8d79904' computed md5 'eef92909a375d18e00c81683aa214911' (rild)
Fri Apr 6 11:03:47 2012: backup NV restored.
Sun Apr 8 17:26:44 2012: MD5 fail. orignal md5 '2f2b22919b661d5aa077c6d5f5421ef5' computed md5 '7ae402a7ca3407a193aba95d31e19b0f' (rild)
Sun Apr 8 17:26:46 2012: backup NV restored.
Wed Apr 11 15:06:10 2012: MD5 fail. orignal md5 '7fb36f1c69a4deb6045987272662fddf' computed md5 'a0cdfff7483cee5689a2fe27d62806d2' (rild)
Wed Apr 11 15:06:12 2012: backup NV restored.
Thu Apr 12 20:48:56 2012: MD5 fail. orignal md5 'f4a6489730d8b589f9c8653194ceab77' computed md5 'cb97acdb8e0a621e06407b0c685c62d3' (rild)
Thu Apr 12 20:48:57 2012: backup NV restored.
Fri Apr 13 13:26:19 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 '47abcb88e4dbf55d1d10b84f382f9bde' (rild)
Fri Apr 13 13:26:21 2012: backup NV restored.
Fri Apr 13 13:48:13 2012: MD5 fail. orignal md5 'aa7c086cb7c98a7a4ddb411597eebe89' computed md5 'e0f62afa0d1a6808ea178f35dda5a960' (rild)
Fri Apr 13 13:48:15 2012: backup NV restored.
Sat Apr 14 23:55:44 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 '7acf3908ac2f6bab96dae0c787da5f09' (rild)
Sat Apr 14 23:55:45 2012: backup NV restored.
Sun Apr 15 23:25:45 2012: MD5 fail. orignal md5 '2f2b22919b661d5aa077c6d5f5421ef5' computed md5 '69f80d7ad8105dadc2cbb4ae51c29a15' (rild)
Sun Apr 15 23:25:46 2012: backup NV restored.
Sun Apr 15 23:40:40 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 '234d933a327a37c274c0f483e84bf49a' (rild)
Sun Apr 15 23:40:42 2012: backup NV restored.
Mon Apr 16 11:05:24 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 '234d933a327a37c274c0f483e84bf49a' (rild)
Mon Apr 16 11:05:26 2012: backup NV restored.
Mon Apr 16 18:28:19 2012: MD5 fail. orignal md5 '2f2b22919b661d5aa077c6d5f5421ef5' computed md5 '69f80d7ad8105dadc2cbb4ae51c29a15' (rild)
Mon Apr 16 18:28:21 2012: backup NV restored.
Mon Apr 16 19:23:18 2012: MD5 fail. orignal md5 '69f80d7ad8105dadc2cbb4ae51c29a15' computed md5 'd0ac6847c6bfb4db716f02762ff3f500' (rild)
Mon Apr 16 19:23:20 2012: backup NV restored.
Mon Apr 16 20:01:07 2012: MD5 fail. orignal md5 '2f2b22919b661d5aa077c6d5f5421ef5' computed md5 '69f80d7ad8105dadc2cbb4ae51c29a15' (rild)
Mon Apr 16 20:01:09 2012: backup NV restored.
Tue Apr 17 09:37:46 2012: MD5 fail. orignal md5 '2f2b22919b661d5aa077c6d5f5421ef5' computed md5 '848963e11b33fe111d162b74335aaff2' (rild)
Tue Apr 17 09:37:48 2012: backup NV restored.
Wed Apr 18 19:41:23 2012: MD5 fail. orignal md5 'e5b35a71ef42d7c8b5e4231108beecdf' computed md5 '418194c06e3cf8bcd6ae56f40b074b4c' (rild)
Wed Apr 18 19:41:25 2012: backup NV restored.
Thu Apr 19 00:03:16 2012: MD5 fail. orignal md5 'e0779b7c50bcadec9914b2b410f04263' computed md5 '067abbec99fc28495a7c3fc600829cc6' (rild)
Thu Apr 19 00:03:18 2012: backup NV restored.
Thu Apr 19 09:23:53 2012: MD5 fail. orignal md5 '3c49581b75220fd49f29d288bde41d9d' computed md5 'dbd9fb6381d961087c6a3ce15296a8e5' (rild)
Thu Apr 19 09:23:54 2012: MD5 fail. orignal md5 '5b8658cbdcaba18e24f2f0d73ddc1b1e' computed md5 '29ea80238521887644a42cc0cd8247cb' (rild)
Thu Apr 19 09:23:55 2012: default NV restored.
Thu Apr 19 09:36:35 2012: MD5 fail. orignal md5 '7fea385ad8f628e8185aa1ef2d234061' computed md5 'f28726a4e62efefbca4fa0a0db109d63' (rild)
Thu Apr 19 09:36:35 2012: default NV restored.
Thu Apr 19 09:49:07 2012: MD5 fail. orignal md5 '04e4c3495a5bfe2fd89f7811cedcaf78' computed md5 '464cf39a2ae667f6d4df310abac8520b' (rild)
Thu Apr 19 09:49:08 2012: default NV restored.
Thu Apr 19 10:17:30 2012: MD5 fail. orignal md5 '3b5c6a882af6b61ff77285ca953112b6' computed md5 '08ea622c5b9627b29eb3da4e74c71b2f' (rild)
Thu Apr 19 10:17:30 2012: default NV restored.
Thu Apr 19 10:34:18 2012: MD5 fail. orignal md5 '3e43c1946dd64c14907df7646f99827f' computed md5 '353302f0c890ae3bcde411f4233ae6aa' (rild)
Thu Apr 19 10:34:18 2012: truncate 10296 -> 5176 bytes
Thu Apr 19 10:34:19 2012: default NV restored.
Thu Apr 19 11:08:40 2012: MD5 fail. orignal md5 '1575df34d18ae5796e69db59b8436707' computed md5 'ea307360a977b55ae56ddc9ecd3336d3' (rild)
Thu Apr 19 11:08:41 2012: default NV restored.
Thu Apr 19 11:14:49 2012: MD5 fail. orignal md5 '86091473a719a8acb7d27a8707d9a146' computed md5 '12fb9592b5c28127883b040e434a2321' (rild)
Thu Apr 19 11:14:50 2012: default NV restored.
Thu Apr 19 11:38:40 2012: MD5 open fail. (No MD5 file) : /efs/nv_data.bin.md5
Thu Apr 19 11:38:40 2012: default NV restored.
you can see on the 19th... it messes up ... and restores a default
Indeed. I infact have a similar series of events on my Nexus S, but i have both current backups and backups in the days where i freshly rooted my phone to compare to.
It looks like i actually have logs of when these files were created with the first MD5 fail back when i first flashed ICS. .nv_data.bin seems to change on each boot while the .nv_data.bak has stayed the same. the .bak's md5 is the same too, but it doesn't correspond to the working .bak file. Odd. Maybe my phone is pending it's (temporary) death since only the backup is left seemingly working. I still ain't touching it though.
These nv.bins are encrypted so there sure as hell isn't an easy way to recreate one with a given imei. Hex editors have yielded very little results for me.
yea ... i dont know what is going on, but i never realised so much stuff was going on in this file before now.. if i do ever get it working again.. wht is the best way to back up this folder? just a straight copy and paste or can it be done cia clockwork
Two types of backup would be best. One straight copy (preferrably directly into a .tar file to keep permissions) of the whole folder, and another cat .img of the mounted block - see here.
Anyone else willing to share their nv.log for comparison? Even better if you have one straight after rooting.
Looks like this is unfixable
Related
Hi,
everytime I try to connect to my Postfix Server (with Cyrus IMAP) I get the following "error"
Code:
/var/log/mail.log
Apr 21 02:49:47 h137XXXX cyrus/imap[11563]: accepted connection
Apr 21 02:49:51 h137XXXX cyrus/imap[11563]: client id: "vendor" "Microsoft" "os" "Windows Mobile" "os-version" "5.2" "os-revision" "0.7.2" "guid" "294b479XXXXb91003c10fcXXXXb5f4a20a657c09"
Apr 21 02:49:52 h137XXXX cyrus/imap[11562]: seen_db: user XXX opened /var/lib/cyrus/user/c/XXX.seen
Apr 21 02:49:52 h137XXXX cyrus/imap[11562]: open: user XXX opened INBOX
Apr 21 02:49:53 h137XXXX cyrus/imap[11563]: login: 16.106.113.82.net.de.o2.com [82.113.106.16] XXX plaintext User logged in
Apr 21 02:49:54 h137XXXX cyrus/imap[11562]: SQUAT failed to open index file
Apr 21 02:49:54 h137XXXX cyrus/imap[11562]: SQUAT failed
Any idea what is going wrong? Using a Prophet with Windows Mobile 6 (Shadow 1.0).
I know its more or less a Linux question, but an XDA is involved
(/usr/lib/cyrus/bin/reconstruct -r user.XXX - had no effect at all)
Alguem já consegui instalar e usar o OpenVPN no milestone 2 com android 2.2 ? podem explicar como fizeram ?
Obrigado
Um. Yah. Might try English.
Sent from my DROID2 using XDA App
I believe he's looking for an explanation on how to use OpenVPN for the milestone 2 or he wants to know how it's made. not sure which. It is Portuguese though.
Sorry,
I am unable to use the openvpn milestone in February with android 2.2
I installed openvpn and openvpn sentings install, busybox.
The options are
Load kernel module tun
lsnmod 'system / lib / modules / tun
Path to configurations
/ sdcard / openvpn
Path to binary openvpn
/ system / xbin / openpvn
client.conf
client
fast-io
dev tun
proto tcp
nobind
remote XXX.XXX.XXX.XXX: 1194
route-method exe
route-delay 2
resolv-retry infinite
persist-key
persist-tun
auth-user-pass
ca / sdcard / openvpn / turquesa.cer
comp-lzo
verb 3
Status / sdcard / openvpn / openvpn_status.log
log-append / sdcard / openvpn / openvpn.log
The error is this
Sun Feb 13 14:38:18 2011 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sun Feb 13 14:38:18 2011 NOTE: --fast-io is disabled since we are not using UDP
Sun Feb 13 14:38:18 2011 LZO compression initialized
Sun Feb 13 14:38:18 2011 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sun Feb 13 14:38:18 2011 MANAGEMENT: >STATE:1297618698,RESOLVE,,,
Sun Feb 13 14:38:18 2011 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Feb 13 14:38:18 2011 Local Options hash (VER=V4): '69109d17'
Sun Feb 13 14:38:18 2011 Expected Remote Options hash (VER=V4): 'c0103fa8'
Sun Feb 13 14:38:18 2011 Attempting to establish TCP connection with 189.71.249.81:443 [nonblock]
Sun Feb 13 14:38:18 2011 MANAGEMENT: >STATE:1297618698,TCP_CONNECT,,,
Sun Feb 13 14:38:18 2011 MANAGEMENT: CMD 'bytecount 0'
Sun Feb 13 14:38:19 2011 MANAGEMENT: CMD 'bytecount 0'
Sun Feb 13 14:38:20 2011 TCP connection established with XXX.XXX.XXX.XXX:1194
Sun Feb 13 14:38:20 2011 Socket Buffers: R=[131072->131072] S=[131072->131072]
Sun Feb 13 14:38:20 2011 TCPv4_CLIENT link local: [undef]
Sun Feb 13 14:38:20 2011 TCPv4_CLIENT link remote: XXX.XXX.XXX.XXX:1194
Sun Feb 13 14:38:20 2011 MANAGEMENT: >STATE:1297618700,WAIT,,,
Sun Feb 13 14:38:20 2011 MANAGEMENT: CMD 'bytecount 0'
Sun Feb 13 14:38:20 2011 MANAGEMENT: >STATE:1297618700,AUTH,,,
Sun Feb 13 14:38:20 2011 TLS: Initial packet from XXX.XXX.XXX.XXX:1194, sid=9e42ad84 c9a371e6
Sun Feb 13 14:38:20 2011 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun Feb 13 14:38:20 2011 MANAGEMENT: CMD 'bytecount 0'
Sun Feb 13 14:38:21 2011 VERIFY OK: depth=1, /C=IT/O=efw/CN=efw_CA
Sun Feb 13 14:38:21 2011 VERIFY OK: depth=0, /C=IT/O=efw/CN=127.0.0.1
Sun Feb 13 14:38:23 2011 WARNING: 'dev-type' is used inconsistently, local='dev-type tun', remote='dev-type tap'
Sun Feb 13 14:38:23 2011 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1544', remote='link-mtu 1576'
Sun Feb 13 14:38:23 2011 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532'
Sun Feb 13 14:38:23 2011 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Feb 13 14:38:23 2011 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Feb 13 14:38:23 2011 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Feb 13 14:38:23 2011 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Feb 13 14:38:23 2011 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sun Feb 13 14:38:23 2011 [127.0.0.1] Peer Connection Initiated with 189.71.249.81:443
Sun Feb 13 14:38:24 2011 MANAGEMENT: >STATE:1297618704,GET_CONFIG,,,
Sun Feb 13 14:38:24 2011 MANAGEMENT: CMD 'bytecount 0'
Sun Feb 13 14:38:26 2011 SENT CONTROL [127.0.0.1]: 'PUSH_REQUEST' (status=1)
Sun Feb 13 14:38:26 2011 PUSH: Received control message: 'PUSH_REPLY,route-gateway 192.168.0.0,route 192.168.0.0 255.255.255.0,route-gateway 192.168.0.0,ping 8,ping-restart 30,ifconfig 192.168.0.240 255.255.255.0'
Sun Feb 13 14:38:26 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:2: route (2.1.1)
Sun Feb 13 14:38:26 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:6: ifconfig (2.1.1)
Sun Feb 13 14:38:26 2011 OPTIONS IMPORT: timers and/or timeouts modified
Sun Feb 13 14:38:26 2011 OPTIONS IMPORT: route-related options modified
Sun Feb 13 14:38:26 2011 Note: Cannot open TUN/TAP dev /dev/tun: No such file or directory (errno=2)
Sun Feb 13 14:38:26 2011 Note: Attempting fallback to kernel 2.2 TUN/TAP interface
Sun Feb 13 14:38:26 2011 MANAGEMENT: Client disconnected
Sun Feb 13 14:38:26 2011 Cannot allocate TUN/TAP dev dynamically
Sun Feb 13 14:38:26 2011 Exiting
Thiago
You might want to put. " CODE /CODE " (with brackets around both without perenths) tags around that for readability and space.
Sent from my DROID2 using XDA App
Okay so as I was trying to put CM7 on my DX all was looking good until the reboot. After the reboot it goes right to the bootloader screen. I have tried resetting the phone multiple times. Still no joy. Below is what I have found, tried and errors that I am getting. Please help.
Errors on Bootloader Screen: A5, 69, 35, 00, 27
Tried to SBF back to stock GB and RSD doesn't work. Error: 0x7029
I did find a link link to remedy the issue but am unable to post it. I have tried literally everything that I can think of.
Which didn't work at all. Below is the error log in rsd.
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 50 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 43 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 2187
ERROR: Device S Flash OMAP3630 MI is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 1024
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 523
ERROR: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Now to sum it all up. I have the latest drivers, I have tried reinstalling the drivers, I have tried reinstalling rsd lite three times, pulled battery, and looked around. If there is something I am missing please tell me. Any help is appreciated. Thanks XDA.
lilb3119 said:
Okay so as I was trying to put CM7 on my DX all was looking good until the reboot. After the reboot it goes right to the bootloader screen. I have tried resetting the phone multiple times. Still no joy. Below is what I have found, tried and errors that I am getting. Please help.
Errors on Bootloader Screen: A5, 69, 35, 00, 27
Tried to SBF back to stock GB and RSD doesn't work. Error: 0x7029
I did find a link link to remedy the issue but am unable to post it. I have tried literally everything that I can think of.
Which didn't work at all. Below is the error log in rsd.
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 50 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 43 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 2187
ERROR: Device S Flash OMAP3630 MI is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 1024
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 523
ERROR: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Now to sum it all up. I have the latest drivers, I have tried reinstalling the drivers, I have tried reinstalling rsd lite three times, pulled battery, and looked around. If there is something I am missing please tell me. Any help is appreciated. Thanks XDA.
Click to expand...
Click to collapse
I had to flash the FULL sbf and reroot and Install the 2 part zip to get back to GB. The FUll sbf should work, but if it fails try doing the system only after.
Can anyone help him out?
I refuse to believe he's the only one who's had this issue.
lilb3119 said:
Okay so as I was trying to put CM7 on my DX all was looking good until the reboot. After the reboot it goes right to the bootloader screen. I have tried resetting the phone multiple times. Still no joy. Below is what I have found, tried and errors that I am getting. Please help.
Errors on Bootloader Screen: A5, 69, 35, 00, 27
Tried to SBF back to stock GB and RSD doesn't work. Error: 0x7029
I did find a link link to remedy the issue but am unable to post it. I have tried literally everything that I can think of.
Which didn't work at all. Below is the error log in rsd.
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 50 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 43 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 2187
ERROR: Device S Flash OMAP3630 MI is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 1024
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 523
ERROR: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Now to sum it all up. I have the latest drivers, I have tried reinstalling the drivers, I have tried reinstalling rsd lite three times, pulled battery, and looked around. If there is something I am missing please tell me. Any help is appreciated. Thanks XDA.
Click to expand...
Click to collapse
Use the full sbf. There's two flavors of sbf files, a system file and a full. Find the other one and you should be fine. I've had this problem and that's how I fixed it.
Save yourself some trouble and trying sbfing it was linux. sbf_flash works wonders.
Hello, this solves service required code corrupt
Download:
Debrick-intel_blank_flash.7z.zip MD5: ea90220f2a6f080c960dcf6254463b89
Extract Debrick-intel_blank_flash.7z.zip
Extract Debrick-intel_blank_flash.7z
Contents of the folder Debrick-intel_blank_flash
Code:
-rw-r--r-- 1 621 sep 26 2014 1RSD_BlankFlash.xml
drwxr-xr-x 2 4096 abr 8 2016 Driver
-rw-r--r-- 1 1781 sep 26 2014 PFT_BlankFlash.xml
-rw-r--r-- 1 66528 sep 26 2014 dnx_firmware.bin
-rw-r--r-- 1 18073088 sep 26 2014 droidboot.img.POS.bin
-rw-r--r-- 1 8413938 sep 26 2014 droidboot.unsigned_raw
-rw-r--r-- 1 1937660 sep 26 2014 ifwi_firmware.bin
-rw-r--r-- 1 2874 ene 13 19:29 intel_blank_flash.bat
-rwxr-xr-x 1 2302 ene 13 22:32 intel_blank_flash.sh
-rw-r--r-- 1 43008 jun 22 2009 libgcc_s_dw2-1.dll
-rw-r--r-- 1 11362 ene 10 2009 mingwm10.dll
-rw-r--r-- 1 66528 sep 26 2014 osr_dnx_firmware.bin
-rwxr-xr-x 1 260 ene 13 19:52 sec_xfstk.sh
-rw-r--r-- 1 880 ago 11 2014 soft_fuse.bin
-rw-r--r-- 1 155648 ene 12 13:01 wdapi1140.dll
-rw-r--r-- 1 1377280 feb 12 2013 xfstk-dldr-api.dll
-rw-r--r-- 1 1292288 feb 12 2013 xfstk-dldr-solo.exe
From Windows
1) We enter the folder Debrick-intel_blank_flash
Install drivers "iSocUSB-Driver-Setup-1.0.4.exe" found in the "Driver" subfolder.
2) Run "intel_blank_flash.bat"
And we turn on the phone while connected to your computer
That should fix your brikck phone.
From GNU / Linux
First way:
1) Install Phone Flash Tool Lite
https://01.org/node/2463
(Depending on your favorite distribution)
2) Link "xfstkFlashTool" from the folder where you installed /usr/local/bin
3) We mark the script as executable
Code:
Chmod + x sec_xfstk.sh
and we execute it sec_xfstk.sh
And we turn on the phone while connected to your computer
Second way:
1) we install xfstk
https://sourceforge.net/projects/xfstk/
2) We connect "xfstk-dldr-solo" from the folder where we installed /usr/local/bin
3) We mark the script as executable
Code:
Chmod + x intel_blank_flash.sh
and we execute it intel_blank_flash.sh
And we turn on the phone while connected to your computer
This repairs the service required code corrupt. the best debrick for motorola razer i (xt890).
Finally flashing with rsd-lite or fastboot with the version of your favorite rom
Sorry for my English
a greetings
Hello! thank you for the magnificient support... but...
I tried your script...
few times it failed, but finally that makes me going into the bootloader.
BUT after that, i was unable to flash anything. I tried with RSD lite and also manual fastboot from stock firmware.
I decided to try tomorrow so i selected "power off". Now the phone is dead. Neither the green led nor the message "service required code corrupt" shows up. Now it's a total brick
ok it discharged. now when i turn on it goes on bootloader but these messages are displayed:
Esip signature missing
E:invalid GPT partition gpt_main
E: not found osip header
E:mismatched osii detected
E: no valid GPT existed
invalid mbr partition os type 0x 0
failed to load GPT partitions no any partition found!
E: no PDS partition found!
How to proceed? every try of using fastboot to load something fails...
Thankyou...
yostyle said:
ok it discharged. now when i turn on it goes on bootloader but these messages are displayed:
Esip signature missing
E:invalid GPT partition gpt_main
E: not found osip header
E:mismatched osii detected
E: no valid GPT existed
invalid mbr partition os type 0x 0
failed to load GPT partitions no any partition found!
E: no PDS partition found!
How to proceed? every try of using fastboot to load something fails...
Thankyou...
Click to expand...
Click to collapse
I GOT THE SOLUTION YAYYYYY
i was able to flash only th gpt.bin contained in the ota update file found here in the forum (that is Blur_Version.91.2.26001.XT890.Retail.en.EU)
after that i flashed (skipping the GPT part) the files contained in 9.8.2I-50_SMI-29_S7_USASMI01UKE1021.0R_USASMIJBRTGB_P007_A005_S1FF_fb that i found at https://firmware.center/firmware/
THANK TO YOU I HAVE MY PHONE ALIVE! :good::good::good::good:
Hi, friends ,
I have a SHV-E210L model and want to use it as daily driver(i dont have other phone). When i flash "LineageOS 14.1 from kmmng"(or other custom rom) mi IMEI goes to 000000000000000, i have a backup of my /efs partition and follow some instructions in OP(restorecon -R -F /efs) or write 0 to .nv_state to, but imei still invalid. If i flash(Via odin) or restore stock rom 4.4.4 mi IMEI is ok again, note that i dont need to restore /efs backup in stock rom. An older version of nv.log shows:
Sun Dec 8 17:50:04 2019: nv data does not exist
Sun Dec 8 17:50:04 2019: MD5 status = (OFF)
Sun Dec 8 17:50:04 2019: MD5 status = (OFF)
Sun Dec 8 17:50:04 2019: invalid /efs/.nv_data.bak file size. It must be 0x200000 bytes but 0x40000
Sun Dec 8 17:50:04 2019: restore_nv_backup_data OK.
Sun Dec 8 17:50:04 2019: NV restored
Sun Dec 8 17:50:16 2019: MD5 status = (OFF)
Sun Dec 8 17:50:21 2019: MD5 status = (OFF)
Sun Dec 8 17:50:28 2019: MD5 status = (OFF)
Sun Dec 8 17:50:31 2019: MD5 status = (OFF)
Sun Dec 8 17:50:36 2019: MD5 status = (OFF)
I need you help fellows, work with Android 4.4.4 in this days is very difficult.
Thank in advance.