Related
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
aukhan said:
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
Click to expand...
Click to collapse
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
mvattoy said:
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
Click to expand...
Click to collapse
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
aukhan said:
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
Click to expand...
Click to collapse
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
mvattoy said:
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
Click to expand...
Click to collapse
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
aukhan said:
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
Click to expand...
Click to collapse
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
mvattoy said:
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
Click to expand...
Click to collapse
first recommend you to flash stock and try see if you've got you IMIE .
mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
1st flash a stock rom and see whether u get imei and baseband back or not.. if it didnt get recovered then service centers can only help you as u didnt make a backup of efs..
There is a slim chance its not his efs,
I did pretty much the same as he to get root thru the toolkit, and had no network, I found I had no APN configured
Perhaps check this.
Settings... more settings .. mobile networks... acess point names.
Make sure you have something here.
if not you will need to search for the settings for whoever your provider is.
good luck
A|c
Hello,
New XDA poster, here... I've watched the intro video, and I've read the forum rules.
I'm not completely new to custom roms; I've previously flashed CM images on 2 other occasions, (on this same device, and 1 other.)
My question is: if I've lost my maguro's IMEI number (presumably by wiping /factory via CWM,) how screwed am I? I do not have a backup of /factory.
Here's how I got myself into this mess:
(Started from CM-10.1.2 or CM-10.1.3, can't remember.)
1. Updated recovery to clockwork-6.0.4.3-maguro
2. Factory reset (from inside recovery)
3. Formatted /system, /cache, /factory (immediately after starting that last one, I had a feeling it wasn't a good idea.)
4. Installed "cm-10.2-20131030-NIGHTLY-maguro.zip"
5. Installed "gapps-jb-20130813-signed.zip"
6. Rebooted
Everything worked peachy, except now my mobile service is permanently unavailable. Confirmed that I now have a generic IMEI number under Settings -> About phone -> Status.
This was a Play Store purchase; I am the original owner.
</ryan>
I have the same issue.
Did the /factory wipe on my phone from cwm. Among other wipes from the mounts menu.
Installed cm-10.2 ... Nightly
Here are the problems which I am facing.
1. The network signal indicator is blank & the phone reports emergency calls only. On my Vodafone's sim. ( also on tata DoCoMo & Idea sim cards).
2. Although the network signal indicator is blank 2g gsm mobile data is still working I.e. I can access websites, sync my phone with Google etc. Its just the call functionality is not working.
3. Tried another SIM from BSNL ( a local service provider in India). This sim works fine all the functionality ie call, sms , data is working on the BSNL sim.
If anyone has any suggestion how to fix this issue please help.
Sent from my Galaxy Nexus
I haven't done this with the Gnex, but this did happen with the i9000 and i9100 back then when moving from CM6 > CM7 and formatting from RFS over to EXT2 partitions destroyed my EFS folder. What I ended up doing was using Odin to flash back to stock from bootloader: the TAR images. I hope that if you flash to stock using Odin that you can achieve similar results. Remember that factory-images for Play Store models are "takju". Outside the US is "yakju".
OK let me try ODIN flashing.
Using the method & files from the following post
http://forum.xda-developers.com/showthread.php?t=2065470
Sent from my Galaxy Nexus
alpha-niner64 said:
I hope that if you flash to stock using Odin that you can achieve similar results. Remember that factory-images for Play Store models are "takju". Outside the US is "yakju".
Click to expand...
Click to collapse
Of course I'm willing to try anything that stands some chance of success, but I wonder: how could flashing Google's stock takju image-- that is the same for everybody-- restore an IMEI number that is different for everybody?
Solution...
Well kinda.
The issue is with Generic IMEI 004999010640000 most network providers have blocked this IMEI no. on their network, which is why the network registration fails & thus we get no network.
Their is a file nv_data.bin in 2 places on the device one is in /factory/nv_data.bin & the other is in /data/radio/nv_data.bin
The file in /data/radio/nv_data.bin determines the phones imei no. & the one in /factory/nv_data.bin is the backup.
In case the phone gets wiped or factory reset the system copies the file from /factory/nv_data.bin to /data/radio/nv_data.bin in order to determine the handsets IMEI no.
When you & I wiped the /factory/ in CWM it removed this backup file, thus on installation of any subsequent roms the phone was getting a generic imei resulting in network error.
If you have a NANDROID backup of the phone in an earlier state when the network was working correctly then restore from that backup & your network should be fine. I did & it restored my network.
Also if you are successful in getting your network & IMEI back I suggest backing up /data/radio/nv_data.bin & /data/radio/nv_data.bin.md5 to your PC because since the nandroid backup does not restore these files in /factory/ I am guessing any future wipe / rom upgrades will reset the radio to generic IMEI.
If you dont have a nandroid backup of a earlier good state of your phone I have no idea how to recreate the files.
in case you need it You can find your handsets IMEI no. in at the back of the phone below the battery.
The following links may help
http://forum.xda-developers.com/showthread.php?t=1570342
http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html
Brilliant post, gaurav1984.
Nope, no remaining backups at all. It seems odd to watch myself type those words, as I'm usually pretty zealous about backups generally. But I'm relatively new to CM, and in this instance my thinking was I wanted a completely fresh wipe; there was nothing I desired to save... or so I thought.
Since the consequences of wiping /factory are so dire, I think it would be a good idea if the CWM developers guard that particular action with a prominent red warning message.
... I might possibly have a Titanium Backup, from almost 2 years ago, somewhere. I wonder if that included nv_data.bin. Hmm...
</ryan>
Ryan,
take a look at the last paragraph on this page:
http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
Sounds like might be a viable option for you.
ryanvbissell said:
Brilliant post, gaurav1984.
Nope, no remaining backups at all. It seems odd to watch myself type those words, as I'm usually pretty zealous about backups generally. But I'm relatively new to CM, and in this instance my thinking was I wanted a completely fresh wipe; there was nothing I desired to save... or so I thought.
Since the consequences of wiping /factory are so dire, I think it would be a good idea if the CWM developers guard that particular action with a prominent red warning message.
... I might possibly have a Titanium Backup, from almost 2 years ago, somewhere. I wonder if that included nv_data.bin. Hmm...
</ryan>
Click to expand...
Click to collapse
Update...
@ryanvbissell any nandroid backup (no matter how old or whichever rom ) will do even if it is not CM.
You may try the procedure on the link above, but from what I have read Galaxy Nexus NV_data uses salted md5 checksums so that method might not work.
Also if you have the nv_data.bin & nv_data.bin.md5 files you can push it into /factory so that whenever you flash a new rom or do a factory wipe the system picks up these files from /factory & restores correct IMEI data.
You will need ADB & Samsung USB Drivers(only on windows) for this procedure to work, Please Google how to installing ADB
& If you are on windows installing Samsung USB Drivers for Galaxy Nexus. drivers for Galaxy Nexus™ (Verizon) Android Smartphone, work for the GSM variant as well.
On MAC you don't need the USB drivers, just install ADB.
Here is how
1. From CWM recovery -> mounts and storage -> mount /factory.
2. From your PC -> adb push nv_data.bin /factory
3. From your PC -> adb push nv_data.bin.md5 /factory
4. From Your PC -> adb shell
5. From Your PC -> # cd factory/
6. From Your PC -> /factory # chmod 700 nv_data.bin
7. From Your PC -> /factory # chmod 700 nv_data.bin.md5
8. From Your PC -> /factory # chown radio.radio nv_data.bin
9. From Your PC -> /factory # chown radio.radio nv_data.bin.md5
10. From Your PC -> exit
After this install a new ROM or do a factory wipe & your IMEI should be back & networks should work.
now any future wipe / rom upgrades will NOT reset the radio to generic IMEI.
I have done the same on my phone with successful results.
ryanvbissell said:
3. Formatted /system, /cache, /factory (immediately after starting that last one, I had a feeling it wasn't a good idea.)
Click to expand...
Click to collapse
I did the exact same thing, felt the exact same way, and on the same day too. And I had also purged all my backups at one point and decided to start over when this happened. Freaky.
@gaurav1984 - That was my solution as well. Luckily, it turned out I had an old lingering backup I made months ago on a network drive from the last time I backed up my desktop to reinstall Windows. Completely forgot about it until just a little while ago, and found out that a regular data backup (at least with TWRP) includes /data/radio, so it contained a good set of nv_data.bin and nv_data.bin.md5. I wound up doing exactly what you did but also pushed them to /data/radio/ and set the same permissions/ownerships there -- more of a spray-and-pray tactic since I hadn't seen your post at the time. Crossed my fingers, rebooted, and it worked! What a nerve-racking 24 hours.
Needless to say, those files are now backed up in several locations. Having /factory in the format list seems odd... should have to go out of your way to format something that important.
From what I found before I discovered my old backup, you'd have to buy a $200 magic box (which I think would just end up being an overpriced UART cable for this particular phone) and possibly some software to do an "IMEI Repair." I found some cheaper options from SRS Services through SamMobile (~$15US UART cable from China plus ~$35US to run a repair once), but it wasn't 100% clear if it could fix a formatted /factory partition with no backup whatsoever. I'm guessing it could since it requires a UART cable and the demo videos showed assigning an IMEI. Rebuilding these files is probably hard to come by since the same process can be used to clone another IMEI or change your IMEI to something other than what it's supposed to be, which is illegal in some countries.
mrbo said:
Ryan,
take a look at the last paragraph on this page:
http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
Sounds like might be a viable option for you.
Click to expand...
Click to collapse
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
---------- Post added 3rd November 2013 at 12:14 AM ---------- Previous post was 2nd November 2013 at 11:51 PM ----------
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
rburrow said:
I did the exact same thing, felt the exact same way, and on the same day too.
Click to expand...
Click to collapse
Misery loves company.
rburrow said:
I did the exact same thing, felt the exact same way, and on the same day too.
Click to expand...
Click to collapse
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.[/QUOTE]
Agreed. My only surviving backup is a Titanium Backup, and it only includes APKs. So, I think my solution will be to buy a Nexus 5.
... And until it arrives, my email .sig will read: "-- SENT FROM MY ANDROID TOUCH", because obvious.
</ryan>
ryanvbissell said:
rburrow said:
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.
Click to expand...
Click to collapse
Agreed. My only surviving backup is a Titanium Backup, and it only includes APKs. So, I think my solution will be to buy a Nexus 5.
... And until it arrives, my email .sig will read: "-- SENT FROM MY ANDROID TOUCH", because obvious.
</ryan>
Click to expand...
Click to collapse
Hah. I finally decided to order a Nexus 5 like an hour or two before I managed to wipe all the nv_data files simultaneously. My friend told me that I had a tiny tablet now when I figured out what I had done.
cardboardhome said:
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
Click to expand...
Click to collapse
If you really don't have a backup anywhere, I think your only solution is to send it in somewhere to have the IMEI repaired (either someone that says they can fix it, or to Samsung). Unfortunately it's more than likely going to cost money. The cheapest potential solution I could find was from SRS Services / SamMobile, where you have to buy a UART cable and pay to do an IMEI repair using their software. I have never used them so I have no idea how all that works out.
I searched quite a bit (albeit only for a like a day) for a free DIY way to regenerate or create a new nv_data.bin file, but I just couldn't find anything. The only thing I didn't try was an OMAP flash because I couldn't install the driver that came with the zip in Windows 8.1 64-bit, but I was already giving up at that point so I didn't go any further.
@ryan
I was just wondering about the ODIN method as posted on post no. 2 & 3.
When you flash your phone using ODIN it wipes the whole internal memory & recreates the partitions.
Thus we can assume all files gets wiped including those in the /factory.
So I was thinking if Odin recreates the whole filesystem as new maybe there might be some file or script or program .... In there which recreates the IMEI files as well.
Ryan if you feel up to it could you please do a Odin flash of your device ( since their is nothing more to loose ) & check if that somehow restores the imei.
If it does that might be really helpful to someone in the same situation as u in the future & you WD be able to resell your Gnex fully working.
Sent from my Galaxy Nexus using xda app-developers app
gaurav1984 said:
Ryan if you feel up to it could you please do a Odin flash of your device ( since their is nothing more to loose ) & check if that somehow restores the imei.
If it does that might be really helpful to someone in the same situation as u in the future & you WD be able to resell your Gnex fully working.
Click to expand...
Click to collapse
Good point. I originally passed up on the Odin angle because on a page that listed versions of Odin for specific phones, there was no suggested version for the i9250. But you have a good point; I really have nothing to lose. So I will try it, but it may take me a few days before I have time.
Meanwhile, I took my GN to a local 'CPR' cellphone repair shop, and explained my predicament. Their tech just shook his head sadly and said 'Only Samsung has the proprietary software to fix this.' I found that surprising because I think I've seen references online to some $200+ kit called SPT ("Samsung Phone Tools") which I thought was geared towards professional phone repair businesses. Oh well.
Sent from my ANDROID TOUCH... sigh.
</ryan>
IMEI
Odin flashing doesn't work
struggled today
dkkerry said:
Odin flashing doesn't work
Click to expand...
Click to collapse
did the same mistake of formatting factory today, it took me a day to find out my old backup dated back june 2013 made via cwm and finally phone is back to normal. Seems without backup restoring is impossible...maybe time to get nexus 5 for u
pvkiniyan95 said:
did the same mistake of formatting factory today, it took me a day to find out my old backup dated back june 2013 made via cwm and finally phone is back to normal. Seems without backup restoring is impossible...maybe time to get nexus 5 for u
Click to expand...
Click to collapse
Same happend with me today, and I dont even have a nandroid backup, as we both are from India you know its hard to get solved from a samsung service centre, can you please upload you CWM backup files??? so that I will try to restore those on my gnex
file too big
my backup file is around 2.1gb which will take me weeks to upload with the internet connection i have, may be if i backup the efs with some tools and send that img to u will that be useful...its really difficult to upload the whole backup
Utkarsh-ezzo said:
Same happend with me today, and I dont even have a nandroid backup, as we both are from India you know its hard to get solved from a samsung service centre, can you please upload you CWM backup files??? so that I will try to restore those on my gnex
Click to expand...
Click to collapse
pvkiniyan95 said:
my backup file is around 2.1gb which will take me weeks to upload with the internet connection i have, may be if i backup the efs with some tools and send that img to u will that be useful...its really difficult to upload the whole backup
Click to expand...
Click to collapse
ya i can understand that,
i think we domt have efs partition on gnex its located at /factory , so if you could share the file from /factory it would be great for me,
nv_data.bin, nv_data.bin.md5 , .nv_data.bak and .nv_data.bak.md5
these files from /factory would help me out..
you will need to use root browser or root explorer or adb shell....
Sent from my Galaxy Nexus using Tapatalk
Hi everybody,
I have rooted my M8 Dual Sim and according to SDFix disabled the limitations to use the SD card in my phone freely. Almost. Moving files around within ES File Explorer is no problem, neither copying files from PC to the card.
BUT: when I open a file on either the phone's memory or the card from the PC, the files open all write protected.
This is what drives me mad, I would like to open the files, write into them, and save them like in a normal environment. Does anybody know how to disable this write protection? Please help. Thank you.
Nobody misses usm on his m8???
maklein said:
Hi everybody,
I have rooted my M8 Dual Sim and according to SDFix disabled the limitations to use the SD card in my phone freely. Almost. Moving files around within ES File Explorer is no problem, neither copying files from PC to the card.
BUT: when I open a file on either the phone's memory or the card from the PC, the files open all write protected.
This is what drives me mad, I would like to open the files, write into them, and save them like in a normal environment. Does anybody know how to disable this write protection? Please help. Thank you.
Click to expand...
Click to collapse
I cannot believe this, 60 views and no answer?! C'MON guys, does nobody use his M8 Dual SIM as a portable HDD???
maklein said:
I cannot believe this, 60 views and no answer?! C'MON guys, does nobody use his M8 Dual SIM as a portable HDD???
Click to expand...
Click to collapse
Its been reported by users here that the SD fix apps don't work on the "regular" (single SIM) M8, so I assume the same is also true with the dual SIM. There is a custom kernel module that fixes the SD limitations, but again not sure if it works on the dual SIM, or if there is a corresponding mod/hack.
redpoint73 said:
Its been reported by users here that the SD fix apps don't work on the "regular" (single SIM) M8, so I assume the same is also true with the dual SIM. There is a custom kernel module that fixes the SD limitations, but again not sure if it works on the dual SIM, or if there is a corresponding mod/hack.
Click to expand...
Click to collapse
SDFix has been used only to check whether I gained access to my SD card. And, according to the possibility to move files freely, i gained full access. Only that my files opened from he PC are all write protected.
I can copy&move files from internal storage to SD card and viceversa, and I can copy and move file from PC to SD card and vicecersa. But the files located on SD card, when opened from the PC are always opened in write protected mode. WHY???
Regards
maklein said:
SDFix has been used only to check whether I gained access to my SD card. And, according to the possibility to move files freely, i gained full access. Only that my files opened from he PC are all write protected.
I can copy&move files from internal storage to SD card and viceversa, and I can copy and move file from PC to SD card and vicecersa. But the files located on SD card, when opened from the PC are always opened in write protected mode. WHY???
Regards
Click to expand...
Click to collapse
Almost seems like a permissions issue but I'm not sure if the device would automatically apply permissions that will have you only "read, write and execute" those files on the device itself and not on the PC. That's probably something that you'll have to "set" yourself.
All the files that I create, pictures that get taken etc all have it as "read and write" which is why we can view it on the pc, but in your case it almost seems like it saves it as "read-only" preventing you from making any other changes. BUT that's how it looks and it might not necessarily be the issue at hand
Change permissions?
BerndM14 said:
Almost seems like a permissions issue but I'm not sure if the device would automatically apply permissions that will have you only "read, write and execute" those files on the device itself and not on the PC. That's probably something that you'll have to "set" yourself.
All the files that I create, pictures that get taken etc all have it as "read and write" which is why we can view it on the pc, but in your case it almost seems like it saves it as "read-only" preventing you from making any other changes. BUT that's how it looks and it might not necessarily be the issue at hand
Click to expand...
Click to collapse
That makes sense, thanks BerndM. Any hint on how to chance permissions easily, without having to flash custom ROM?
To be more exact, I am talking only about doc(x), xls(x), txt files, nothing executable.
Truth is, only the windows explorer can handle the files, opening a word file and trying to save it directly from the program to the SD card isn't possible. But I guess you knew that already... I don't recall how it was with my last HTC (the HD2), but at least I could save an opened file in its original storage.
If you have a USB card reader, try to connect to your PC and format the card. I'd suggest FAT32 as its the most universal; although ExFAT should be supported by the M8 (but only really needed if you have huge files).
I've seen a number of folks on here have various read/write issues with the SD, even when the card works perfectly on other devices. The permissions issue is a logical conclusion, but might just be a wild goose chase. Reformatting the card sometimes solves the issue. Even using the phone to format the card doesn't solve the issue, when formatting on PC works.
redpoint73 said:
There is a custom kernel module that fixes the SD limitations
Click to expand...
Click to collapse
Actually, I'm mixing this up, the kernel module is to disable system write protection, not SD write protection. I'm having a brain fart on how to do the SD fix.
But as mentioned, this might not be the OP's issue anyway. At least, I don't think so based on the described symptoms.
Need relief from system write protection
redpoint73 said:
Actually, I'm mixing this up, the kernel module is to disable system write protection, not SD write protection. I'm having a brain fart on how to do the SD fix.
But as mentioned, this might not be the OP's issue anyway. At least, I don't think so based on the described symptoms.
Click to expand...
Click to collapse
Hi there, @redpoint73 if you could provide some guidance as how to get a hold of that insecure kernel, I'd certainly be grateful. A link would be a boon.
I'm trying, with no avail, to edit hostapd.conf (my hotspot configuration file). There are a few options on it that I can't switch on a GUI, like SSID Broadcast and 802.11n toggles. Also, my hotspot has a difficult time upholding the wakelock it needs to stay on without a data interruption at screen off. I don't know if Amplify (by Ryan Steckler aka "cryptyk") might be to blame, because I haven't told it (and isn't) restricting Wi-Fi related wakelocks at all.
Please check my signature below for any details you'd like to ponder. Good night.
furboom1240 said:
Hi there, @redpoint73 if you could provide some guidance as how to get a hold of that insecure kernel, I'd certainly be grateful. A link would be a boon.
Click to expand...
Click to collapse
I'm not at all familiar with the things you are trying to modify. But to remove the system write protection: http://forum.xda-developers.com/showthread.php?t=2701816
redpoint73 said:
I'm not at all familiar with the things you are trying to modify. But to remove the system write protection: http://forum.xda-developers.com/showthread.php?t=2701816
Click to expand...
Click to collapse
@redpoint73 it looks like the link on the OP's post for my phone is dead. Any other ideas (or more reliable links)?
Sent from my One M8 using XDA Free mobile app
furboom1240 said:
@redpoint73 it looks like the link on the OP's post for my phone is dead. Any other ideas (or more reliable links)?
Click to expand...
Click to collapse
Post to that thread, and see if the OP can re-post; or if another user can post it.
But I just noticed your are running CM11? Custom ROMs should already have this implemented, or not applicable in the first place (AOSP?).
redpoint73 said:
Post to that thread, and see if the OP can re-post; or if another user can post it.
But I just noticed your are running CM11? Custom ROMs should already have this implemented, or not applicable in the first place (AOSP?).
Click to expand...
Click to collapse
I thought so, too. But I will take your advice and post to the OP. Thanks.
Sent from my One M8 using XDA Free mobile app
My friend deleted a very important video from her Xperia Z1 Compact. The video was recorded with camera and stored in internal storage. Is there ANY way to recover it? Internal storage is mounted through MTP when connected to PC, so I can't do it via PC. Is there any way to connect internal storage as mass storage so I'm able to dig through it with a software on PC?
If not, there are apps for Android which can do this but they require root. This phone is not rooted and it's under warranty, but she said that the video is very important so she's ready to risk the phone and lose warranty. I've done rooting hundred times on my old X10 phone, but never on my Z1 (yes, I have it too, but c6903, not compact) so I'm a total newbie here. There's a 14.4.A.0.157 firmware on the phone currently (android 4.4.4) and as far as I know, I'll have to flash .108 first, root the device and then flash .157 again. But, would this wipe data on internal storage? If not, there's still a high possibility that something will overwrite the deleted video, since this is a free location now?
What should I do?
It might be possible to connect the phone to PC in USB Debugging mode, open a command prompt and adb pull the internal storage to the PC then dig through it with recovery software. Not sure if it will work but might be worth a try and make sure you have correct drivers installed to use adb. Good luck
spudata said:
It might be possible to connect the phone to PC in USB Debugging mode, open a command prompt and adb pull the internal storage to the PC then dig through it with recovery software. Not sure if it will work but might be worth a try and make sure you have correct drivers installed to use adb. Good luck
Click to expand...
Click to collapse
Thank you for your answer! I tried this: adb pull/ \test and it pulled everything to C:\test but while it was doing, in CMD I saw a lot messages "Ignored special file ...." etc. and I tried with Recuva to deep scan that folder but it didn't found not a single one deleted file. Am I doing something wrong or it's not possible to do this in that way? Maybe another program instead Recuva?
xplod2841 said:
Am I doing something wrong or it's not possible to do this in that way? Maybe another program instead Recuva?
Click to expand...
Click to collapse
I've yet to see a success story of recovering something deleted from the internal memory.
XperienceD said:
I've yet to see a success story of recovering something deleted from the internal memory.
Click to expand...
Click to collapse
You're saying that this is impossible or almost impossible? If it is, tell me now, before I proceed with rooting the device. Don't want to risk the phone and void the warranty for nothing.
xplod2841 said:
You're saying that this is impossible or almost impossible? If it is, tell me now, before I proceed with rooting the device. Don't want to risk the phone and void the warranty for nothing.
Click to expand...
Click to collapse
I'm saying based on the number of times People have tried and failed the odds suggest it's more likely to be impossible than possible.
I've rooted the phone successfully and tried with Disk Digger app. It found 100+ deleted MP4 files, but if I understood right, those are not mp4 files but sectors containing mp4 data, and I can't do nothing with them. Each of them contains a few MBs and this video was 1080p and more than 5 minutes length so it should have a few hundred MBs. So, this app is practically useles, as long as it doesn't join all those sectors and give me a full video.
So I proceeded to this method: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
But I have problems with it. My post with screenshoots is on the last page (last post). This thread is in the nexus forum so it could be that there's something different on our Xperia Z1 Compact. Can somebody take a look and see if I'm typing something wrong?
What are other possibilities to create a complete image of internal storage, now when I have root access?
xplod2841 said:
What are other possibilities to create a complete image of internal storage, now when I have root access?
Click to expand...
Click to collapse
None of your screen shots are showing in the thread, but the partition number doesn't look quite right to me so this might help finding the right one - http://forum.xda-developers.com/showthread.php?t=2450045.
XperienceD said:
None of your screen shots are showing in the thread, but the partition number doesn't look quite right to me so this might help finding the right one - http://forum.xda-developers.com/showthread.php?t=2450045.
Click to expand...
Click to collapse
Thank you for warning me, I didn't even notice. That's because I'm stupid: I uploaded my photos to my dropbox, and shared the link but I thought that if I shared link, a direct link to photo will be visible as well, but it was visible only to me
Thanks for this link, I'll try.
xplod2841 said:
Thanks for this link, I'll try.
Click to expand...
Click to collapse
No worries, you've shown a bit more persistence but you're on your own at this stage with any trial error. Fingers crossed.
XperienceD said:
No worries, you've shown a bit more persistence but you're on your own at this stage with any trial error. Fingers crossed.
Click to expand...
Click to collapse
Thanks! It's not me who is persistent, I wouldn't problably do all this if this was my phone and my video, but this is not my phone. I'm just doing a favour to my friend and now when I've already rooted the phone, it would be shame to give up.
Hello, there is my problem with OP9 Pro – phone was stuck with some bug and only way to fix it was Wipe Data. Now it's ok, but I do really need to restore photos and videos. Phone is NOT rooted.
After reading tons of information I'm not sure that it's possible to get data back. As I understand I need to follow next steps:
1. Unlock bootloader without wiping data again in order not to lose old structure.
2. Root device, or at least temporary root it.
3. Use some tools to search and restore photos.
But now I'm not sure that everything would be fine. Even the first step is not 100% guarantee that it's possible to avoid data wiping.
So, If there are someone who understand this better, could you please advice me what should I do? Should I waste tons of time or it's muck more likely impossible to do?
Thanks!
mrGenry said:
Hello, there is my problem with OP9 Pro – phone was stuck with some bug and only way to fix it was Wipe Data. Now it's ok, but I do really need to restore photos and videos. Phone is NOT rooted.
After reading tons of information I'm not sure that it's possible to get data back. As I understand I need to follow next steps:
1. Unlock bootloader without wiping data again in order not to lose old structure.
2. Root device, or at least temporary root it.
3. Use some tools to search and restore photos.
But now I'm not sure that everything would be fine. Even the first step is not 100% guarantee that it's possible to avoid data wiping.
So, If there are someone who understand this better, could you please advice me what should I do? Should I waste tons of time or it's muck more likely impossible to do?
Thanks!
Click to expand...
Click to collapse
If you are not bootloader unlocked right now. All hope is lost since unlocking will force a wipe of data that can't be stopped.
MrSteelX said:
If you are not bootloader unlocked right now. All hope is lost since unlocking will force a wipe of data that can't be stopped.
Click to expand...
Click to collapse
I just wiped phone and restored some latest backup (which did not contain media ofc). I was reading about scenario, when we can backup current system, patch it somehow, unlock bootloader and keep old data somehow in place. But it looks so unstable for me.
The folder structure was destroyed when the data was deleted. Although the files still exist -if- they haven't been overwritten, they would be completely juxtaposed. A vast sea of files that could only be sorted by size and file type. No associated time stamps, exif data, original file names and no way to restore it. Let that sink in for a moment.
Just recovering a flash card with a 100 images on it and then trying to sort them is a major headache unless you have a photographic memory. The files names are gone. The recovered images will have a new assigned number generated that is unrelated to the file's original name. Now imagine trying to do that with a 100gb jigsaw puzzle from hell.
Always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
blackhawk said:
The folder structure was destroyed when the data was deleted. Although the files still exist -if- they haven't been overwritten, they would be completely juxtaposed. A vast sea of files that could only be sorted by size and file type. No associated time stamps, exif data, original file names and no way to restore it. Let that sink in for a moment.
Just recovering a flash card with a 100 images on it and then trying to sort them is a major headache unless you have a photographic memory. The files names are gone. The recovered images will have a new assigned number generated that is unrelated to the file's original name. Now imagine trying to do that with a 100gb jigsaw puzzle from hell.
Always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Click to expand...
Click to collapse
Yeah, thanks! Really, there is nothing critical, just default amount of family photos and videos (phone is my father's, I'm just investigating possibility of recovering).
And tons of different information is all across the web. Also, latest Android 12 is pretty new and I guess lots of articles are not suite for that phone.
So, I guess it's too overwhelmed even to try root phone and search files. Maybe, data value is lower that possibility to turn phone into a brick.
mrGenry said:
Yeah, thanks! Really, there is nothing critical, just default amount of family photos and videos (phone is my father's, I'm just investigating possibility of recovering).
And tons of different information is all across the web. Also, latest Android 12 is pretty new and I guess lots of articles are not suite for that phone.
So, I guess it's too overwhelmed even to try root phone and search files. Maybe, data value is lower that possibility to turn phone into a brick.
Click to expand...
Click to collapse
If you want the best possible outcome take it to a data recovery specialist. That's all they do.
Don't use any apps like FoneDoctor, they will find stuff but encrypt the drive $o only that app can unencrypt it.
blackhawk said:
If you want the best possible outcome take it to a data recovery specialist. That's all they do.
Don't use any apps like FoneDoctor, they will find stuff but encrypt the drive $o only that app can unencrypt it.
Click to expand...
Click to collapse
Thanks! A bit upset, but Im great to get useful information.
mrGenry said:
Thanks! A bit upset, but Im great to get useful information.
Click to expand...
Click to collapse
Losing critical data is never pretty.
I've lost a database with decades of data on it. The only way to help prevent this is redundant backups.
Perhaps your father had backup them up deliberately or by happenstance to a PC or other device.