Hi all,
I expect to receive my new SGSII in the next few days, but want to make sure that I have a full backup concept in place, so that I can always get back to a state that I want.
At the moment I am not too concerned with custom ROMs, just the abaility to Backup the state of my own device, and then bviously be able to restore it later.
My current intention is the following,
1) Get SGSII
2) Perform root as per thread- http://forum.xda-developers.com/showthread.php?t=1056334&page=1' by Chainfire.
3) Then install 'Titanium Backup Root' (To be able to backup application settings, and freexe apps where necessary)
4) Install ROM Manager from ClockWorkMOD.
5) Flash ClockWorkMOD Recovery(requires Custom Recovery image to have been developed by ClockWorkMOD devs).
6) From Custom Recovery select Nandroid and created backup.
7) Then if needed repeat step 5 then perform Nandroid Restore.
My concern is regarding Step 5. As I read it someone needs to have written a custom recovery image for SGSII for this step to be possible. Does anyone know if a custom recovery image exists in ClockWorkMOD for SGSII? Or whether one is likely to come soon?
Secondly, is a better option to use SPRecovery and Nandroid backup\restore, or does this have the same Custom recovery image problem?
p.s. Does ClockWorkMOD Custom Recovery image replace the standard recovery image, or is it possible to backup this up somehow, so that I can always get back to the factory default.
Thanks
link does not work
AaronUK said:
link does not work
Click to expand...
Click to collapse
Fixed link, sorry about that
Clockworkmod will come soon. But the kernel devs need the full kernel sources, which have not yet been released. Once they are out work on adding clockworkmod will begin. I would say 2-3 Weeks max before clockworkmod.
My concern is regarding Step 5. As I read it someone needs to have written a custom recovery image for SGSII for this step to be possible. Does anyone know if a custom recovery image exists in ClockWorkMOD for SGSII? Or whether one is likely to come soon?
Secondly, is a better option to use SPRecovery and Nandroid backup\restore, or does this have the same Custom recovery image problem?
p.s. Does ClockWorkMOD Custom Recovery image replace the standard recovery image, or is it possible to backup this up somehow, so that I can always get back to the factory default.
Click to expand...
Click to collapse
Unlike what some people say, you don't actually need kernel source to make a kernel with CWM. It is by no means easy, and not always possible to do, but usually it's possible (the SGS2 kernels are weird, though).
There is no kernel with CWM yet. But I expect it won't take long. I'll probably get started on one as soon as I have an SGS2 myself (3 more weeks from now at least) - assuming I have time at that point. I won't even try before I have the device myself, too much things need to be tweaked / adjusted / tested for CWM.
Any decent recovery needs a custom kernel, SPRecovery, CWM, something homegrown, it's all the same A recovery tool needs to be in the kernel's file system to work perfectly. It can be done outside of the kernel's file system, but it'd be less reliable.
I'm saying kernel here instead of recovery image, because on previous Galaxy devices they are the same thing, unlike some other brands of Android devices. I'm not sure if it is the same thing with the SGS2 (yet), but so far I assume so (I have no reason to believe otherwise so far). In this case, it is usually not possible to actually backup your original recovery image, because you need root for this. But to get root, you need to flash a custom kernel. Do you see the cyclic reference? Luckily, we have the flash binaries for a fair number of firmwares, so it's possible you will actually be able to download your original recovery image and/or kernel.
Thanks for the clear explanation Chainfire, and for all the'Root' work thus far
Thanks for the explanation Chainfire, but I have a question. Is it safe now to root it before having the CWM? I mean can we restore the phone if we do something wrong and the phone comes to brick? It's the first time I use Android so I'll have many questions
In such a case you download a full firmware and flash that ...
i was wondering how i can backup firmware before rooting but now it clear that i don't need to as one can download and flash the full original firmware. Thanks for the info chainfire.
Chainfire said:
I'm saying kernel here instead of recovery image, because on previous Galaxy devices they are the same thing, unlike some other brands of Android devices. I'm not sure if it is the same thing with the SGS2 (yet), but so far I assume so (I have no reason to believe otherwise so far).
Click to expand...
Click to collapse
Checking the .PIT file, RECOVERY is blank which 99.9% means that the kernel and recovery are the same thing.
Unlike the SGS1 though, FACTORYFS and DATA seem to be two seperate images, which seems strange, since in the SGS1 data.img was inside factoryfs.img and was copied across whenever /data was blank. This might/might not have implications for custom roms.
Related
I have been reading all the threads for several days. It may be a dumb question. But I am really curious if we can do everything only with stock 1.1 recovery since CWM .8 does not update bootloader and bring potential danger to soft-brick your gTab when future 3991 based builds include the new bootloader from VS. As far as I have found, flashing a ROM or kernel does not necessarily need CWM to do it. But with CWM we can do data wiping, which stock recovery is not able to. Calkulin posted a Format_All.zip file in his thread. It can do a wipe. I guess it works with CWM just like flashing any ROM or update. But I am not sure if I can use stock recovery to flash it to do a data wipe. Or does anyone know a good way to wipe/format data with only stock recovery?
Of course, one can use stock recovery to flash safely while use CWM to wipe the data. It is just because I am lazy and want to stick with stock recovery.
This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).
This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.
I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.
In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.
roebeet said:
This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).
This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.
I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.
In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.
Click to expand...
Click to collapse
Thanks a lot, Roebeet! for everything you have done for this community. I have saved your "recovery pack".
Can Standard Recovery update kernels as well?
vegeetz said:
Can Standard Recovery update kernels as well?
Click to expand...
Click to collapse
I think so,TMK. Just rename the whatever kernal.zip to "update.zip" and add recovery folder with command file in it and flash .....
Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.
Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.
vegeetz said:
Can Standard Recovery update kernels as well?
Click to expand...
Click to collapse
Check with the developer - if they say "clockworkmod only" then you should follow their instructions, imo. My guess is that they only test with cwm, but that's only a guess.
vegeetz said:
Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.
Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.
Click to expand...
Click to collapse
I will probably go with Calkulin's 1.1 and clemsen v6. It looks Calkulin's one is the fastesd so far.
roebeet said:
I also create a standalone package if you wanted to add it to a 1.1-based rooted mod.
Click to expand...
Click to collapse
Roebeet
Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.
Rumbleweed said:
Roebeet
Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1005080
samsung s3 gt i9300 16gb 4.1.2 xxemb2
i am going to follow this guide to root (the basic one u can find in stickies things )
Step 1. Download Odin3.07 from HERE
Step 2. Power off your Galaxy S3. Then hold down Volume Down, Center Home, and Power buttons together until you see the warning screen.
Step 3. Hit Volume Up button to enter Download mode and connect a microUSB cable from your Galaxy S3 to your computer.
Step 4. Next, download GalaxyS3RootNew.zip, unzip the files and run odin3.07.exe by double-clicking on the file.
Step 5. When ODIN program opens, you should find a highlighted yellow box with a random COM number. If you don’t see this, download and install Samsung USB drivers below:
SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Step 6. DO NOT TOUCH ANYTHING ELSE, hit “PDA” button and select the file CF-Root-SGS3-v6.4.tar.
Step 7. Hit “Start” button. This will install ClockworkMod Recovery on your Galaxy S3 i9300. If you get stuck on this step, just try a different USB port.
Step 8. Once ODIN is done flashing, you will see “PASS!” in green highlighted box.
Step 9. Your Galaxy S3 will reboot once into CWM Recovery and automatically install root and Superuser app.
Step 10. Once your phone reboots, you will find an app called “SuperSU”, this is your superuser app.
Step 11. Download and install Titanium Backup app from Play Store to verify you have root, a Superuser request window should pop up.
my questions are : do i need an external memoory card to root ( i have 3GB free space left)
whats the difference bitween CF-root and CF-autoroot ??
THANKS IN ADVANCE
Hey.
No, you don't need any external card to use root. About 10 MB on your internal card should be fine .
CF-AutoRoot isn't same as CF-Root. If you're not going to change your rom/kernel/recovery/etc and you just want to have your stock rom rooted then CF-AutoRoot suits you best. However, if you want to change your rom/kernel/recovery/etc in future then it's highly advised to use CF-Root which basicly roots your phone and installs custom recovery CWM 5.5 afaik.
If you want to choose second option then I'd recommend flashing modern recovery, for example PhilZ Touch, TWRP or even CWM 6.0.3.0. In fact it won't root your phone but most of the "cooked" roms are already rooted so you just need to reflash rom later or use AutoRoot described above. You can also flash CF-Root and then custom recovery, basicly you don't even need any other recovery than CF-Root but it's highly recommended to do so.
can u please give me the advantages of custom roms in breef , why would i need them for ? all what im thinking about right now is Adblocker and such things ..
and can i use CF root without installing a ROM for the moment ?? thx a lot
and i didnt understand a word in this paragraph
"If you want to choose second option then I'd recommend flashing modern recovery, for example PhilZ Touch, TWRP or even CWM 6.0.3.0. In fact it won't root your phone but most of the "cooked" roms are already rooted so you just need to reflash rom later or use AutoRoot described above. You can also flash CF-Root and then custom recovery, basicly you don't even need any other recovery than CF-Root but it's highly recommended to do so."
what is PhilzTouch ???
By the sound of things I would just root for now for the adblocking and then start reading like mad and getting familiar with all the terminology and methodology before going any further.....this is the bit so many people miss and hence end up with a very expensive paper weight and a lot of disappointment and heartache
Basicly "cooked" roms have newest firmware versions, many tweaks, optimization and many things which full stock roms are missing. I'm not going to list all these things, check yourself if you wish.
@2
There are two ways to "flash" software to your device. Using USB cable and computer (via Odin) or directly from recovery. To do so directly from recovery you need custom (non-stock) recovery which gives you an option to do so. CF-AutoRoot gives you root while CF-Root gives you root + old CWM 5.5 recovery (because CF isn't supporting this method anymore). So basicly if you want to have a great time with your device, flash different roms etc. then you can directly flash modern recovery through odin f.e. PhilZ Touch Recovery without needing to use CF-Root.
All i want now is to have a rooted device on stock .. then i will take my time and read if i wanna add ROM/kernel
what do u think i should do
CF-AutoRoot. Best, easiest and nice solution for rooting full stock rom. You don't need anything else if you're not going to change roms/kernels or whatever.
Just a note that you may want to use the thanks button....it's kind of traditional courtesy when asking for help and receiving it
R: just two little small questions about root
JustArchi said:
CF-AutoRoot. Best, easiest and nice solution for rooting full stock rom. You don't need anything else if you're not going to change roms/kernels or whatever.
Click to expand...
Click to collapse
Actually i would suggest the op also get a cuatom recovery into his phone.
Cuz if he f*** up his phone real bad and doesnt have a pc with him (cuz otherwise you would have to use odin to flash, or odin mobile from phone but if ure phone doesnt work, u cant) he can still fix things thru recovery.
Other things recoveries are for is making NANDROID BACKUPS. basically an almost total backup of your phone data: it backups rom, kernel , apps and their data, modem, system cache a bunch of technical stuff.
It doesnt backup other files of course (such as music on ur phone or videos or documents) just what is necessary to make the phone run with ur apps.
The reason this backup is important is because if you f*** up your phone real bad (again, phone can be tricky to hande) you can just flash it clean (you internal phone storage, such as music or any folder which doesnt concern rom, or microsd stuff, wont be touched when you choose "factory reset" in custom recovery)
And restore from a backup when your phone was working. Then u reboot and voila, a trip back into the past!
Might i suggest you also backup the efs folder which is found in the root directory. Nandroids DO NOT cover that. And basically for an s3, if you've got root and internal components are not damaged, if youve got the efs you can fix anything....if ya dont - not so much.
Might suggest once more that IF YOU DONT CARE about all this 'faster roms' kernels and mumbo jumbo root stuff, you still flash a recovery: the most stable one is CWM (clockworkmod recovery). To get it just boot into ur rooted phone, install free app from store "rom manager" and install latest version of recovery. you can boot into phone recovery at ANY GIVEN TIME, just follow instructions u can find on google, pressing buttons at same time and ****.
If ure curious, other recoveries exist:
Clockworkmod touch(premium):it's basically cwm just that it's touch. If you want my point of view...having touch on recovery is stupid and useless...recoveries are for fixin or doing important stuff, you dont wanna mess everything up cuz u touched the screen for mistake. Much better to use buttons and be sure.
Twrp...whatever cant remember da name: same thing as cwm touch, only .......i dunno but cwm is better.
Philz Touch(now this is the real ****!):not stable as cwm. It's a mod of cwm with MANY added cool features such as aroma file browser within the rom and look changing and of course touch( all toucb/double tap touch/touch only for scrolling) but the BEST option is BACKUP COMPRESSION. This little guy made me earn 1gb of free-er space out of my nandroid backups i perform onto my microsd. I went fron 3.5gigs to 2.5gigs. Awesome! Plus you can skip md5 checksum...which is a safety thing of course...but it slows down the backup/restore process, for the most daring disabling it spares them some waiting (nandroids are faster than kies from the pc anyways, no more than 20mins guaranteed!).
If ure interested about kernels i suggest:
Siyah kernel (or syiah...never know which)
Perseus kernel.
They both are good and fast, syiah is more performance, but you can get just the same performance on perseus if you handle the tweaking well and yiu get more battery time.
If youre interested about roms:
Foxhound (most complete one for the s3 i believe, it's packing all you need, and of course it's faster than stock samsung rom)
Rootbox(light rom. Its got less features but still fully packed for speed)
Omega (never tried it. Still have to...but it looks like in this rom look-costumization of look is the easiest thing to do. But i believe foxhound to be fully customizable as well...)
others are also
Jellybam
ResurrectionRemix
Hope i helped you get some root **** together
Sent from my GT-I9300 using xda app-developers app
I totally agree with your point of view but I've been using PhilZ Touch for about a few months now, flashing stuff, making backups and having fun about 1 time per day. Don't call this masterpiece "unstable" because it's based on latest CWM and without any "unstable" thing . I haven't got any problem with that recovery since 4.01 or so.
JustArchi said:
I totally agree with your point of view but I've been using PhilZ Touch for about a few months now, flashing stuff, making backups and having fun about 1 time per day. Don't call this masterpiece "unstable" because it's based on latest CWM and without any "unstable" thing . I haven't got any problem with that recovery since 4.01 or so.
Click to expand...
Click to collapse
Totally agree, never had a problem with it
R: just two little small questions about root
JustArchi said:
I totally agree with your point of view but I've been using PhilZ Touch for about a few months now, flashing stuff, making backups and having fun about 1 time per day. Don't call this masterpiece "unstable" because it's based on latest CWM and without any "unstable" thing . I haven't got any problem with that recovery since 4.01 or so.
Click to expand...
Click to collapse
Impossible, much less than a month ago there was a versione of the recovery (4.8.8.1 i think) in which it did not save any of the recovery settings i had changed, cuz when i rebooted into recovery for backup/restore stuff i had to keep reenabling some features (like max compression, save to excard ecc ecc). Then there was an update (and they changed selection menu to [x] kinda like thing, if u boot into it now u see md5 checksum if enabled has an x) and the recovery rememberes all settings now (all interface tweaks amd stuff).
that's what i meant for unstable, also cuz rom manager doesnt recognize updated version of clockwork...but thats another story.
Thou i do think philz is a masterpiece, but its missing some stuff...for example aroma file manager needs to be included into the recovery already, also it needs its own updating app, also aroma file manager is a bit too low on features for me. like...if im gonna move some pixtures from a folder i wanna see them first...and if my rom isnt working i cant do that with aroma..
Sent from my GT-I9300 using xda app-developers app
Thanks a lottr guyysss especially u killbubble u really helped me im gona ask u for one more favor
U said install rom manager on ur rooted phone and install CWM (so i guess i should root with CF root rightt???)
And if i chose Philz how can i really get it on my phone ?? Will i find it in Rom manager also??
Thanks in advancee!
killbubble said:
Impossible, much less than a month ago there was a versione of the recovery (4.8.8.1 i think) in which it did not save any of the recovery settings i had changed, cuz when i rebooted into recovery for backup/restore stuff i had to keep reenabling some features (like max compression, save to excard ecc ecc). Then there was an update (and they changed selection menu to [x] kinda like thing, if u boot into it now u see md5 checksum if enabled has an x) and the recovery rememberes all settings now (all interface tweaks amd stuff).
that's what i meant for unstable, also cuz rom manager doesnt recognize updated version of clockwork...but thats another story.
Thou i do think philz is a masterpiece, but its missing some stuff...for example aroma file manager needs to be included into the recovery already, also it needs its own updating app, also aroma file manager is a bit too low on features for me. like...if im gonna move some pixtures from a folder i wanna see them first...and if my rom isnt working i cant do that with aroma..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
4.89.4 (14.03.2013)
- New Custom Install Zip mode: set a default folder to start with + browse backward up to the root
4.88.5
- toggle menus are now formatted to device screen width (right align menu option)
- add 30mn timezone offset
- merge CM 10.1 commit: Fix segfault with dead symlinks in char** gather_files()
- add extra check for carriage return for get_rom_name function: ensures windobe noobs do not get stuck
4.88.2
- fix: ors backup could overwrite an existing folder and end up with mixed old/new backup images
Click to expand...
Click to collapse
Impossible, Phil would include it in his changelog . Also I know what you're talking about, it happens when there isn't a folder clockworkmod on /sdcard , sometimes you need to create it manualy but how often do you format /sdcard anyway? Recovery restores it after reboot anyway.
Also autoupdate from one point of view is a nice feature, I totally agree with that but on the other hand it would require many more things included in the recovery because itself it doesn't support many options, that's why it's called recovery, not a software . Personally I prefer having an option to choose, newer version isn't always better, usually yes, but not always . Also recovery just need to "work", flash roms, make backups and eventually some simple other tasks. I don't need anything else .
Just archi can u help me with My question please?? thank u so much
georgeskhater said:
Just archi can u help me with My question please?? thank u so much
Click to expand...
Click to collapse
Root using auto root, then use mobile Odin to flash recovery.img
Or
Root with cf root then just flash Phil's with the cwm recovery that comes with cf root
georgeskhater said:
Thanks a lottr guyysss especially u killbubble u really helped me im gona ask u for one more favor
U said install rom manager on ur rooted phone and install CWM (so i guess i should root with CF root rightt???)
And if i chose Philz how can i really get it on my phone ?? Will i find it in Rom manager also??
Thanks in advancee!
Click to expand...
Click to collapse
Doesnt really matter how u root as pong as u do. Once u do run rom manager and update clockworkmod (cuz if u rooted the otherway cwm is probab uoutdated).
If u chose philz just google philz and find the thread (gonna be first on google, if not google philz recovery)
Read the thread well and find i9300 version (best if u choose .zip version flashable with cwm, if not u gotta use tar.gz flashable thru odin) then put it on phone and in recovery flash dat pakage. Then reboot recovery and make sure u configure philz to your liking.
no philz is not included in rom manager.
Rom manager is a weird name, since it's only of use to update to the latest version of cwm, or install it if you still have stock. Thou it does have a list where u can download roms...i dont recommend it cuz it suks..much better for this is goo manager.
But i prefer googling the rom or recovery (if cwm, i would use the app of course) or whatever and downloaing it from source, much safer and has full instructions (needed for some stuff, for example if a rom needs latest gapps cuz not included, apps like rom manager would not tell ya).
Glad to help, if u wanna thank just hit the :thumbup: button...
Sent from my GT-I9300 using xda app-developers app
Yeah, I don't recommend tools like Rom Manager as well. It's not bad of course but some kind of useless, in my honest opinion at least.
P.S. Like I said if you're going to change rom then you don't need ANY CF-Root, just flash PhilZ (or clean CWM) through odin then flash any pre-rooted rom. CF-Root isn't required here, only if you're not going to change rom, then use cf-autoroot.
I've beeing trying to change my ROM. I'm trying to install Clockworks recovery and it doesn't work. I've tried using Rom Manager, EZ recovery and doing it manually. Each time it just goes into the default recovery. I've also tried twrp. Any help?
GT-I9200T
Andriod version: 4.1.2
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
MistahBungle said:
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
Click to expand...
Click to collapse
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Also what about Rom Toolbox? Will that be bad aswell?
AcademyA said:
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Click to expand...
Click to collapse
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
MistahBungle said:
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
Click to expand...
Click to collapse
When finding the Kernel code, I type in getprop in terminal. I see stuff like the build number but I can't find the Kernel code anywhere. The only thing I see that is related to Kernel is ro.kernel.qemu: [0]
What are you doing in terminal ? You're overthinking this. I realise it's in the thread, but that's completely unnecessary nonsense
Phone settings/about device - build number.
My final post to this thread. You're on your own.
Alright! Everything's working now. Thanks for the help.
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options. It is also relevant to know just how much information you want to recover.
File replacement:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- will retain all existing data & customization. Maybe worth a try, but I don't recommend it
Dirty-flash:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You will be able to flash a (custom) samsung-based firmware, which WILL overwrite /system, but will NOT overwrite your /data partition, likely allowing you to boot and properly back-up the stuff you want to keep, or even create a nandroid of the existing setup. <-- Will retain all existing data, will lose /system customisations. I have used this method.
Start-fresh:
Use desktop-Odin to flash the official firmware may be your only other option, which will retain everything in internal memory (photos, downloads, music, nandroid backups), but not messages, or any app data.
-Cyril
Mr. Barker said:
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
Click to expand...
Click to collapse
cyril279 said:
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options.
Click to expand...
Click to collapse
Well I do have CWM installed, but am curiously (and annoyingly) unable to boot to it now, for whatever reason. It boots to stock recovery instead, every time.
cyril279 said:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- maybe worth a try, but I don't recommend it
Click to expand...
Click to collapse
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Mr. Barker said:
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Click to expand...
Click to collapse
I would be glad to provide more detailed information, but I prefer to do so from a desktop computer, and I won't be near one for several days, so this may be a slow process unless one of our peers steps in to help.
In the meantime, you should gather:
-Odin 1.85 or 3.07
-A Siyah s2-v5.x or s2-v6.x .tar.md5 kernel (for the i777 or i9100)
The latter you can find at http://www.gokhanmoral.com
I will outline the process in a later post, explaining the purpose of each step.
Sure, I'm OK waiting a few days. I appreciate the help, I haven't done any flashing in quite some time and don't want to make a mistake, especially with all the important data that's at stake.
Thanks.
File Replacement Method
1) Use desktop Odin to flash Siyah kernel
-Installs a kernel that will allow you to perform a nandroid backup, and MAY allow you to adb push the missing file to the device.
-This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
-If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Adb push missing file to /data/path_file_belongs
5) Shell chmod XXX the missing file
-to correct file permissions; that 0.xml file has -rw------ on my device, which translates to 600 (I think)
6) Flash appropriate ajk kernel
-for stock jb, use "NoSwap" http://forum.xda-developers.com/showthread.php?t=2110542
-custom kernel that will boot stock rooted android.
7) Attempt Reboot into android
-If successful, reboot to recovery and perform another backup.
-If not successful, then we use a different method.
This is the trickier method of the three, but will retain all customization if it works. I have not tried it, and we're assuming that the missing file is actually the problem.
Please be sure that you are comfortable with all of the steps before attempting any of them. I will be able to provide step by step instructions, but not for several days.
Happy flashing,
-Cyril
Well, that was fun. Followed the instructions to a "t" and even learned some things. But, sadly, did not achieve the results I'd hoped for.
I was indeed able to push the wallpaper file over to data\system\users\0 and CHMOD it. But after flashing AJK "NoSwap" the phone shows the "Android is upgrading..." message, with "Starting apps." trying to process. But it doesn't. The little circle swirls a bit, then the screen goes black. The "Starting apps." message appears again, then the screen goes black again. And then it repeats this cycle forever. I eventually got irritated and yanked the battery.
So... *sigh*... what's my next best option?
The Nandroid backup completed successfully? If so, that's great, any APP customization is likely captured in the backup. How well they will restore is a different concern, but we need to get the device booted completely into android first.
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
cyril279 said:
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
Click to expand...
Click to collapse
I say wipe caches and fix permissions first. If that doesn't work format /system, and install a ROM of the same version of android.
After that if it's still not booting suck it up do a full wipe and start from scratch.
Sent from my SGH-S959G
@Mr. Barker
If the cache wipes / permissions fix doesn't help, then our next attempt is:
**this assumes that you were running stock Android 4.1.2 when the trouble began**
get i777UCMD8 cooked v2.2 onto a flashdrive, (or prepare it for sideload)
reboot to recovery
format /system
install cooked v2.2
attempt to boot into android
OK, I'll give it a try, thanks.
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM is needlessly flashy.
Mr. Barker said:
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the black notification pull-down menu? This ROM sets it transparent by default, which doesn't work for me.
Click to expand...
Click to collapse
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
To change the notification background go to the mods section of the installer, and just install the black notification background.
Sent from my SGH-S959G
mr-cook said:
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
Click to expand...
Click to collapse
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
"needlessly flashy"
Simply asking 'how to change the icon' is sufficient, and inherently implies that you prefer something different.
Cooked v2.2 is definitely quicker than stock;
The premise of both cooked and shostock are that they have taken the stock firmware, and stripped it down of unnecessary junk, and run it over a well-optimized kernel for the best touchwiz experience that you could possibly have on this device.
If your firmware desires are different than what cooked v2.2 provides, then I suggest creating a nandroid backup, wiping /system, and giving shostock a try. It's the other touchwiz favorite for the i777, packaged with a different very good kernel, and also runs quicker than stock.
Mr. Barker said:
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
Click to expand...
Click to collapse
To close the loop, now your initial boot screen is a yellow triangle with an exclamation point? It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
Summary:
Nandroid-backup desired setup
Flash official stock-firmware to the device via Desktop-Odin (clears the warning)
Root & recovery via Framaroot/Mobile-Odin (a method that does NOT trip the custom-flash monitor)
Restore nandroid to return to the established custom setup
Procedure:
gather onto internal memory, or micro-sd:
-Framaroot
-Mobile Odin APK
-Mobile Odin flash kernel for i777
-Boot.img (extracted from your chosen firmware.zip)
boot to recovery
perform nandroid backup
^^ this MUST complete successfully
perform factory reset
boot to download mode
flash official UCMD8 using Desktop ODIN
^^ clears the custom-flash warning
install and use framaroot
^^ uses an exploit to establish and manage root access
install mobile Odin and the mobile Odin flash-kernel
^^ the method that will NOT trip the custom-flash monitor
flash the boot.img via Mobile Odin
^^ flashes the kernel and recovery of the firmware that you are going to restore
boot to recovery
restore nandroid backup
enjoy
-Cyril
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup? Or could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards) My point is, are nandroid backups firmware-specific?
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Before all this I've never flashed anything but stock firmware, and never had to create nor restore nandroid backups. So most of this is all new to me. But I enjoy the learning process.
Mr. Barker said:
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup?
Click to expand...
Click to collapse
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Edit: As Mentioned below, a CWM nandroid will restore the entire backed-up firmware installation, which can be done over ANY firmware.
If the goal is to keep your App data across different firmwares, then a Titanium backup restoration may be what you're after. /Edit
Mr. Barker said:
[...]could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards)[...]
Click to expand...
Click to collapse
I don't think that the stock recovery allows to restore nandroid backups at all. The restrictive nature of the stock recovery is one of the more practical reasons to root the device & use a custom kernel.
Mr. Barker said:
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Click to expand...
Click to collapse
Mobile Odin will flash a zImage, no need to rename it. I didn't check to see that shostock or cooked use a zImage instead of boot.img.
cyril279 said:
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Click to expand...
Click to collapse
?? I thought that because a nandroid copied (backup) and then formatted/recopied the 5 partitions (restore), that it didn't matter what firmware you had installed?
Hi, this is my first post. I'm a total noob in customizing phones and since my phone is quite old, all the information I can find is years old, talking about file versions that don't exist anymore, or became outdated since there are so many different versions of android.
I have been trying to find a good guide to help me do the correct steps to follow to flash Cyanogenmod. I might try the latest 12.1, and then see if I like it.
This is what I have so far:
- international i9100, I live in panama if that's relevant to any help I need
- stock ICS 4.0.3 (with XWLP7 kernel)
- used superoneclick to root, it installed CMW PhilZ touch 6.0.1.7 (I think, can't remember the last digit.)
- used "galaxy s unlock" app to unlock the phone
I downloaded this: philz_touch_6.07.1-i9100 from d-h.st/hUX, sorry I can't post the links correctly for being a new user.
I just made a backup before i will attempt to load philz touch 6.07.1. I read that I need to have a kitkat compatible recovery, is this one compatible. Can I simply flash it or do I need to do anything specific before.
I am trying to follow the steps explained in wiki.cyanogenmod.org/w/Install_CM_for_i9100, but the warnings scare me a bit, can someone please explain the workarounds, thanks.
So, what I'd like to know is the specific steps for my version of android to make it migrate to CM12.1, and what to do about the warnings (should i find a custom kernel, do i need to backup anything else, I read also that the recovery I have doesn't backup efs, so how can I do that?)
Thanks a lot for taking your time to help me out.
@milen_506
So when you reboot into recovery, you have philz recovery?
If yes, all you need to do is install a newer recovery such as the one from this post. Once you flash it, reboot straight back to recovery(you will get a bootloop if you try to reboot into the system). This newer recovery is compatible with the latest versions of android and gapps, so just need to have the rom .zip and gapps(if you want play store/services) .zip ready to flash before you upgrade this recovery. Do a nandroid backup before you flash the new rom/gapps
There are several ways to backup efs, HERE is a link to one option
And as far as custom kernels, you are probably better off sticking to the kernel that comes with the rom unless you are comfortable adjusting kernel settings and you know what you are doing. It would be easy to mess things up if you didin't have a basic knowledge of the changes. Also with cm12/LP roms on the S2, custom kernels are only starting to be developed and are a little unstable for some users at this stage.