Hi guys
Is true that "Rom manager" has problems with CF-Root?
By the way, how can I get an insecure-kernel for XWKI4?
Thank you all for your help.
1) Yep. Do not use Rom Manager & CW together on SGS2. One or the other. Rom Manager has a tendency to break CW & cause bootloops. Some people will tell you they use both successfully, but it's just a matter of time. You'll have problems eventually.
2) CFRoot thread.
Thanks MistahBungle,
Your suggestion is to use CFroot and is there any application compatible and similar to the "Rom manager"? CWM is not very user-friendly...
You're welcome
Clockwork Manager app is normally installed when you flash a kernel that has CW Recovery. This performs many of the same functions as Rom Manager. Personally speaking, I always reboot into CWRecovery whenever I do a backup, restore or flash a rom/kernel, because I've never had any problems doing it this way. I don't think there's anything 'un user-friendly' about it at all. It's a case of rebooting, scrolling through & up/down a few screens & pressing a few buttons.
There are obviously ways to root your phone other than CFRoot which don't install CW, up to you if you want to use one of those. Zergrush & SuperOneClick are the two that immediately spring to mind. I can't advise you about those as I've never used either of them/know nothing about them.
Definitus said:
Thanks MistahBungle,
Your suggestion is to use CFroot and is there any application compatible and similar to the "Rom manager"? CWM is not very user-friendly...
Click to expand...
Click to collapse
Hey guys,
I just installed Rom Manager and wanted to try out to make a backup of my current Rom. The Rom Manager asked me if I wanted to Install Clock Mod Recovery, which was kind of strange since I thought I had it installed with the Siyah Kernel 3.3.3d but I proceeded and installed it, and after that it asked my Galaxy Model, I picked Galaxy SII of course and then it rebooted. However after the Galaxy SII Logo (With the yellow Triangle) nothing happened. Black Screen. So I tried to go into Recovery Mode. Doesn`t work either. Normal Boot also doesn`t work any more.
Download Mode is working however.
So I thought to try to flash the Siyah Kernel trough Odin to get it to work the way it was. Should I flash the Kernel or try to flash a normal Firmware through Odin?
Any advice on how to proceed?
Flash the kernel first. Hopefully that fixes things. If it doesn't work, then back to stock, re-root your phone & restore a backup/flash whatever rom you want to use.
Don't use Rom Manager on a phone that has CWM/Recovery installed, it's not uncommon for Rom Manager to break CWM and/or cause bootloops (as you've discovered). I'd freeze/uninstall Rom Manager if you're using a kernel that has CWM/Recovery.
MistahBungle said:
Flash the kernel first. Hopefully that fixes things. If it doesn't work, then back to stock, re-root your phone & restore a backup/flash whatever rom you want to use.
Don't use Rom Manager on a phone that has CWM/Recovery installed, it's not uncommon for Rom Manager to break CWM and/or cause bootloops (as you've discovered). I'd freeze/uninstall Rom Manager if you're using a kernel that has CWM/Recovery.
Click to expand...
Click to collapse
Flashing the Kernel didn`t work, same as before
Going back to Stock ICS Samsung Firmware now and will apply root afterwards. I Just hope that works and that I didn`t brick my phone.
You should be fine, I can't recall seeing any instances of Rom Manager bricking a phone outright when this happens. It's just really annoying that you have to go back to stock/re-root/restore backup/etc. Happened to me when I tried Rom Manager out not long after I got my phone when I was running Miui GB. Pain in the neck but I'd be surprised if you can't fix it ;-)
MistahBungle said:
You should be fine, I can't recall seeing any instances of Rom Manager bricking a phone outright when this happens. It's just really annoying that you have to go back to stock/re-root/restore backup/etc. Happened to me when I tried Rom Manager out not long after I got my phone when I was running Miui GB. Pain in the neck but I'd be surprised if you can't fix it ;-)
Click to expand...
Click to collapse
Ok everything works now again, thanks for the support
Installed Stock ICS 4.0.3 Firmware but then I got stuck at the Galaxy SII Bootanimation.
Then I flashed Chainfire Kernel and got into CWM and then without a full wipe just installed my old rom and it worked. All apps are still there.
One thing I know for sure though, I will never use Rom Manager again
Good news. Not losing your apps & so on certainly saves you a fair bit of time. No probs, happy to help. Yeah, use CWM/Recovery to do all your flashing/backups/restores/etc instead of Rom Manager. Main thing is you recovered fairly easily ;-)
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.