First these zips are very alpha and need to be tested, don´t use them if you don´t know what you do!
I heard a few times that the efs got lost by downgrading the Stockrom so I tried to make a easy way to make a efs-backup before downgrading to an older Stockrom via Odin.
I made a flashable zip , wich backs up the efs to /sdcard/efs.tar. This tar should be flashable with Odin.
And now I need someone who test it for me, because I don´t have a i9100
I´ve two Versions (attached):
1. cwm-efsbackup-i9100.zip - The first on is based on the temporary CWM from here: http://forum.xda-developers.com/showthread.php?t=1746794 and can be "flashed" from the stock recovery. (Ive only edited killrecovery.sh)
2. efsbackupi9100.zip - This is vor flashing from a CWM. Its based on a CM9 ROM where I deleted unnaccesary files from (but there much unnaccesary stuff left) (sorry wasn´t able to creat my own)
It would be nice if someone could test my zips (i tested a modified version of the second with my i9001, but never had the chance to test the first) and may be improve them....
Soryy for my bad english
Related
Hi, I have the I9100 from two weeks, and I had noticed that samsung phone architecture is slightly different from other android phones.
Before I9100, I had an HTC MAGIC, HTC HERO, NEXUS ONE, ZTE BLADE.. all of these phones are managed and structured in the same way: Bootloader, Recovery, and ROM.
When I get the root, I can flash the recovery, and then I'm sure that if I flash a buggy rom (with a buggy kernel) I can always start the recovery and flash another one.
In samsung is different and I can't find a technical guide on how this phone works.
It seems that the recovery is INSIDE the kernel. Then if I flash a buggy kernel I loose the recovery!
Another strange thing... why do I need to use odin? And why some of the roms (also here in xda) must be installed trough it and others trough recovery?
Why some people have flashed a buggy kernel and can't flash trough odin?
What's the download mode is used for?
Is download mode is a state of the phone that is loaded before and without the kernel?
Why I can't use rom manager (installed trough the market) to flash my recovery and I need to use the CWM that is hardcoded inside the kernel?
I need some answers because I don't wanna follow the guide without knowing what I am do.
Can someone help me?
... no one answered me yet?
Are my questions, silly questions?
I looked into the guides I found here and I didn't found any answer for me..
Well I Don't own a s2 but samsung androids are different
There is no separate recovery partition so it needs to be in the kernel/rom
So its obvious an other method is needed to flash roms if something bad happens with the current rom/kernel so odin and download mode exist
Very Interesting... but.. is download mode loaded before (ad instead) kernel?
If this it is a restore operation should be loaded always.. also from a complete wipe of everything right?
But.. I read somewhere that some buggy kernel does not allow odin to find the phone..
Then.. If I lose the recovery and odin does not recognize my phone... Am I in a 'deadlock' situation?
Hi
I'm having issues with doing a nandroid backup and restore using current stock roms such as KI3.
I read the boot loader changed here compared to older roms, but I'm not sure that this alone is the issue.
What I did is install a frakenstein stock rom, meaning the whole rom was put together from seperate parts of different versions from http://forum.xda-developers.com/showthread.php?t=1075278:
This Frankenstein™ Non-Wipe package has: PDA: XXKI3| Modem/phone: XXKI3| CSC: XEUKD1
Download: http://www.multiupload.com/7JTWS2E37R
Over this I installed the rooted rom from http://forum.xda-developers.com/showthread.php?t=1103399: CF-Root-SGS2_XX_OXA_KI3-42-v4.2-CWM4.zip
Just from the rom side of view, so using the phone with it everything was fine.
However now I did a nandroid backup and later a restore since I wanted to try Cyanogen mod 7.1
The restore itself ran through without errors, however I found that almost all .apk files of /data/app were missing, even google apps like gmail and market.
I heared CWM did not go well with the new boot loader so I tried running the restore after applying an older rom (first just the old boot loader) but this did not help.
I then found that the backup itself did not contain the missing apk files, so the backup process itself was not done properly.
To get to a working state again I had to extract the apk files from an older backup and collect the apks that were still missing manually.
After restoring again and then copying the apks using adb push I had the system working again.
Anyway:
It seemes to me that i had the original boot loader applied when doing the nandroid backup, but that was apparently not enough to get it running properly.
Can anyone help in creating a properly working nandroid backup from one of the newer stock roms like KI3 and KI8?
Thanx!
Can anyone help in creating a properly working nandroid backup from one of the newer stock roms like KI3 and KI8?
Standard method works CWM restore+ backup . Should know i have done ten backups and restores on KI3 today no problem
jje
>Can anyone help in creating a properly working nandroid backup from one of the newer stock roms like KI3 and KI8?
You mean so you do not have to use odin to flash a such roms?
I think you can make those yourself. Just do a factory reset, clear all caches and then use odin to flash the rom, and then apply root and go into cwm to create a backup.
You could share that backup with others.
Ofcourase that would not be entirely stock anymore since root and CWM would be included there.
>Standard method works CWM restore+ backup . Should know i have done ten backups and restores on KI3 today no problem
Interesting - so no problems at all with CWM backup and restore based on a KI3 at all? Including custom settings and own apps installed?
Which rom exactly did you flash and how did you apply CWM?
JJEgan said:
Can anyone help in creating a properly working nandroid backup from one of the newer stock roms like KI3 and KI8?
Standard method works CWM restore+ backup . Should know i have done ten backups and restores on KI3 today no problem
jje
Click to expand...
Click to collapse
+ 1
Standard CWM backup/restore works for me too.
I used the same KI3 Frankenstein firmware as you (OP) but KI3-v4.1 of cf-root.
Thanx.
I installed the 4.1 kernel and also to be sure the old boot loader and made a CWM backup the data.img is now 259mb instead of just 100mb so I think now its a proper backup.
Now I can go ahead and properly try out CM 7.1
Before I install any of the custom ROM, I want to backup my existing stock ROM. But most of the applications which work for other cells like xrecovery and rom manager do not seem to work for Xperia Mini ST15i. So how do I back up my existing ROM before I start trying other ROMs.
I have read the the thread freeXperia and I am aware of the bugs in CM7.1.0 .
Can any one help me with this problem .
My cell is already rooted and is running on the DoomLord Kernel.
Thanks,
just an idea, not sure if this can be considered as a ROM backup i've just bought my first android and still have a lot to learn about it: i'm sure someone with more knowledge will come and resolve your doubt properly but in the meantime think about this:
- flash boot.img from CM7 which has recovery
- make a backup of your settings with recovery
- install CM7 and see if you like it
- to return to stock rom flash kernel.sin and system.sin which are inside the ftf file from your stock FW, and flash them; again, flash boot.img from CM7 (has recovery, remember) then do a restore of your settings. Last, flash doomlord kernel and you should have your stock rom back the way you left it before installing CM7. (not sure if would work if just system.sin is flashed without kernel.sin to avoid the reflashing of CM7's boot.img ) (i suppose it would be rooted again since that was the status when you made the backup).
that's it, some one correct me please if i'm wrong...
hey man, I m brazilian an than cold b that i dont understand your question,
but goes there, you need know 1 thing, after you'd maked a backup with xrecovery ,
could happen that not make work in to recovery, but the backup is right and working, you need make it, 1 recovery original of mobile ,2 instal the custom zip rom, 3 after all, go to xrevovery and make the recovery, from your backup, ha dont forget that reset full wipe
@rael2000ix
Hello everyone,
I have SGS2 with latest stock firmware (XWKI4) for my region.
Now, I would like to start playing with it with roms and such (yes, I already have Jig just as safety net), however I would like to creat as close as possible original configuration.
Now, I have rooted the phone with zergRush by Doomlord sucessfully and made efs backup as well as kernel image backup via HC-kTool. (This is kernel image backup right?) This way I presume I got pretty much untouched kernel image except rooting, right?
What now I would like to do is to make ROM backup and install some recovery. I know that Clockwork that comes with Rom Manager isnt exactly the same as Chainfires CW that comes with CF-Root and I know that Chainfires CW is optimized for Samsung phones (not to mention that they are not compatible with each other).
I guess my question would be is above that I did make sense, and shall I install CW from ROM Backup or get some CF-Root kernel with CW? I mean what do I lose with each solution, or any other advice how to complete ROM backup so that I can recover it if something, God forbid(knock on the wood), gets fishy?
Cheers
Kepavi said:
Hello everyone,
I have SGS2 with latest stock firmware (XWKI4) for my region.
Now, I would like to start playing with it with roms and such (yes, I already have Jig just as safety net), however I would like to creat as close as possible original configuration.
Now, I have rooted the phone with zergRush by Doomlord sucessfully and made efs backup as well as kernel image backup via HC-kTool. (This is kernel image backup right?) This way I presume I got pretty much untouched kernel image except rooting, right?
What now I would like to do is to make ROM backup and install some recovery. I know that Clockwork that comes with Rom Manager isnt exactly the same as Chainfires CW that comes with CF-Root and I know that Chainfires CW is optimized for Samsung phones (not to mention that they are not compatible with each other).
I guess my question would be is above that I did make sense, and shall I install CW from ROM Backup or get some CF-Root kernel with CW? I mean what do I lose with each solution, or any other advice how to complete ROM backup so that I can recover it if something, God forbid(knock on the wood), gets fishy?
Cheers
Click to expand...
Click to collapse
If you take some time and search different threads in xda developers forum, you will find many user posting statements not to use ROM manager.
As I do not use ROM manager at all, I did not read the whole posts. That's why I do not exactly know, what the issues are about ROM manager.
(Incompatibility with many ROMs and kernels, but there must be more issues.)
I am using CWM Manager app (included in Chainfire's CF-Root kernel) or CWM5 recovery mode to create a complete system / nandroid backup.
So, in case of an emergency I only have to flash a kernel containing CWM5 recovery and restore my last system backup.
Just to be on the "safe" side, I also copied my efs folder to my external sd card.
And all my apps (+ app data) are under Titanium Backup control.
So, I recommend to use plain CWM recovery backup.
If you are not sure about ROM manager, please search the forums and make up your own mind.
Good luck !
So basically, I can instead of Rom Manager install DarkyROM2 Tool, flash some kernel with CWM support e.g. Hellcat, CF-Root, and boot to recovery and make backup of current rom(with higher compatibility), right?
Sorry if this is obvious, but I have just started with this kind of tweaks...
So first of all, hello
I'm pretty new to this whole universe of custom roms, rooting etc.
My main problem is that I tried to install a custom rom (2 to be exact,
http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
and http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864)
So, the whole rooting process was on this side:
http://www.techverse.net/root-samsung-galaxy-s3-android-4-3-jellybean/
I did everything and it worked like a charm
now I wasn't really sure about the crossfire recovery so I wanted to get cwm (because I had that one on my s2)
I downloaded it here:
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
flashed it via odin 3.07 and everything worked fine
now I just wanted to install a custom rom:
Trying to install the cyanogenmod 12 resulted in a status 7 installation aborted error. I figured that this may have something to do with my
cwm version so I left it alone. The bootloop started on this try. I wiped Dalvik, Cache and Data
I thought that the bootloop resulted because I didn't have a single firmware installed so I tried to install a second rom. This time it was Archidroid. The Aroma launcher started, everything started, I chose my stuff etc. The installation began and I thought it would work. I was dead wrong. Some things failed on the installation but it still resulted in a finished message. This didn't help the bootloop tho. I made a factory reset, wiped dalvik, wiped cache and data, but nothing helped so far.
The only options I haven't tried are restoring my stock firmware and flashing another recovery (most like CF auto root).
Can somebody help me? I should mention that my phone is a samsung galaxy s III gt-I9300
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
TheRuan said:
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
Click to expand...
Click to collapse
I'm about 90% sure that my s3 is the international version (I'm not really sure how to check that)
as for the recovery update option in Archidroid. I'm actually really afraid that the update could somehow damage the recovery. Is it a safe process?