Hei,
I was running 4.3.1 Dirty Unicorns and wanted to flash Smartdroid.
So, flashed Devil recovery and tried to flash the ROM.
It gave me message that there's an error in the zip file.
I was just playing with the options available in the recovery and selected some option, which I don't remember now.
After that, the went into bootloop. "Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
This loop continued.
The phone could be put in Download mode.
Then, I flashed CWM 6.0.4.4 and flashed 4.1.2, which I downloaded some time back.
It went on well. I could boot the phone and had set it up.
However, I couldn't connect to network.
The IMEI was some default one.
Rooted the phone and tried to restore the backup of efs folder using HC-Ktool.
After restore, when I booted the phone, it didn't boot.
"Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
I tried flashing the ROM again, CWM again etc etc.
Nothing worked.
In one occasion, after installing CWM 6.0.4.4, I restored from NANDROID backup. Restore was successful.
But, it wouldn't boot.
Same "Samsung Galaxy S3" appears on the screen and the phone reboots again and again.
Once, I flashed Dirty Unicorns ROM from zip via CWM. Still the same.
What is happening and how to solve it?
Any help is greatly appreciated.
Regards,
Babloo
Wipe Data/Factory Reset -> Download mode
Flash latest Android 4.3 from Sammy through Odin, preferably XXUGMK6 or newer.
Hei,
This worked!!!
Thanks.
Why flashing 4.1.2, Dirty Unicorns didn't work and this one worked?
If you can explain, that will be helpful to all.
Now, though the phone is booting, the efs folder is corrupted.
IMEI number is not what it should be.
I have a backup of the efs folder taken using HC-Ktool long back.
So, the ROM on which efs folder was backedup will be different that the ROM I have now. (Does it make any difference?)
Can I just root and restore that efs folder using HC-Ktool?
Thanks for the help!!
Regards,
Babloo
Edit:
If I flash CWM Recovery 6.0.4.4 and restore the NANDROID backup that I took before I started screwing my mobile, will everything be fine?
Sounds like you tried to flash a corrupt file, always check the md5 before you flash.
EFS is totally separate to the rom, format the partition, restore your backup then factory reset should return your imei on the current rom.
Nandroid will not fix the efs, unless you used a custom backup process that included the partition -the default settings would not do this.
Hei,
"format the partition, restore your backup"
For this, can I just root the phone and use Ktool to restore backup?
If you suggest any other procedure, pls give me more info.
-Babloo
Hei,
After the previous post, I could restore my phone from NANDROID backup that I took yesterday, before the whole mess.
After that, I tried to restore the efs folder using HC-Ktool from efs.img.
It gives the message that restore is completed.
But, after reboot, the IMEI remains the same wrong one (the generic 004999...)
The size of efs.img is 20.48 MB.
I tried to restore using the terminal method.
With the command "unmount /efs" I get error message "sh: unmount: not found"
How can I restore the efs and get back my IMEI?
When I tried to "open" the img file in Windows, it couldn't open. It says that the file is corrupted.
Could it have been really corrupted or it is just that Windows is unable to open it?
I restored the efs using the same backup file.
Why is it not working now?
-Babloo
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Hei,
boomboomer said:
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Click to expand...
Click to collapse
I have been searching for a proper procedure to format the efs partition since your post.
Whatever I found didn't work for me.
Can you please point me to any post that you know?
-Babloo
Guys,
Any ideas?
-Babloo
Related
I have been using JB I9100XWLSN_I9100OXXLS8_NEE for several months without problem. Rooted, with PhilZ-cwm6-XWLSN-OXX-4.92.3-signed.
3 days ago I updated to I9100XWMS1_I9100NEELS1_NEE with no problems. Today the phone stuck and when I booted into recovery I saw the default recovery not Philz. So I flashed it again (the newer version)
But I had a boot loop, so I tried to restore nandroid backup, it didn't work.
I tried to reinstall earlier ROM (LSN) but it gave errors.
Now I can only boot to Philz recovery without doing anything.
How can I restore the phone to anything which works, so that I can root it again.
Back to stock via Odin/download mode, re-root your phone, restore nandroid or reflash custom rom/kernel & start again from scratch.
I did as you said. Flashed the earlier ROM with ODIN but still cannot boot. I just read the Galaxy S II logo at the start and the phone will not start.
Boot into recovery - factory reset ?
Edit - Failing that, search for Hopper8's 'Odin troubleshooting' thread. There's a link to a 3 part firmware in that thread, try flashing that via Odin if you can't factory reset or it doesn't work.
All right, trying.
Well I booted, thanks. If you don't mind, can you guide me further? I'll just write what I intend to do:
1- Boot into recovery and flash Philz again.
2-Using Philz, will try to restore Nandroid backup. I had copied the backup to my computer. As Philz had errors restoring the backup, I copied the one on the computer to SD card, but the MD5 had changed. So I had to disable MD5 check in Philz. Is it normal to change after copying?
Yep those steps make sense. Simply copying a nandroid from your PC back to your phone (I've done this in the past) shouldn't normally change the MD5. The only way the MD5 would change is if any of the files/directories are different in any way.
I guess you're only going to find out if this makes any difference when you try to restore the backup.
Unfortunately, the backup did not work. You need this once in a while and it fails... So dissappointing. I will have to install everything manually. Lots of backup to put into the trash!
Thanks a lot.
Maybe see what you can salvage from the nandroids you have with some of the various apps on GP that allow you to extract files from nandroids (Nandroid Browser, etc) ?
OK. I'll give a try. It would be quite an help if I rescued some.
I also have a Titanium Backup. I'll check if it does most of the job.
Yep, you should be able to get most of your apps/settings back easily with Ti given you'll be restoring them to the same rom/kernel setup. Just remember not to restore system apps or settings. Hopefully you'll be able to pull other stuff out of your nandroids (contacts/call logs/sms/calendar/etc) with those apps I mentioned if you don't have those backed up to Google/elsewhere.
Actually, I just need Call logs and SMS. Most of other stuff are already online, no problem with Contacts, etc.
I had an earlier backup of SMS but will see whether it works or not.
If Nandroid Browser saves these, all will be OK.
I restored almost everything. Just some hours spent.
Thanks again.
Good job, glad you got everything working as it should again. I know doing everything from scratch is a pain, I did a completely clean install on an I9505 on Friday night which took a few hours. You're welcome
I tried to do a full nandroid backup but it failed saying that "error while making a backup image of /data". The progress bar while taking backup of data went from 0% to 90%, then paused for some time, and then went to 100% and then I got the error. In the clockworkmod folder, I saw that two files related to data were made, one of around 500MB and the other of around 0.9GB. So the backup seems to fail in the end. Some History: Last time some months ago, I had tried to restore a backup but was getting md5 mismatch so I had edited the file and put the correct md5 for one field, others were correct. Then the restore was successful.
I am also attaching the log and other details:
Phone: Samsung galaxy Note N7000
ROM: CM11 of June, 2014
Log is attached with the name of "recovery.rar" and here's the link to the log as well:
http://paste.ubuntu.com/8520572/
usman farhat said:
I tried to do a full nandroid backup but it failed saying that "error while making a backup image of /data". The progress bar while taking backup of data went from 0% to 90%, then paused for some time, and then went to 100% and then I got the error. In the clockworkmod folder, I saw that two files related to data were made, one of around 500MB and the other of around 0.9GB. So the backup seems to fail in the end. Some History: Last time some months ago, I had tried to restore a backup but was getting md5 mismatch so I had edited the file and put the correct md5 for one field, others were correct. Then the restore was successful.
I am also attaching the log and other details:
Phone: Samsung galaxy Note N7000
ROM: CM11 of June, 2014
Log is attached with the name of "recovery.rar" and here's the link to the log as well:
http://paste.ubuntu.com/8520572/
Click to expand...
Click to collapse
I'm not the best at reading logs (stll learning), but the one thing that sticks out to me is the fstab errors. Have you used a mod /app / script to swap your storage points perhaps?
If you haven't done anything like that, then I would suggest checking out another recovery and see if you have the same issue. Either Philz, which is based off of CWM, or TWRP (my favorite).
Hello i have messed up real bad, i flashed a philz recovery which I had used in a stock based rom and the backup was successful but then the phone couldn't boot up. So i restored the boot patrition from a previously made backup. This way i successfully booted up my phone and got previous recovery. So far so good. Now i knew that the problem is in recovery. I also had a raw kernel file which I had used to flash the cm11 rom so i flashed that kernel. But then i restated device to find out that i have now lost root access. I tried flashing super su via raw kernels twrp recovery but I saw no effect despite it being flashed. I cannot flash the recovery because the curreny twrp recovery crashes when i try to flash that.
Current situation is that I am getting constant unlimited, system process is crashed, errors and I can see no signal from mobile operator. Wifi is working fine.
Sounds like it might be wise to restore to stock and start over.
Tried to flash a latest version of cm11 and now booted up correctly. root checker says I am rooted.
got latest cwm as well
Now I need to take backup to see if the initial problem is there or not.
Good deal. Glad you're back up and running again.
Hello, I'm new member in here. Today I flashed UltimaROM to my SGS3. Before the flashing I installed Philz touch recovery and saved Nandroid, modem and EFS backups in my PC. After the flashing no IMEI number was shown and I got a message saying " Insert SIM card....". So i tried to restore EFS in custom restore option in philz recovery. Even though it showed restore successful , IMEI number is still unavailable and i couldn't connect to mobile network. I also tried ktools to restore efs but no result. Can someone please help me regarding this issue.
What version firmware did you have before you first flashed? If it was really old then that could be the problem.
Flash a 4.3 stock rom, factory reset them boot and see if your efs is read again.
boomboomer said:
What version firmware did you have before you first flashed? If it was really old then that could be the problem.
Flash a 4.3 stock rom, factory reset them boot and see if your efs is read again.
Click to expand...
Click to collapse
Thanks for the reply. I had 4.1.2. If I flash 4.3 stock ROM can i retrieve my IMEI ?
If you flash a 4.3 stock it will update your efs to v2 and should enable it to be read in all newer firmwares.
I was trying out some ROMs. At first it was fine. Then when I flashed a particular ROM, I started getting "INVALID IMEI" and could not connect to the network anymore.
Luckily I had a full backup of the phone taken with TWRP. I could not see my backup listed in the TWRP that came with the present ROM. So I flashed the Recovery with which I backed up the phone. (TWRP_v2.7.1.1_P780_ROW_KK_Corrected found in stympy's KK rooting tutorial) Then I could see the Backups listed.
When I tried to restore it, it failed with this error:
Code:
Unable to mount '/data'
I guess the partitioning changed. Anyways, I could restore 'Nvram' alone and the INVALID IMEI got replaced by "EMERGENCY CALLS ONLY".
How do I fix this? Can I somehow restore the backup (by fixing Unable to mount /data)?
This is what I am intending to do. Flash a working ROM again (http://www.needrom.com/download/ultralight/), but using my old partition table (the corresponding scatter file would be one among the three provided by stympy in his KK rooting tutorial), and then attempt a restore from TWRP.
daltonfury42 said:
I was trying out some ROMs. At first it was fine. Then when I flashed a particular ROM, I started getting "INVALID IMEI" and could not connect to the network anymore.
Luckily I had a full backup of the phone taken with TWRP. I could not see my backup listed in the TWRP that came with the present ROM. So I flashed the Recovery with which I backed up the phone. (TWRP_v2.7.1.1_P780_ROW_KK_Corrected found in stympy's KK rooting tutorial) Then I could see the Backups listed.
When I tried to restore it, it failed with this error:
Code:
Unable to mount '/data'
I guess the partitioning changed. Anyways, I could restore 'Nvram' alone and the INVALID IMEI got replaced by "EMERGENCY CALLS ONLY".
How do I fix this? Can I somehow restore the backup (by fixing Unable to mount /data)?
This is what I am intending to do. Flash a working ROM again (http://www.needrom.com/download/ultralight/), but using my old partition table (the corresponding scatter file would be one among the three provided by stympy in his KK rooting tutorial), and then attempt a restore from TWRP.
Click to expand...
Click to collapse
Update TWRP!
Link Here! TWRP 2.8.4.0 rev.2
stympy said:
Update TWRP!
Link Here! TWRP 2.8.4.0 rev.2
Click to expand...
Click to collapse
I've tried TWRP_v2.7.1.1_P780_ROW and TWRP_v2.7.1.1_P780_ROW_KK (using the scatter which came with the ROM, ultralight) and they give the same error during backup.
daltonfury42 said:
I've tried TWRP_v2.7.1.1_P780_ROW and TWRP_v2.7.1.1_P780_ROW_KK (using the scatter which came with the ROM, ultralight) and they give the same error during backup.
Click to expand...
Click to collapse
I think your storage partition is corupted!
Try to flash again your stock firmware!
So I have Samsung Tab A6, I rooted it, and removed some bloatware, but then something went wrong and the tablet became inoperable. Not a problem, I took my daughter's tablet, exactly the same model, flashed TWRP on it, created a backup and then went to restore it onto the non-functioning tablet.
The restore didn't go as smoothly as I hoped, TWRP wasn't seeing the backup files on the SD card. After some digging I found out that I have to change the directory name where the back up was. Did that, and then I was able to restore the backup. The problem is that the tablet's serial number abd the MAC address now were identical to my daughter's tablet. I downloaded the factory image from sammobile, and flashed that via ODIN, still the wrong serial number and MAC address persist. I've tried wiping completely via TWRP, reflashing factory image via ODIN, checking "Nand erase" and "EFS clear" boxes, no luck, the wrong MAC address is still there. Can anyone give me an idea on how I can wipe any remnants of what was flashed before to start out with a truly blank device and to flash a factory image onto it.
Thank you in advance
krazyvladimir said:
So I have Samsung Tab A6, I rooted it, and removed some bloatware, but then something went wrong and the tablet became inoperable. Not a problem, I took my daughter's tablet, exactly the same model, flashed TWRP on it, created a backup and then went to restore it onto the non-functioning tablet.
The restore didn't go as smoothly as I hoped, TWRP wasn't seeing the backup files on the SD card. After some digging I found out that I have to change the directory name where the back up was. Did that, and then I was able to restore the backup. The problem is that the tablet's serial number abd the MAC address now were identical to my daughter's tablet. I downloaded the factory image from sammobile, and flashed that via ODIN, still the wrong serial number and MAC address persist. I've tried wiping completely via TWRP, reflashing factory image via ODIN, checking "Nand erase" and "EFS clear" boxes, no luck, the wrong MAC address is still there. Can anyone give me an idea on how I can wipe any remnants of what was flashed before to start out with a truly blank device and to flash a factory image onto it.
Thank you in advance
Click to expand...
Click to collapse
You would have to use a jtag for. That. This is why we tell people not to restore any backups from other devices. Nandroids are for the device they were made from only.
Sent from my Nexus 6 using Tapatalk
can't I wipe it completely
zelendel said:
You would have to use a jtag for. That. This is why we tell people not to restore any backups from other devices. Nandroids are for the device they were made from only.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
But isn't there any way to simply wipe it clean and flash the file that I downloaded from sammobile ???? I did a wipe from TWRP, but still the MAC address stayed the same. Can't I wipe the file where it is stored?
krazyvladimir said:
But isn't there any way to simply wipe it clean and flash the file that I downloaded from sammobile ???? I did a wipe from TWRP, but still the MAC address stayed the same. Can't I wipe the file where it is stored?
Click to expand...
Click to collapse
The issue is that the file that controls it is not touched by flashing. IT is in an untouchable partition (well under normal setup) You can flash what ever one you want it still wont touch that partition. This is why it is always advised to backup the EFS partition. Mainly on samsung devices as they are known for corrupting.
I just wanted to post a follow-up in case someone runs into similar problem.
I was able to solve the issue by running the commands
adb shell
su
echo -n "001122334455" > /persist/wifi/.macaddr
That solved the issue and created a new mac address.
Looking For SM-T280 EFS
Where can I find efs file to download for SM-T280?