Related
So I installed Rom manager and rooted but have not put any custom roms on the phone yet. Only things I have done was to put VOODOO lag fix and battery widget on phone. I made 2 backup files in ClockworkMod recovery under the nandroid option and thought I would verify that the last backup I did was good. I went through the rom manager into the recovery and into backup/restore and restored my last backup in ClockworkMod recovery. It started the backup and on the screen right now it shows it is restoring system and then starts restoring data and gets to this point and stops:
ClockworkMod Recovery v2.5.1.0
Checking MD5 sums...
Restoreing data...
fota
It has been on the screen for about 45min. If I pull the battery and restart the phone it comes right back to the recovery screen. The only change I made on the phone prior to restoring my backup was to go into rom manager and updated clockworkmod to the latest version. I can get into download mode. Would I just need to get it into download mode and copy a different backup file onto the phone? Any help is appreciated!
Go into download mode and re-flash from the computer. Odin is your friend...
So last night, I tried to restore an backup of mine. Because I had installed CM 7.10 and it removed all of my contacts so I went to restore my backup.
This backup happened to be an incomplete backup so my phone was somewhat bricked. When I boot my phone I see a black background, with a phone and a red triangle with a red exclamation mark in it.
Luckily I have a second backup, which is complete. But I have to find someway to restore this backup. I´ve copied the backup to my pc. My phone is rooted, and I have tried to write all of the images to the phone, now I get this error:
remote: signature verificition fail
How can I bypass this and restore my phone?
Thanks in advance!
Have you try restoring from Rom manager?
Accidentally sent from my Google Nexus S using XDA Premium
I was restoring the backup from Rom Manager yes, but I don't see how I can restore this anymore via my cell phone, since I can't access nothing but fastboot and Hboot and all that.
Red exclaimed mark means you don't have clockworkmod recovery. You need it. Use Rom manager to download it
Accidentally sent from my Google Nexus S using XDA Premium
How am I supposed to download clockworkmod recovery if I can't access the phone? When I boot my phone I can only see the phone with the red exclamation mark, nothing more.
Bump, I really need to use my phone...
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
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.
Hi there - at work we have a number of these Lenovo S6000 tablets. One of them has been returned to us with a weird error that keeps making it reboot at random times. Before I throw it out, I was going to have a go at wiping it and reflashing - just in case it is a software/OS error rather than hardware.
As I said, we have loads of these kicking around, so I've rooted a known good one using framaroot, made a Nandroid backup on an SD card using Online Nandroid Backup, but I can't restore it onto the target device (also rooted) as I don't have a custom recovery installed (neither TWRP or CWM are supported on the Lenovo S6000, apparently).
Is there a way to restore from the backup without going into recovery mode? Or, is there another custom recovery I can install that would support the S6000, does anyone know?
Many thanks in advance