Database Users

Need help from i5800 users - finding the way restoring IMEI

Dear all user i580x that rooted pls help post your mount result as a picture
$su
#mount
here is mine which lost IMEI, and i can't see the /efs mounted anymore
{
"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"
}
And it'll be greatfull if you guys can even share me your origin /efs folder (without nv_data.bin offcourse). Mr. Qbanin @ samdroid.net can help us for the nv_data.bin fixed, but only copy this file can't revise G3s IMEI...
Pls help and we can find out the 100% method for restore IMEI @ our phone in the future. so we can do the flashing freely without worry losing our precious IMEI anymore.
Many Thanks and Best Regards

From a thread about the Galaxy S it seems that the IMEI is stored in encrypted form in a file called nv_data.bin. I suggest that in future anyone who flashes keeps a back up of that particular file just in case.
I can't suggest a fix for you if you don't have an uncorrupted backup of it, but maybe reading this thread http://forum.xda-developers.com/showthread.php?t=771158&page=11 could help? (it seems to suggest deleting the file might cause it to be regenerated, but I'd be careful with that!)
Confirmation of this by someone who has a spare/free one Galaxy 3 would be handy, but I dunno if we have anyone around who does. (Ideally we'd test the effects of deleting nv_data.bin, corrupting it with random data and the effects of restoring the file)

AHHHH! Just thought as I posted this (sorry for DP but it deserves it) - Your nv_data.bin file is stored on /efs. In principle you should be able to remount this partition and fix everything... I have no USB cable to hand, but when I do I'll give you its /dev/block/stXXX designation.

ElliotJH said:
AHHHH! Just thought as I posted this (sorry for DP but it deserves it) - Your nv_data.bin file is stored on /efs. In principle you should be able to remount this partition and fix everything... I have no USB cable to hand, but when I do I'll give you its /dev/block/stXXX designation.
Click to expand...
Click to collapse
Thanks. i'll wait for your information.
TIA

Need origin /efs content and stl4, bml4 partitions image
Dear all rooted i580x user!
Pls kindly help compare your "good" /efs folder... maybe mine missing something???? due to one time Erase Phone EFS using Odin Debug Options.
Mine /efs now as below:
Code:
/efs/nv_data.bin
/efs/imei/.nvmac.info
/efs/.files/.dm33 (empty folder)
/efs/.files/.dx1 (empty folder)
/efs/.files/.mp301 (empty folder)
And if you can do adb shell, it'll be very kind of you by sharing your good backup stl4 and bml4 - for research purpose (those partitions did not content any of yours personal data - so PLS HELP!!!). Pls do the backup partions as below and share your img here if possible.
Code:
$su
#cat /dev/block/stl4 > /sdcard/efs_dev-block-stl4.img
#cat /dev/block/bml4 > /sdcard/efs_dev-block-bml4.img
TIA and Best Regards

Hi
I lost my IMEI too but I have a back up of my /efs folder.
So if you still need the files just tell me.
My story is ...
The phone was locked to SFR France, I tried a lot of instructions but nothing worked for me.
Finally I found one who said change the files in the /efs folder to jpc, here it is:
http://forum.xda-developers.com/showpost.php?p=7930170&postcount=7
what I got:
1. the phone is unlocked now and working (call, sms, ...).
2. I lost my IMEI, its now all zeros like 00000000!
what I have in my /efs folder now:
.files (folder)
imei (folder)
root (folder)
batt_cal
nv_data.bin
nv_data.jpc
nv_data.jpc.md5
specs:
GT-I5800 Galaxy Teos
Android 2.1 Update 1
I5800XXJG3
Protuct Code: GT-I5800DKASFR

/efs is located on /dev/block/st14 it should be configured the same as /data

I lost my IMEI too
I lost my IMEI too. If you get any methods of recovering it, please let me know too.

divzzen said:
I lost my IMEI too. If you get any methods of recovering it, please let me know too.
Click to expand...
Click to collapse
Please describe how you lost your IMEI, so that others don't do this way.

I am working on the very same problem and willing to help.
But for this, I need original nv_data.bin files.
Of course (just like ANY "remote" unlocking, NOT only the imei-based code) this involves sending your data (IMEI) to me.
Well, I am a member for a while, and thus may have earned a degree of reputation.
Anyone willing to help (NOTE: you need to HAVE IMEI..) please drop me a pm.

deleted.. deprecated

UPDATE:
forget all that.
http://forum.xda-developers.com/showthread.php?p=11328766#post11328766
check here

2.37 has been rooted!

I have tested it on my phone, it works perfect!
SORRY FOR MY BAD ENGLISH. I HAVE THE CHINESE WORDS ON MY PHONE, SO I DO NOT KNOW WHAT THE ENGLISH EXACTLY IS. I TRANSLATED THEM ON MYSELF, IF YOU DONOT UNDERSTAND MESSAGE ME.
1, you should FLASH RECOVERY TO YOUR PHONE, and that will not be talked here. lots of threads can tell you how to do it.(I HAVE PLACED ONE WAY TO DO IT ON THE SECOND PAGE)
2, unpack "root.rar" into your DISK C, and the folder must be "root"
3, now mark the "debug mode"( you can find it in application Settings) , connect your phone to your computer( just CHARGING MODE)
4, press win+R on your PC keyboard, and type in "cmd".
5, now we can see dos commond, you should type in the following commond one by one.
CD C:\root
adb shell
reboot recovery
6, now your phone should reboot into recovery. select mounts and storage. there select 3 items( mount /system, mount /data, mount /sdcard)
7, disconnect your phone, and connect it again. then type the following commonds into your PC. NOTE THE SPACE
adb push su /sdcard/su
adb push superuser.apk /sdcard/superuser.apk
adb push psneuter /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
8, if you can see "~#" on your screen, you have made it. I have encountered a error on the 5th commond but it seems like ok, afterall I have been rooted.
9, you still have some commond to type.
cp /sdcard/su /system/bin/
cp /sdcard/Superuser.apk /system/app/
ln -s /system/bin/su /system/xbin/su
chmod 06555 /system/bin/su
10, now on your phone you should still have the recovery, unmount the /system, data, sdcard.
11, reboot your phone, and enjoy it!
Thanks very much for the help of pxw816, without him I still in dark.

is this for real? :\

adkz said:
is this for real? :\
Click to expand...
Click to collapse
Sorry for forgeting to upload the file. It works on the chinese rom, I think all rom can be rooted this way...

Anyone willing to see if this would work on a Telus Desire HD with 2.43?

Anyone tried this ?

I'm quite sure this only works on the Chinese ROM. But I might give it a try

I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.

torkaberry said:
I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.
Click to expand...
Click to collapse
Same problem, booting into recovery just shows 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"
}
I think this is the second method posted that only works in China

CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Seems like the chinese OTA's have an unpatched exploit, maybe one of the mods would like to change the title of this thread.

hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help

CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Hey guys, you cannot use the official recovery, flash a recovery that is usually used to install a rom...My recovery is 3.0, I don't know if 2.0 is ok....

evanbigfan said:
hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help
Click to expand...
Click to collapse
I'm not quite sure about that, for people who do not have a recovery may place the following file on your TF card( DO NOT PLACE IT INTO ANY FOLDER!), and shut down your phone(I MEAN COMPLETELY OFF, OR YOU CAN PULL OUT YOUR BATTERY). Then try to press the volume down button and the switch button at the same time to start your phone. See if the recovery can be installed automatically or not. if not, I'm afraid you have to downgrade to root and get a S-Off. If you do not know how to downgrade, post here, and see if i can give you any help or not.

This will never work, you will need Root and S-OFF to flash recovery. (thanks hawks556 for pointing that out)
closed.

[Q] hinkpad Tablet 1: Errors on Recovery Menu (/cache)

Hi
I have a problem with the Thinkpad Tablet 1 (1838-22U).
It does not boot anymore, it hangs on lenovo static logo (not the animated one). So I tried to access the recovery menu by power it on and press Up volume several times.
It says "Booting recovery kernel image". Sometime it hangs in there, some other times it access the recovery menu.
But it gives too many error messages.
E:Can't open /dev/block/mmcblk0p5
(no such file or directory)
E:failed to mount /cache (no such file or directory)
E:failed to mount /cache/recovery/last_log
etc.
Here it goes a pic:
{
"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"
}
Any ideas how to recover the Thinkpad Tablet image when you get that errors? The wipe does not work too, it also give the "E:failed to mount /cache" errors.
Regards
Martin

Maybe try the reformat zip in the CM thread? - http://forum.xda-developers.com/showthread.php?t=1846044
Its under the additional steps.

da_reeseboy said:
Maybe try the reformat zip in the CM thread? - http://forum.xda-developers.com/showthread.php?t=1846044
Its under the additional steps.
Click to expand...
Click to collapse
Thanks for the link, it looks interesting, but I can not mount the sdcard on the "Android Recovery" menu. I'm using the default one, not CWM.
The recovery menu does not recognize the SDcard at all, so I don't know how to copy that .zip file to the tablet.
Martin

I have no idea then... sorry.

martiniturbide said:
E:Can't open /dev/block/mmcblk0p5
(no such file or directory)
Click to expand...
Click to collapse
This looks like your EMMC partitiontable is corrupt.
If the recovery menu doesn't have access to the partitions, you can't format them or install anything.
Maybe flashing a complete fresh ROM will help, but I'm not sure.
Micky

Ameisentaetowierer said:
This looks like your EMMC partitiontable is corrupt.
If the recovery menu doesn't have access to the partitions, you can't format them or install anything.
Maybe flashing a complete fresh ROM will help, but I'm not sure.
Micky
Click to expand...
Click to collapse
Thanks for the reply.
The issue is that I can not copy a fresh ROM via SDCard since the "Recovery Menu" can not mount the SDCard. If there is another way to load the rom I will appreciate any pointer.
Since this tablet has nvidia tegra processor, I had been reading that maybe it can be fixed by using nvflash, but I don't know how to use it yet.
Any experiences to recover a ROM with nvflash are welcome.

I have a simular problem with my tablet, but i can access the recovery at all, and lenovo has locked apx, so i cant flash it by using nvflash

I'm trying to use nvflash. But I'm having a problem with it.
- I turn the table by pressing "Rotate Button" and "power Button" for 4 seconds. (The display does not show anything)
- I connect the USB cable.
- Windows recognize the device (and I have installed the APX drivers).
But when I run "nvflash" with a simple command to display information, it get disconnected from Windows just like if the device get unplugged.
I still don't know what that means.

slippern said:
I have a simular problem with my tablet, but i can access the recovery at all, and lenovo has locked apx, so i cant flash it by using nvflash
Click to expand...
Click to collapse
Hi slippern
I think we have the same issue. Sometimes the "Recovery" runs and show me the error I listed, and sometimes it just hangs on "Booting recover kernel image".

OK, I found the thread where everybody shares my problem.
http://forum.xda-developers.com/showthread.php?t=1745450&page=5
The bad news is that there is not a solution for us.
For what I understand the problem seems that the bootloader of some Thinkpad Tablet device is locked and that why nvflash does not work. We need a 'sbk' code to be able to unlock the tablets, and only lenovo has it. This code has to be leaked for the community try to fix this problem with the Lenovo Tables. It is said that the bootloader is encrypted using AES128, so it will be very hard to obtain this SBK by brute force.

Lame...

I'm fighting with this problem on the Lenovo Forums:
http://forums.lenovo.com/t5/ThinkPa...-1-Errors-on-Recovery-Menu/m-p/1084539#M23085
I was contacted by someone from Technical support and told on the forum that:
"The teams are still investigating into this issues. Currently no work around has been provided at the moment. I'll be sure to post an update as soon as I can get further updates on the case."
He also asked that if your Thinkpad Table 1 is under warranty and having bricking problems, contact the service team and send it in for service.
Too bad mine is not under warranty.
Regards
Martin

Write to /proc/asound not possible

Since 3 months im having audio problems with my moto g4 plus , when i checked log
its something like
/proc/asound/card---/state failed:no such directory
i posted a thread in another forum and advised to check the proc directory, so using root explorer and on comparison with the xda member's asound directory, i found that the card0 folder in which the state file is there is missing
I got the files and tried to copy paste them using many root browsers
result: permission denied,cant copy..etc
tried pushing through adb, tried asb shell su and then cp command
i can write to almost all directories in the root but not proc
I know that /proc is a directory linked to the kernel where info about all running process is stored
but Pasting the missing file is the only thing that can save my phone, heard that i need a insecure kernel to do that,
Can anyone please help me with this?? i badly need to write to /proc
Can any kernel developer make a insecure kernel with these requirements for stock android 7.0.0 xt1643(Sorry,if i sounded noob)

Have you tried to mount the 'proc' partition?
From a terminal emulator app, type:
# su
# mount -o remount,rw /proc
Whether this display an error message, install BusyBox (i recommend this one) and type:
# su
# busybox mount -o remount,rw /proc
Always without the numeral sign.

moonlightdrive said:
Have you tried to mount the 'proc' partition?
From a terminal emulator app, type:
# su
# mount -o remount,rw /proc
Whether this display an error message, install BusyBox (i recommend this one) and type:
# su
# busybox mount -o remount,rw /proc
Always without the numeral sign.
Click to expand...
Click to collapse
Still, couldnt write to proc.See here
Note: I just checked whether i can write or not using cat and mkdir commands
{
"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"
}

Karthik Veenam said:
Since 3 months im having audio problems with my moto g4 plus , when i checked log
its something like
/proc/asound/card---/state failed:no such directory
i posted a thread in another forum and advised to check the proc directory, so using root explorer and on comparison with the xda member's asound directory, i found that the card0 folder in which the state file is there is missing
I got the files and tried to copy paste them using many root browsers
result: permission denied,cant copy..etc
tried pushing through adb, tried asb shell su and then cp command
i can write to almost all directories in the root but not proc
I know that /proc is a directory linked to the kernel where info about all running process is stored
but Pasting the missing file is the only thing that can save my phone, heard that i need a insecure kernel to do that,
Can anyone please help me with this?? i badly need to write to /proc
Can any kernel developer make a insecure kernel with these requirements for stock android 7.0.0 xt1643(Sorry,if i sounded noob)
Click to expand...
Click to collapse
did you found the solution to the audio problem,
the same problem happened to me too.
dot know what to do.

Moto G4 audio not working
Moto G4 audio not working (works after reboot for 2mins and audio goes off)...suddenly my mobile rebooted and after that no audio is playing
Tried hard reset changed custom roms ,stock ROM 6.0 and nougat
Still issues not solved
Tried lot of ways but not working
Please anybody share the method to solve the issue (I have been trying for 2 weeks )
Please help!!

TWRP Serious problem after failed restore: unable to decrypt storage

So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...

yelti said:
So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
Click to expand...
Click to collapse
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup

strongst said:
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
Click to expand...
Click to collapse
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
{
"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"
}
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.

yelti said:
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
Click to expand...
Click to collapse
So I tried a sideload of the factory images.
Flashing is successfull, next I reboot the phone.
It shows me the oneplus logo and reboots to recovery.
I tried installing the stock recovery, but then when I try to sideload the firmware, the usb device is not recognized.

I have an idea, but I don't know if is doable.
I would want to backup the data partition, (adb pull /dev/block/sda13 data_encrypted.img).
Next I would wipe the phone completely, setup encryption with the same pincode.
Next I would like to restore the old data, but I don't know how.
I hope this way I will ask to decrypt my data partition again.
Anyone an idea?

So an update:
I dumped the data and recovery partition.
Code:
adb pull /dev/block/sda13 data_encrypted.img
adb pull /dev/block/sde22 recovery.img
5494 KB/s (67108864 bytes in 11.927s)
Next I wiped the data partition, phone started normally.
I encrypted the phone again with the same pin code.
Next I tried a nandroid backup and restore while the phone was encrypted, no issues there.
Next I flashed an older recovery to the phone.
Now the test to restore the recovery from the image.
On the phone with an adb sheel:
Code:
dd of=/dev/block/sde22 | nc -l -p 9999
On the pc:
Code:
adb forward tcp:9999 tcp:9999
nc 127.0.0.1 9999 < recovery.img
On the phone I get a lot of data on the screen and the message
Code:
8+0 records in
8+0 records out
4096 bytes transferred in 64.155 secs (63 bytes/sec)
First thing I noticed: number of bytes transferred where not the same as the original recovery.
Next I dumped the recovery partition again to disk and compared the md5 hashes, not the same.
Rebooted the phone and it did not go into recovery.
So this process did not work.
Any ideas?

So, It didn't work with netcat, so I did the following:
connect an usb-c to usb-a coverter to the phone, and connected the external drive with the "bad" image on it.
Then dd-ed the image to the data partition.
When I rebooted the phone, it didn't ask for a pin code and the file and folders where gibbirish again.
So I was back to the starting position.
I'm affraid my data is lost forever :s.

Hello @yelti , I know it's been a long time but I'm kinda into the same issue. Have you been able to fix yours? Do you remember how? Thanks.