Related
Although I've flashed non-phone devices in the past (routers, PAP2, Ipod classic, etc.) This is the first time I'm going to be flashing a SmartPhone that I've ordered which I should be getting very soon.
I ordered a Samsung Galaxy S II and have been crawling the forum trying to learn all I can before I try rooting and unlocking my phone when I get it. But I'm having trouble deciding on a few things.
Hopefully my question can become a guide for other new people who are just starting off like me.
Rooting:
To begin, I'm trying to figure out what's best for rooting.
I've looked at a few different methods..
Chainfire's direct method: http://forum.xda-developers.com/showthread.php?t=1103399
lyriquidperfection's one-click method: http://forum.xda-developers.com/showthread.php?t=1125414
CLShortFuse's one-click method: http://forum.xda-developers.com/showthread.php?t=803682
LitePro's ROM and Root method all-in-one: http://forum.xda-developers.com/showthread.php?t=1095274
All of these have their own merits. But I'm trying to figure out the best approach for myself.
Although Lightn'ing (LitePro's) looks interesting and I may try that ROM later, for now I want to avoid changing the ROM till I know I like the phone. So I'm looking at the first three choices.
The one that I think I would be able to do easiest is either lyriquidperfection's or CLShortFuse's methods as they both are one-click solutions and I just need to grab the right kernels.
I don't know if there's any reason I would want to go with Chainfire's instead of the two previously mentioned. If there is please let me know.
I asked this question on the respective threads but as of posting haven't gotten an answer of if there's any reason to flash the original kernel back after rooting and if I keep root if I flash it back.
I also don't know much about the use of Jigs to avoid the flash counter going up. Is there any reason I need to worry about the flash counter going up? Is there a limit on number of flashes on a phone?
Unlocking:
For unlocking I looked at:
http://forum.xda-developers.com/showthread.php?t=1092451
However it seems for my specific phone (Virgin/Bell) we use this method as posted in the same thread:
http://forum.xda-developers.com/showthread.php?p=16482293#post16482293
This seems pretty much straight-forward. I just got to root the phone then get and run the app mentioned. Phone will crash/reboot and then no SIM lock.
If there's anything that seems wrong with this let me know please.
Other stuff:
At some stage here I want to be able to back up the stuff on the phone and get other typical tools.
I keep hearing about ClockWorkMod constantly and it seems to be a tool for backing up the phone data and making it easier to flash stuff in without use of ODIN.
I haven't found clear documentation on how I would do this on the SGII specifically.
I also here Titanium backup (sp?) is also a good idea to install at some point.
Is there other apps or otherwise I should be looking into before I start this journey into the wonderful world of hacked smartphones?
-This is a place marker for me making amendments so that later this may be more or less a guide for other beginners-
Dav_Edward said:
Although I've flashed non-phone devices in the past (routers, PAP2, Ipod classic, etc.) This is the first time I'm going to be flashing a SmartPhone that I've ordered which I should be getting very soon.
I ordered a Samsung Galaxy S II and have been crawling the forum trying to learn all I can before I try rooting and unlocking my phone when I get it. But I'm having trouble deciding on a few things.
Hopefully my question can become a guide for other new people who are just starting off like me.
Rooting:
To begin, I'm trying to figure out what's best for rooting.
I've looked at a few different methods..
Chainfire's direct method: http://forum.xda-developers.com/showthread.php?t=1103399
lyriquidperfection's one-click method: http://forum.xda-developers.com/showthread.php?t=1125414
CLShortFuse's one-click method: http://forum.xda-developers.com/showthread.php?t=803682
LitePro's ROM and Root method all-in-one: http://forum.xda-developers.com/showthread.php?t=1095274
All of these have their own merits. But I'm trying to figure out the best approach for myself.
Chainfires simplest method less problems for most .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
I also don't know much about the use of Jigs to avoid the flash counter going up. Is there any reason I need to worry about the flash counter going up? Is there a limit on number of flashes on a phone?
Zero as Samsung will invalidate warranty for custom roms or rooted phones .
Other stuff:
At some stage here I want to be able to back up the stuff on the phone and get other typical tools.
I keep hearing about ClockWorkMod constantly and it seems to be a tool for backing up the phone data and making it easier to flash stuff in without use of ODIN.
I haven't found clear documentation on how I would do this on the SGII specifically.
Their is no documentation its probably written up in the FAQ or Wip but is a relativity simple tool anyway .Backup restore phones rom install custom rom wipe data factory reset reset battery stats to zero .
FAQ
http://forum.xda-developers.com/showthread.php?t=1065995
Wip
http://forum.xda-developers.com/showthread.php?t=1125282
I also here Titanium backup (sp?) is also a good idea to install at some point.
On a rooted phone Titanium pro allows you to back up your apps and also to freeze apps .
jje
Click to expand...
Click to collapse
Thorough stuff, props to you sir - you know search so you'll get your first thanks...
I would advice you to go with Chainfire's method. It's the easiest and most versatile method IMO. Definitely the best for beginners because you keep your stock ROM yet still are rooted and get Clockwork Mod.
The installed CWM (Clockwork Mod) Manager app with Chainfire's work is an easy way to see what it does - basically you can backup and restore your whole system/device, plus flash custom ROM/kernels/themes etc. Look into the flashing part later - baby steps are good here!
Titanium Backup is an excellent backup app for backing up/restoring apps and data, as opposed to the whole system. Buy the Pro version, definitely worth it.
I also like My Backup (also on Market), excellent for backing up contacts/SMS/MMS. The free version is a 30 day trial.
Can't help with unlocking, never needed to - sure others can help.
Good luck
Edit - JJ beat me too it, hadn't seen his post. Must type faster...
@JJEgan & @B3311, thanks for the useful information.
I was going to try those one-click methods because I thought those were the more newbie friendly methods. Thanks for the information to try using Chainfire's instead.
I will try using Chainfire's method instead with your advice when I get the phone. Having the tools like his CWM hopefully will make things easier.
I am a bit concerned though about his mention that Rom Loader won't work with his version of the build. I'd still like the ability to use custom roms down the road once I learn how to properly back up the phone so I can experiment with various roms till I find the one I like most.
Any advice about using rom loader or other possible difficulties using Chainfire's kernel?
Dav_Edward said:
@JJEgan & @B3311, thanks for the useful information.
I was going to try those one-click methods because I thought those were the more newbie friendly methods. Thanks for the information to try using Chainfire's instead.
I will try using Chainfire's method instead with your advice when I get the phone. Having the tools like his CWM hopefully will make things easier.
I am a bit concerned though about his mention that Rom Loader won't work with his version of the build. I'd still like the ability to use custom roms down the road once I learn how to properly back up the phone so I can experiment with various roms till I find the one I like most.
Any advice about using rom loader or other possible difficulties using Chainfire's kernel?
Click to expand...
Click to collapse
Most just put custom rom on sd card and flash via CWM .
Sorry no nothing about Rom Loader .
jje
I would also advice using CF-Root. I was scared of rooting my phone, but after using CF-Root, I don’t know why I was so scared. The process took a little over 30 seconds (I need practice). To me at lease I think it’s the easiest method, you just need to make sure to download the right kernel.
EDIT:
Get a UBS jig, After rooting, I had the "yellow triangle" I turned off phone, removed battery, inserted jig, put back battery, entered download mode, restarted phone and no more "yellow triangle"
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.
hey every1 call me hatcher, soo many pages of info didnt know where to start also, most of you will think im an idiot probably asking simple questions! here goes:
bought my sgs2 and love it to death only had it a week and its on orange , i went ahead and rooted my phone using odin 3 and s2 root. i decided to install an original secure kernel again. all seems good, but i didnt know what kernal was is the best? and is it the whole firmware thing? my current android version is 2.3.4 is this the newest and best because i saw something on the web about ics 4 or something. went onto kies and no update was found so maybe that is the latest official, but then i was confused about it saying u have to root again after ics. so yea if anyone could give me a heads up it will be great.
basically i want my phone rooted but running the latest OFFICIAL version with updates available thanks.
did download the newest kernel on this site but phone didnt boot so reverted and thinking there is more to this, dont want to break my phone!! thanks
also another really random question if any1 can answer does powervr plugin meant to take soo long for loading on shadow guardian for example thanks very much, soory for bad punctuation and grammer my english is not perfect yet
just realised that kernel 4.03 i downloaded is 8 mb and another ics 4.03 was 300 mb! really getting confused about os, firmware kernel etc and dont want to miss anything!
hatchermagic said:
hey every1 call me hatcher, soo many pages of info didnt know where to start also, most of you will think im an idiot probably asking simple questions! here goes:
bought my sgs2 and love it to death only had it a week and its on orange , i went ahead and rooted my phone using odin 3 and s2 root. i decided to install an original secure kernel again. all seems good, but i didnt know what kernal was is the best? and is it the whole firmware thing? my current android version is 2.3.4 is this the newest and best because i saw something on the web about ics 4 or something. went onto kies and no update was found so maybe that is the latest official, but then i was confused about it saying u have to root again after ics. so yea if anyone could give me a heads up it will be great.
basically i want my phone rooted but running the latest OFFICIAL version with updates available thanks.
did download the newest kernel on this site but phone didnt boot so reverted and thinking there is more to this, dont want to break my phone!! thanks
also another really random question if any1 can answer does powervr plugin meant to take soo long for loading on shadow guardian for example thanks very much, soory for bad punctuation and grammer my english is not perfect yet
just realised that kernel 4.03 i downloaded is 8 mb and another ics 4.03 was 300 mb! really getting confused about os, firmware kernel etc and dont want to miss anything!
Click to expand...
Click to collapse
Your latest firmware should be ICS 4.0.3, (you can flash ICS 4.0.4 official/custom rom!) not gingerbread 2.3.4! You can download (after registering!) your "OFFICIAL" firmware/rom from here: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regiona Just choose your region/network/firmware, & then flash with odin 3 again! This will unroot you because you'll be flashing original stock firmware, so you will have to root again with your rooting method of choice! I personally prefer to root using this method: http://forum.xda-developers.com/showthread.php?t=1501719 to just keep the latest OFFICIAL stock rom on my device but still have root! Also, using this method wont give you the yellow triangle on each reboot because you're not flashing a kernel to root your device! If you ever need to put your phone in for repair under warranty & your flash counter in download mode doesn't say "No" (0), then they'll possibly charge you for it, as you've flashed your device ! Use this: http://forum.xda-developers.com/showthread.php?p=22463153#post22463153 to reset it (ONLY FOR USE ON ICS ROMS!!), but make "SURE" the app gives the "EXACT" same count that it says in download mode, or you could potentially HARD BRICK your expensive toy! The warnings are there to be read, good luck!
thamkyou for your swift and informative reply.
so did kies not update when u have rooted your device?
if so i take it you have to manually flash to the newest firmware everytime a new release comes out?
is this the only thing i need to worry about with updating the firmware no other donloads or auto updates im missing, because like i said i saw a firmware update that was 300mb and i cldnt find anywhere online official kernely/firmware builds, and it seems that a simple flash of 8mb or so updates everything? i saw people talking about connecting via kies to update firmware and it was a big 300 meg file!
thanks for your links also mate.
hatchermagic said:
thamkyou for your swift and informative reply.
so did kies not update when u have rooted your device?
if so i take it you have to manually flash to the newest firmware everytime a new release comes out?
is this the only thing i need to worry about with updating the firmware no other donloads or auto updates im missing, because like i said i saw a firmware update that was 300mb and i cldnt find anywhere online official kernely/firmware builds, and it seems that a simple flash of 8mb or so updates everything? i saw people talking about connecting via kies to update firmware and it was a big 300 meg file!
thanks for your links also mate.
Click to expand...
Click to collapse
Whenever you root, kies gives you the "wrong firmware to update" error! No worries though, because YES, you can always flash the latest firmware or custom roms manually! This is usually done through Odin 3 or CWM (clockworkmod recovery!) If done through Odin 3, your flash counter in download mode escalates/goes up, & the only way you can reset it for warranty purposes is using Triangle Away (link in my previous post!) which can be DANGEROUS!! Or if you flash roms through CWM then your counter's not affected also! The majority of people however, prefer to use Mobile Odin on the Galaxy Sll, as flashing with this app also does not give you the boot up triangle warning, or affect your download mode counter! Here's the link to Chainfires lates free version here on XDA: http://forum.xda-developers.com/showthread.php?t=1347899 Or if you appreciate the work the devs (for this particular app, Chainfire!) do for us in this forum, you can obtain the "PRO" (paid/donate!) version here: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en
thanks for the reply again crock daddy! mobile odin sounds awesome,
i see i was getting confused because whenever i have ran kies, it has never asked/said anything about updating firmware, guess ive installed an older firmware version than what my phone came with oops lol. i guess im all good to go, cant believe what this handset can do! and yes i will be donating to the clever gits, chainfire is insane, thanks to that i have shadowguardian dead space and backstab working
thanks for your time again peace out.
right flashed to ics, love it, u sir are a legend....
BUT i tried rooting and it said my kernel was secure thus no temp root access. so closed s2 root down. (would this of done any damage or corrupted data btw?)
tried the cwm zip in sd card method, but cldnt find su zip, also read that it doesnt give full root access or sumin. (again would going into clockwork recovery have done any damage because i didnt complete the rooting process-cldnt find su file so just shut it down)
and im guessing there are no insecure kernels for ics yet?
sorry to be so pedantic and worrying about silly things lol.
also have had a couple of jitters and games completley freezing since ics is this common and or should i reinstall games?
this is the kernel version im using for an orange sgs2 19100p
I9100PBVLP6
just doule checking this is the most up to date and stable build.. cheers
hatchermagic said:
right flashed to ics, love it, u sir are a legend....
BUT i tried rooting and it said my kernel was secure thus no temp root access. so closed s2 root down. (would this of done any damage or corrupted data btw?)
tried the cwm zip in sd card method, but cldnt find su zip, also read that it doesnt give full root access or sumin. (again would going into clockwork recovery have done any damage because i didnt complete the rooting process-cldnt find su file so just shut it down)
and im guessing there are no insecure kernels for ics yet?
sorry to be so pedantic and worrying about silly things lol.
also have had a couple of jitters and games completley freezing since ics is this common and or should i reinstall games?
this is the kernel version im using for an orange sgs2 19100p
I9100PBVLP6
just doule checking this is the most up to date and stable build.. cheers
Click to expand...
Click to collapse
When you root using the cwm & superuser.zip you won't see the su.zip in recovery mode! You have to put an sd-card in your device (external sd-card!) & put su.zip on that rather than your internal sd-card! that way recovery sees it! & YES you do gain full root! (read the whole thread! : http://forum.xda-developers.com/showthread.php?t=1501719)
If Superuser shows up in your app's, then that's the indication you need to tell you that you have root!
Either this method, CF root method or any other method will allow you to install custom ROMS, but there is an advantage and a disadvantage for both.
:;This method: Doesn't affect custom rom counter or triangle, but CWM recovery is not permanent. (but once you flash a custom ROM that has a different kernel with CWM recovery included then your rom counter will still be unaffected and whatever CWM recovery is included in the custom ROM will become your new permanent recovery)
You can still use CWM recovery to flash stuff with this method, by using clockworkmod (Rom manager!) & booting straight into CWM recovery & doing everything you need to do from there!
This method keeps the stock recovery, so that if you have to send your phone in for a repair, the repairer doesen't see that you have a custom recovery (CWM recovery!) which tells them you have rooted your device & void your warrenty!
:-CF-Root Method: Flashing the CF-root kernel (or ANY insecure kernel!) with Odin will increase your custom ROM counter, which can be cleared with TriangleAway.apk (only on ICS). But Chainfire has warned that it is dangerous and can permanently brick the device (i've used it on XWLP7 ICS 4.0.3 and it works perfect.)
I've used both methods, but I found this method easier and generally safer.
As for some of your games freezing on ICS, try going to settings/developer options & try checking "Force GPU rendering" to see if that makes a difference!
The latest official Samsung firmware for Orange here in the UK is: I9100PBVLP6 (ICS 4.0.3!) so you do have the correct one, but I don't think there's an insecure ICS kernel available for that version as of yet!
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
cdroid93 said:
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
Click to expand...
Click to collapse
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Phone version
liljoe727 said:
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Click to expand...
Click to collapse
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
cdroid93 said:
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
Click to expand...
Click to collapse
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
liljoe727 said:
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
Click to expand...
Click to collapse
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
cdroid93 said:
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
Click to expand...
Click to collapse
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
skeezer308 said:
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
Click to expand...
Click to collapse
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
cdroid93 said:
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
Click to expand...
Click to collapse
3.72
Jesus loves you!
Also keep in mind that you can only install TW ROMs or GPE ROMs that are SS friendly. If you try to install Cyanogen or other AOSP ROMs that require custom kernels you run the chance of bricking your phone
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!