Hi folks.
I attempted to root my S2 a few moments ago with the method in http://forum.xda-developers.com/showthread.php?t=1331784 and everything looked like it was going well. It got to the end of the batchfile and rebooted the phone, only this time nothing came up, just a black screen. Then, I noticed some random pixels on the black screen, only a few, and random colours. Then I noticed more of them appearing slowly, filling the screen. I was confused and watched it in horror for a minute until the whole screen was full and the colours were turning white. I switched off the phone and tried again. No good.
The instructions say to try holding volume up, home and power to turn it on so it starts recovery mode but nothing different happens. I tried download mode and at least that responds.
What are my options? I'm new to all this but having read up I thought I understood it. It seems I was very wrong.
Help!?
Considering that's meant for the Galaxy Note, what zImage did you use with it (assuming you did step 1.2, not-yet-rooted.bat)
I used the one linked, called CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip.
I had seen people posting in the thread that it worked on the SG2 though. Now you mention it I can clearly see the SGN refers to the Galaxy Note. I was feeling reasonably confident about things but now I think I'm either going to scream or cry.
Is there any way I can salvage this?
You mentioned download mode works, so just flash a stock kernel (or CF-Root kernel if that's what you're after anyway) for the correct device as PDA in Odin and hope for the best!
If you do indeed have an I9100 (check before flashing anything else), CF-Root or Official.
Directly flashing a CF-Root kernel in download mode will increment your binary counter though. So probably best to go for stock kernel.
Thank you for your responses.
I have seen the following on that page;
Orange UK ORAKJ4 CSC: *The URL goes here*
(above link modified as I'm a new user)
I'm from the UK and with Orange so I think that's the one, it has the KJ4 in the name too. Do I use Odin for this?
It's a stock kernel you need, not CSC. Carrier branded ROMs/kernels are in a different thread, [ROMS]Official i9100 carrier branded firmware download for Odin Flash. Do you have any idea what your phone was running before? I would hazard a guess that it's actually the BVKJ4 kernel from that thread which would match, based on the one you flashed earlier.
My bad, I didn't see you mentioned Odin in your reply. I'm feeling a bit stressed out and not thinking well. Unfortunately, having looked down the various packages, I'm unsure now which I need. The one I quoted is a "CSC package", whatever that is.
Can you guide me further because I don't know what my old version was originally.
I have looked in the new thread you sent and I think I need the;
Firmware info: PDA:BVKJ4|PHONE:BVKJ4|CSC:ORAKJ4
You are absolutely right, it did start with BV! If I use the branded Orange one I should be back to where I started? Would flashing it increment my counter? It's the least of my worries at the moment, but if there's a way of preventing it, I'm all ears.
Thanks again.
Flashing a stock kernel in Odin should not increase your counter and will hopefully get your device booting again.
If that's the kernel you go for, you should be picking the file Kernel_I9100BVKJ4.tar.md5 (not Kernel_I9100BVKJ4.exe, extract it first) as PDA in Odin. Just make sure your Odin options look like the ones in Intratech's first screenshot in his guide (linked earlier).
Thank you, it's half downloaded at the moment. I'm glad you mentioned having to extract the contents because I'd have tried sending the whole 300mb or so to the phone.
Hopefully then, this will flash ok and I'll be back in business!
I feel very much out of my depth now.
It should only be about 5MB, it's just the stock kernel you need (i.e. the second BVKJ4 link).
Oh, it's finished downloading and I see when extracted it's actually just that one file.
Here we go, fingers crossed...
I saw your post just in time. I have downloaded the stock one, at 5.1mb.
I could have made another horrible mistake if I'd gone ahead with things. I will now attempt to flash the 8mb Kernel_I9100BVKJ4.tar.md5 file from that archive I've just downloaded (the 5mb one).
Have I missed anything?
hollal said:
I will now attempt to flash the 8mb Kernel_I9100BVKJ4.tar.md5 file from that archive I've just downloaded (the 5mb one).
Have I missed anything?
Click to expand...
Click to collapse
I don't think so. Just make sure you follow the instructions from Intratech's thread linked earlier, specifically Flashing Firmware with Odin.
Well, flashing that stock kernel has done wonders. Thank you so very, very much!
I will try to find the thread where I was reading about this zergrush exploit working on this phone. I can only assume I'd read it and read this one after and put the two together by mistake. I don't particularly understand the whole thing which is why I liked the idea of this exploit as it keeps things stock.
I will see if I can find that thread and read it carefully.
I think I'll call it a night now, and get to bed. Thanks again.
You're probably still rooted, since zergRush did its thing earlier, and flashing a kernel shouldn't have changed that. The only thing you did wrong was using a CF-Root kernel (zImage) for a different device. If you'd have used one for the right device, it should have worked fine.
I'm not sure how I'd check for root. I don't have that superuser program available as an app.
You could try running an app which requires root and see if it works, but if you don't see the Superuser app, it seems unlikely it will. Anyway, if you're still feeling up to it, the simplest way to root (in my opinion) is using the same exploit you tried earlier, but from a different thread (and it doesn't come with the risks of using the wrong kernel ;-))
[16/Nov][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v3.0](zergRush Exploit).
Takes about 3 minutes.
I think I've found thread I was reading earlier today...
http://forum.xda-developers.com/showthread.php?t=1321582
What part did the ZergRush affect, if not the kernel? If I use this version, with the correct zImage file if I can find it, then I should be ok second time around.
lol.. the joy of cross posting!
I was going to go to bed but now you've made me want to finish what I started.
Please work....
Related
Hello everyone.
Just a few questions before I attempt to root my GS2. It's my first Android phone and don't have years of experience, and I've done some reading around and am bit confused and would like clarification before I attempt.
First the info. about my phone.
Kernel version is (2.6.35.7-I9100XWKE7-CL2215725)
Build number (GINGERBREAD.XWKE7)
To root the device and because I don't want custom rom for now, I need to follow this guide? http://forum.xda-developers.com/showthread.php?t=1103399
But there are 4 Files which one do I need to use for my phone?
File Type: zip CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip
File Type: zip CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip
File Type: zip CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.zip
File Type: zip CF-Root-SGS2_XW_OJV_KF1-v4.0-CWM4.zip
I Assume it's this: CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip? Once I use that file will I still get the red triangle? Or does that not happen any more?
Also when I got my phone it was sim free and unbranded, do I still need to root it or is there a way to check if the phone is pre rooted too?
Finally before I do anything is there a way to backup the rom and anything else I might need if things go wrong? So i have them from the phone instead of downloading from somewhere.
Thank you very much.
Download the zip file CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip, extract the .tar install it with Odin as PDA, then in the CWM app flash the CF-Root zImage to remove the yellow triangle!
Bingo!
It details it all in that post, just follow the steps!
yes it is the file u have chosen
even if your phone is not carrier locked, it will still be unrooted
just flash cf-root matching the build number of your phone
and u should have a rooted sgs2
cheers
Thanks guys, I now have it rooted.
now for the removal of the triangle.
For my phone I need to find this? (GT-I9100_XWKE7_XXKE4_OXXKE2).
Then unzip and flash with this file? I9100XWKE7_PDA.tar
And flash same as before Odin>PDA>select file>click flash.
If not where can I find the file for step 4 of the guide?
(4) Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)
Click to expand...
Click to collapse
now for the removal of the triangle.
http://forum.xda-developers.com/showthread.php?t=1075278
or us the usb jig method .
http://forum.xda-developers.com/showthread.php?t=1068522
jje
coolfi said:
Thanks guys, I now have it rooted.
now for the removal of the triangle.
For my phone I need to find this? (GT-I9100_XWKE7_XXKE4_OXXKE2).
Then unzip and flash with this file? I9100XWKE7_PDA.tar
And flash same as before Odin>PDA>select file>click flash.
If not where can I find the file for step 4 of the guide?
Click to expand...
Click to collapse
Seriously mate, its on the first page of the development forum... http://forum.xda-developers.com/showthread.php?t=1075278
Find your Kernel there....
Rather than creating a new thread, I'll post here. Got my SII (Vodafone branded, PDA - i9100buke1, Phone - i9100buke1, CSC - i9100vodke2) yesterday, love it, want to root. Had a Desire previously, and thought I had mastered the art of rooting, unrooting, custom roms etc, however, seems the Samsung way is slightly different, a bit daunting if I'm honest, though I guess practice makes perfect! From the main guide, should I be doing anything else in the root procedure due to the fact that my phone is branded. Any advice is much appreciated guys.
This place rocks, thanks for the warm welcome All sorted.
Guess it was paranoia of bricking it more than how hard it actually was.
reudyfam said:
Rather than creating a new thread, I'll post here. Got my SII (Vodafone branded, PDA - i9100buke1, Phone - i9100buke1, CSC - i9100vodke2) yesterday, love it, want to root. Had a Desire previously, and thought I had mastered the art of rooting, unrooting, custom roms etc, however, seems the Samsung way is slightly different, a bit daunting if I'm honest, though I guess practice makes perfect! From the main guide, should I be doing anything else in the root procedure due to the fact that my phone is branded. Any advice is much appreciated guys.
Click to expand...
Click to collapse
Hi don't worry m8 go for it, don't matter if it's branded or not as long as you stick to your kernel version, should be OK.
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Entropy's Thread entitled "[Heimdall][Odin][Stock][Root]UCKH7 Return/Unbrick to Stock (or Root)" is the closest you are going to find to a complete restore to stock.
http://forum.xda-developers.com/showthread.php?t=1286432
I believe this will work for a good majority of folks needing to get back to stock (provided they haven't completely hosed or done something crazy).
Basic steps:
1. Flash the package in the second link of the OP - *NEW* - Kernel + non-rooted system package using either Odin or Heimdall (user's choice - and extract or prepare files accordingly)
2. If the user has accidentally flashed a i9100 International ROM, then they may need to also reflash the stock ATT modem (also in the thread)
3. For good measure, after those items are flashed, probably best to do a factory reset (either via # code or in the UI)
As I mentioned, that should work for 95% of folks that need to go back to stock.
The other 5% are people that flashed a ROM that had new or alternate bootloaders. In this case, I am not aware of any Odin one-click package or bootloader pack available (yet) for the stock ROM, so this may been an issue. But someone may have some more updated information on that.
First settings> privacy> factory data reset.
Then boot into download mode and flash stock plus non root package from here
http://forum.xda-developers.com/showthread.php?t=1286432
With heimdall or Odin
And for anyone who has flashed a different modem you can get the stock modem from the above thread also.
and encase you need to repartition you will need a stock .pit file as well - though as of now as far as I know this is not needed for any reason - non of the roms or kernels in the dev section here in the att xda forums would cause any need for a repartition. Take care with .pit and repartitioning you could end up with a soft brick, a situation that can be recovered from but still not desirable
And if you have flashed anything containing the boot loaders you will need stock boot loaders too, but be very careful with boot loaders as a mistake with boot loaders can result in a hard brick
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Click to expand...
Click to collapse
How to Prepare Your Phone to Return to the Store or for Warranty Replacement
There you go. A nice easy to read guide by creepy. Good work.
Sent from my SAMSUNG-SGH-I777 using XDA App
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Entropy512 said:
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Click to expand...
Click to collapse
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Click to expand...
Click to collapse
did you use the UNROOTED version of the package that he provided?
no, superuser is NOT provided by ATT, for obvious reasons.
dayv said:
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Well there's something interesting. I will retry. I had both on my computer and may have used the wrong one.
so i have the i777 and i rooted using a guide on the android central forum
basically i downloaded kies, odin, cwm, and superoneclick
i put the cwm.tar file through odin, and than ran superoneclick, and i was rooted pretty easily
i than downloaded rom manager and through there i flashed CWM. I tried to make a back up using rom manager but that failed, no biggie i hear other people have the same problem. I boot up into CWM using rom manager and it says stuff like "failed to verify whole file signature"
im not sure if this means i rooted incorrectly?
i made a back up just fine using CWM. However i found out this stuff about flash increments and how i flashed a custom CWM kernal or something (sorry my definitions in this subject are still noob)
i decided i want to get rid of the yellow triangle + i9100 message every boot, no biggie but i am here to learn and i figure might as well if i can. I read a couple threads here and im not sure if this is my answer but i think it is please advise
my plan is to go back completely as if i never rooted and than root by using a stock rom/kernal so i dont get the error triangle message as well as the incorrect international i9100 display
i think this is my solution
"2b.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
* Tested on Linux, should work on Mac OS
* Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
* Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
* Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
* Reboot the phone. Success. You're Rooted.
"
i am under the impression that if i flash the .tar file that is 200+mb (why so big) that i will be RE ROOTED and COMPLETELY stock, therefore no error message and no international thing popping up
also, no more flash counter increments ? << this one is also important as this is one major reason i want to re root
im not really sure but i think that by flashing this new .tar it will over ride my custom.tar file that i do not want any more, i dont know how to get rid of it so this is the only thing i can think of
im worried because i dont know if i have to UNROOT before i install entropys thing or if it will just over ride
thanks so much to any one who can give me advice
Really the best instructions are in creepncrawly's write up on how to return to stock. It covers any question you could have:
http://forum.xda-developers.com/showthread.php?t=1313659
And for doing it right:
http://forum.xda-developers.com/showthread.php?t=1311081
Plus new tools:
http://forum.xda-developers.com/showthread.php?t=1367319
The write ups he does are top notch and should be mandatory reading for first time visitors.
The file is so big because it contains the entire android os.
The issues you're having in cwm sound like clockworkmod needs to be reflashed.
The triangle will be removed simply by the stock kernel being replaced. The flash counter as of now can only be reset by a usb jig ~ less than $10.
Though a few have reported returning the phone for warranty issues and they did not check the flash counter.
The only way the flash counter is tripped is by using pc Odin to flash a non stock kernel.
Sent from my páhhōniē
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
There's a stock plus root package. One of the best ways to root in my opinion.
Root means installing SuperUser.apk, su, and busybox. That's it. The stock + root package has those already included, but also gives you the bone stock kernel.
You install a custom kernel to, among other things, get ClockworkMod Recovery.
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
in reality, 'rooting' your phone is nothing more than placing 2 files on the /system (only one is really needed, since you can download Superuser from the market)
what happens is this:
android version release (say 2.3.5)
extremely smart people find way to exploit a memory hole in the OS, and create a 'rooting' method. what this method does is exploit that hole, which allows for a 'temp root' while it injects the needed files for root
needed files for root:
/system/bin/su <- this is the binary that allows you to retain root access
/system/app/Superuser.apk
without root access, /system is a read-only partition. utilizing the exploit, it will create temp root, then remount the /system partition as read/write, allowing your rooting tool to inject the required files into /system
rooting actually has nothing to do with the device at a true hardware level. it is all within the OS itself. anything outside the OS (recovery, boot, bootloaders, etc) dont get 'rooted' because root is only access to the /system within the OS
samsungs have this awesome ability to be easily rooted via CWM. its extremely easy with ODIN or heimdall to flash recovery/new kernel with recovery built in, and use a cwm zip file to inject the needed files into /system rather than relying on an exploit to do it for you.
its a common misconception that i hate to see when people associate rooting with access to anything outside the OS itself.
'i am having problems flashing this rom/kernel/mod in cwm'
'are you sure you are rooted? try re-rooting'
asinine logic...to say the least
^^
That needs to be stickied in every android forum on xda.
Sent from my páhhōniē
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
DroidBehavior said:
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
Click to expand...
Click to collapse
Sounds like you still have reading to do. And kudos to you for taking what they said as constructive criticism.
The flash counter can only be reset by a usb jig. Mobile Tech videos make some very good quality ones.
The delay from the home button is due to the vlingo app shortcut being tied to the home button (double tap home button) so it's waiting to see if you hit it twice before it takes you to the home screen. Cusom roms remove the vlingo app from being there which helps cut down on the delay.
But you may notice it more since what you did. And you should. By adding cwm you likely flashed Entropy512's kernel. Which is an awesome kernel. One of the ways that kernel helps battery life is by setting the cpu govener to conservative. It slows the cpu from jumping too high too quick. That explains why you may have not noticed the delay before you did anything. As well as the delay from unlocking the phone.
For me the extra battery life is worth it. If you don't like the delay one of the easier ways to set it back to ondemand (stock) is to use the app SetCpu:
https://market.android.com/details?id=com.mhuang.overclocking&hl=en
Hope that explains everything.
Sent from my páhhōniē
yeah that makes perfect sense thanks for the explanation
right now i installed miui and i ****ing love it! the interface is so smooth and sexy its like iphone spliced with android
minimalistic ftw
the interface was so much smoother i ran quadrant but the score was the same heh, but still its impressively smooth
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
So...
I was asked to root a Samsung Galaxy S II i9100 the other day...
I got the person to back up all of their stuff through Kies and then they bought the phone back to me to try and root.
(Why do they want to root it? To remove the noise on the camera when capturing video - I believe this will help narrow down which version it is..)
I managed to download and install a Siyah version, through Odin, and i have the CWM recovery mode, and also the Download mode available.
When i boot up the phone, it comes up to the Yellow triangle image, and no further...
I thought it was a pretty simple task, clearly i have messed up and not realised the extent of the process - i am clearly missing something out - or downloading the wrong things... Should i be downloading a different version - i can't find what files i should have already - and i don't know how i would be able to download apps to the phone now it's only on recovery mode...
I understand everyone asks these and you direct them to other previous threads, but i've doubted myself on everything i've done up to now, so could anyone clarify the correct steps i should be taking?
I believe the phone was on 2.3.3 before my attempted root, but i don't personally have any other details of the phone....
I don't even mind if i can't root it, but if i could possibly revert it back to stock i would be equally happy as we currently have an unusable phone.. (I don't think it's bricked is it?)
Thanks in advance,
Tom.
MrTommo said:
So...
I was asked to root a Samsung Galaxy S II i9100 the other day...
I got the person to back up all of their stuff through Kies and then they bought the phone back to me to try and root.
(Why do they want to root it? To remove the noise on the camera when capturing video - I believe this will help narrow down which version it is..)
I managed to download and install a Siyah version, through Odin, and i have the CWM recovery mode, and also the Download mode available.
When i boot up the phone, it comes up to the Yellow triangle image, and no further...
I thought it was a pretty simple task, clearly i have messed up and not realised the extent of the process - i am clearly missing something out - or downloading the wrong things... Should i be downloading a different version - i can't find what files i should have already - and i don't know how i would be able to download apps to the phone now it's only on recovery mode...
I understand everyone asks these and you direct them to other previous threads, but i've doubted myself on everything i've done up to now, so could anyone clarify the correct steps i should be taking?
I believe the phone was on 2.3.3 before my attempted root, but i don't personally have any other details of the phone....
I don't even mind if i can't root it, but if i could possibly revert it back to stock i would be equally happy as we currently have an unusable phone.. (I don't think it's bricked is it?)
Thanks in advance,
Tom.
Click to expand...
Click to collapse
If you are still able to access cwm and download mode I am pretty sure that you are not bricked(but still there is always a small probability) so I recommend you flash a stock rom via Odin, read lots because I have read of an old siyah kernel which has the brick bug, be careful with ics stock as well.
For all the above recommended matters there are hundreds of threads with extensive details.
For Rooting read several threads and choose the easiest method.
Sent from my GT-I9100 using xda app-developers app
Somebody correct me if I'm wrong, but as far as I know, the kernel you flashed ( siyah ) is not compatible with gingerbread....
So as another poster commented, flashing a firmware in Odin will be the easiest way to recover. Then you can try rooting again....
But do your research first....
Afaik. ...rooting methods for gingerbread are "not prolific". It might be advisable to flash 4.0.3 ics or 4.1.2 jellybean and then root that........
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Why did you not advice him to update his phone????? You went through all that trouble of using KIES to backup and you didn't update the phone?
A firmeware update might have already solved his problems.
And how could you not read that the flashed Kernel does not support such an old Android version. Rooting has a possibility to cause your phone harm, so it should come naturally that you inform yourself on the topic and double check everything in order to minimze the risks.
I am really sorry for what I wrote, but I just can't understand such a mentality!