Related
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....
No need for a long explanation, just a link or two, and/or some terms I can google for.
And, yes, I have been reading/searching the forum, and only find old posts mentioning Odin as a technique. Is there anything like SuperOneClick out?
Thanks!
Hi, Rooting through odin currently seems to be the most reliable and safest option.
There is other methods however can cause problems with the phone.
Head over to http://forum.xda-developers.com/showthread.php?t=1103399
Based on the current firmware download the cf root that matches it, extract it and flash using odin.
Hope this helps.
I literally just received my SGS2 about 2 hours ago and read a bit of the thread, not all considering how large it is.
I know this roots but does this unlock the BL at the same time since its installing CWM?
Sent from my SAMSUNG-SGH-I777 using xda premium
Up until recently, SGS2 bootloaders have been 'unlocked'. The easiest way to test this would be to try and use a jig to reset the flash counter on the phone after you've rooted it.
If you can't reset the counter, then the firmware that came with your phone has the locked bootloader (I'm sure someone will be along any second now & tell us exactly which version the bootloader started to be locked in . The details are somewhere on the forum).
Easy fix to this is to flash firmware that has the bootloader unlocked. Alternatively, you simply flash the old bootloader over whatever firmware you're running. This is also available on the forum *somewhere* (I don't have a link handy).
Edit to add - About halfway down the page in this thread , there's a section in bold red type which has a link to a tar of the old bootloader you can flash in Odin should you need to.
Auxilium said:
I literally just received my SGS2 about 2 hours ago and read a bit of the thread, not all considering how large it is.
I know this roots but does this unlock the BL at the same time since its installing CWM?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
MistahBungle said:
Up until recently, SGS2 bootloaders have been 'unlocked'. The easiest way to test this would be to try and use a jig to reset the flash counter on the phone after you've rooted it.
If you can't reset the counter, then the firmware that came with your phone has the locked bootloader (I'm sure someone will be along any second now & tell us exactly which version the bootloader started to be locked in . The details are somewhere on the forum).
Easy fix to this is to flash firmware that has the bootloader unlocked. Alternatively, you simply flash the old bootloader over whatever firmware you're running. This is also available on the forum *somewhere* (I don't have a link handy).
Edit to add - About halfway down the page in this thread , there's a section in bold red type which has a link to a tar of the old bootloader you can flash in Odin should you need to.
Click to expand...
Click to collapse
Hi,
I've rooted my sgs2 using CF-Root, i found it better than OneClickRoot, reason for that is when i used oneclickroot the phone rooted then went back after i rebooted, which is weird. So i flashed CF-Root using ODIN and its perfect.
What I want to ask if you could help me please, is how can i see my flash counter? (if there is any)
and what is a jig, does it mean usb connection or is it a device i need to buy?
Thanks
Go into download mode (switch phone off - then do 3 finger reboot - hold home, volume down & power button at the same time), if you've flashed a non-stock rom/kernel in Odin it will show Custom binary download: x, where x is the number of times you've flashed a rom or kernel in Odin.
The jig is a usb plug with a certain amount of resistance over some of the pins of the plug (301k Ω or thereabouts I believe). To use it, you switch the phone off, plug the jig into the usb port on the phone, it reboots the phone into download mode and you'll get a message saying "Erasing download information successful". It will now show Custom Binary Download as no & Custom Binary as Samsung Official.
This will also get rid of the yellow warning triangle that appears at boot as long as you're using an "old" bootloader. Samsung recently started including "locked" bootloaders with their newer firmware in the last few months that don't allow a jig to reset the flash counter.
These cost a few dollars on eBay, do a search for "Samsung Galaxy S2 jig" or similar.
ab.riyami said:
Hi,
I've rooted my sgs2 using CF-Root, i found it better than OneClickRoot, reason for that is when i used oneclickroot the phone rooted then went back after i rebooted, which is weird. So i flashed CF-Root using ODIN and its perfect.
What I want to ask if you could help me please, is how can i see my flash counter? (if there is any)
and what is a jig, does it mean usb connection or is it a device i need to buy?
Thanks
Click to expand...
Click to collapse
Search for the zergRush method. Its the easiest one so far. I personally used odin to flash a rooted cf-kernel but used zergRush to root a friens sgs2 and its really easy. You must have the adb drivers installed for sgs3.
Sent from my GT-I9100 using Tapatalk
bobkoure said:
And, yes, I have been reading/searching the forum, and only find old posts mentioning Odin as a technique. Is there anything like SuperOneClick out?
Thanks!
Click to expand...
Click to collapse
Wanna bet 100$ that you didn't? Paypal only.
There's a ****ing sticky with one non-Odin method, which you just missed, because you were too busy furiously searching for other methods, which were also described many times in the same forums.
Hi kinda off topic, i already rooted my SGS2 by flashing insecure kernel from Odia for DXKL3 and rooting it then flashing back the original kernel. now i want to install CWM, I see a lot of guides and searched, all looks like that need to install a CWM enabled rom or use a kernel that is compatible with CWM, thats where the part i get confused since most of the guide points you to a diffrent kernel from the insecure kernel, cant you use the insecure kernel tha odia posted specific for my DXKL3? and i dont want to install a custom ROM just for CWM it would defeat the purpose since i want to back up my stock firmware.
MistahBungle said:
Go into download mode (switch phone off - then do 3 finger reboot - hold home, volume down & power button at the same time), if you've flashed a non-stock rom/kernel in Odin it will show Custom binary download: x, where x is the number of times you've flashed a rom or kernel in Odin.
The jig is a usb plug with a certain amount of resistance over some of the pins of the plug (301k Ω or thereabouts I believe). To use it, you switch the phone off, plug the jig into the usb port on the phone, it reboots the phone into download mode and you'll get a message saying "Erasing download information successful". It will now show Custom Binary Download as no & Custom Binary as Samsung Official.
This will also get rid of the yellow warning triangle that appears at boot as long as you're using an "old" bootloader. Samsung recently started including "locked" bootloaders with their newer firmware in the last few months that don't allow a jig to reset the flash counter.
These cost a few dollars on eBay, do a search for "Samsung Galaxy S2 jig" or similar.
Click to expand...
Click to collapse
Thanks for the explanation mate, so then the jig is a device to buy not just the normal usb wire.
I'm thinking of getting it but now that its useless if firmware wont allow counter resets using jig......
quick Q, is there another method of resetting the counter and removing the yellow triangle? (it doesnt matter to me but incase i need to take it back for warrantee id need to do that i reckon)
There's no other way to reset the counter that I'm aware of. There's another method you can use to get rid of the triangle tho. 2nd post of the CFRoot thread details how to do this.
I suggest you get a jig. For less than $5 the peace of mind having one gives you is priceless.
ab.riyami said:
Thanks for the explanation mate, so then the jig is a device to buy not just the normal usb wire.
I'm thinking of getting it but now that its useless if firmware wont allow counter resets using jig......
quick Q, is there another method of resetting the counter and removing the yellow triangle? (it doesnt matter to me but incase i need to take it back for warrantee id need to do that i reckon)
Click to expand...
Click to collapse
i used the zergrush exploit, worked fine
http://forum.xda-developers.com/showthread.php?t=1319653
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 guys,
I want to know potential ways to brick my phone so I will be more careful.
Which ones will brick my phone?
1. Flashing recovery for another phone
2. Flashing ROM for another phone
3. Flashing just the kernel for another phone
4. Flashing wrong ROM without the kernel
5. Flashing a mod for another phone
6. Pulling the battery when doing a NAND restore/backup
7. Pulling the battery when installing a mod or a ROM
Or any others you know about. Thanks!
And no, I don't want to brick my phone, this is for prevention
To be honest its seriously not recommended to do any of the things you listed, some of them you may be able to restore your NAND to fix others will kill your phone. Just make sure you follow the guides on here and you'll be fine. But seriously don't install mods or roms that are for another phone.
Sent From My Omega'd Galaxy S3 ...
Don't do any of those....its still a £500 phone and doing any of those things you mentioned will reduce your phone to a rather uncomfortable form of loo roll! If you catch my drift....
Sent from my GT-I9300 using xda premium
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Flashing kernels (even if wrong ones) won't brick your phone. They will render your phone unuseable until a proper kernel is flashed, but it isn't a brick.
Also, wrong ROMs won't brick your phone UNLESS they also contain a bootloader and/or a Partition Information Table (PIT) file, which is quite rare.
So, bricking (by my definition), only happens when you mess with the bootloader and/or the PIT, because those are either impossible or extremely hard to fix.
No matter what you do, DO NOT mess with the bootloader: as long as the bootloader is ok, everything else (including the PIT) can be fixed with some effort.
Simonetti2011 said:
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Flashing kernels (even if wrong ones) won't brick your phone. They will render your phone unuseable until a proper kernel is flashed, but it isn't a brick.
Also, wrong ROMs won't brick your phone UNLESS they also contain a bootloader and/or a Partition Information Table (PIT) file, which is quite rare.
So, bricking (by my definition), only happens when you mess with the bootloader and/or the PIT, because those are either impossible or extremely hard to fix.
No matter what you do, DO NOT mess with the bootloader: as long as the bootloader is ok, everything else (including the PIT) can be fixed with some effort.
Click to expand...
Click to collapse
Thank you, that's exactly the answer I was looking for. So it's impossible to hardbrick my SGS3 unless I flash the bootloader?
Glebun said:
Thank you, that's exactly the answer I was looking for. So it's impossible to hardbrick my SGS3 unless I flash the bootloader?
Click to expand...
Click to collapse
Yes, or the PIT (Partition Information table).
Never, EVER, flash any of these, unless you know EXACTLY what and why you are doing it: PIT, Bootloader, Recovery.
Flashing kernels and simple ROMs (such as the stock ones) don't brick your phone.
Simonetti2011 said:
Flashing kernels and simple ROMs (such as the stock ones) don't brick your phone.
Click to expand...
Click to collapse
What bout custom ROMs, like CM10?
Glebun said:
What bout custom ROMs, like CM10?
Click to expand...
Click to collapse
You have to know if they include a recovery and/or bootloader before flashing.
Usually they DON'T, but you have to check.
Besides, you don't need CMW ( = recovery) to use CM10 ( = ROM), although some badly informed people will tell you that you do.
Glebun said:
Hey guys,
I want to know potential ways to brick my phone so I will be more careful.
Which ones will brick my phone?
1. Flashing recovery for another phone
2. Flashing ROM for another phone
3. Flashing just the kernel for another phone
4. Flashing wrong ROM without the kernel
5. Flashing a mod for another phone
6. Pulling the battery when doing a NAND restore/backup
7. Pulling the battery when installing a mod or a ROM
Or any others you know about. Thanks!
And no, I don't want to brick my phone, this is for prevention
Click to expand...
Click to collapse
Well, even though it's only for prevention;
this is the ultimate way of bricking a device:
Take a picture or download a picture of the desired device, make sure it fits onto a brick, then glue the picture onto a brick, voilà, you now have a bricked device.
Now to serious things:
All the things you wrote are correct.
Hope I could help!
LG familyguy59/Beatsleigher
familyguy59 said:
Now to serious things:
All the things you wrote are correct.
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
What do you mean? I just asked a question. Are you saying that all of the actions I listed will hardbrick my device? So who should I believe then?
Glebun said:
What do you mean? I just asked a question. Are you saying that all of the actions I listed will hardbrick my device? So who should I believe then?
Click to expand...
Click to collapse
They can potentially brick your device, because they use different drivers, files, etc. ... and the partitions are stored in different parts of the memory, changing these partitions can confuse the device and therefore brick it.
I said "serious things" because the first thing I wrote, was a n00b joke, I saw on the forums a while back...
Believe what you wish, all I'm saying is this:
if you flash something to your device, that was intentioned for a different device, then it's your responsibility, because most devs/modders warn you, and I did here, now. Everything you do to your device voids your warranty, and potentially harms your device, what you do to your phone is your thing, all we can do is advise you not to do things, it's your responsibility..
Hope I could help!
LG familyguy59/Beatsleigher
---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------
Simonetti2011 said:
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Click to expand...
Click to collapse
You can always repair a bricked device with a JTAG, it's just the cost and the time consumption, that scares people off
LG familyguy59/Beatsleigher
I'd just pull the battery while flashing a bootloader. Guaranteed brick with little chances of recovery. You need to be fast though, that bootloader is really small and flashes fast
familyguy59 said:
They can potentially brick your device, because they use different drivers, files, etc. ... and the partitions are stored in different parts of the memory, changing these partitions can confuse the device and therefore brick it.
Click to expand...
Click to collapse
So Simonetti2011 is wrong?
familyguy59 said:
They can potentially brick your device, because they use different drivers, files, etc. ... and the partitions are stored in different parts of the memory, changing these partitions can confuse the device and therefore brick it.
Click to expand...
Click to collapse
You are incorrect.
Only a PIT file can change partitions.
Besides, the location of files are standardized across firmwares.
that is why I wrote (page 1 of this thread) that the ROM being flashed must inform if they contain PIT's or recoveries. Stock ROMs (and all ROMs based on Samsung stock ROMs) do not change the PIT, recovery or bootloader.
If the user is going to flash a ROM that is not stock-based AND the developer of the ROM won't tell what it does, then simply avoid that ROM.
I stand correct: as long as the PIT and bootloader are untouched, the phone can be revived with very little effort (matter of minutes).
A JTAG can certainly be used in most cases, but not only it will take a few days (to get the thing delivered), but it will also be quite expensive and demand a lot of technical knowledge. So, I usually consider a device that requires a JTAG to be revived as bricked since I'd rather send it to an authorized service center than try to do it myself and make things worse.
My (most of ours, I guess) S III has a 1 year warranty. I figure that I can mess with it pretty bad and if it gets FUBAR I'll simply send it a service center.
So far, I'm yet to brick my SII, my SIII or even a HTC Kaiser which came with Windows Mobile 6.0 and got an upgrade to Android 2.3.7! I've flashed more ROMs than I can remember, I've wiped, I've lost data, but I have never bricked a single phone.
the thing is that whatever I do I read a lot beforehand and if I think - no matter how little - a ROM can be insecure, I simply don't do it.
My experience has taught me that something others consider a "must-have", I consider a waste of time and unnecessary headache and trouble: one such example is CWM.
There are dozens of people here with USB and MHL problems and 99% of them have CWM. That is NOT a coincidence.
I loved overclocking my S II, using SiyahKernel for that, but the device driver support in it (specially for wifi) was so bad that it was a waste of time.
What most people don't get is the definition of BRICKING. Will an improper stock ROM render your phone unusable? YES. Can it be fixed in 5 minutes? YES. Is that bricking? NO.
UNUSABLE <> USELESS
I am on jellybean can I directly flash any ics custom rom from cwm and then wipe and this wont brick my s3 I am asking this question because I had a galaxy note which was on ics and I flashed cm10 on it I had made a backup of the stock rom I found it to be little unstable so I restored the nand backup of stock rom this hard bricked my device
Simonetti2011 said:
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Flashing kernels (even if wrong ones) won't brick your phone. They will render your phone unuseable until a proper kernel is flashed, but it isn't a brick.
Also, wrong ROMs won't brick your phone UNLESS they also contain a bootloader and/or a Partition Information Table (PIT) file, which is quite rare.
So, bricking (by my definition), only happens when you mess with the bootloader and/or the PIT, because those are either impossible or extremely hard to fix.
No matter what you do, DO NOT mess with the bootloader: as long as the bootloader is ok, everything else (including the PIT) can be fixed with some effort.
Click to expand...
Click to collapse
Did You Mean If I Flashed Custom ROM Made Specially For My Phone (Codec For i9300) My Phone Will Not Hard Brick?
THE.W!ZARD said:
Did You Mean If I Flashed Custom ROM Made Specially For My Phone (Codec For i9300) My Phone Will Not Hard Brick?
Click to expand...
Click to collapse
that means if you flash ANY custom ROM, you won't hard brick, because they don't touch the bootloader
Glebun said:
What bout custom ROMs, like CM10?
Click to expand...
Click to collapse
CM10 is safe. It does not include any of these information that can brick your phone.
---------- Post added at 09:33 AM ---------- Previous post was at 09:27 AM ----------
Glebun said:
that means if you flash ANY custom ROM, you won't hard brick, because they don't touch the bootloader
Click to expand...
Click to collapse
Yes, typically but keep in mind that if you flash rom from different phone model then it might soft brick your phone or some core services might not work.
I kinda did it to myself a couple of weeks ago. I have international i9300 and I flashed a rom for att. everything went smooth but my phone reception was not working. I was like WTF. then I checked rom correctly and I find it was for ATT. I was terrified that I might have broke my phone's reception forever. But then I again flashed CM10 for i9300 international and I am back into game again.
So when you flash any rom, try to double check phone model and reviews in discussion thread.
Yeah, but a soft brick is not a problem at all. I'm sure all of us have had a couple of them
Glebun said:
Yeah, but a soft brick is not a problem at all. I'm sure all of us have had a couple of them
Click to expand...
Click to collapse
yes
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!